Skip to content

Surge Roster

Pre-planned activation protocol — instantiates Slack Capacity Design

Pre-identifies the people, skills, and activation steps for a temporary capacity surge, so expansion under stress follows a rehearsed plan instead of frantic improvisation.

Surge Roster secures capacity that is dormant until triggered. Its defining trait is that the reserve exists not as standing free time but as a pre-arranged activation plan — a named list of who can be pulled in, with what skills, through what contact and authorization paths, mapped to the specific surge scenarios it must cover. The value it protects is speed-to-mobilize: when a rare, severe spike hits, the organization executes a rehearsed roster instead of improvising a scramble. This distinguishes it from a standing float of people kept free every day, and from a review that vets draws on an already-held reserve; the surge roster's whole job is to make summoned capacity arrive in hours, not days.

Example

An electric utility knows a major storm can knock out power to hundreds of thousands of customers, far beyond what its normal crews can restore quickly. Long before storm season, it builds a surge roster: which internal crews can be redeployed, which contractor crews are on call, which neighboring utilities will send help under mutual-aid agreements, the contact and staging paths to reach them, and the trigger thresholds that activate each tier (for example, a declared storm or outages past a set count). When the storm lands, the utility executes the roster rather than starting to dial — mobilization that would otherwise take days happens in hours because it was pre-arranged. (Utility mutual aid is a real, named practice.[1])

How it works

The distinguishing features are that the reserve is a pre-arranged plan rather than idle standing capacity, mapped explicitly to named surge scenarios it is designed to cover, and gated by defined triggers and authorization so activation is fast and unambiguous under stress. Its output is mobilization speed; its currency is rehearsal, not idle headroom.

Tuning parameters

  • Roster depth — how many tiers of surge capacity are pre-arranged (internal redeployment, then contractors, then mutual aid). More tiers cover bigger surges but cost more to maintain.
  • Trigger thresholds — how severe an event must be before each tier activates; too low burns goodwill and cost on minor events, too high mobilizes late.
  • Activation authority — who can pull the trigger, and how fast that decision can be made.
  • Scenario coverage — which surge scenarios are planned for; an unplanned scenario finds the roster improvising after all.

When it helps, and when it misleads

It helps for rare-but-severe surges where the constraint is how fast you can expand, not how much slack you hold day to day — disasters, incident spikes, seasonal peaks. Its characteristic failure is staleness: rosters silently rot as people leave and numbers change, so activation fails at the worst moment; the roster written once and never rehearsed or refreshed is worse than none, because it breeds false confidence. Over-activation for minor events is the mirror failure, burning cost and partners' goodwill. The discipline is to drill the roster and keep it current, treating it as a living plan. It sits close to a dormant Emergency Reserve — the emergency reserve is the dormant capacity; the surge roster is the plan that activates it.

How it implements the components

  • protected_capacity — the activation-ready surge capacity the roster secures, even while dormant, is the reserve it protects.
  • release_condition — the trigger thresholds and activation authority are the release condition that turns dormant capacity live.
  • surge_scenario — the roster is built against defined surge scenarios it must be able to cover.

It does not implement the standing-float utilization_ceiling and slack_type_catalog — those are Reserve Staffing — nor the replenishment_rule and slack_use_log review of routine draws, which is Slack Release Review.

  • Instantiates: Slack Capacity Design — Surge Roster is the pre-planned activation reserve within the broader slack system.
  • Sibling mechanisms: Reserve Staffing · Slack Release Review · Innovation Time · Maintenance Window · Buffer Resources · Capacity Pool · Learning Time · Schedule Slack · Unallocated Budget · Utilization Ceiling Dashboard · Emergency Reserve

References

[1] Mutual aid — pre-arranged reciprocal agreements (common among electric utilities and fire services) to lend crews during declared emergencies. The roster and activation protocol are what make the borrowed capacity available in hours rather than days. ↩