Relocating a live women's-and-newborn service into a new or renovated facility is the highest-acuity, highest-consequence move in any hospital activation, because every move event is a dual-patient event — a mother and her infant, or a critically ill neonate whose life depends on an uninterrupted chain of warmth, oxygen, and monitoring. This article addresses the move-day logistics unique to labor/delivery, postpartum, and the NICU: how to plan and sequence the transfer of mothers, well newborns, and intensive-care infants from a legacy environment into the activated building without lapses in safety, security, or physiologic stability.

Why perinatal moves are categorically different

General-population patient moves treat the patient as a single transportable unit. Perinatal moves break that assumption in three ways, and the move plan must explicitly account for each:

• Two patients per event. A mother-baby couplet is two distinct medical records, two armbands, two care plans, and — under the facility's infant-security regime — a bonded electronic pair that must not be separated or alarmed during transit. A move plan that schedules "the patient" undercounts the population by roughly half.
• A continuous life-support envelope for the NICU. A Level III or IV neonate cannot tolerate even brief interruptions in thermal regulation, oxygen/air/blends, mechanical ventilation, infusion, or continuous monitoring. The transport must reproduce the bedside microenvironment on wheels — a transport isolette/incubator with self-contained power, gas, and monitoring — for the entire route, including elevators and outdoor segments if the move crosses buildings.
• An active security perimeter. Infant-abduction prevention (RFID/wireless tagging, mother-infant matching, exit-control on stairwells and elevators) must remain operational on both the legacy and new sides during the changeover, and the move route itself becomes a temporary, staffed, monitored security corridor. The companion sibling Article on infant-security systems covers the permanent installation; here the concern is preserving that protection while patients are physically in motion.

These three properties drive nearly every decision below: census-reduction strategy, sequencing, transport-cart engineering, route hardening, and the go/no-go criteria.

Move strategy and census reduction

The single most effective risk-reduction lever is moving fewer patients. Activation planning for women's services almost always begins with a deliberate census ramp-down on the legacy unit in the days before the move:

• Diversion and elective-load management. In coordination with the medical staff, scheduled inductions and elective cesarean sections are sequenced to either deliver well before move day (so the couplet discharges from the legacy building) or after activation (so they deliver in the new building). The labor floor cannot be placed on full obstetric diversion the way a general unit can — active labor and emergent obstetric presentations must always have a receiving location — so the plan defines a precise cutover instant after which all new arrivals route to the new triage/L&D, while in-progress labors finish where they started.
• The "no patient in transit while delivering" rule. A patient in active second-stage labor is not moved. The plan must hold delivering patients in place and accept that a small number will deliver in the legacy building during the cutover window; staffing and a functioning delivery room are retained on the legacy side until the last such patient is delivered and stable.
• NICU census floor. Unlike the obstetric units, the NICU census cannot be electively emptied — its patients are there by clinical necessity. The strategy instead focuses on accelerating safe discharges and step-downs in the days prior, declining new transport-in admissions during the move window where another facility can receive them (EMTALA obligations honored — no inappropriate transfer or refusal of emergency care), and accepting that the most fragile infants will move last and most deliberately.

A realistic women's-and-newborn move therefore reduces, but never zeroes, the move-day population. The plan is sized to the expected residual census — a typical mid-size unit might move on the order of a handful of postpartum couplets and a single-digit-to-low-teens NICU census — with explicit surge contingency if labor volume spikes.

The dual command structure: clinical lead + move lead

Perinatal move day runs under a unified incident-command structure (commonly Hospital Incident Command System, HICS) but with a domain-specific pairing at the unit level. Each unit (L&D, postpartum, NICU) is staffed during the move by:

• A clinical charge lead who owns patient stability, the decision to move or hold each patient, and the receiving handoff.
• A move/logistics lead who owns sequence, transport assets, the route, elevators, and communications.

Neither moves a patient without the other's concurrence. A neonatologist or attending obstetrician is present and reachable for every NICU transport and for any move of a clinically unstable mother. A dedicated communications channel (radio or equivalent, not reliant on personal cell coverage in shielded stair/elevator cores) connects the legacy unit, the receiving unit, the elevator controllers, security, and command. Many programs run a dry-run / "patient-less" rehearsal of the full route and handoff days beforehand to surface dead zones, badge-access gaps, cart-clearance problems, and elevator timing.

Sequencing the move

Sequence is built around two competing priorities: move the most stable patients first to validate the route and the receiving environment, but reserve the freshest, fully-staffed receiving capacity for the most fragile patients. A common, defensible ordering: