DISTROBOLT ARTIST GUIDES
Change a release date before delivery: decision checklist
Before delivery, change the release plan at its source and obtain approval from the people affected. First verify that the distributor has not already sent the release to stores: a draft label alone is not proof of delivery status.
Establish the current state
Record the release reference, old date, proposed date and reason for the change. Ask the authorised account owner to confirm whether submission, review or store delivery has occurred. If a delivery has already been sent, use the after-delivery process instead. Do not delete a draft merely to avoid checking its status.
Approve one revised brief
Example: the final master will arrive a week later than planned. Move the intended launch far enough to allow file checks and campaign preparation, then ask collaborators to approve the revised plan. Name one person who can approve the final date. Keep the earlier brief as a superseded version rather than silently overwriting the record.
Update dependent commitments
Check cover artwork with printed dates, press emails, paid creative work, listening events and scheduled announcements. A date change does not automatically cancel a separately ordered service or move a booked production slot. Ask the relevant supplier about the existing order before making assumptions about charges or refunds.
Confirm before announcing
Ask DistroBolt which editable field or support route applies in your actual account; this guide does not promise a self-service rescheduling button. Save the confirmed new date and time zone with the release materials. Only then update public announcements. If a first Spotify profile is involved, access may depend on delivery having happened, so do not mistake missing profile access for an unsuccessful draft edit.
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
Ask the DistroBolt team about your release. Send a concise question and release reference; never send account passwords or verification codes.