Examples
The formats an engagement delivers.
Three pieces of working material, drawn the way the real ones are drawn: a calendar that carries statuses, a register that carries owners, and a request route that carries one change at a time.
A publishing calendar.
Every entry carries its format and its status, so a glance answers what is live, what is being reviewed and what is still being drafted. The structure holds in a spreadsheet as well as in a dedicated tool.
Publishing calendar
- Published
- In review
- Scheduled
- Draft
Guide Returns page rewrite Published
Rule sheet Naming rules for help articles In review
Checklist Quarterly content audit Scheduled
Record Homepage banner change Published
Guide New service page In review
Checklist Image alt-text sweep Draft
Record Pricing page owner handover Scheduled
Rule sheet Archive policy note Draft
Guide Contact page refresh Scheduled
Record Monthly release review Scheduled
- Day 2 Guide Returns page rewrite Published
- Day 4 Rule sheet Naming rules for help articles In review
- Day 7 Checklist Quarterly content audit Scheduled
- Day 9 Record Homepage banner change Published
- Day 12 Guide New service page In review
- Day 15 Checklist Image alt-text sweep Draft
- Day 18 Record Pricing page owner handover Scheduled
- Day 21 Rule sheet Archive policy note Draft
- Day 24 Guide Contact page refresh Scheduled
- Day 27 Record Monthly release review Scheduled
A page ownership register.
The register is the answer to "whose page is this?" before the question is asked. Review cycles sit beside owners, so nothing ages quietly.
Page ownership register
Working copy
| Site section | Owner | Review cycle | Status |
|---|---|---|---|
| Product pages | Head of product | Every quarter | Current |
| Help centre | Support lead | Monthly | Review due |
| News and updates | Marketing editor | Each release | Current |
| Legal pages | Operations manager | Every six months | Current |
| Careers | Awaiting assignment | Quarterly | Awaiting owner |
An update request record.
When every change arrives in the same shape, nothing is lost between an inbox, a chat thread and a hallway conversation. The record holds the change, the reason, the owner and the approval in one place.
Update request record
One route for every change
- Request
- Refresh the returns information before the seasonal campaign
- Page
- /help/returns
- Requested by
- Customer support lead
- Page owner
- Support content editor
- Reason
- Policy wording changed; current text is out of date
- Approval
- Operations manager
- Status
- Approved, scheduled