The patient move is the single irreversible event in an inpatient-unit project: the hour the first occupied bed crosses the threshold, the new floor becomes a live care environment governed by every applicable life-safety, infection-control, and licensure requirement. This Article covers the planning and execution of the move event itself — the go/no-go decision, the sequencing of patients and beds, the day-of command structure, and the early stabilization period that turns an activated shell into a functioning unit.

It assumes the floor is already physically built out, commissioned, licensed, supplied, and staffed — that work belongs to the readiness and full-floor-activation Articles that precede this one. Here the question is narrower and harder: how do you move living patients from a place where care works to a place where care is unproven, without harming anyone and without losing the ability to fall back?

The move is a clinical event, not a logistics event

It is tempting to treat occupancy as the back half of a construction schedule — punch list closed, certificate of occupancy in hand, hand the keys to operations. That framing is the most common source of patient-move failure. From the moment a patient who depends on oxygen, telemetry, infusion, or simply call-bell response leaves a known-good environment, the move is a patient-care episode subject to the same standards as any other transfer of care.

Two consequences follow. First, clinical leadership — not the project or facilities team — owns the go/no-go authority and the patient-by-patient decisions. The construction and activation teams enable the move and own the building; nursing and medical leadership own the patients. Second, the controlling standards are clinical: the move must preserve continuity of monitoring, medication administration, and documentation, and it must not create an Emergency Medical Treatment and Labor Act (EMTALA) lapse for any patient who could deteriorate in transit. The accreditor — The Joint Commission (TJC) or DNV — will look at the move as a transition of care and expect a documented hand-off (a structured SBAR-style transfer) for every patient.

A useful test for any move decision: would this be acceptable as an ordinary intra-facility transfer on a normal Tuesday? If the answer is no, the move plan is wrong, not the standard.

Move types and what each one demands

The shape of the move drives almost every downstream decision. Three patterns dominate.

A single large project frequently combines all three: a new tower opens empty (net-new), legacy units relocate into it (occupied move), and the vacated legacy floors are renovated with patients decanted into the now-freed swing capacity (backfill). Each leg gets its own sequence, its own go/no-go, and its own rehearsal.

The pre-move readiness gate (go/no-go)

A patient move is authorized at a single, documented go/no-go meeting — typically held 24 to 72 hours before move day, with a final short confirmation the morning of. The gate is binary and owned by a named decision-maker (commonly the Chief Nursing Officer or a designated incident commander). It is not a status update; it is a decision to proceed, defer, or descope.

A defensible go/no-go checklist confirms, at minimum: