DISTROBOLT ARTIST GUIDES
Plan overlapping releases without competing with yourself
Overlapping releases need an agreed focus, enough working capacity and a clear message for each audience. A busy calendar is not a campaign strategy; plan what your team can actually deliver and measure.
Put the campaigns on one calendar
List release dates, asset approvals, announcements, pitching tasks and booked creative work for each project. Include the people responsible rather than recording dates alone. Highlight tasks that need the same editor, artist or approval owner. Resolve those conflicts before buying additional work or promising daily content.
Choose the focus for each period
For example, a single may lead the first fortnight while an EP takes over after launch. Define the main destination link and message for each period. Supporting an older release is still possible, but avoid making every post ask the same audience to prioritise two different launches. Agree the hierarchy with collaborators.
Check platform constraints independently
Spotify permits one song pitch at a time under its pitching process. Check the current eligibility and upcoming-release state before relying on a crowded pitching schedule. A calendar slot does not reserve editorial attention, and a second release does not guarantee another placement. Other destinations have their own campaign tools and conditions.
Review capacity before moving a release
Decide whether to simplify the campaign, share suitable approved assets or request a date change. If delivery has happened, use the delivered-release process rather than treating the calendar as the scheduling system. Keep separate release references and performance notes so that overlapping listening is not automatically attributed to the newest campaign.
Sources and review
Reviewed 4 November 2026. Platform requirements and plan terms can change. Examples are planning aids, not a promise of account access, release acceptance or earnings.
Continue your release planning
- UPC versus ISRC: identify the product and the recording
- Contact distribution support with a case they can resolve
Ask the DistroBolt team about your release. Send a concise question and release reference; never send account passwords or verification codes.