Music Release Postmortem Template: Day 1 to Day 90
Run a music release postmortem at four checkpoints across the first 90 days. At each checkpoint, save the platform exports, match the date and territory scopes, record campaigns and outside events, compare with an equivalent baseline, and write three decisions: what to keep, what to change, and what to stop. Assign each decision an owner before the next release.
Lead visual
Music analytics map
Context
Audience · Analytics
What this guide is helping you understand.
Decision
Release postmortem template
The practical choice or setup step to get right.
Next
Action
What to check before you move the release forward.
Audience · Analytics
Review record map
Use this for
Give each checkpoint one decision instead of repeating the full dashboard at every meeting.
Watch for
A release-day verdict can mistake preliminary delivery data for the longer performance of the music.
Check
Native exports, matching scopes, baseline, campaign context, outside events, and the prior decision record.
Result
A keep, change, and stop record with owners and a clear test for the next release.
Velveteen postmortem cadence
Day 1 to day 90
- 01
Day 1
Verify
Check release mapping, metadata, links, tags, spend delivery, and preliminary platform counts.
- 02
Day 7
Read reach
Compare unique audience, source mix, territories, first-week performance, and creative delivery.
- 03
Day 28
Close engagement
Review matching ratios, active audience, release engagement, and the full campaign context.
- 04
Day 90
Find continuation
Measure later catalog listening, followers, returning audience, campaign lag, and next-release implications.
What evidence should you capture at each checkpoint?
| Evidence to save | Decision to make | |
|---|---|---|
| Day 1 | Store links, mapping, live counts, delivery screenshots, spend status, and any technical incident | Fix measurement or delivery now; defer the performance verdict. |
| Day 7 | Export reach, source mix, top territories, creative results, first-week plays, playlists, press, and posts | Keep or adjust live media and follow-up while documenting exposure context. |
| Day 28 | Export matching listeners, streams, ratios, active audience, release engagement, spend, and lag events | Decide which audience, creative, source, and content path deserves another test. |
| Day 90 | Export catalog continuation, followers, returning audience, reactivation, final campaign reports, and costs | Lock the keep, change, and stop list for the next release brief. |
A checkpoint is not a cumulative data dump
Each review owns a different decision. Reuse the core baseline, but do not repeat every early screenshot at day 90. Carry forward the decision, the unresolved question, and the source file needed to test it.
Which fields make the postmortem reproducible?
Evidence record
Complete the file before the meeting
Goal
State one primary outcome, the target audience, and the release-stage deadline
Prevents the team from choosing a different definition of success after seeing the result.
Baseline
Name the equal-length prior period or comparable release and why it belongs
Gives every change a visible reference instead of a lifetime or outlier comparison.
Scope
Record platform, song or release, dates, UTC boundary, territory, and source filters
Makes ratios and checkpoint comparisons possible to reproduce later.
Context
List spend, creative changes, playlists, press, creators, live events, and technical issues
Shows which outside events may explain movement without pretending to identify causation.
Evidence
Link the native exports, statements, screenshots, and calculation sheet used in the conclusion
Keeps the postmortem auditable when dashboard views or labels change.
Decision
Write keep, change, and stop items with owners, due dates, and the next test
Moves the learning into the release brief instead of leaving it in a meeting note.
How should the meeting end?
| Write one evidence-led sentence | Attach the operating detail | |
|---|---|---|
| Keep | Name the part of the release system that performed the intended job | Owner, reusable asset, audience, source evidence, and next scheduled use |
| Change | Name the uncertain or weak element and the smallest useful revision | Hypothesis, new version, budget, measurement window, and pass condition |
| Stop | Name the activity that used time or money without supporting the objective | Saved cost, archived evidence, dependency check, and replacement if one is needed |
Which current reporting windows support the timeline?
Frequently asked questions
What should a music release postmortem include?+
Include the release goal, baseline, distribution and mapping status, reach, source mix, engagement ratios, audience change, spend, campaign delivery, territories, playlist and press events, reporting limitations, and keep, change, or stop decisions. Store source exports and screenshots beside the written conclusion.
When should an artist do a release postmortem?+
Use several checkpoints because the questions change. Early checks cover the release system and initial reach; later checks close the main engagement window and examine continuation. A single review immediately after release confuses preliminary delivery data with the longer performance of the music.
Who should attend a music release review?+
Include the people who can explain and change the plan: the artist, project lead, distributor or label contact when relevant, campaign buyer, content lead, and anyone responsible for live, press, playlist, or fan communication. Keep the meeting small enough that every decision receives an owner.
Should I compare every release with my biggest song?+
No. Choose comparable release stages, formats, audiences, campaign levels, and source conditions. A catalog outlier or major playlist event can be useful context, but it is a poor default baseline. Preserve a small set of comparable releases and explain why each one belongs in the review.
What if the release missed its target?+
Separate a weak result from a broken test. Check delivery, mapping, tracking, creative, audience, source mix, and outside events before judging the song. Keep any element supported by evidence, change the uncertain part, stop the clearly unproductive part, and state what the next release will test.
Get better release strategy in your inbox
Release planning checklists, royalty explainers, and artist strategy notes from Velveteen. No daily noise.
Was this useful? Send a signal or flag a correction.
Keep reading
Pillar guide
Music analytics for artists
A decision system for artist data: match the metric to the goal, keep platform definitions separate, and turn each report into a concrete release decision.
Related guide
Music metrics that matter
A twelve-metric decision hierarchy that separates audience reach, signs of intent, and retention from totals that look impressive but do not answer the question.
Related guide
Measure a music marketing campaign
A campaign ledger that keeps ad delivery, link intent, DSP response, cost, timing, and outside events separate enough to support the next budget decision.
Plan your pre-save campaign
Get a dated pre-save checklist — launch, reminders, link placement, and incentive messaging — working backward from your release date.