Active Case Cap¶
Caseload rule — instantiates Work-in-Progress Limiting
Caps how many cases a worker or team may actively own at once, so each assignment still means real attention rather than a name parked on a queue.
An Active Case Cap limits how many cases a worker or team may hold under active ownership at one time — in support queues, care coordination, legal review, investigations, benefits administration, and other case-based systems. Its distinctive concern is the meaning of an assignment: a case marked "assigned to Maria" is supposed to imply that Maria is actually working it, and once a caseworker is carrying forty of them that implication is false — the case is parked, not handled. The cap protects that implication by making a caseworker's active set scarce, and — because a routine renewal and a complex investigation are not the same load — it typically counts cases by class, weighting the heavy ones so the cap tracks real attention rather than a raw headcount.
Example¶
A child-protection agency assigns incoming reports to caseworkers. Without a cap, a busy intake week pushes some workers to twenty-five or thirty open cases; the newest ones get a cursory call and then wait, and the label "assigned" quietly stops meaning "being worked" — precisely where the cost of a neglected case is highest. The agency sets an active cap of roughly twelve, with high-risk cases counting double, in the spirit of the professional caseload standards that fields like child welfare and social work have long published.[n1] Now when a new report arrives and every worker is at cap, the supervisor cannot simply add it to a pile: a case must first be closed, transferred, or moved to a monitoring status to open a slot. The visible consequence is uncomfortable and deliberate — unassignable reports become a queue the agency must see and staff for, rather than an invisible overload buried inside individual workloads.
How it works¶
- "Active ownership" is defined first. The cap needs a clear line between a case being actively worked, one merely monitored or dormant, and one closed or transferred — otherwise the count is meaningless.
- The cap binds the owner's active set. Each worker (or small team) has a ceiling on cases in active status at once.
- Cases are counted by class, not by ones. Heavier or higher-risk case types consume more of the cap, so twelve simple cases and six complex ones can weigh the same.
- A new assignment requires a freed slot. At the cap, intake waits for a completion, transfer, or status change — which is what forces the closing conversation instead of silent accumulation.
Tuning parameters¶
- Cap value per class — the ceiling for each case type. Lower protects attention and clients but pushes more demand into a visible waiting queue; higher absorbs demand at the cost of the label's meaning.
- Class definitions and weights — how case types are bucketed and how much of the cap each consumes. The weighting is where sustainability is really encoded — and where it can be gamed or politicked.
- Per-worker vs. pooled cap — a ceiling on each individual versus a shared team allowance. Pooling flexes around uneven days; per-worker caps guard against individual overload.
- What counts as "active" — how aggressively cases move to monitoring or dormant status. Loose definitions let real load hide below the cap.
- Emergency intake — whether a genuinely urgent case may exceed the cap, and how that overflow is made visible rather than absorbed silently.
When it helps, and when it misleads¶
Its strength is keeping assignment honest: a capped caseload means taking on a case is a real commitment of attention, and it converts hidden individual overload into a queue the organization is forced to confront and resource. In fields where a neglected case has serious human cost, that visibility is the point.
Its failure modes turn on what happens at the cap. If cases do not close — because they are genuinely stuck — the cap simply freezes intake, so it depends on a working way to unblock or escalate stalled work. Workers under pressure game the boundary, tagging active cases as "monitoring" to duck the cap while the real work continues. Class weights can be set to manage optics rather than load. And the classic misuse is to raise the cap to make a backlog disappear — which does not add a minute of anyone's attention; it just re-inflates the number until "assigned" means nothing again. The discipline that guards against this is to anchor the cap to a real capacity basis, keep the waiting backlog visible, and treat a rising cap as a demand-for-staffing signal, not a solution.
How it implements the components¶
Active Case Cap fills the human-caseload slice of the archetype:
wip_limit— the per-owner ceiling on active cases is the cap.class_specific_wip_limit— its signature: cases are counted by class and weight, so the limit reflects the real load a complex case imposes rather than treating all cases as equal.active_work_boundary— it defines what "under active ownership" means, separating actively-worked cases from monitored, dormant, and closed ones so the count means something.
It does not justify the number against measured capacity (capacity_basis → Team Workload Cap and Throughput-Based Limit Review), decide what to do when a case blocks (completion_bias_rule, blocked_work_policy → Blocked Work Swarming), pull the next case in when a slot opens (admission_control_rule → Pull Replenishment Signal), or govern urgent over-cap intake (exception_and_override_policy → Project Portfolio Limit).
Related¶
- Instantiates: Work-in-Progress Limiting — it is the archetype applied to human caseloads, where the active set is owned cases.
- Sibling mechanisms: Team Workload Cap · Project Portfolio Limit · Concurrency Limit · Kanban WIP Limit · Blocked Work Swarming · Pull Replenishment Signal · Sprint Capacity Rule · Work Slot Token · Throughput-Based Limit Review
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: The mechanism caps how many cases a worker or team may actively own at once, so each assignment still means real attention rather than a name parked on a queue, so its operative form is a standing rule, policy, threshold, or commitment.
Independent corroboration: The frozen evidence defines Active Case Cap as 'Caps how many cases a worker or team may actively own at once, so each assignment still means real attention rather than a name parked on a queue', so its operative form is Rule, Policy & Commitment.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Work-in-process limits and workload management cap concurrent commitments so attention is not fragmented and unfinished cases do not silently accumulate.
Related originating lineages:
- Operations Research — Queueing theory explains why high utilization and excess work in process produce long waits, unstable flow, and hidden backlog.
- Public Administration & Policy — Case-management systems in social services, courts, and public programs developed caseload standards to preserve timeliness and service quality.
Review resolution: Both reviewers exactly agree that organizational work-in-progress control is primary and converges with operations research and public administration. The historical ambiguity does not change the shared classification.
Attribution caveat: Lean and agile management popularized explicit WIP caps, while public-service caseload limits arose independently under related capacity pressures.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The cap governs one owner's active set; it says nothing about the total demand landing on the team or which waiting case should be taken next. Left alone it can simply relocate an overload from inside a caseload to an invisible queue upstream — so it earns its keep only alongside a visible backlog and a team-level view of capacity.
[n1] Many case-based professions publish caseload standards — recommended ceilings on how many cases one worker can competently carry — with child welfare and social work among the longest-established examples. They are the real-world evidence that an active-ownership cap is about sustainable attention, not administrative tidiness. ↩