Operational readiness is the structured program that converts a physically complete, commissioned ICU into a unit that can safely accept its first critically ill, ventilated patient — and the high-acuity staffing model is the workforce engine that must be hired, credentialed, trained, and drilled in parallel so that the building and the care team go live together rather than one waiting on the other.

Why operational readiness is a distinct workstream in critical care

Substantial completion, commissioning, and the certificate of occupancy confirm that the ICU is built and that its systems function. They do not confirm that the unit can operate — that nurses can find the code cart, that the ventilator fleet is biomedically tagged and networked, that the pharmacy can deliver high-alert infusions to the new pneumatic-tube station, or that a deteriorating patient can be moved to the OR on the intended path at 0300. Operational readiness (often termed Activation, Transition Planning, or Operational Readiness & Activation Planning, "ORAP") is the bridge between a commissioned shell and a functioning service line.

The ICU concentrates this risk more than almost any other inpatient environment because its patients are the least able to tolerate a gap. A medical-surgical floor can absorb a rough first day; an ICU receiving ventilator-dependent, vasopressor-dependent patients cannot. For this reason, operational readiness for critical care is treated as its own governed workstream with its own owner, schedule, budget, and gate criteria, running for roughly 9–18 months ahead of go-live for a new tower or unit and integrated with — but distinct from — construction commissioning and the clinical move planning that sibling articles address.

This article covers the program and the people: the readiness governance, the activation timeline, the high-acuity staffing model, and the competency and simulation regime. The mechanical proof that booms, monitors, gas, and power actually work is covered under equipment commissioning and validation; the choreography of physically relocating patients is covered under critical-patient move planning; ongoing infection, alarm, and patient-safety operations are covered under their own article. Stay oriented to those boundaries — the readiness program schedules and verifies those activities but does not duplicate their detail.

The operational readiness program structure

A defensible ICU readiness program is organized around a small number of governing artifacts and a clear command structure.

Governance. An Activation/Transition committee, chaired by clinical operations leadership (commonly the CNO or a critical-care service-line director) with the project's owner's representative, meets on a fixed cadence. It owns the master activation schedule and is the decision body for go/no-go gates. Below it sit functional workstream leads — nursing, respiratory therapy, pharmacy, biomedical/clinical engineering, supply chain/materials management, environmental services, IT/clinical informatics, facilities, and infection prevention — each maintaining a readiness task list rolled up into one integrated tracker.

The activation work breakdown. Readiness is typically decomposed into recognizable domains:

• People — recruitment, credentialing, orientation, competency, scheduling, and staffing-model design.
• Process — clinical workflows, policies and procedures, downtime procedures, and standard work specific to the new environment.
• Equipment & supplies — procurement, receipt, biomedical incoming inspection, par-level setting, and first-fill of clean/soiled, med rooms, and supply nooks.
• Technology — EHR build and unit configuration, physiologic monitoring and middleware, nurse call, RTLS, secondary alarm notification, and device integration.
• Facility & systems — confirmation that commissioned systems (medical gas, emergency power, HVAC pressurization) are accepted and that the AHJ, life-safety, and accreditation prerequisites are satisfied.
• Activation events — day-in-the-life simulations, mock codes, integrated systems tests, and the patient move itself.

The countdown structure. Mature programs run a milestone countdown (frequently expressed as "T-minus" weeks to first patient) with named gates — for example T-180 (staffing plan and recruitment approved), T-120 (equipment POs released), T-90 (EHR unit build complete, training begins), T-45 (unit substantially furnished and stocked), T-30 (day-in-the-life simulations), T-14 (final readiness assessment and go/no-go), and T-0 (first patient / move day). The exact intervals flex with project size; the discipline of a published, gated countdown does not.

Operational readiness assessment and the go/no-go gate

The readiness program culminates in a formal Operational Readiness Assessment (ORA) — a structured, evidence-based check that the unit can safely operate, typically conducted 2–4 weeks before go-live and re-confirmed in the final days. It is the clinical analogue to the construction punch list and is the input to the go/no-go decision.

A robust ORA verifies, at minimum:

• Regulatory and accreditation prerequisites — certificate of occupancy issued; AHJ sign-offs complete; life-safety (NFPA 101) and electrical (NFPA 99, NEC 517) acceptance documented; the change has been handled per the accrediting organization's process (TJC or DNV), including any required survey or notification for a new or relocated unit, and CMS Conditions of Participation obligations addressed.