Label-Ready 14 · Final Pre-Release QA & Baseline Metrics

DEPLOY · 6 of 6 · Label-Ready 14

Final Pre-Release QA & Baseline Metrics

WHERE YOU ARE: The release operation is built. Before launch, reconcile the live deployment against the approved package, remove avoidable Red failures and capture the baseline that Phase 4 will measure against.

YOU SHOULD ALREADY HAVE

  • Release Deployment Plan.
  • Distribution Submission Record.
  • Platform Readiness Record.
  • Discovery & Audience Path Record.
  • Launch Asset & Outreach Calendar.
This is a reconciliation gate, not another planning exercise. Compare what is actually scheduled/submitted against the package and deployment records. Fix only the real mismatch. If a material identity, rights, metadata, master or artwork issue appears here, route back to the stage that owns it rather than patching around it on release day.

THE DECISION

If the release went live tomorrow exactly as currently configured, is there any known preventable issue serious enough to stop or move it?

RUN THE QA

  1. Package reconciliation: master, title, artist identity, artwork, credits, rights status and release objective still match the approved source records.
  2. Distribution: release date and store status are correct; no unresolved distributor warning or artist-mapping problem.
  3. Platforms: profile access/mapping is verified where possible; every unresolved platform action is classified as timed, optional or blocking.
  4. Discovery: pre-save/release link works; Spotify pitch was completed when eligible and strategically intended; owned-audience destination works where used.
  5. Content: launch assets open, play and display correctly; captions/credits/links match the release identity.
  6. Compliance: no known sample, collaborator, artwork, impersonation, metadata or disclosure issue has reopened.
  7. Operations: you know what happens on release day and who is responsible for any collaborator or partner action.

CAPTURE THE BASELINE

Before the release changes anything, save the baseline needed for Phase 4. Use only metrics that exist and matter to the release objective.

  • Spotify followers/monthly listeners or equivalent platform audience indicators where accessible.
  • YouTube subscribers/views or relevant channel baseline where used.
  • Email/community/owned-audience size where used.
  • Social audience baseline only for channels actually used in the launch.
  • Existing catalogue benchmarks if the creator already has releases.
  • Campaign spend committed before Day 0.
Zero is valid data. A first release may have little or no baseline audience. Record the truth instead of manufacturing a professional-looking starting point.

RED / YELLOW / GREEN

  • RED: wrong master/date/artist mapping; unresolved rights or contributor problem; material metadata/artwork contradiction; broken primary release path; deceptive/fraudulent promotion dependency.
  • YELLOW: optional profile feature unavailable; non-critical asset missing; short runway already understood; small outreach/content gap with a workable fallback.
  • GREEN: no known release-blocking issue and a usable Day 0 operating plan exists.

ROUTE & FOUNDATION

Back to 13 · Launch Content & Outreach — repair launch inventory or outreach operations there.

DEPLOY Hub — review the entire phase if QA exposes an earlier deployment-stage problem.

One-Song Release Package — return here for package-level identity, metadata, artwork or master contradictions rather than patching them at launch.

Free · AI Music Release Compliance Checklist 2026 — final free rights/disclosure/pre-release cross-check.

Free Label-Ready Resources — foundation/support for a readiness gap that should be repaired before release.

SAVE THIS

Create the Pre-Release QA & Day 0 Baseline Record: package/version reference, QA date, Red/Yellow/Green decision, blocking issues/fixes, known timed/optional platform items, primary live links, baseline metrics, spend committed and owner/date for release-day checks.

DO NOT ADVANCE IF

  • Any Red issue remains unresolved.
  • You cannot identify the exact master/package the live submission came from.
  • The primary release link or artist mapping is known to be wrong.
  • You have not captured a baseline appropriate to the release objective.

READY TO CONTINUE WHEN

The release is Green, the remaining Yellow items are documented and controlled, and the baseline is saved before Day 0.

NEXT PHASE · PROVE

Release the song. Then measure what actually happens.

Phase 4 begins at Day 0. Use the saved baseline and deployment records to run Day 0 → Day 14 → Day 30 → Day 60 → Day 90 evidence reviews. The goal is not to prove that every release succeeded; it is to make the next catalogue decision from evidence.

Continue to Phase 4 · PROVE