A creator campaign can stall in two ways. The creator misses an agreed delivery date, or the creator accepts the partnership and then stops replying. In both cases, confirm what was agreed, check whether your team owes the creator anything, and ask for one clear answer by a stated time. Compare that answer with the remaining review window before you move work elsewhere. Keep scheduling decisions separate from decisions about payment, cancellation or breach of contract.
A missed date or a silent thread tells you an update is missing. It does not tell you why, so find out whether the work can still go ahead without accusing anyone.
The procedure below is an operating recommendation. It does not decide your contractual rights or replace legal advice.
Check what was agreed before sending a reminder
Open the acceptance thread, the agreement or signed terms if there are any, the latest accepted brief, later changes and the delivery thread. Find out what the creator accepted. It may have been a discussion, a product shipment or specified paid work. If work is late, find out which milestone was missed: a concept, first draft, revised file, approved asset or live post. A file that waits for your feedback needs a different response from a file the creator has not sent.
Write down these facts in the campaign record.
- Note the agreed date, time and time zone of each milestone, with any changes both sides accepted.
- Note the last action each side agreed to take and the date it was due.
- Check the agreed delivery location and whether a file arrived somewhere else.
- List what your team has supplied, approved or paid, and what is still outstanding.
- Name the person who owns the next action, which may be an agent if one manages the agreement.
- Note the contact person and communication channel the creator agreed to use.
- Copy any terms that cover notices, delays, payment, changes or cancellation.
- Name the first downstream commitment the delay affects, such as review, publication or a booked launch placement.
An enthusiastic reply can leave important details open. Record those gaps without deciding their legal effect yourself. For questions to gather before a contract review, use the creator contract discussion guide.
Check your own dependencies first. Did your team send the final brief? Has the creator received the product they need? Did someone promise feedback and not send it? Modash's article on communication bottlenecks names unclear next steps and brand-side delays as problems worth fixing, and it recommends a clear summary of next steps. Check your side of the exchange before you describe the problem as creator nonperformance. If your team sent feedback late, say so in the recovery conversation.
| What your records show | Your next move |
|---|---|
| Your team owes a brief, approval or payment | Route that task to its owner and tell the creator what happens next. |
| Acceptance exists, but the next step has no date | Ask for a dated next step, and do not call it overdue. |
| An agreed response date passed | Ask for a status update and offer a way to raise a blocker. |
| A delivery deadline passed | Work out the last usable delivery time and use the decision tree below. |
| Money, scope or cancellation is disputed | Send the record to the person authorized to review the agreement. |
Keep the original deadline visible. Add a proposed recovery date next to it, so the record shows what changed. For a record that keeps those dates apart, use deliverable tracking that keeps revisions attached to their milestones.
Work backward from the last usable delivery time
The original deadline tells you that something is late. The last usable delivery time tells you whether the campaign can still use it.
Start with the publication commitment. Allow time for review, any needed correction, disclosure checks and upload preparation. Use the real availability of the people who do that work. An overnight gap does not help if nobody can review overnight.
Here is a hypothetical schedule, not a recommended service level.
| Milestone | Agreed or required time |
|---|---|
| Original draft deadline | Tuesday, 12:00 UTC |
| Creator's proposed recovery delivery | Wednesday, 09:00 UTC |
| Last usable draft delivery | Wednesday, 12:00 UTC |
| Reserved review and correction period | Wednesday afternoon and Thursday |
| Publication | Friday, 09:00 UTC |
The proposed recovery time fits this schedule if the reviewer confirms availability and the creator confirms the correction window. Hold the publication slot for now, with a check at delivery. A proposal to send the draft on Thursday evening would need a different plan.
Do not treat the last usable time as permission to remove review. For endorsements that reach U.S. consumers, FTC guidance says a material brand connection must be disclosed with the endorsement. In a video, the disclosure belongs in the video, not only in its description. A compressed schedule still needs that check. Other jurisdictions may have more requirements.
Use this decision tree for late or unanswered work
Start at the first row and follow the next action. The reply cutoff is an operational decision point. It is separate from any formal notice period in the agreement.
| Question | If yes | If no |
|---|---|---|
| Has the milestone passed, after checking agreed changes and delivery locations? | Identify the blocker and the campaign impact. | Correct the record or ask for clarification. |
| Is your team blocking completion? | Supply the missing input and ask for a revised schedule. | Ask the creator for status and a realistic delivery time. |
| Has the creator confirmed a usable recovery time? | Confirm review capacity and record the recovery plan. | Start the check-in sequence below and prepare a fallback. |
| Can the recovered work pass the required checks before publication? | Keep the slot with a named checkpoint. | Decide whether to move the placement or use fallback work. |
| Would the change affect fees, scope, rights or termination? | Route it to the authorized contract owner before committing. | Record the scheduling change and tell affected colleagues. |
A usable recovery time says what will arrive and which dependencies remain. "Soon" does not tell a reviewer when to reserve time. Ask whether the promised delivery is a complete draft or a partial file, and whether the creator can handle the agreed revision step afterward.
A fallback can mean checking whether an approved brand asset is already available. It does not have to mean hiring a replacement creator at once. Confirm budget authority and the fallback asset's permitted use before you commit spend or schedule it.
Run a check-in sequence with a stop point
Assign one person to own the conversation in the established channel. Other teammates add facts to the internal record instead of sending their own reminders. If a call settles the problem, summarize the agreed actions in writing afterward.
Choose reply cutoffs around the agreed schedule, working days, time zones, urgency and any known absence. No set number of days fits every campaign. These cutoffs are operational recommendations, not contractual notice periods or a cure period, which is the time a contract allows to fix a breach. If a formal deadline is close, involve the contract owner now instead of waiting for every step below.
First check-in when a draft is late
State what you expected, ask where the file is, and ask for the earliest time the creator can send a complete draft. This hypothetical message uses the schedule above. Change the facts and timing to match your agreement.
Hi Alex, we expected the draft on Tuesday at 12:00 UTC and have not found it in the delivery folder. Could you confirm whether it has been sent elsewhere?
If it is still in progress, please tell us what remains, whether you need anything from us, and the earliest time you can send a complete draft. Please also confirm your availability for the agreed revision step.
We need the draft by Wednesday at 12:00 UTC to keep the review window before Friday's publication. Could you reply by Tuesday at 17:00 UTC so we can decide the schedule? If that timing is no longer possible, please say so and we can discuss the available options.
We will confirm any revised delivery and publication dates in writing after checking reviewer availability.
First check-in when the creator stops replying after accepting
Reply in the established partnership thread. State the pending action, say what your team has sent or still owes, and ask one question. This message is for a hypothetical partnership.
Hi Morgan, checking our plan for the autumn launch. We sent the final brief on October 5 and have the first concept pencilled in for October 12. Can you confirm by October 8 at 3 p.m. London time whether that date works? If you are waiting on something from us, please tell me what is missing.
Before you send either message, replace the example facts with verified facts. Do not call a proposed date an agreed deadline. Do not comment on the creator's social activity or ask them to explain their personal circumstances.
Second check-in asks for a decision
If the reply cutoff passes, offer a short set of useful answers. Ask whether the creator can continue, needs a revised date, or wants to discuss ending the arrangement. Offer only options you have authority to discuss. Here is a follow-up in the same hypothetical partnership.
Hi Morgan, I still need an update on the concept date. Could you confirm October 12, suggest a revised date, or tell me if you would like to discuss stopping the project? Please reply by October 9 at 3 p.m. London time so I can update our launch plan. Any change to the agreed work or fees will need separate confirmation.
Stay in the agreed channel. If the creator named a manager or an escalation contact for this partnership, use that contact. Do not look for personal contacts or post public reminders. This procedure does not authorize a new marketing message through a public address or a DM button.
At the stop point, move the decision inside your team
When the second reply cutoff passes, stop routine reminders. Tell the campaign lead that the delivery is still unconfirmed, and mark the partnership as awaiting internal review. Remove unconfirmed work from forecasts of output you can rely on. Ask the campaign owner whether to prepare a fallback within existing commitments and budget approval, and stop describing the original slot as secured.
Do not record the partnership as cancelled unless the authorized person has established and completed the required process. A planning status change does not settle fees, usage rights or contract obligations.
If the creator replies later, summarize the revised plan in writing and get the needed agreement before you rely on new dates.
Keep an escalation record someone else can act on
Write facts and link the original records. Avoid labels such as unreliable or ghosting, because they add a judgment and say nothing about the state of the work.
Here is a hypothetical internal record for the Morgan partnership.
| Field | Example entry |
|---|---|
| Accepted scope | One sponsored video, with signed terms and the acceptance thread attached. |
| Last creator reply | October 2, confirming receipt of the product. |
| Brand tasks | Final brief sent October 5, with no approval pending. |
| Pending confirmation | Whether the October 12 concept date works. |
| Check-ins | October 6 and October 8 in the existing email thread. |
| Last requested reply | October 9, 3 p.m. London time, with no reply recorded. |
| Campaign impact | The launch forecast excludes this unconfirmed video. |
| Decision needed | The campaign owner reviews a fallback, and the contract owner reviews any formal action. |
| Next review | October 9, 4 p.m. London time, owned by the partnership manager. |
The Australian Government's dispute guidance recommends checking the facts, naming the outcome you want, discussing the issue and keeping a record. It treats further dispute steps separately. The same split works here, although that guidance is written for Australia.
When a late delivery is resolved, close it with the same kind of record. Write down the deliverable, the accepted new timing, the reviewer, the publication decision, any remaining blocker and the next checkpoint. Send that record to the creator and to the people whose work depends on it.
Separate recovery from contractual remedies
The absence of a signed document does not settle the question. California Courts' contract guidance explains that agreements can be written, verbal or implied, subject to enforceability requirements. It also notes that a contract can set its own dispute procedures and governing law. Those explanations are for California and do not decide anything about your partnership.
The Australian Government's guidance on ending contracts explains that not every breach gives a right to end a contract. It advises reviewing the terms, judging how serious the breach is and getting legal advice before ending a contract for breach. That is Australian guidance, not a rule for every jurisdiction or every creator agreement.
Before you threaten cancellation, withhold an agreed payment, ask for a refund, send a breach notice or ask for extra work as compensation, have the authorized contract owner review the delivery obligation and any accepted changes. They should also check notice requirements, any chance to correct the failure, payment milestones, completed work, the governing law and whether you need local legal advice.
Give the reviewer the acceptance history, amendments, payment records, each side's completed tasks and the communication log. Ask what action is available, who must receive notice and which deadlines apply. Use the creator contract discussion guide to organize the questions. A scheduling message should not promise a refund, waive rights or impose a new remedy.
If the creator confirms they cannot continue, move to the withdrawal workflow for deciding what happens to unfinished work. Stop sending deadline reminders once that decision has changed.
For your next action, open the acceptance thread and the delivery folder, and write down the one unresolved decision. If your team has supplied what it owes, send the first factual check-in and assign an owner to the reply cutoff.
