Recurring Inspection¶
Inspection routine — instantiates Cadence Design
Checks readiness, quality, or compliance on a repeating schedule whose frequency scales with risk, producing a verdict that catches problems before they compound.
A Recurring Inspection is a repeating check of condition, compliance, or readiness whose occurrences produce a verdict — pass, fail, conditional — and whose frequency is tuned to risk: sites and items that keep passing are inspected less often, while those that fail or trend badly are inspected more. Its defining move is that the cadence reads its own results. An inspection isn't merely scheduled; the schedule bends toward wherever the risk actually is. This is what separates it from a fixed calendar of care tasks — it exists not to do the upkeep but to judge whether the state is acceptable, and to let that judgment reset how often it looks.
Example¶
A city health department inspects roughly 3,000 food establishments. Under a flat annual schedule, a spotless bakery and a repeatedly-cited late-night grill got the same one visit a year — wasteful on the bakery, dangerously thin on the grill. The department moves to a risk-based recurring inspection. Every establishment is scored at each visit; the score drives the next interval. A restaurant that passes cleanly earns a longer leash — say the next check in twelve to eighteen months — while one cited for a critical violation drops to a re-inspection in weeks, with the verdict (and required corrections) recorded and posted.
The payoff appears at the grill. A critical temperature violation in March triggers a fail verdict, a mandated fix, and a re-inspection in three weeks instead of the following year. The problem is caught and closed while it is still one violation rather than an outbreak. The inspection didn't clean the walk-in or fix the cooler; it rendered a verdict and pulled the next look forward to where the risk had moved.
How it works¶
What distinguishes a recurring inspection from a generic recurring task is that each occurrence returns a graded result and that result feeds back into the interval:
- Every visit yields a verdict. Pass / conditional / fail against an explicit standard, with findings recorded — the occurrence is not complete until the state has been judged, not merely visited.
- The interval is risk-weighted. Clean history lengthens the gap; a failure or adverse trend shortens it. The cadence concentrates attention where the probability or cost of a problem is highest.
- Findings drive re-inspection. A fail spawns a corrective deadline and a follow-up check, so the loop closes on the specific defect rather than waiting for the next routine cycle.
The cadence's value is proportioned vigilance: it looks often where looking matters and rarely where it doesn't, and it never lets a bad result simply age into the next scheduled visit.
Tuning parameters¶
- Risk banding — how many frequency tiers exist and how far apart they sit. Coarse bands are simple but blunt; fine bands target attention precisely but demand more scoring discipline.
- Interval floor and ceiling — the shortest and longest gaps allowed. A long ceiling saves cost but can let a slow-degrading site drift; a short floor guarantees vigilance but at real expense.
- Verdict granularity — binary pass/fail versus a graded score. Grades enable fine risk-tuning but invite disputes at the boundaries.
- Announced vs. unannounced — whether the subject knows a visit is coming. Announced checks measure best-case readiness; surprise checks measure true steady state but cost goodwill.
- Escalation trigger — how many or how severe the findings before frequency jumps a band or authority is invoked. Sensitive triggers catch decline early; jumpy ones thrash the schedule.
When it helps, and when it misleads¶
Its strength is proportioning: risk-based inspection spends scarce inspector-time where the expected harm is greatest, and its verdicts create a paper trail that both drives correction and defends the process later.[n1]
Its failure modes are familiar to any inspectorate. It slides into a compliance checkbox — a visit logged as "done" while the actual look was cursory, so the verdict certifies nothing. It suffers gaming: an announced schedule lets a subject present a clean face on inspection day and revert the next. And a mis-tuned risk model can starve a slow failure, stretching the interval on something that was quietly degrading below the threshold that would have shortened it. The discipline that guards against these is to mix in unannounced visits, to audit that recorded verdicts reflect real observation rather than a signature, and to revisit the risk model against actual failure data so the frequency tracks reality rather than last year's assumptions.
How it implements the components¶
A Recurring Inspection owns the judge-and-re-aim corner of the archetype — the verdict and the risk-tuned rhythm:
recurrence_interval— a repeating check whose baseline gap is set by how fast risk accumulates for the item or site.expected_output— each occurrence must produce a verdict against a standard (pass / conditional / fail) with recorded findings; that graded result is the guard against an empty walk-through.adjustment_rule— the frequency itself is adjusted by results: clean history lengthens the interval, a failure or adverse trend shortens it and spawns a re-inspection.
It does not gate a participation_boundary of decision rights (→ Governance Meeting Cycle) or fix a calendar trigger_or_anchor the way Budget Cycle pins to the fiscal year. Its adjustment logic runs parallel to Training Cycle's, but on a different clock — inspection frequency tracks risk and findings, whereas a training cycle's tracks skill decay. Distinct again from Maintenance Schedule, an upkeep-timing mechanism from a neighboring archetype: that schedule fires care tasks before failure, while a recurring inspection renders a verdict on whether the state is acceptable and re-aims itself accordingly.
Related¶
- Instantiates: Cadence Design — the inspection supplies a risk-proportioned when whose verdicts keep neglect from compounding.
- Sibling mechanisms: Budget Cycle · Governance Meeting Cycle · Release Train · Standup Meeting · Status Digest · Training Cycle · Weekly Review · Maintenance Schedule
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Recurring Inspection operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it checks readiness, quality, or compliance on a repeating schedule whose frequency scales with risk, producing a verdict that catches problems before they compound.
Independent corroboration: The frozen evidence defines Recurring Inspection as 'Checks readiness, quality, or compliance on a repeating schedule whose frequency scales with risk, producing a verdict that catches problems before they compound', so its operative form is Assessment, Review & Assurance.
Nearest alternative: Monitoring, Sensing & Alerting — Recurring Inspection includes features of ongoing observation, sensing, or alerting that detects and surfaces state without itself executing the response, but its defining operation is a bounded evaluation of existing evidence or work that produces a finding or disposition.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Risk-scaled periodic inspection is foundational reliability, maintenance, and safety engineering.
Related originating lineages:
- Accounting & Auditing — Compliance and control testing independently developed recurring inspection schedules and verdicts.
Review resolution: Both blind reviewers agree that engineering_design is the primary origin. Explicit reconciliation of alternate origin disagreement adopts reviewer_a's classification because risk-scaled periodic inspection is foundational reliability, maintenance, and safety engineering. The resulting lineage records alternates=accounting_auditing, origin_mode=convergent, and domain_reach=multi_domain; these describe formative provenance separately from later applicability.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Risk-based inspection (RBI) is the established practice — in food safety, pressure-vessel and pipeline integrity, and financial audit alike — of setting inspection frequency in proportion to the likelihood and consequence of failure rather than on a flat interval. It is the formal justification for the adjustment rule at this mechanism's core: look more where a bad outcome is more probable or more costly. ↩