Policy Review¶
Rule revision — instantiates Periodic Review and Reset
Re-examines a standing rule against the reality it now governs and revises, renews, or retires it — resetting the reference itself rather than restoring the world to it.
Policy Review is the one mechanism in this family whose reset is aimed at the reference, not the system. Where a reconciliation or a calibration drags the world back toward a fixed standard, a Policy Review asks whether the standard is still the right one. A rule written for a past reality — an expense policy, a data-retention rule, a building code, an eligibility criterion — is re-read against the practice and context it now governs, and the corrective move is to change the rule: tighten it, loosen it, clarify an ambiguity, or retire it outright because it no longer fits. Its defining idea is that drift can live in the baseline itself, and the fix is to update the baseline rather than to restore a stale one.
Example¶
A company's remote-work policy was written in a hurry during an office closure: it caps remote work at two days a week and requires manager sign-off for each day. Two years on, a scheduled policy review takes it up. The reviewers gather what actually happened — most teams quietly ignore the two-day cap, the per-day sign-off is universally skipped, and two disputes escalated to HR because the written rule and real practice diverged so far that no one knew which governed.
The reset here is not making everyone comply with the old cap; it is rewriting the rule to fit reality and intent. The review revises the policy to a flexible hybrid standard, deletes the unworkable per-day approval, and adds a clear exception path for roles that must be on-site. What the review learned — that a rule ignored in practice becomes a liability, and that the sign-off step was pure friction — is written into the rationale so the next review isn't starting blind. Findings that touched legal exposure were escalated to counsel before the rewrite was adopted. The reference state moved; the world was not forced back to a baseline that had already died.
How it works¶
- Read the rule against lived practice. Compare what the policy says to how the system actually behaves and what the policy was meant to achieve.
- Diagnose the gap's direction. Decide whether practice has drifted from a still-good rule, or the rule itself has gone stale — the second calls for changing the reference.
- Revise, renew, or retire. The corrective move edits the rule: tighten, relax, clarify, or sunset it. A rule that no longer earns its keep is removed, not restored.
- Escalate rules with external stakes. Changes touching legal, safety, or regulatory exposure go to the authority that must approve them before adoption.
- Capture the rationale. Record why the rule changed so future reviews inherit the reasoning instead of relitigating it.
Tuning parameters¶
- Review interval — frequent review keeps rules current but churns them faster than people can adapt; long intervals give stability but let rules ossify against a changed world.
- Change bias — a disposition toward revising keeps policy fresh but risks thrash; a bias toward preserving gives predictability but breeds stale rules kept by inertia.
- Sunset default — whether rules expire unless renewed (forcing justification) or persist unless repealed (favoring stability).
- Stakeholder breadth — consulting everyone the rule touches improves fit but slows the cycle; a narrow review is fast but risks blind spots.
- Escalation threshold — how much legal or safety exposure a proposed change must carry before it needs higher approval.
When it helps, and when it misleads¶
Its strength is that it attacks the failure the other siblings can't: a stale baseline. When the reference itself has gone wrong, no amount of restoring-to-it helps, and only a mechanism willing to rewrite the rule can realign the system with current reality.
Its failure mode runs both ways. Retire too eagerly and you strip out a rule[1] whose quiet benefit — a guardrail against a rare but severe failure — was invisible precisely because it was working, a Chesterton's-fence mistake. Revise too timidly and the review becomes a ritual that reaffirms dead rules. The classic misuse is a review that rubber-stamps the status quo because changing anything is harder than leaving it. The guarding discipline is to make each rule earn renewal on its current merits and to force the reviewer to articulate what a rule is for before removing it.
How it implements the components¶
reference_state— the standing rule is the reference under examination; uniquely, this mechanism treats the reference as the thing that may need to change.reset_action— the corrective move revises, renews, or retires the rule, editing the baseline rather than restoring the system to it.learning_capture— the rationale for each change is recorded so future reviews inherit the reasoning.escalation_rule— changes with legal, safety, or regulatory stakes are routed to the approving authority before adoption.
It does not implement a live drift_indicator reading or the exception_trigger for off-cycle early review — those belong to Retrospective, which resets a team's own working agreements from its felt experience; a Policy Review revises formal rules that govern others rather than the reviewers' own process.
Related¶
- Instantiates: Periodic Review and Reset — the Policy Review supplies the update-the-reference-itself path through the loop.
- Sibling mechanisms: Audit Cycle · Calibration Check · Data Quality Recertification · Financial Reconciliation · Health Checkup · Preventive Maintenance Check · Quarterly Business Review · Retrospective
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Policy Review operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it re-examines a standing rule against the reality it now governs and revises, renews, or retires it — resetting the reference itself rather than restoring the world to it.
Independent corroboration: The frozen evidence defines Policy Review as 'Re-examines a standing rule against the reality it now governs and revises, renews, or retires it — resetting the reference itself rather than restoring the world to it', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Public Administration & Policy
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Periodic reconsideration, renewal, revision, or retirement of standing policy is a core administrative-governance practice.
Related originating lineages:
- Law & Governance — Law contributes authority, validity, and procedural requirements for changing the governing reference.
Review resolution: Both blind reviewers agree that public administration policy is the primary origin. Reconciliation resolves origin mode disagreement. Formative alternate lineages are retained as law_governance; later breadth of use is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among origin lineages.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
Policy Review is the sibling that most directly serves the archetype's own warning about resetting to a stale baseline: it is the mechanism you reach for when the problem is the reference, not the drift. Because its reset changes the standard everything else is measured against, it should be the most deliberate and best-documented of the family — a careless rule change quietly redefines "correct" for every downstream check.
References¶
[1] Chesterton, G. K. The Thing. Sheed & Ward (1929). Warns against removing an existing rule or institution before understanding the purpose for which it was established. registry ↩