Operational readiness (OR) is the structured program that turns a physically complete inpatient nursing unit into a unit that can safely admit, treat, and discharge patients on day one. It runs in parallel with — and well ahead of — construction completion, translating the design intent of the unit (its care model, staffing plan, and supply logic) into trained people, working processes, stocked supplies, and validated equipment so that the building, the operations, and the clinical team go live as one coordinated system.
This article covers the planning and process side of bringing a med-surg or specialty inpatient unit into service: the operational readiness program structure, the care-model and staffing decisions that drive everything physical, the supply-par and logistics build, equipment and consumables provisioning, the policy/workflow scaffolding, and the validation and dry-run discipline that proves the unit is ready. The physical build-out and bulk move-in of rooms, the patient-move sequencing on go-live day, and the fall/infection-control/patient-safety program are each handled by neighboring articles in this Chapter; here the focus is the operational backbone those activities depend on.
Operational readiness is distinct from commissioning. Commissioning (Cx) verifies that building systems perform as designed — air balance, medical gas, nurse call, normal/emergency power, controls. Operational readiness verifies that the clinical enterprise can run in the commissioned building: that staff are hired and oriented, supplies are on the shelf, equipment is biomed-accepted and on the network, workflows are written and rehearsed, and the unit is licensed and accredited to operate. A unit can be 100% commissioned and 0% operationally ready.
A mature OR program is typically led by a dedicated activation or transition manager reporting into the owner's project executive, working alongside the design and construction team, the facility's clinical leadership, supply chain, biomedical engineering, IT/clinical informatics, environmental services, and infection prevention. The program is governed by an activation plan and master schedule that back-schedules every readiness milestone from the target first-patient-day, and it is tracked through gated reviews — commonly an Operational Readiness Review (ORR) at major thresholds (typically 90, 60, 30, 14, and 7 days out, then a final go/no-go).
Key principles that separate disciplined OR from ad-hoc move-in:
Before a single par level is set or a single piece of equipment is ordered, the unit's care model must be explicit. The care model is the operating logic of the unit — who cares for the patient, in what ratios, with what support, using what workflow — and it is the upstream driver of nearly every readiness and physical decision.
Core care-model decisions and their downstream effects:
| Care-model decision | What it drives |
|---|---|
| Nurse-to-patient ratio (e.g., 1:4–1:5 med-surg, 1:2 step-down/PCU, 1:1–1:2 ICU) | Staffing plan and FTE count; number of decentralized work areas; supply-station density |
| Acuity / acuity-adaptable model | Whether rooms must support escalation in place (gas outlets, monitoring, power) and therefore equipment and supply depth per room |
| Centralized vs. decentralized nursing | Location and number of supply alcoves, med rooms, charting stations; pneumatic-tube and supply-replenishment routing |
| Nursing-care delivery model (total patient care, team nursing, primary nursing) | Support-staff mix (PCT/CNA, unit clerk), workflow design, communication tooling |
| Patient population / specialty (general med-surg, ortho, oncology, telemetry, observation, behavioral) | Specialized equipment, isolation/AII counts, bariatric provisions, security and ligature considerations |
| Family-presence and care-partner model | In-room sleep/work zones, supply for visitors, food-service workflow |
| Documentation and technology model (EHR, barcode med administration, RTLS, virtual nursing/tele-sitting) | IT device counts, network and WiFi readiness, workstation locations, integration testing scope |
The care model is normally captured in a functional program (or operational narrative) authored during planning. Operational readiness treats that document as the contract: every readiness activity exists to make the as-built unit deliver the care model. A frequent and costly readiness failure is discovering that the staffing model assumed at design (say, fully decentralized 1:4 care) was never funded or recruited, leaving an as-built unit that the actual staffing model cannot operate efficiently.
People are the longest lead item in any activation. The readiness program must confirm not only that positions are filled but that staff are unit-ready on go-live day.
The staffing-readiness workstream typically covers: