Periodic Review And Reset¶
Use recurring review points to detect drift, clear accumulated errors, and reset the system before degradation compounds.
The Diagnostic Story¶
Symptom: Small deviations accumulate invisibly between check-ins until the gap between actual and intended state is too large and expensive to ignore. Surprises keep occurring at the same interval, which tells you correction is only happening after the damage is done. Reviewing without the authority or mechanism to reset means the exercise produces observations but no change.
Pivot: Create a recurring point where current state is explicitly compared to intended state, drift is distinguished from normal variation, and a reset action is authorized when the gap exceeds the threshold — not after failure forces it.
Resolution: Compounding degradation is interrupted before it becomes a crisis. Detection happens early enough that correction costs remain proportionate. Each review cycle informs the next by tuning what counts as drift, raising the quality of the baseline, and calibrating how often the review needs to run.
Reach for this when you hear…¶
[software platform] “We keep doing post-mortems after outages but never a proactive health check — we only find the drift after it bites us.”
[clinical protocol] “The guideline was good when we adopted it and has never been looked at since — we need a scheduled review or it will keep drifting from the evidence without anyone noticing.”
[financial controls] “Monthly reconciliation is supposed to catch this, but reconciliation without the power to correct is just documentation of the problem.”
When This Archetype Applies¶
Partial catalog groundingSome structural conditions are represented by existing abstractions, but no sufficient condition set is fully represented.
Diagnostic problem
A system gradually drifts from intended state, but continuous monitoring or correction is impractical, so accumulated error remains invisible or normalized until it becomes expensive failure.
What this problem means
The structural problem is compounding drift under intermittent attention. The system gradually moves away from its intended state, but the movement is too slow, distributed, or quiet to trigger immediate correction. By the time the drift becomes visible, correction is more expensive: an account no longer reconciles, a policy no longer fits practice, a model threshold no longer predicts well, a team norm has eroded, or equipment has deteriorated beyond routine adjustment.
This problem often hides inside normal operation. Each small exception seems reasonable. Each stale record is manageable. Each skipped check is defensible. The danger comes from accumulation: the end of one operating interval becomes the starting condition for the next, so uncorrected drift compounds.
Show the applicability expression
Applicability expression2 distinct conditions
groundedpartly groundedopen
2 conditions, all required.
2Required in every casenumbered 1–2
These hold no matter which pattern applies.
Accumulating inter-review drift · grounded
Small losses or deviations accumulate gradually between interventions.
The source archetype describes the situation as follows: Small deviations accumulate between interventions. The normalized requirement above isolates the load-bearing portion used in this condition set.
Excessive continuous correction · open
Continuous correction is impractical or excessive.
Use this archetype when a system needs recurring correction but does not justify or tolerate continuous control. The narrower requirement in this condition set is: Continuous correction is impractical or excessive.
Other requirements and context (3)
Why these sit outside the expression
Solution feasibility — it describes whether the intervention can work, not whether the diagnostic problem exists.
Application gate — it governs whether applying the archetype is appropriate or material, rather than defining the structural problem itself.
Solution feasibilityThe intended state is known enough to compare against.
The system gradually moves away from its intended state, but the movement is too slow, distributed, or quiet to trigger immediate correction. In this archetype, the relevant feasibility condition is: The intended state is known enough to compare against. It identifies something that must be possible or available for the intervention to be workable.
Solution feasibilityThe system can be reset without rebuilding from scratch.
Application gateReview has enough authority to change the system.
Coverage
1 of 2 conditions grounded · 1 open.
Mechanisms / Implementations¶
- Audit Cycle: Independent, scoped examination of a system against an external standard on a fixed cycle, producing evidence-backed findings and tracked remediation owners rather than fixing anything itself.
- Calibration Check: Compares an instrument's reading against a traceable reference standard at intervals set by its drift rate, and adjusts it back into alignment when the error exceeds tolerance.
- Data Quality Recertification: Requires the named owner of each data asset, definition, or access grant to re-affirm on a cycle that it still meets standard; anything left un-attested is revoked or quarantined by default.
- Financial Reconciliation: Matches two independent records of the same money against each other on a cycle, itemizes every discrepancy, and clears each one until the two balances agree and are documented.
- Health Checkup: Screens a whole living system's vital signs against age- and role-appropriate norms on a recurring schedule to catch developing problems early, referring anything abnormal to deeper diagnosis.
- Policy Review: 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.
- Preventive Maintenance Check: Services equipment on a usage- or time-based schedule set to intercept wear before failure — inspecting wear indicators and replacing or restoring worn parts on the spot.
- Quarterly Business Review: A recurring executive review of performance against targets across a portfolio, where an accountable owner explains variance, decisions reallocate resources, and off-track bets are escalated.
- Retrospective: A team periodically reflects on its own way of working, surfaces process drift from lived experience, and resets its working agreements — with learning, not blame, as the point.
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (3)
- Feedback: Outputs influence inputs.
- Homeostasis: Maintain internal stability.
- Periodicity: Regular cycles.
Also references 7 related abstractions
- Accountability: Responsibility for actions.
- Adaptation: Systems adjust to conditions.
- Continuity: Smooth change without jumps.
- Entropy (Thermodynamic Sense): Degree of disorder.
- Half-Life: Time to halve quantity.
- Observability: Infer internal state externally.
- Resilience: Absorb shocks and adapt.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Calibration Review and Reset · domain variant · recognized
A periodic reset focused on restoring measurement, model, threshold, or instrument alignment against a reference state.
Audit and Reconciliation Cycle · governance variant · recognized
A periodic review that compares records, obligations, or states, resolves discrepancies, and restores agreement before errors compound.
Retrospective Reset Cycle · implementation variant · recognized
A recurring reflection point that reviews recent work, identifies process drift, and resets team agreements, norms, or operating rules.
Policy Sunset Review · governance variant · candidate
A periodic or expiry-triggered review that forces stale rules, permissions, or commitments to be renewed, revised, or retired.
Editorial Notes¶
Problem Classification¶
Classification: Accumulation, Depletion & Degradation → Gradual Drift, Disorder & State Decay
Problem kernel: periodic correction is absent while error normalizes
Rationale: Earliest causal condition: A system gradually drifts from intended state, but continuous monitoring or correction is impractical, so accumulated error remains invisible or normalized until it becomes expensive failure.
Independent corroboration: The earliest necessary condition in the frozen evidence is: A system gradually drifts from intended state, but continuous monitoring or correction is impractical, so accumulated error remains invisible or normalized until it becomes expensive failure. That is a gradual drift disorder and state decay problem because Small perturbations, disorder, stale thresholds, or uncorrected deviations gradually move a system away from a useful state even though no single event appears sufficient to explain it.
Review outcome: Independent reviewer agreement; high confidence.