How to create a document review cycle
Create a document review cycle with named owners, risk-based due dates, change triggers, evidence of review and explicit keep, revise or retire outcomes.
A document review cycle assigns an owner and due date to each controlled item, then records whether review keeps, revises or retires it.
The short version
- Set each interval from the document's risk and rate of change, then spread due dates across the year.
- Treat material changes and findings as review triggers before the calendar date.
- Record keep, revise or retire; a no-change decision still needs an owner and date.
Make the review decision visible
A reminder alone is not a review cycle. The owner needs time to compare the instruction with current work, a route for resolving discrepancies and a place to record the outcome even when nothing changes. Incidents, system changes and audit findings can bring the review forward.
Stagger work according to risk and capacity rather than making every document due on the same day. A register should show the last review, outcome, next due date and open change request. The lifecycle diagram below closes the loop by sending a revision back to its change request instead of creating an informal side path.
Close the periodic review loop
The final decision in the lifecycle either reaffirms the issue, returns it to change control or withdraws it.
Establish the issue and owner
Approval, register entry and publication establish which revision the named owner will be asked to review later.
Trigger a real review
The in-use phase includes a scheduled review trigger; the reviewer compares the instruction with current practice and change evidence.
Record one of three outcomes
The final decision records continued validity and a new date, sends revision to a change request, or retires and withdraws the document.
How it works
Assign cadence and triggers
Give every controlled item an owner and due date; define incidents, law or system changes, and audit findings that call for earlier review.
Review against evidence
Use a recent work example and affected users to test steps, roles, systems, controls and records; capture discrepancies rather than simply renewing the date.
Close and reschedule
Record the reviewer, date and keep, revise or retire outcome. If unchanged, set a new due date; if changed, route through approval and withdrawal.
Mistakes to avoid
Changing the date without checking the work
A refreshed due date does not show whether the instructions still match current systems, roles and controls. Record what was checked.
Related QueryChart feature
Map your review cycle
Open the document control process and adapt its keep, revise and retire branches.
Frequently asked questions
Does a no-change review need a new revision?
No. Record the review decision and next due date without changing the approved content revision.
Can a document be reviewed early?
Yes. A process change, incident or finding can trigger review before the scheduled date.
Who tracks overdue reviews?
The document owner performs the review; a register owner or document controller monitors due dates and escalates overdue items.