All guides

What to do when website content arrives late

Content delays become expensive when the delivery date stays fixed but the inputs keep changing.

Define a content handover

Before the build begins, list the pages, copy, images, legal text and approvals you need. Give each item an owner and a date. Explain what “ready” means: final copy, agreed image choices and permission to use the supplied assets.

Tell the client what the delay affects

Avoid a generic warning that the project will be late. Say which work cannot proceed and which work can. If you can build the page structure with sample text, explain what may need revisiting once the real copy arrives.

We are ready to populate the Services and About pages. The final copy was due on [date]. Please send it by [date] so I can confirm the next available build slot. The current launch estimate needs to be revised once the content is complete.

Price new work separately

A delay alone is not a reason to invent a penalty. Follow your agreed terms. If the client asks you to write missing copy, source replacement images or redo completed layouts, describe and estimate that additional work before starting it.

At closeout, note which inputs arrived late and how many hours were spent handling changes. Use that information to improve the next project brief and timeline assumptions.