A rollout is more than a release date
Most independent releases are planned across three or four places at once: a date in a calendar, a list of tasks somewhere else, a folder of assets, and a set of links created ad hoc in the last fortnight. Nothing is wrong with any one of those. The problem is the seams — the pre-save that was built a week late because it lived outside the plan, the second single that quietly slipped because nothing was holding its date.
A campaign in Playloudr is one rollout. A standalone single is a campaign with one release. An EP or album rollout is a campaign with several connected releases: the two singles, then the record, in the order you intend to put them out. Everything else — the pre-save, the smart link, the fan capture, the content around it — hangs off the release it belongs to.
What you look at day to day
The planner has two views, and they answer different questions.
The upcoming rail answers “what is next”. It is the short list of releases with dates ahead of you, in order, so a two-single build-up to an album reads as a sequence rather than three unrelated entries.
The month calendar answers “what does this month look like”. Releases and content sit on the same grid, month by month, which is where you notice that your second single lands in the same week as the tour announcement and that one of them should move.
Planning an EP rollout
- Create the campaign. Name it for the record, not for the month — it will outlive the month.
- Add the releases in order. First single, second single, the EP itself. Each gets its own date and its own pages.
- Set each release date honestly. Distribution needs lead time, and a date you have not delivered to your distributor is a wish, not a plan.
- Attach a pre-save to each release. Four to six weeks ahead of its date. The release URL follows automatically from there.
- Fill in the gaps between the dates. The weeks between singles are the campaign, not the dead air around it. The release checklist is a reasonable starting shape.
- Check the month view before you commit. Two releases eleven days apart is a plan; two releases in the same week is an accident.
The release URL keeps itself current
Every release in a campaign has a public URL, and Playloudr keeps it pointed at the right thing. Before the date, that URL is backed by the release’s pre-save. It is the link you put in the bio, in the ad, in the email and on the poster, and you do not have to swap it out when the situation changes.
This matters more than it sounds. The usual failure is a printed or paid-for link that was correct for a fortnight: the pre-save URL in an ad that is still running on release day, or a bio link nobody updated. Because the release owns the URL and the campaign owns the release, there is one place to change and everything downstream follows.
It is also what release ads point at. Ads are attached to a specific release rather than floating free, so the ad, the page and the date cannot drift apart.
A single rollout, roughly
| What you set up | Where it lives | |
|---|---|---|
| 6 weeks out | Release delivered to your distributor, UPC in hand, campaign created | Campaigns |
| 4–5 weeks out | Pre-save page live, announcement post, release URL in the bio | Pre-Saves |
| 2–3 weeks out | Teasers and clips scheduled, ads prepared against the release | Content · Release Ads |
| Release week | Last-chance pre-save push, launch-day email armed | Pre-Saves |
| Release day | Saves delivered, smart link becomes the permanent home | Smart Links |
| After | Read the numbers, add the new contacts to the fan list | Analytics · Fans |
Shift the whole thing later if your distributor needs more time. The point of a plan is that moving it is a decision rather than a scramble.
Why the plan and the links belong together
A spreadsheet can hold dates perfectly well. What it cannot do is tell you that the pre-save for your second single does not exist yet, or that the release URL in your running ad still points at a page for a song that came out last month.
Keeping the rollout next to the pages means the plan is checkable. You are not comparing a document against your memory of what you built; you are looking at the releases and seeing what each one has attached to it. That is most of the value, and it is why the calendar is the front door to the product rather than an extra.
When the date slips
It will. Distribution takes longer than expected, a mix comes back needing another pass, a feature does not clear in time. Move the release date on the campaign and the pages attached to it stay attached — the pre-save is still collecting, the fans who already saved are still on the list, and the release URL is still the URL you have been promoting.
What you should change by hand is the promotion. A three-week delay means the posts you scheduled around the old date are wrong, and the ads pointed at that release need their end dates revisited. The plan is the place you notice both.