Stratum-Specific Threshold Schedule¶
Document — instantiates Stratified Treatment
Lists different eligibility, review, escalation, inspection, or intervention thresholds for each stratum.
Stratum-Specific Threshold Schedule is the reference document that tabulates, stratum by stratum, the different cut-offs that govern eligibility, review, escalation, inspection, or intervention — and explicitly defines the grey zone around each cut-off so a small measurement difference cannot produce a large treatment cliff. Its defining feature is the pairing of a threshold table with a boundary band: it is not a live workflow that routes cases and not a monitor that watches outcomes; it is the authoritative artifact that says this stratum trips at this number, and within this margin of the number, do not snap — re-measure or blend. Making the numbers explicit is half the value; making the edges honest is the other half.
Example¶
A national food-safety authority inspects thousands of establishments with a fixed inspection budget. It stratifies premises by hazard profile: high (handling raw meat and ready-to-eat foods), medium, and low (sealed packaged goods only). The schedule sets the operative thresholds per stratum — high-hazard premises inspected twice a year, medium annually, low every three years — and states the score cut-offs that place a premises in each stratum. Crucially, it also defines a boundary band: a premises whose hazard score sits within, say, two points of a cut-off does not simply drop to the lighter cadence. Instead it gets a confirmatory re-inspection or a blended cadence until the reading settles, so a borderline kitchen cannot ride a hard line into a three-year gap.
The result is that inspector effort concentrates on genuinely high-hazard premises, borderline cases are not quietly gamed across a cliff, and every inspector consults one artifact rather than negotiating cut-offs case by case. The figures are illustrative; the mechanism is the table plus the honest edge.
How it works¶
- Tabulate the operative threshold per stratum. For each stratum, one authoritative cut-off for each governed action (eligibility, review, escalation, inspection, intervention).
- Draw a boundary band around each cut-off. Define the margin within which a case is "too close to call" and the rule that applies there — re-measure, blend the two treatments, or route to review.
- State the tie-break. Say which way an unresolved boundary case defaults, so the edge is deterministic and auditable.
- Version and date it. The schedule is a controlled document; cut-offs change, and the current one must be unambiguous.
Tuning parameters¶
- Cut-off placement — stricter cut-offs pull more cases into intensive treatment, raising cost and false positives; looser ones save effort but miss cases.
- Boundary-band width — a wide grey zone smooths cliffs and resists gaming but sends more cases to the costlier re-measure/blend path; a narrow band is cheap but sharp.
- Blend vs. re-measure at the edge — blending treatments is gentle but complex to administer; re-measuring is cleaner but delays a decision.
- Update cadence — frequently revised cut-offs track reality but destabilize expectations; static ones are predictable but decay.
When it helps, and when it misleads¶
Its strength is turning implicit, negotiable cut-offs into an explicit, auditable, cliff-aware artifact — everyone treats the boundary the same way, and the grey zone defuses the worst of the boundary harm the archetype warns about.
Its failure mode is the cliff itself: any hard threshold creates a notch effect, where a case just over the line is treated very differently from one just under it, which both harms borderline cases and invites gaming right at the boundary.[n1] A published, precise cut-off is especially gameable — actors optimize to land on the favorable side rather than to change the underlying condition. A stale schedule is the quieter failure, locking in cut-offs the world has moved past. The discipline that guards against these is the boundary band itself — never a bare line — plus periodic recalibration of where the cut-offs sit.
How it implements the components¶
resource_or_threshold_differentiation— it is the per-stratum cut-off table: the document where each stratum's eligibility, review, escalation, inspection, or intervention threshold is fixed.boundary_uncertainty_zone— it defines the grey band around each cut-off and the re-measure-or-blend rule that keeps a small measurement difference from becoming a large treatment difference.
It is a static reference, not an actor. It does not carry the assignment_rule that applies these thresholds to a live case — that is Risk Stratification Protocol or Segmented Customer Treatment Rules; it does not state the classification_basis for why the strata exist — that is Clinical Risk Banding; and it does not run the monitoring_feedback that watches whether the thresholds are working — that is Fairness Audit by Stratum.
Related¶
- Instantiates: Stratified Treatment — Stratum-Specific Threshold Schedule is the authoritative artifact that fixes each stratum's cut-offs and handles their boundaries.
- Sibling mechanisms: Case Management Tiers · Clinical Risk Banding · Fairness Audit by Stratum · Risk Stratification Protocol · Segmented Customer Treatment Rules · Tiered Service Catalog · Vulnerability-Based Support Workflow
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Stratum-Specific Threshold Schedule operates as a standing rule, threshold, contractual commitment, or policy constraint governing future conduct because it lists different eligibility, review, escalation, inspection, or intervention thresholds for each stratum.
Independent corroboration: The frozen evidence defines Stratum-Specific Threshold Schedule as 'Lists different eligibility, review, escalation, inspection, or intervention thresholds for each stratum', so its operative form is Rule, Policy & Commitment.
Nearest alternative: Representation, Specification & Plan — Stratum-Specific Threshold Schedule includes features of a static representation, map, specification, schema, or prospective plan that externalizes information, but its defining operation is a standing rule, threshold, contractual commitment, or policy constraint governing future conduct.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Public Administration & Policy
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Publishing different action thresholds for defined population, location, or exposure strata is regulatory risk-management practice joined to statistical calibration. EPA removal-management levels demonstrate differentiated thresholds by exposure scenario and receptor; statistics supplies estimation and uncertainty.
Related originating lineages:
- Data Science & Analytics — data_science contributes data science, analytics, and operational monitoring to this mechanism's defining operation—Lists different eligibility, review, escalation, inspection, or intervention thresholds for each stratum—without displacing the selected primary historical lineage.
- Environmental Science & Climate Studies — environmental_climate contributes environmental monitoring and sustainability science to this mechanism's defining operation—Lists different eligibility, review, escalation, inspection, or intervention thresholds for each stratum—without displacing the selected primary historical lineage.
- Law & Governance — Legal doctrine, regulatory governance, and procedural accountability supplies a parallel or contributing lineage for the mechanism's defining operation: lists different eligibility, review, escalation, inspection, or intervention thresholds for each stratum.
- Medicine & Healthcare — Triage thresholds vary by risk.
- Organizational & Management Science — Organizational design, management, and operational governance supplies a parallel or contributing lineage for the mechanism's defining operation: lists different eligibility, review, escalation, inspection, or intervention thresholds for each stratum.
- Statistics & Experimental Design — Statistics, experimental design, and measurement theory supplies a parallel or contributing lineage for the mechanism's defining operation: lists different eligibility, review, escalation, inspection, or intervention thresholds for each stratum.
Review resolution: The blind reviewers disagree on primary lineage (statistics_experimental_design versus public_administration_policy). Authoritative or primary research supports public_administration_policy as the best historical origin: Publishing different action thresholds for defined population, location, or exposure strata is regulatory risk-management practice joined to statistical calibration. EPA removal-management levels demonstrate differentiated thresholds by exposure scenario and receptor; statistics supplies estimation and uncertainty. The cited EPA, Regional Removal Management Levels: Frequently Asked Questions directly supports the mechanism's defining operation. All independently supported contributing domains are retained without an arbitrary cap. origin_mode=cross_disciplinary_synthesis records lineage, while domain_reach=multi_domain records later applicability separately from provenance.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
[n1] A notch (or cliff) effect occurs when crossing a threshold by a hair produces a large, discontinuous change in treatment — familiar from benefit "cliffs" in social policy, where earning one dollar more can cost far more in lost eligibility. Notches distort behavior at the boundary and are the specific harm a boundary-uncertainty band is designed to soften. ↩