If the build depends on content you agreed to supply, a missed content date can move the launch. That does not mean the schedule should become unknowable. Both sides need an inventory of what is missing, what work can still proceed, and the decision that would unblock each page.
Find the dependency, page by page
Open the signed scope and make a simple table: page, required copy, required images, owner, approval status, and deadline. “Content is late” is too broad to manage. “The pricing page needs approved plan descriptions and legal review” is specific enough to assign.
Separate material that is truly blocking from material that can be replaced later without reworking the page. A missing logo may block a header approval; a missing team photograph may permit the layout to proceed with a clearly marked placeholder. Do not assume placeholders are safe for launch. An unapproved price, claim, or staff biography should remain unpublished until an authorized person verifies it.
Agree what can move forward
Ask the provider to identify work that does not depend on the missing material: component build, mobile layout, form routing, redirect planning, or a staging review. Ask whether late content creates rework and which milestone it affects. If an agency claims the entire project is blocked, request the list of deliverables it cannot complete and the dependency for each one.
Choose one of three paths for each missing item: supply it by a revised date, commission the provider to create it under a new written scope, or remove/defer that element. If copywriting was not included, do not treat “we will write it for you” as free or approved. If your team has several reviewers, appoint a single person to deliver consolidated final copy.
Reset the schedule from the next decision
A workable update says, for example: “Approved service copy due Tuesday; staging page ready for review three working days after receipt; launch date recalculated after final form and DNS tests.” The actual durations depend on the project. Avoid substituting one new launch date for an explicit chain of dependencies.
Record the new date, owner, and approval in the shared project channel. Keep the original plan and the changes visible so later invoice or delay discussions have a factual timeline. If the provider misses a milestone after the input arrives, ask for a separate provider-side recovery plan.
Prevent the same stall in a new proposal
Before signing, ask who supplies copy, imagery, legal text, product data, and access credentials; what “approved” means; and what happens to the schedule if an input is late. ARCHV’s public website process ties timing to scope, content readiness, and review stages. A particular deadline is set in the project proposal, not promised across all projects.
If you are still selecting a provider, put both proposals through the website quote comparison. Look for content ownership and schedule dependencies alongside the page count. A public client review about shifting launch dates during a platform change is one reported experience, and underscores the value of writing down the cause of each schedule change rather than assuming which party caused it.