Before choosing a page layout, decide what the visitor needs to understand and do. A design filled with placeholder text can hide missing answers, unclear offers and content nobody owns.
## Write a brief for each important page
Record the audience, the question that brought them there, the answer the page must provide and the next action. A service page might need to explain who the service is for, what is included, where it is available and how to request a quote.
Gather the facts before asking someone to polish the wording. Prices, service boundaries and opening hours need an accountable owner. A writer should not have to invent them to fill an empty section.
## Work with representative content
Use real headings, a realistic description and the longest likely service name before settling the layout. Check a narrow screen as well as a desktop. A button label that fits a mockup may wrap after a client replaces it with approved wording.
Mark incomplete copy as incomplete in the working document. Keep it out of the public page until the responsible person confirms it. A convincing placeholder can otherwise be mistaken for an approved claim.
## Separate repeated records from individual sentences
Team members, locations and events usually need a repeatable structure. Define which fields are required and what should happen when an item is removed. Individual explanatory paragraphs may need a simpler editing workflow.
This is the point to decide whether an existing CMS is sufficient. Do not add a headless system just because it is fashionable. Include the time needed to build previews, publishing, permissions and recovery in the decision.
## Give each content item an owner
Use a short inventory: page, content item, authoritative source, approver, update frequency and editing location. If a price appears in several places, identify whether those displays share one field or need separate changes.
A website can have several sources of truth. Copy in the page editor might sit beside information supplied by a booking platform. Document those boundaries rather than assuming one tool controls everything.
## Test the editing workflow before handoff
Have the intended editor replace one approved sentence, publish through the agreed process and inspect the live result. Confirm that their role cannot change unrelated settings.
For existing page wording, an installed in-place editor such as ReCopyFast may be an option. It does not replace a CMS for creating new pages or managing structured collections. The [handoff checklist](/blog/website-handoff-checklist-client-updates) helps turn the chosen approach into instructions the client can actually follow.
## Write a brief for each important page
Record the audience, the question that brought them there, the answer the page must provide and the next action. A service page might need to explain who the service is for, what is included, where it is available and how to request a quote.
Gather the facts before asking someone to polish the wording. Prices, service boundaries and opening hours need an accountable owner. A writer should not have to invent them to fill an empty section.
## Work with representative content
Use real headings, a realistic description and the longest likely service name before settling the layout. Check a narrow screen as well as a desktop. A button label that fits a mockup may wrap after a client replaces it with approved wording.
Mark incomplete copy as incomplete in the working document. Keep it out of the public page until the responsible person confirms it. A convincing placeholder can otherwise be mistaken for an approved claim.
## Separate repeated records from individual sentences
Team members, locations and events usually need a repeatable structure. Define which fields are required and what should happen when an item is removed. Individual explanatory paragraphs may need a simpler editing workflow.
This is the point to decide whether an existing CMS is sufficient. Do not add a headless system just because it is fashionable. Include the time needed to build previews, publishing, permissions and recovery in the decision.
## Give each content item an owner
Use a short inventory: page, content item, authoritative source, approver, update frequency and editing location. If a price appears in several places, identify whether those displays share one field or need separate changes.
A website can have several sources of truth. Copy in the page editor might sit beside information supplied by a booking platform. Document those boundaries rather than assuming one tool controls everything.
## Test the editing workflow before handoff
Have the intended editor replace one approved sentence, publish through the agreed process and inspect the live result. Confirm that their role cannot change unrelated settings.
For existing page wording, an installed in-place editor such as ReCopyFast may be an option. It does not replace a CMS for creating new pages or managing structured collections. The [handoff checklist](/blog/website-handoff-checklist-client-updates) helps turn the chosen approach into instructions the client can actually follow.