1. Inventory the parts that change
Start with page types and functions: services, contact details, forms, images, language versions, integrations and technical configuration. Mark what changes often, what rarely changes and what matters to the visitor’s next step.
Connect every part to a source and an owner. A page list without owners cannot show who checks a claim or approves a change.
2. Define how changes are approved
Record how someone submits a request, what information it needs and who approves release. Identify changes that need technical review, such as adding an integration or changing where a form is sent.
Permissions should match the task. Do not give everyone administrator access for convenience, and do not store shared secrets in the documentation. Point to the organisation’s approved account and recovery process.
3. Make checks repeatable
Choose a short check for each type of change. A content edit may need a mobile, heading, link and language review. Test a form with a fictional enquiry and follow it from validation to confirmed receipt. Record what was checked and by whom.
Do not prescribe one universal review interval. Set it according to publishing pace, the cost of an error and the team’s capacity. Revisit the plan after significant platform or organisational changes.
4. Decide where outside help is needed
Compare the work with the team’s available time and skills. An internal owner may be responsible for facts and approvals while a specialist handles technical diagnosis. Hosting, licences, development and content should appear as separate responsibilities.
Finish with contact routes, the documentation location, the next review and unresolved questions. An ownerless task is a decision to resolve, not something to hide under a generic maintenance heading.
| Part | Owner | When to review | Evidence |
|---|---|---|---|
| Service information | Subject owner | When the offer changes | Approved copy |
| Contact form | Web owner | After a change and on the agreed schedule | Fictional test reaches the right recipient |
| Accounts | Account owner | When roles change | Permissions and recovery checked |