Do not begin a website project by trying to fill a blank document with finished copy. Begin by collecting the material that makes finished copy and design honest: the business facts, the proof, the limits, the assets, the account information, and the people who can verify each one.

That shift matters because a design can accommodate incomplete wording; it cannot responsibly invent a service boundary, a credential, a photo right, a policy, or a contact promise. When those gaps surface late, the project is usually not delayed by writing. It is delayed by unanswered ownership and truth questions.

Gather evidence by page decision

The useful inventory is not a pile of files called "website content." It connects a material item to the page decision it supports. W3C’s guidance on headings and images is a useful reminder: headings convey how content is organized, while an image’s text alternative depends on the information or function it represents. In other words, content needs context before someone can design or describe it well.

The table below is the checklist to use before a visual direction is treated as ready. Do not fill a row from memory when a source or approver exists.

Owner, material, source checklist

What to gather Owner who can verify it Best source or evidence What it will support Status to record
Service names, plain-language descriptions, and fit limits Business subject-matter owner Current operating notes, intake interview, approved service documentation Service and homepage messages Verified / needs decision
Service area, availability, hours, and contact expectations Operations owner Current public listing or operating policy checked by the owner Fit, contact, and location language Verified / may change
Price, price drivers, financing, or the decision not to publish prices Authorized business decision-maker Current approved price material or written decision Pricing explanation and quote expectations Approved / do not infer
Credentials, licenses, memberships, reviews, examples, and case material Claim owner plus public-use approver Original record, permission, attribution, and date Proof beside relevant claims Permissioned / unavailable
Images, logo, video, diagrams, and brand files Asset owner Original file, license, creator, intended page use Design, media, and text alternatives Cleared / source missing
Existing pages, important URLs, forms, and integrations Site or platform owner URL inventory, account access confirmation, known dependencies Migration, navigation, and launch planning Verified / investigate
Privacy, terms, regulated claims, and required disclosures Authorized owner or qualified adviser Current approved text and jurisdiction-specific advice where needed Required pages and form wording Approved / legal review
Decision-maker, reviewers, and approval deadline Project sponsor Named responsibility record Copy and design approval sequence Named / unresolved

The status column is as important as the material itself. "We will get that later" is not content. It is a project risk that should be visible before a page is designed around it.

Separate facts from claims

A fact such as a service area, a phone number, or a stated opening hour still needs a person who can confirm it. A stronger claim—"best," "fastest," "most trusted," "guaranteed," or an outcome claim—needs a defensible basis or should not appear. Images follow the same rule: an attractive project photograph is not automatically permission to use it as proof, and a stock image is not evidence that the business performed the pictured work.

This is not an argument for bloodless copy. It is how a business gets specific without borrowing confidence from something it cannot substantiate. A clear limit can be more useful than a broad promise, especially on a service page or a quote path.

Do not make the designer the final fact checker

A web partner can lead an interview, organize evidence, propose a page hierarchy, and draft a clearer explanation. The business still has to verify its services, policies, proof, availability, pricing statements, and regulated claims. That split protects the buyer as well as the project: the draft becomes a useful decision document instead of an attractive record of guesses.

Set one factual approver for each major page group. That does not mean a committee must approve every sentence. It means there is a named person who can say whether the page is true, what needs correction, and when the material is ready. If five people give conflicting feedback, the project sponsor—not the page layout—needs to resolve the conflict.

What can wait, and what cannot

Some inputs can wait without distorting the work: a future blog topic, a secondary photo, an optional testimonial, or a refinement to a low-priority page. Other gaps should stop a decision: the real service scope, the correct contact route, an essential legal disclosure, an approved claim, ownership of the domain or key account, or the person who can accept the page.

Use that difference to sequence the work. Build the page map around verified core material first. Mark lower-priority pages as deferred rather than filling them with generic copy. A smaller site with honest routes is more useful than a larger site that makes the owner promise to provide facts they have not decided.

The checklist is not the writing process

Collecting material does not turn the owner into a copywriter. It gives the writing and design process something real to work with. The final work still needs a reader, a decision, a page structure, and an appropriate next action. It also needs edits: raw intake language rarely belongs unchanged on a public page.

What this checklist prevents is the false handoff in which a provider says "send content" and the business assumes that means a logo, an old brochure, and a few photos. The real inputs are facts, proof, constraints, assets, access, and authority to decide.

If the sitemap itself is unclear, settle the page jobs first with How Many Pages Does a Service-Business Website Actually Need?. Then use the checklist row by row, recording what has been verified and what is still waiting on a decision.

Sources