ER surge staffing with a level two on call list for high trauma days

Emergency departments can handle predictable variation. What breaks the plan is a true surge that arrives fast and stays intense for hours. Multi vehicle collisions, community events with alcohol related injuries, weather disasters, and local incidents can quickly push an ER past safe staffing ratios even if the baseline schedule was built well.

Many teams rely on a single on call list. That works when the surge is small and short. It fails when the first layer is already covering sick calls or boarding pressure. The solution is a level two on call list that is planned, contracted, and activated in a controlled way.

This post lays out how to build a level two on call system that is fair, fast, and measurable.

Clarify the operating goal and activation criteria

Level two on call is not a vague backup. It needs a clear purpose and clear triggers.

Define what level two exists to solve

Common goals

• Add surge capacity for high acuity arrivals
• Add coverage for extended boarding with increased nursing workload
• Add coverage for trauma activations and critical procedures
• Add respiratory, imaging, or tech support when throughput stalls
• Add security or patient sitter coverage when behavioral health volume spikes

Write the goal in terms of roles and hours, not general statements.

Example goal statements

• Add two ER RNs and one ED tech within sixty minutes for sustained ESI one and two volume above baseline
• Add one charge capable ER RN and one paramedic within ninety minutes when trauma activations exceed a defined threshold

Set objective triggers tied to real signals

Activation criteria should use signals your team can observe reliably in real time. Avoid criteria that depend on one person feeling overwhelmed.

Possible triggers

• Triage arrivals per hour above a threshold for a sustained period
• Number of ESI one and two arrivals within a set window
• Ambulance arrivals waiting offload beyond a set time
• Boarding count beyond a threshold combined with high acuity arrivals
• Trauma activations count within a set window
• Staff shortage beyond a threshold due to sick calls

Use a small set of triggers and test them against past surge days. You want to avoid activating too late, but also avoid frequent unnecessary activations that erode trust.

Define who can activate and who must be notified

Activation authority should be explicit.

Typical roles

• ED charge nurse
• ED nursing supervisor
• House supervisor
• Incident command leader during events

Notifications should include the staffing office, security, and any departments you routinely pull from such as float pool.

Design the level two pool so it is fast and sustainable

Level two on call is not a random list of names. It is a pool with defined eligibility, expectations, and compensation.

Choose the right roles for level two

Do not limit level two to the same roles as level one. Think about the tasks that bottleneck during a surge.

Roles that often help

• ER RN with triage and resuscitation competency
• Charge capable ER RN
• ED tech
• Paramedic
• Respiratory therapist
• Unit clerk or patient flow coordinator
• Sitter pool or behavioral health support staff if available
• Imaging support, depending on local model

Build role specific pools. One person can be eligible for multiple pools, but do not mix them operationally.

Set eligibility and competency requirements

Level two responders must be safe to deploy with minimal orientation.

Eligibility requirements can include

• Home unit or recent ER experience within a defined time window
• Core competencies validated and current
• Required certifications current
• Familiarity with the department layout and workflows
• Fit for night or weekend work if your surge risk peaks then

Keep eligibility objective and auditable. This prevents disputes and supports fairness.

Define response expectations clearly

People will not join a pool if the expectations are vague.

Define

• Response time expectation such as arrive within sixty or ninety minutes
• Shift length expectation such as four to eight hours
• Role assignment on arrival such as triage support, resuscitation support, fast track, or task nurse
• Cancellation terms such as pay if canceled within a certain window
• Limits on consecutive activations to protect rest

Be careful with response expectations across a large geography. If travel times vary, either adjust expectations by region or maintain multiple pools by location.

Set compensation and labor rules up front

Compensation needs to match the burden of being on call and being activated. Work closely with HR and labor relations. Keep it transparent.

Components often used

• On call standby pay for the level two period
• Activation pay, often time and a half or a premium rate
• Minimum hours paid when called in
• Transportation reimbursement if applicable
• Rest period protections after extended activation

Whatever you choose, codify it in policy and communicate it before go live.

Build the schedule mechanics that make the pool work

A pool exists on paper. It works only when the schedule mechanics are simple and reliable.

Choose a coverage pattern for level two periods

Match the pattern to your surge risk. Common patterns

• Weekend evenings and nights when local events peak
• Holiday periods
• High risk seasons such as winter storms in some regions
• Special event coverage planned in advance

Start small. Pick the highest value windows and expand if the data supports it.

Use equitable rotation and availability capture

A sustainable pool balances organizational needs and personal constraints. Use a rotation model with clear rules.

Options

• Fixed rotation, where each eligible person covers a predictable cadence
• Bid based model, where staff volunteer for level two slots
• Hybrid, where a base rotation is filled and remaining slots are volunteered

Whatever you choose, build guardrails

• Maximum level two slots per person per month
• Minimum rest between a worked shift and an on call period
• Rules for swapping slots, with manager approval where needed

Capture availability in a way that is easy to maintain. If staff must email changes, your pool will drift out of date.

Keep contact information and preferred channel current

Activation fails when contact data is wrong. Require a periodic confirmation.

At minimum track

• Primary phone
• Backup phone
• Text permission where legally required
• Preferred channel such as text or call
• Distance estimate or typical response time if relevant

Activation workflow that is fast and controlled

During a surge, people do not have time to debate. Activation should be a repeatable runbook.

Use a stepwise call tree

Do not blast the entire pool unless your surge is severe. Use a call tree or batch approach.

Suggested steps

• Confirm activation trigger with objective data
• Identify roles and headcount needed
• Activate level two for specific roles in a defined order
• Track accept, decline, no response
• Escalate to next group if acceptances are insufficient

Keep the message short and consistent.

What to include

• Required role
• Arrival time expectation
• Expected duration
• Where to report
• Who to contact on arrival
• Confirmation method such as reply yes or call back

Time box the response window

A surge gets worse while you wait. Set a response window for each batch.

Example approach

• Send to first batch and wait ten minutes
• If short, send to second batch
• If still short, activate additional options such as float pool or agency

Do not rely on endless calling. Use your staffing office as the coordinator.

Confirm assignment and stop calling once filled

When staffing is met, send a stop message so people do not self deploy. Confirm each accepted responder in the schedule system and notify the charge nurse with names and arrival estimates.

Plan for partial fulfillment

Sometimes you will not fill all requested roles. Decide what to do.

Options

• Activate alternative roles that can offload tasks
• Reassign internal resources such as charge nurse duties
• Open a short internal overtime shift in addition to on call
• Pull a designated cross trained unit resource for a limited time

Document these options in the runbook.

Integration with core staffing so you do not create burnout

The biggest risk of any surge program is pushing the same people into constant extra work. Level two should reduce burnout, not hide it.

Protect your baseline team

Your baseline schedule should still be built to the usual volume. Do not under schedule on the assumption that level two will cover. That turns level two into routine staffing, which defeats the purpose.

Limit repeated activations for the same person

Set rules that protect rest.

Examples

• No more than one level two activation in a rolling seven day window unless volunteered
• Mandatory rest period after a long activation before the next scheduled shift, consistent with policy
• Manager review when a person crosses a threshold

Track it. If the system does not track it, it will not happen reliably.

Offer cross training to expand the pool

If the pool is too small, you will burn it out. Build a cross training pipeline.

Focus on staff who already have relevant exposure

• ICU nurses who float to ER for specific roles
• Med surg nurses who can support task nursing under supervision
• Paramedics for specific ER support functions
• Float pool nurses with strong triage support potential

Tie training completion to eligibility for the level two pool.

Measure performance and adjust quickly

Level two is operational. Treat it like an operational product with metrics.

Core metrics

• Activation count per month by trigger type
• Time from activation to first arrival
• Fill rate by role
• Hours worked under level two activation
• Cancellation rate and cancellation lead time
• Repeat activation burden per person
• Impact on key ED outcomes such as left without being seen and door to provider time, where you can attribute

Staff experience metrics

Do not guess how it feels. Ask in a structured way.

• Perceived fairness of rotation
• Clarity of expectations
• Adequacy of compensation
• Impact on sleep and recovery
• Suggestions for trigger refinement

Post event review that improves the system

After a major surge, run a short debrief focused on operations. Keep it blameless and specific.

Topics

• Trigger accuracy
• Activation speed
• Staffing match to needs
• Role assignments on arrival
• Communication quality
• Any safety events

Update the runbook and the trigger thresholds based on what you learn.

Common failure modes and how to prevent them

Triggers that are too subjective

If activation depends on one person feeling it, it will be inconsistent. Anchor triggers in objective signals.

A pool that is too small or too narrow

If only a few highly skilled people are eligible, they will burn out. Expand capability and add support roles that offload tasks.

Confusing messages

During a surge, people skim. Standardize activation messages and keep them short.

No tracking of outcomes

Without metrics, the program becomes an extra burden with no proof of benefit. Track response time, fill rate, and burden distribution.

Implementation checklist for a level two on call program

• Define the goals in terms of roles, headcount, and response time
• Select a small set of objective activation triggers
• Create role specific pools with clear eligibility requirements
• Define expectations and compensation in policy
• Schedule level two coverage for high risk windows first
• Build a stepwise activation workflow with time boxed response windows
• Integrate safeguards to protect rest and avoid repeated burden
• Train and expand the pool to reduce dependency on a few people
• Track performance metrics and staff experience, then adjust triggers and coverage

A level two on call list is not a luxury. It is a way to convert unpredictable surges into a controlled staffing response. When it is built with clear triggers, fair rotation, and firm rest protections, it improves patient safety and reduces the chaos that burns out the team.