What to Do When a Label Services Deliverable Is Late
Check a late label-services task against the agreed scope, ask for a concrete recovery plan, protect dependent work, and document the next decision.
The short answer
When a label services deliverable is late, confirm the agreed task, due date, required inputs, and acceptance criteria. Ask the partner for its current status, blocker, recovery date, and effect on dependent work. Decide what to continue, reassign, simplify, or pause, and record the decision without assuming a late task settles payment or agreement questions.
Three things to know
- 01
A missing promised file or task is different from a campaign outcome the partner cannot control. Check what was actually agreed.
- 02
Use a recovery plan with an owner, usable output, review point, and fallback decision. A vague reassurance does not tell the rest of the team what to do.
- 03
Keep delivery recovery, release-date choices, and payment or agreement questions separate. Escalate unresolved terms to qualified counsel rather than inventing a remedy.
What belongs in a late-deliverable recovery record?
Use this constructed record for one missed item. It supports a factual delivery decision and does not determine either party's legal rights or payment obligations.
- 01
Original commitment
Identify the agreed item, owner, date, required format, and definition of a usable delivery.
- 02
Inputs and current state
List assets or approvals supplied, unresolved dependencies, available work, and information still needed.
- 03
Next affected decision
Name what is blocked, who decides, and which current external deadline or approval matters.
- 04
Recovery commitment
Record the proposed output, responsible person, delivery estimate, review point, and any assumptions.
- 05
Approved fallback
State what happens if the checkpoint fails and who can authorize added work, cost, or reassignment.
- 06
Closeout evidence
Save the accepted version, actual delivery date, unresolved questions, and next engagement improvement.
What exactly was due, and what would count as delivered?
Find the latest agreed scope and any approved changes. Name the item, owner, date, file or action expected, and acceptance criteria. A strategy deck uploaded without its promised task calendar may be incomplete; a completed outreach log with no replies may still document the agreed work. Velveteen Records' public scope guide distinguishes controllable deliverables from uncertain market outcomes. Use that distinction before raising the issue. If the original wording only said promotion, acknowledge the ambiguity and ask both sides to define the missing work rather than retroactively treating an unstated result as a deadline.
How should you establish the facts without assigning blame first?
Check the shared folder, task record, approval history, and agreed communication channel. Confirm that the partner had the correct assets, permissions, feedback, and other inputs on time. Record what is known and what needs a response: perhaps the file exists but access is broken, or an artist approval is still outstanding. A missing input does not automatically resolve responsibility; it changes the recovery conversation. Keep the record factual and include your own missed dependencies. Avoid announcing a failure publicly or assuming silence tells you why the work has not arrived.
What dependent work needs attention first?
Map what cannot proceed without the deliverable and identify the next real decision point. A late internal recap may affect learning; late approved assets may block a scheduled launch action. Check external rules independently of the partner's revised estimate. Spotify Support currently says a song is no longer eligible for its editorial pitching flow once it has gone live. A later handoff cannot reopen that pre-release song-pitch opportunity. This is distinct from video pitching, which has separate eligibility rules. Do not treat every late item as a reason to change the release date, and do not treat catching a deadline as assurance of editorial selection.
What should you ask the partner to provide now?
Send one focused request through the agreed channel. Identify the task and original date, describe what you can currently access, and ask for the work completed, remaining blocker, proposed recovery date, and next review point. State the decision your team must make and when it needs enough information to make it. A constructed message could say: the approved task calendar was due at our last checkpoint; we cannot find it in the shared folder; please confirm its status and whether a usable version can arrive before our asset review. Adjust the wording to the facts rather than sending a generic accusation.
How do you choose between recovering, reassigning, and simplifying?
Compare the options against the remaining time, dependencies, capacity, and approvals. Recover with the current owner when a specific usable output and credible review point are available. Consider reassignment only after clarifying who is responsible, what files can be transferred, and any added cost or permission question. Simplify a nonessential deliverable when a smaller approved version still serves the release. Pause an action that would otherwise use incomplete or unapproved material. Make one owner responsible for each active task so two people do not unknowingly duplicate work. Confirm any change in scope, spending, or publishing authority before treating it as approved.
What does a constructed delivery-recovery decision look like?
Constructed example, not a Records result or policy: an artist has approved the final photos, but the promised asset calendar has not arrived. Scheduled posts depend on that calendar, while the music has already been delivered correctly. The partner confirms that its scheduling owner is unavailable and proposes a smaller calendar for the essential posts, followed by the remaining plan. The artist reviews whether that output is useful, names the approver and check-in, and holds posts that lack approval. They keep the broader release-date decision separate. If the revised checkpoint fails, they review the agreed fallback instead of silently repeating the same promise.
When should you escalate beyond the day-to-day contact?
Escalate when the working contact cannot provide an actionable status, a revised checkpoint is missed, or the proposed fix introduces a decision that person cannot approve. Use the escalation contact or process in the written arrangement where one exists. Send a concise record of the agreed item, dates, inputs, current gap, attempted recovery, and decision needed. Request clarity on undelivered work, remaining costs, and handoff rather than assuming a refund, cancellation right, or fee deduction. This guide is operational education, not legal advice. Take disputed payment, ownership, termination, or other agreement questions to qualified music counsel with the actual documents.
How should you close the issue and improve the next scope?
Record the accepted final output, actual delivery date, open items, and the person who confirmed the next action. If work changed, keep the approved change alongside the original scope. Review the pattern after the immediate decision: was the task unclear, the input late, capacity missing, or the warning raised too close to the next deadline? Improve the next engagement with a clearer definition of done, dependency dates, an early warning point, and a named escalation contact. A recovery meeting is useful when it changes those operating details; it should not become another place to leave ownership unresolved.
Frequently asked questions
- Is a lack of playlist adds evidence that a deliverable is late?
- Check the agreed work. Research, pitch preparation, submission, or reporting may be deliverables; a curator's decision is an uncertain outcome. Do not substitute one for the other.
- Should I stop paying as soon as a task misses its date?
- Do not infer a payment remedy from this guide. Review the actual written terms and raise disputed charges or obligations with qualified counsel before deciding how to respond.
- Can I move the release date without involving the partner?
- Coordinate with the people responsible for delivery, approvals, and campaign activity. First establish what a date change would affect instead of changing one calendar entry in isolation.
- What if I supplied the approved artwork late?
- Record when it was supplied and ask how that affects the remaining work. Agree on a realistic revised decision point instead of hiding the dependency or assuming its effect.
- Does one missed task mean the partnership should end?
- Assess the importance, explanation, recovery, and wider pattern. Ending or changing an engagement also raises handoff and written-term questions; a single date alone does not answer them.