Policy Drift Review¶
Oversight review — instantiates Divergence Detection and Correction
Audits how a policy is actually being implemented in the field against its stated intent, using independent evidence, and escalates the gap to the policy owner.
A written policy states an intent; the field decides what it actually means. Across many offices, inspectors, or front-line workers — each interpreting, each facing local pressures — implementation can drift steadily away from the intent while every individual decision looks defensible. Policy Drift Review is the oversight cycle that measures that gap. Its defining trait, and what separates it from a project's own internal review, is distributed subjects observed through independent evidence: it does not trust the implementing units' self-reports of compliance, because the units causing the drift are exactly the ones reporting on it. Instead it samples actual field behavior — case files, outcomes, on-the-ground audits — on a recurring cadence, and when it finds implementation diverging from intent, it routes the gap upward to whoever owns the policy. It detects and escalates; it does not itself rewrite the program.
Example¶
A regional environmental agency has a policy: high-risk facilities are to be inspected in full annually, to a common standard. Two years on, a drift review pulls a sample of actual inspection records across twelve field offices rather than reading each office's compliance dashboard. The independent evidence tells a different story than the dashboards do. Under quota pressure to hit an inspection count, several offices have quietly redefined "inspection" downward — desk reviews and partial visits logged as full inspections — so the numbers look compliant while the intent (genuine on-site risk assessment) is being missed at the highest-risk sites. This is the divergence signal: field practice has moved away from policy intent, detected through evidence the field offices did not curate. The review does not tune the offices or rewrite the standard itself — that authority sits above it. It escalates: a documented finding to the policy owner showing where practice diverged, why (a count-based incentive crowding out the quality intent), and which sites are exposed, so the owner can change the incentive or the standard. What the review caught is a hidden target shift — success silently redefined to hide the divergence — precisely the failure self-reported metrics conceal.
How it works¶
- Sample field behavior, not self-reports. Draw independent evidence — case files, outcomes, direct audit — from the implementing units, deliberately bypassing the metrics those units control.
- Compare practice against intent. Read the gap between what the policy meant to achieve and what field practice is actually producing; the signal is movement away from intent, not mere procedural non-compliance.
- Run it on a cadence. Repeat on a schedule matched to how fast interpretation and incentive drift accumulate, so the gap is caught before it becomes entrenched norm.
- Escalate the finding. Route a documented divergence — with its likely cause — to the policy owner who holds authority to change incentives, standards, or the policy itself. The review's output is a routed finding, not a fix.
Tuning parameters¶
- Evidence independence — how far the review reaches past self-reported metrics toward direct field observation. More independence resists gaming but costs audit effort.
- Sampling breadth — how many units and cases are examined. Broad sampling catches localized drift but is expensive; narrow sampling is cheap but can miss a single rogue office.
- Review cadence — annual, quarterly, event-triggered. Frequent review catches drift early but burdens field units with oversight; infrequent lets divergence normalize.
- Escalation threshold — how large or systemic a gap must be before it is routed upward versus flagged locally. A low threshold surfaces problems early but can flood the policy owner; a high one filters noise but delays action.
When it helps, and when it misleads¶
Its strength is seeing what self-reported compliance hides: the slow, distributed reshaping of a policy by the discretion of the people who implement it — what scholars of street-level bureaucracy describe as front-line workers effectively becoming the policy through the choices they make.[n1] By insisting on independent evidence and a repeating cadence, it catches hidden target shift — success quietly redefined to mask divergence — that no internal dashboard will show.
Its failure mode is measuring the wrong gap. A review anchored on easy proxy metrics can flag procedural deviation that actually serves the intent (a smart local adaptation) while missing substantive drift that keeps the paperwork clean. Over-aggressive escalation, meanwhile, can punish exactly the legitimate front-line adaptation that good policy needs, teaching field units to hide judgment rather than exercise it. The guarding discipline is to anchor the review on outcomes and intent rather than proxy counts, and to distinguish adaptation that advances the intent from drift that abandons it before escalating.
How it implements the components¶
divergence_signal— the finding that field implementation has moved away from policy intent, with direction, scope, and affected units.monitoring_cadence— the recurring review schedule matched to how fast interpretive/incentive drift accumulates.escalation_path— the routing of a documented gap upward to the policy owner who holds correction authority.independent_signal_check— sampling actual field behavior rather than trusting the implementing units' own compliance reports.
It deliberately does not implement correction_rule or recovery_target — it detects and routes but does not itself reset the program. Fixing scope in place against a recorded intent is the job of its near-twin Project Drift Correction Review; the separating components are correction_rule and recovery_target, which that review owns and this one hands off.
Related¶
- Instantiates: Divergence Detection and Correction — divergence detection for distributed policy implementation.
- Sibling mechanisms: Project Drift Correction Review · Model Training Divergence Monitor · Runbook-Based Course Correction · Negotiation Derailment Repair Protocol · Process Control Alarm and Tuning · Loss-Limit Correction Rule · Learning Remediation Loop
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Policy Drift Review operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it audits how a policy is actually being implemented in the field against its stated intent, using independent evidence, and escalates the gap to the policy owner.
Independent corroboration: The frozen evidence defines Policy Drift Review as 'Audits how a policy is actually being implemented in the field against its stated intent, using independent evidence, and escalates the gap to the policy owner', 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: Comparing field implementation with stated policy intent is a classic implementation-evaluation and administrative-oversight practice.
Related originating lineages:
- Law & Governance — Law contributes fidelity to the authorized rule and mechanisms for escalating departures from it.
- Organizational & Management Science — Compliance and management-system auditing independently developed intent-versus-practice reviews for internal policy.
Review resolution: Both blind reviewers agree that public administration policy is the primary origin. Reconciliation resolves alternate origin disagreement, origin mode disagreement, encyclopedia synthesis disagreement. Formative alternate lineages are retained as law_governance, organizational_management; later breadth of use is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among origin lineages.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Street-level bureaucracy (Michael Lipsky) — the observation that front-line public workers, through the discretion they exercise under caseload and resource pressure, effectively make policy as much as the written rule does. It is why a policy drift review must observe field behavior directly rather than trusting compliance reports. ↩