Case Management Tiers¶
Procedure — instantiates Stratified Treatment
Assigns cases to light, standard, intensive, or specialist management tracks according to need, risk, or complexity.
Case Management Tiers is the working procedure a service uses to sort an active caseload into a short ladder of management-intensity tracks — and, just as importantly, to re-sort it on a schedule as cases change. Its defining move is not the initial placement but the re-tiering: a case is never permanently a "tier 3" case, only a tier-3 case until the next review. That distinguishes it from a one-time intake screen. The whole point is to keep scarce hands-on attention pointed at the cases that currently need it, and to release cases whose situation has stabilized so the same staff can absorb newcomers without hiring.
Example¶
A county probation department supervises roughly 1,800 people with about thirty officers. Uniform monthly check-ins mean low-risk clients burn officer time they don't need while a few high-risk clients get far too little contact. The department stands up a tiering procedure. At intake, and again every six months, each case is scored on risk and need and placed on a ladder: administrative (mail-in reporting, no visits), standard (monthly office contact), intensive (weekly contact plus home visits), and specialist (co-managed with a mental-health or substance-treatment partner). A trigger event — a positive drug test, a new arrest, a lost job — bumps a case up before its scheduled review; sustained stability across two review cycles steps it down.
The outcome is a visible reallocation: officer hours drift toward the intensive and specialist tracks, dozens of quiet low-risk cases move to administrative and later close, and a client who relapses in month three is re-tiered upward within a review window rather than languishing under a stale "low-risk" label until his term ends. The re-tiering is what makes the ladder a live instrument instead of a filing scheme.
How it works¶
- Fix a short ladder. Three to five rungs, each a named management track, not a score. More rungs fragment the caseload; fewer recreate one-size-fits-all.
- Set a reassessment cadence. Every case is re-scored on a clock (say, every six months) regardless of whether anything visibly changed — this is what prevents label lock-in.
- Write movement rules. Trigger events bump a case up immediately; a dwell requirement (stable across N cycles) gates step-downs, so cases don't oscillate on noise.
- Allow reasoned override. An officer may place a case off-formula, but must record why, leaving an audit trail.
Tuning parameters¶
- Rung count — more tracks fit need more finely but multiply administrative overhead and boundary disputes; fewer are simpler but blunter.
- Reassessment cadence — frequent re-scoring catches change fast but adds workload and churn; slow cadence is cheap but lets labels go stale.
- Step-up sensitivity vs. step-down dwell — a hair-trigger for escalation and a long dwell for de-escalation errs toward safety at the cost of keeping cases over-supervised.
- Override latitude — wide discretion captures tacit judgment but erodes consistency; narrow discretion is uniform but brittle at edge cases.
When it helps, and when it misleads¶
Its strength is matching a limited pool of intensive management to the cases that currently justify it, while the scheduled review keeps the assignment honest over time — the ladder adapts as lives do. It rests on the same logic as the risk-need-responsivity principle: supervision intensity should track assessed risk and criminogenic need rather than being handed out uniformly.[n1]
Its failure mode is churn — if triggers are too twitchy and dwell times too short, cases thrash between tiers, wasting the very attention the procedure was meant to focus, and clients lose the continuity that makes management work. The mirror failure is label lock-in: skip the reassessment and an "intensive" case stays intensive long after it should have stepped down, quietly consuming capacity. The classic misuse is letting the tier harden into an identity — a case treated as a high-risk person rather than a case at high risk this cycle. The discipline that guards against both is to honor the reassessment clock as non-negotiable and to audit step-downs, since under caseload pressure the temptation is always to defer the review that would free up a slot.
How it implements the components¶
stratum_definition— specifies the management ladder itself: how many tracks, who belongs on each, and the evidence that places them there.treatment_policy— binds each track to a concrete management regime (contact cadence, home visits, partner co-management), so a rung means a different set of actions, not just a different number.reclassification_rule— its signature: the scheduled re-scoring plus trigger-based movement and step-down dwell rules that keep cases moving as their situation changes.
It does not name the underlying classification_basis — the indicator set that justifies the strata — which is supplied by a scoring method such as Clinical Risk Banding or by Vulnerability-Based Support Workflow; nor does it run the monitoring_feedback or check the outcome_equivalence_standard that would tell whether the tiers are working fairly across groups — that is Fairness Audit by Stratum.
Related¶
- Instantiates: Stratified Treatment — Case Management Tiers is the operational procedure that keeps a caseload sorted into governed treatment tracks over time.
- Sibling mechanisms: Clinical Risk Banding · Risk Stratification Protocol · Fairness Audit by Stratum · Segmented Customer Treatment Rules · Stratum-Specific Threshold Schedule · Tiered Service Catalog · Vulnerability-Based Support Workflow
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Assigns cases to light, standard, intensive, or specialist management tracks according to need, risk, or complexity, making its operative form a case-specific gate, selection, routing, prioritization, or disposition decision.
Independent corroboration: The frozen evidence defines Case Management Tiers as 'Assigns cases to light, standard, intensive, or specialist management tracks according to need, risk, or complexity', so its operative form is Decision, Gate & Allocation.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Criminology & Forensic Studies
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Corrections practice cohered risk–need–responsivity tiering, matching supervision intensity to assessed risk and changeable needs.
Related originating lineages:
- Medicine & Healthcare — Stepped-care and clinical triage similarly assign light, standard, intensive, or specialist pathways.
- Public Administration & Policy — Social-service administration generalizes tiered case management under finite staff capacity.
Review resolution: Criminology and corrections are primary because risk-needs classification linked assessed cases to differentiated supervision intensity and periodic reassessment. Public administration institutionalizes tiered caseload governance, while medicine developed a parallel acuity-stratification lineage, making the broader pattern convergent.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
- U.S. Department of Justice: Risk/Need Client Classification Guidelines
- Bureau of Justice Assistance: Structured Decision-Making in Community Supervision
Notes¶
The re-tiering clock is the feature people cut first under pressure and the one that most defines the mechanism. A caseload that is tiered once at intake and never re-scored is not this procedure; it is a static intake screen wearing a ladder's clothes.
[n1] The risk-need-responsivity (RNR) model in corrections holds that the intensity of supervision and services should be proportioned to a person's assessed risk and to their changeable, crime-linked needs. It is the standard rationale for tiering supervision rather than applying it uniformly, which is why it anchors this mechanism's logic. ↩