A website is difficult to maintain when every text change needs a developer or every editor can publish anything without review. Commission the editing workflow alongside the public design so responsibility remains clear after launch.
Related service: Website and ecommerce development- 01Create a draft
- 02Preview real layouts
- 03Review meaning and links
- 04Publish the approved version
- 05Verify or restore
SECTION 01
Define roles and the meaning of approval
List who writes content, who checks technical or commercial accuracy, and who can publish. One person may perform several tasks in a small team, but the responsibilities still need names. Distinguish ordinary copy changes from changes to pricing statements, forms, navigation, or tracking. Those may need a different review path.
WordPress documents roles and capabilities as one example of task-based publishing permissions; this is a reference, not a promise of a specific platform implementation. Ask the agency to demonstrate equivalent controls in the selected system. Define draft, review, scheduled, published, and archived states only where they solve a real operational need.
SECTION 02
Illustrative example: a service page changes during a campaign
Imagine a marketing editor updates the description of a workshop while a campaign is already sending visitors to the page. The draft changes the preparation requirements and the inquiry link. A reviewer checks both the wording and the destination in preview before publication. The public page remains on the approved version until that decision.
A second editor should not silently overwrite the first person's work. Depending on the system, editing locks, revision checks, or a clear operational rule can prevent conflicting changes. MDN's conditional-request guidance explains one technical approach to detecting changed resources. The important buyer requirement is that conflicting updates are visible and recoverable, not that a particular mechanism appears in the proposal.
SECTION 03
Test editing with the people who will operate the site
Give an editor representative tasks: change a heading, add a resource, replace an image, schedule a correction, and restore an earlier version. Check long content and missing optional fields in preview. A flexible editor that lets users destroy the page structure may be less useful than a small set of controlled components.
Acceptance should include permissions, draft visibility, review notifications where agreed, and the public result after publication. Verify that private preview links do not expose confidential material and that retired staff lose access. The handoff should explain content fields, publishing steps, ownership of integrations, and what needs developer assistance. Keep the first workflow simple enough that the team will actually use it; elaborate approvals that are routinely bypassed provide little protection.
SECTION 04
Frequently asked questions
Should every change need two people?
Not necessarily. Match review to risk, while naming who is accountable for the published content.
Can editors change the page layout?
That depends on the agreed component controls. Demonstrate the actual editing tasks before accepting the content system.
Is a revision history enough for recovery?
It helps, but test what it restores. Content revisions may not reverse files, integrations, permissions, or a code deployment.
PRIMARY REFERENCES
Sources and further reading
These references cover the standards, platforms, or published prices discussed in the guide. Worked examples and checklists are our editorial guidance.
- Roles and CapabilitiesWordPress Documentation
- HTTP conditional requestsMDN Web Docs
EDITORIAL METHOD
About this guide
We use AI to assist with drafting and editing. Catapult AI Work is responsible for the published content. Examples illustrate possible approaches; they are not client case studies unless identified as such.
Budget examples are not Catapult package prices. Check linked provider pages for current fees and plan limits before making a purchase.
Read the editorial policy