Bed Management & Capacity Center Runbook

Purpose and scope

This runbook gives capacity centers a reproducible, operational approach to coordinate beds, staffing, and transfers in real time. It focuses on brief, data-driven daily meetings, clear decision rules, fast escalation, and simple communication templates that units and families can use immediately.

Who should use this

Capacity center staff, bed managers, ED charge nurses, discharge coordinators, unit leaders, transport/logistics, and operations leaders responsible for throughput.

Core principles

• Keep meetings short, time-boxed, and decision-focused.
• Use the same concise data snapshot every time so trends are visible at a glance.
• Make transfer priority rules explicit and simple to apply.
• Escalate using pre-defined triggers and accountable contacts.
• Communicate proactively and transparently with unit teams and families.

Daily capacity meeting (stand-up) — agenda & roles

Frequency: Every 4–8 hours (at shift change and midday is typical). Duration: 10–15 minutes. Goal: reconcile the data snapshot, assign immediate actions, and clear bottlenecks for the next period.

Suggested attendees (core)

• Capacity Center Coordinator (facilitator)
• Bed Manager / Assignment Nurse
• ED Charge Nurse or Flow Nurse
• Discharge Coordinator / Case Manager
• ICU/Step-down nurse leader (rotating)
• Patient Transport / Logistics rep
• Housekeeping or Environmental Services rep (when cleaning delays matter)

Agenda (10–15 minutes)

1. Quick statement of the current hospital state (facilitator, 1 min)
2. Review the data snapshot (2–3 min)
3. Identify 3 highest-priority actions (3–4 min): admissions, discharges, transfers
4. Assign owners and expected completion times (2 min)
5. Escalations / barriers (2 min)
6. Confirm follow-up check or handover (1 min)

Data snapshot template (use same fields every meeting)

Present as a single-line summary or one small table so it fits on a dashboard or slide.

Optional additional fields: isolation bed needs, behavioral precautions, pending transport ETA, OR recovery holds.

Transfer priority rules (simple, actionable)

Use a small set of priorities so assignments are consistent and defensible.

• Priority 1 — Immediate: Patient in ED with critical needs (e.g., time-sensitive intervention required, clinical instability resolved but bed needed now). Action: assign within 15–30 minutes.
• Priority 2 — Urgent: ED patient clinically ready for transfer or inpatient patient needing escalation (e.g., step-up to ICU) with moderate risk. Action: assign within 60 minutes.
• Priority 3 — Routine: Scheduled admissions, transfers for capacity optimization, or non-urgent holds. Action: schedule within next available bed window.

Tiebreakers: clinical acuity, infection/isolation needs, specialty bed match, and expected length-of-stay consequences. When in doubt, escalate to the capacity coordinator.

Escalation ladder (triggers and contacts)

Define specific triggers so everyone knows when to escalate.

• Trigger A: ED boarders > 8 or ED median board time > 4 hours → Escalate to Operations Director (phone) and open bed surge protocol.
• Trigger B: No available ICU beds > 60 minutes for a Priority 1 transfer → Notify ICU medical director and on-call intensivist; consider temporary holding with intensivist oversight.
• Trigger C: Cleaning turnaround > 30 minutes causing bed unavailability → Notify EVS supervisor; request overtime or reallocate cleaning resources.
• Trigger D: Staffing shortfall flagged on snapshot → Contact staffing office and unit leader; consider holding non-urgent admissions.

List actual contact names, roles, and preferred contact methods near this ladder in local copies of the runbook.

Communication templates (short, modifiable)

Message to receiving unit (text/email/EMR note)

Subject: Incoming transfer — Patient [Last, First] — ETA [time]

Body: Bed assigned: [Unit/Room]. Expected arrival: [time]. Transfer reason: [brief]. Isolation: [yes/no]. Assigned transport ETA: [time]. Contact: Capacity Center [phone].

Message to sending team (ED / referring unit)

Patient [Last, First] assigned to [Unit/Room]. Transport scheduled at [time]. If clinically changed, please notify Capacity Center immediately.

Family-facing message

We are actively arranging a bed for [patient name]. We expect placement within approximately [estimated time]. We will update you if that estimate changes. Contact [family liaison/phone]. (Keep it brief, honest, and avoid clinical detail in automated messages.)

Meeting actions and short checklist

• Confirm bed assignments and who will move the patient.
• Agree on 1–3 blocking issues to resolve before the next check.
• Record owners and deadlines in the capacity log.
• If an escalation is triggered, ensure the next-level contact has been reached and documented.

Key performance indicators to track

• ED boarder count and median board time
• Time from bed assignment to transport arrival
• Cleaning turnaround time for discharge-to-ready bed
• Percent of scheduled admissions accommodated within target window
• Number of escalations per week and time to resolution

Common pitfalls and quick fixes

• Too many metrics: keep the snapshot short so decisions are simple.
• Undefined ownership: always name an owner and a deadline.
• Lack of timely transport: prioritize transport for imminent transfers and list transport ETA in the snapshot.
• Poor family communication: use brief templated updates to reduce calls to the unit and keep families informed.

Implementation checklist (first 30 days)

1. Create and standardize the data snapshot in your common dashboard or a one-page PDF.
2. Announce the daily meeting cadence and required attendees.
3. Populate escalation contact list and publish it in the runbook.
4. Run the meeting for one week in ‘observe and refine’ mode—capture suggestions, then lock the agenda and snapshot fields.
5. Train units on the communication templates and where to find the capacity center contact.

Tailoring and notes

Copy this runbook and replace contact names, thresholds, and local constraints with your site-specific values. Keep a short change log so future updates are traceable.