The short answer: the business owns the facts; writing must be assigned
Before design begins, agree who gathers information, writes, checks the facts, approves and maintains each page. The business must remain responsible for the accuracy of its services, conditions, people, evidence and limits. An internal colleague, an external writer or a mixed team can produce the copy, but that work should not be silently assumed to sit inside “web design”.
If your company has time, a clear voice and one decision-maker, it may be able to supply finished copy. If its knowledge is scattered across people and documents, commission research and writing based on real interviews and evidence. A collaborative model often works best: the business supplies facts; the supplier turns them into a readable structure; one business owner approves. The right choice follows available capacity, not a convention about who ought to write.
Separate five responsibilities instead of calling everything content
The subject owner explains how the business works and provides internal sources: services, process, common questions, limits, images and documents. The writer turns that material into messages and pages. An editor checks clarity, consistency and voice. An approver confirms that claims are accurate and publishable. Finally, someone must update the content when hours, people, services or terms change.
Two people may cover all five roles, but each role needs a name or function. “The client will send the copy” does not say whether that means notes, rough drafts or finished pages. “Copy included” does not explain the interviews, page count, revisions or checks. A comparable proposal describes inputs, deliverables, owners and the approval test.
- Subject knowledge: supplies facts, evidence and service boundaries.
- Writing: drafts for the page's audience, purpose and next action.
- Editing: removes ambiguity, repetition and unnecessary jargon.
- Approval: validates facts, claims and permission to publish.
- Maintenance: keeps information correct after launch.
Three commissioning models—and where each one breaks down
Business-supplied copy works when useful messages already exist, a colleague has protected writing time and the supplier receives finished pages before detailed design. It reduces the writing scope, but does not remove web editing, adaptation to each page or gap analysis. The risk appears when the project promises finished copy but receives only an old brochure and disconnected notes.
Supplier-written copy works when the knowledge exists but nobody inside the business can shape it into pages. The proposal should specify interviews, required materials, page count, revision rounds and factual approval. The supplier can organise and express the evidence; it should not invent experience, customers, figures or outcomes to fill blank sections.
A collaborative model asks the business for evidence and answers, while the supplier proposes the page map, outlines and drafts. One internal owner consolidates feedback. This often balances accuracy and clarity, but it still needs a decision-maker. Five departments sending conflicting edits without a final owner does not create collaboration—it moves the blockage into review.
Put the content sequence in the proposal
You do not need a universal schedule, but you do need ordered dependencies. Begin with an inventory of pages and existing materials. Define who each page serves, the question it answers and its next step. Then gather facts and evidence, prepare outlines, draft and run a factual review. Detailed design and final editing follow when the content has enough shape to support real decisions.
Google recommends content made for a real audience and clear purpose that leaves people with enough information to achieve their goal. It also says there is no preferred word count. Acceptance should therefore not be “500 words per page”; it should test whether the page answers what matters without invention or forcing a second search for basics. web.dev also explains that headings form a page outline and should communicate what is important. Structure is not decoration added after writing.
- Inventory: pages, documents, photography, evidence and gaps.
- Purpose: audience, primary question and next step for each page.
- Raw material: interviews, answers and verifiable internal sources.
- Draft and review: facts first, then clarity, voice and structure.
- Approval and design: an identified version moves into layout and testing.
A hypothetical cleaning company compares three proposals
Imagine a fictional office-cleaning company commissioning a new website. The first proposal assumes the client will provide all copy. The business accepts because it sounds simple, but nobody has allocated time and each manager describes the services differently. Design advances with placeholder text. When the real information arrives, sections no longer fit and unpriced decisions appear.
A second proposal includes full writing but says only “professional copy”. Before choosing it, the company asks for specifics: one discovery interview, a service inventory, outlines for six pages, a first draft, one consolidated factual review and final editing. It also excludes fabricated case studies and environmental claims without evidence. The scope can now be assessed.
The third option divides the work. Operations provides processes, locations, exclusions and practical answers; sales contributes real customer questions; the supplier writes and structures; a director approves one version. The company chooses this route because it preserves internal expertise without turning managers into copywriters. The choice is not based on one model being universally superior, but on who has the time, judgement and access to facts.
Review against decisions, not personal taste
Agree review questions before the first draft. Does the page identify whom it helps and in what situation? Does it explain inclusions and exclusions? Can its claims be supported? Will a newcomer understand the terms? Is the next step clear? Can someone scan the headings and understand the route? These prompts produce actionable feedback. “It doesn't feel right” or “make it more premium” does not identify a problem to solve.
Clarity is also an accessibility concern. web.dev recommends clear, concise and unambiguous language, predictable navigation and an understandable order. This does not strip away brand personality; it prevents essential information from hiding behind jargon. Test links, forms, image alternatives and mobile reading too. Approved copy is not finished until it works in the published page.
When professional help is worth commissioning
Bring in writing or content-strategy help when knowledge is spread across several people, no one has time to turn it into pages, the offer is difficult to explain or a redesign requires decisions about what to retain. Do the same when several languages are involved: translating words does not decide who adapts claims, examples, customer service and maintenance for each audience.
Specialist review is also needed when claims touch regulated subjects, rights, safety or personal data; a writer cannot replace appropriate technical or legal validation. Before signing, ask for a page-level table naming the subject owner, draft owner, approver, revision allowance and delivery condition. Content then stops being the material that will “come later” and becomes a visible part of the commission.
Sources and documentation
- Google Search Central: Creating helpful, reliable, people-first content ↗
- Google Search Central: Search Essentials ↗
- web.dev: Content structure ↗
- web.dev: How is digital accessibility measured? ↗
Content created with AI assistance. Check the sources, date and scope of each guide.