Use this guide when circumstances change, a review date passes or somebody finds evidence that the record is wrong. A record being overdue means it needs attention; it does not automatically make its decision false or create a replacement.
Open the record and its sources
Ask your connected agent to find overdue operating records or open the specific record you intend to review. Check the current effective status, owner, scope and review date. Read the sources and any linked successor before treating its wording as today's rule.
Your account must have access to the record's area. Missing or refused results do not establish that a decision never existed. Zones and permissions explains that boundary.
Decide what has actually changed
Compare the record with current evidence. If the rule still applies, record the review and the appropriate next review date through the supported governed change route. If it should change, describe the new decision and the evidence for it. If nobody has made the new decision yet, keep the question open rather than presenting a draft as settled.
Save a successor when the decision changes
Create a new record of the same type and name the active predecessor it supersedes. A decision supersedes a decision; a policy supersedes a policy. The chain must not form a cycle. Keep the old rationale and sources available as history rather than rewriting them to look as if the new decision had always applied.
The saved successor makes the predecessor effectively superseded. The earlier record's stored status may be updated separately, so use the record reader's effective status and successor link when deciding what applies. Current information and its history explains why an earlier source is still useful evidence without being current guidance.
A new decision keeps the earlier reasoning
Current guidance and historical evidence remain distinguishable.
The earlier active decision or policy states the rule that applied. A proposed successor names that active record and the new decision and evidence. While the proposal waits, it is not a saved successor. Once the successor is active, it supplies the current guidance and the predecessor is effectively superseded. The earlier rationale remains available within the reader’s access.
Check the result and dependent work
Read the proposal's actual outcome. After it is applied, open the successor and predecessor and check the relationship. Then identify tasks, briefings or loops that rely on the old rule. A loop can check that its referenced operating context is still current; do not assume that saving a new record silently rewrites every dependent workflow.
If the source changed while your proposal was waiting, reconcile the current records before proposing again. Reviewing saved changes covers that check.
Related
Practical guides for people and agents