A useful publication review ends in an explicit decision: publish, revise, or escalate. Save enough evidence that another maintainer can understand what was checked and what remains open.
Finish with
Outcome
A saved editorial record containing the reader need, claim evidence, rendered-page checks, owner, trigger, unresolved questions, and a publish, revise, or escalate decision.
What you need
- The complete draft and a rendered preview at its intended address.
- Source records for names, numbers, dates, quotations, prices, credentials, and material claims.
- A keyboard, narrow viewport, and access to inspect links and image alternatives.
- A person authorized to resolve editorial, operational, privacy, legal, or safety uncertainty.
The observable problem
A draft can be grammatical while giving the wrong date, sending the primary link to an expired form, or relying on an image to carry essential details. Reviewing only prose misses behavior; reviewing only the rendered page can miss unsupported claims.
Separate a blocker from follow-up polish. An unsupported material claim, incorrect critical fact, broken primary action, or inaccessible primary task blocks publication. A minor consistency edit may be scheduled only when the page remains accurate and usable. Uncertainty about authority, privacy, legal duties, or safety should be escalated, not waved through.
Invented for instruction
Fictional worked example
Fictional worked example: East Mere Workshop is an invented organization preparing an event page. The draft says “our most popular course,” lists Saturday 21 June, links “Book now” to an old form, and places the accessible entrance only in text baked into a poster image.
The reviewer cannot find evidence for “most popular,” so the phrase is removed. The signed event sheet shows Sunday 21 June, so the visible date is corrected. The booking owner supplies the current form. The entrance information becomes HTML text beside the venue address, and the poster receives context-appropriate alt treatment.
Change log: unsupported comparison, removed; wrong weekday, corrected from signed event record; stale booking route, replaced and submitted in test mode; access detail trapped in image, added to page text. Decision: revise, retest, then publish. This fictional example demonstrates process, not an actual client outcome.
Procedure
Write the reader need and page job
Complete the sentence “This page helps a reader…” with one primary outcome. Check whether every major section supports it. Move unrelated organizational history or secondary campaigns to a suitable destination rather than making the page answer competing needs.
Verify material claims and dates
List names, numbers, quotations, prices, credentials, results, event details, deadlines, and comparative claims. Record a source location and verification date for each material item. Remove, qualify, or escalate claims that lack adequate evidence.
Follow the rendered primary path
Start from the likely entry point, read headings and labels, activate the main link, and complete a safe test where possible. Confirm destinations, downloads, error messages, and content after submission. Never use live personal or payment information merely to satisfy a checklist.
Run access and layout checks
Use the keyboard through the primary task, check visible focus and escape from components, inspect image alternatives in context, and view the page at a narrow width and zoom. Record the exact path and state for a barrier rather than declaring the whole page inaccessible.
Decide, assign, and preserve
Choose publish, revise, or escalate. List blockers separately from non-blocking follow-up. Name the owner and event-based review trigger, then save evidence and the change log with the page record. A future review date never excuses a known current error.
Reusable worksheet
| Review area | Observation | Evidence or test path | Blocker or follow-up | Owner | Decision or change |
|---|---|---|---|---|---|
| Event date | Draft says Saturday 21 June; source says Sunday | Signed event sheet, verified today | Blocker | Events owner | Correct weekday before publication |
| Primary booking link | Old form is closed | Followed Book now from preview | Blocker | Bookings owner | Replace link and run safe test |
| Style consistency | One heading uses sentence case differently | Rendered preview | Follow-up | Editor | Schedule only after blockers close |
Decision rules
- If a material claim lacks adequate evidence, block publication until it is removed, qualified, sourced, or escalated.
- If a critical fact is wrong or the primary action is broken, revise and retest before publishing.
- If the primary task cannot be completed from the keyboard, treat it as a blocker and seek technical repair.
- If the page is accurate and usable but has minor polish remaining, publish only when the follow-up has an owner and does not hide a barrier.
- If authority, privacy, legal, medical, or safety implications are uncertain, escalate to an appropriate responsible person.
Limitations and escalation
- A short editorial pass samples important paths. It is not complete accessibility, legal, privacy, security, performance, factual, or technical testing.
- A source can itself be wrong or outdated. High-consequence claims may require independent confirmation and subject expertise.
- Preview behavior may differ from production because of hosting, authentication, caching, third-party services, or configuration.
Review list
Check the work
- The primary reader need and page job are explicit.
- Material claims and dates have source locations and verification dates.
- The primary action, links, image purposes, keyboard path, and narrow layout were reviewed.
- Blockers are separated from non-blocking follow-up.
- The record names an owner, review trigger, unresolved questions, and final decision.
Review again when
- A material fact or source changes
- The primary link or form changes
- A new image or interactive component is added
- An event passes
- A reader reports an error or barrier