Client Content Is Late: Reset the Launch Without the Rush
A four-step workflow to handle late client content, move dependent dates and protect QA without turning the delay into your team’s emergency.
This week, your client promised the homepage copy on Tuesday. It is Friday, development is waiting, and they still expect the same launch date—so identify the missing dependency, notify the client, reset every date it blocks, then confirm the revised plan when the complete package arrives.
Do not absorb the gap by quietly squeezing three weeks of work into three days. Relative schedules tie delivery to client-controlled events: for example, launch four weeks after final website content or complete the next phase three weeks after all feedback arrives.
Set the dependencies before work starts
At kickoff, name every client-owned input: page copy, product images, brand assets, consolidated feedback and the sign-offs needed to proceed. Give each one an owner and due date. Beside it, record the work that cannot finish without it—design, development, QA or launch. Agencies can often anticipate the content a web project will require and should tell the client what is needed and when as early as possible.
Keep the record lean: dependency, request date, due date, actual delivery date, agreed decision and revised milestone. Define “complete” too. Five product images without filenames, final crops or approval may be a delivery, but they are not necessarily a usable package.
A useful schedule line reads: “Development completes three weeks after approved homepage copy and final image assets are received as one complete package.” For feedback: “The next phase starts after one consolidated feedback set and the named approver’s sign-off.”
Use the right response for the blockage
REMIND — The input is approaching its due date or has just passed it, but useful work can continue. Send the direct reminder and restate the dependency.
RESET — The missing input now blocks critical-path design, development, QA or launch work. Move the dependent dates and state why. PMI practitioners recommend first determining whether a delay affects the critical path.
ESCALATE CHOICES — The client still wants the original launch date. Our recommendation is to present four choices: move the date; reduce scope; phase lower-priority requirements; or consider added resources, subject to their availability and cost. PMI practitioners separately support scope reduction, phased requirements and evaluating resource cost and availability when compressing a schedule.
RESTART — The agreed complete package has arrived. Confirm receipt and issue the revised sequence for development, QA and launch.
Send the first reminder
Address delays early and directly. Matchstick recommends a face-to-face or video conversation for difficult delay discussions, with a phone call as the next option, because email can be ignored or invite line-by-line rebuttal. For a routine nudge, however, a short written message gives both sides a precise action to follow.
Subject: Homepage copy due [DATE]
Hi [NAME] — a quick reminder that the final homepage copy is due on [DATE]. We need it to complete [DESIGN/DEVELOPMENT], which is scheduled next. Please send the approved copy in [LOCATION/FORMAT] by [TIME]. If it arrives after that point and blocks the next task, we will revise the dependent delivery and launch dates. Let me know today if you expect a problem.
Reset the schedule when the work is genuinely blocked
A missed date alone does not require theatre. Reset the schedule when the missing item prevents critical work from finishing. State the fact, the blocked work and the scheduling consequence. Keep blame out of it, but keep responsibility visible.
Subject: Schedule reset — [MISSING ITEM]
Hi [NAME] — we have not yet received the approved [MISSING ITEM], due on [DATE]. It is now blocking [DESIGN/DEVELOPMENT/QA], so the dependent delivery and launch dates can no longer remain as scheduled. Once we receive the complete, approved package, we will confirm the revised plan. Under our current scheduling basis, [MILESTONE] will be completed [NUMBER] weeks after complete delivery. Your next action is to send [EXACT ITEM] via [DIRECT LOCATION] or tell us when it will be ready.
For a difficult delay discussion, move the conversation to video or phone, then document the agreed dates and decisions in writing. The aim is not to win an email tennis match. It is to leave both teams with one workable plan.
Show the knock-on effect with one real sequence
Suppose the approved homepage copy and final product images are due before design completion. Without them, the designer cannot finish the page states; development cannot build the final modules; QA cannot test the finished experience; and launch remains dependent on that sequence. When the assets arrive late, do not leave design, development, QA and launch on their old dates. Recalculate them from receipt of the complete package.
You may still advance work that does not depend on those assets. PMI practitioners suggest using simultaneous tasks to bridge a non-critical delay. For a critical-path problem, the responses they identify include adding resources, subject to budget and availability; reducing scope; or using a change request to confirm the missing items and time.
Confirm the restart only when the package is complete
Subject: Materials complete — revised project sequence
Hi [NAME] — we received the complete approved [COPY/IMAGES/FEEDBACK], originally due on [ORIGINAL DUE DATE], on [RECEIVED DATE]. This clears the block on [WORK]. The revised sequence is: [DEVELOPMENT MILESTONE], then [QA MILESTONE], then launch on [DATE OR RELATIVE DATE]. Your next action is [APPROVAL/ACCESS/ATTENDANCE] by [DUE DATE]. These dates replace the earlier dependent milestones.
Check the package before sending that note. Confirm the requested items, usable formats, consolidated feedback and required sign-off. If something is still missing, name it precisely and keep the project in reset status.
If the original launch still matters, offer choices
Schedule compression is a separate decision, not a courtesy hidden inside the existing fee. PMI practitioners identify resource availability and cost as deciding factors when adding people to recover time. They also recommend reprioritising requirements or phasing less critical functionality, with stakeholder explanation and approval.
Our recommended menu has four options: move the launch date; reduce scope to the must-have release; phase lower-priority work into a later release; or explore added resources, with their availability and cost considered explicitly. The client chooses the trade-off with you. Your team does not silently fund it with evenings and crossed fingers.
Do not compress QA, accessibility checks or testing by default. If the original launch must stay, agree explicitly which scope changes, resources, costs and trade-offs make that possible. PMI identifies scope and cost alongside schedule as major project constraints.
Treat extra fees as agreed terms, not surprise penalties
Paid copywriting, image production, migration help or training can solve a content bottleneck, but present them as separately scoped services. Sakas recommends offering content creation and making the client’s input and sign-offs clear; he also advises stating what is and is not included in the proposal.
Matchstick recommends putting any delay fee or idle-day fee expressly in the SOW and discussing the clause during sales or kickoff, with reminders as deadlines approach. For a critical-path problem, a PMI practitioner identifies a change request as one possible way to confirm the missing items and time. Any fee, charge or change request depends on the specific contract and must be agreed there or approved separately.
The professional move is simple: define client dependencies at kickoff, remind before they become blockers, reset dependent dates when critical work stops, and restart from complete delivery. If the fixed launch date survives, something else must change—scope, phasing, resources or cost.
Preguntas frecuentes
Should every late client item move the launch date?
No. Send a reminder while useful work can continue. Reset dependent dates when the missing input blocks critical-path design, development, QA or launch work.
Can the agency keep the launch date by working faster?
Only through an explicit recovery decision. The recommended choices are moving the date, reducing or phasing scope, or exploring added resources while considering their availability and cost. Do not silently shorten QA, accessibility checks or testing.
When can an agency charge for a client delay?
Matchstick recommends stating delay or idle-day fees expressly in the SOW and discussing the clause during sales or kickoff. Paid content help should be separately scoped. Any fee or change request depends on the specific contract and must be agreed there or approved separately.