Content collection, and why it slips timelines

Content collection is the stage of gathering the real words, images and data a website will actually contain, and it is the single most common cause of a slipped timeline on a website project — more often than design revisions, more often than technical build problems.

The reason is structural, not a matter of any one client being disorganised. Design and build proceed on the supplier’s own schedule; the supplier controls that labour and can commit to dates for it. Content collection depends on the client supplying product descriptions, staff bios, photography, pricing information or legal text that only the client holds, and on internal approval from people inside the client’s business who are not part of the supplier relationship at all. A supplier can promise a delivery date for their own work. They cannot promise one for someone else’s.

What “content” actually covers

Content is a wider category than most clients expect going in. It typically includes:

Content type	Common source of delay
Body copy for each page	Often needs writing, not just supplying, and writing takes longer than expected
Photography	Real photos of the actual business, not stock images, if the brief calls for authenticity
Staff or team bios	Requires each person’s own sign-off, not just the business owner’s
Product data (for ecommerce)	Descriptions, pricing, variants and stock levels, often needing extraction from another system
Legal and policy text	Terms, privacy policy and any industry-specific disclosures, sometimes requiring a lawyer’s review
Logos and brand assets	Frequently exist only as a low-resolution file pulled from an old website, not the original artwork

Each row is a separate task with its own owner and its own possible bottleneck, which is why “send us your content” as a single instruction reliably produces a slow, patchy response — it is really six different requests bundled into one sentence.

Why the content collection stage stalls builds

Three patterns account for most delays here. First, the person who can approve content is not always the person managing the project day to day, and getting their attention competes with their actual job. Second, writing genuinely new copy — rather than repurposing an old page — takes longer than almost anyone estimates on the first attempt, because it requires decisions about tone and emphasis that a business owner has not had to make explicit before. Third, photography in particular is often treated as an afterthought that “we’ll sort out later,” and later routinely becomes the week before launch, under time pressure that produces rushed, low-quality images.

Who is responsible for content collection, and where the line actually sits

The client supplies the substance — the facts, the words specific to their business, the images of their actual premises or people, the pricing and policy detail nobody else could write. The supplier specifies exactly what is needed, in what format, and by when, and is responsible for chasing that request with enough lead time that a delay is caught early rather than discovered at the point design or build is meant to start. A supplier who asks for “all your content” once, with no structure and no deadline, and then treats the resulting delay as entirely the client’s fault, has not done their half of this stage.

Some suppliers offer copywriting as part of the engagement rather than requiring the client to write everything themselves — see website copywriting for what that service typically covers and why it is priced separately from design. Bringing in a writer is frequently the single fastest way to remove this bottleneck, because it converts an open-ended task the client has to fit around their job into a defined task someone else is accountable for on a schedule. A dedicated content-gathering tool such as Content Snare, which splits one bundled request into individually tracked items each with its own reminder, solves the same structural problem from the software side rather than the people side, and can be worth the modest cost on a project with many separate content clients or contributors involved.

What to prepare and gather before a build starts, if you want to avoid the slip

Before a project starts, or as early as possible within it, gather: final logo files in their original vector format, not a screenshot from the old site; a list of every page the site will need and one paragraph of rough notes on what each should say, even in unpolished form, ideally captured in simple templates so each page’s content arrives in a consistent format; real photography of the actual business, staff and premises, taken specifically for the new site rather than salvaged from social media; and any legal or policy text that needs a second person’s sign-off, sent to that person before the content deadline, not on the day it is due. A short walkthrough call with the supplier, going page by page through what still needs to be supplied, catches gaps a written request alone tends to miss.

What happens to this content once it is ready

Gathering the raw material is a separate task from placing it into the built site — the collected content is what gets loaded once the site itself has been built against the approved design. See content population for what happens to this material once it exists, and why loading content is its own stage rather than an automatic side effect of having collected it.

The cost of leaving it late

A stalled content stage rarely shows up as an explicit cost line, but it produces real ones. A build team idle while waiting on client content still has to be paid, or is reassigned to another project and has to be re-briefed and re-scheduled when your content finally arrives — either outcome costs someone money. A launch date set before content exists is a date built on an assumption rather than a fact, and moving it has knock-on effects on any marketing, signage or campaign timed against it.

The reverse is also true: content gathered too early, before the design and page structure are settled, sometimes has to be reworked once the site’s actual layout is known — a paragraph written for a page that turns out not to exist, or a photo cropped for a header shape that changes. The right timing is content collection starting immediately, run in parallel with wireframing, so that the raw material and the structure it fills converge at roughly the same point rather than one waiting idle for the other.

Where this sits in the sequence

Content collection typically begins as early as possible, in parallel with wireframing and design, precisely because it is the slowest and least predictable stage. A supplier who waits until the build stage to ask for content has scheduled the least controllable task last, which is the opposite of good project management. See scoping and estimating for how a realistic content deadline should be built into the original timeline, and wireframing for the stage that runs alongside this one.