SNF Evacuation Tracking: Reconcile Every Resident, Staff Member and Receiving Location

Track movement as events

42 CFR 483.73(b)(2)–(5) requires tracking on-duty staff and residents in the facility's care during and after an emergency, including the specific receiving name and location when they relocate. Evacuation planning also considers care needs, staff responsibilities, transportation and communications, while preserving confidential and available medical documentation.

The operational record needs at least four different facts: intended destination, departure, confirmed arrival and subsequent movement. Overwriting “Facility A” with “Facility B” may leave the current location correct while destroying the explanation of what happened. Keep event time, entered time, source and confirming party where the workflow supports them.

Reconcile the starting population

Capture a dated roster when the evacuation workflow is activated, then reconcile admissions, hospital transfers, leave and other movements already in progress. A bed census alone may not represent everyone still within the facility's accountability process. Qualified staff determine the care and transport requirements; the manifest records their decisions without inventing a transport category from diagnosis labels.

Assign a stable resident identifier and a distinct movement identifier. An individual's second transfer should not look like a duplicate first departure. Keep the resident-location view separate from the on-duty staff view, with staff escorts linked to the movement where appropriate.

A resolved 24-resident exercise

This fictional exercise begins with 24 residents in the activated roster. Clinical and emergency leaders have approved all destinations and transport arrangements for the scenario.

At the first reconciliation, 20 residents have confirmed arrivals, two are in transit and two remain onsite. Those states total 24. The destination summary, however, says 12 arrived at Harbor and nine at Valley: 21 arrivals. The discrepancy is not closed by choosing the larger number.

The event review finds that one resident first assigned to Harbor was redirected to Valley. The Harbor plan was counted as an arrival even though no receiving confirmation existed. The team corrects the status history: Harbor remains the superseded intended destination, Valley is the confirmed actual destination, and the resident contributes only once to current location totals.

A second issue concerns a vehicle carrying two residents. Dispatch confirms departure for both, but the receiving acknowledgment names only one. The other remains “arrival unconfirmed” until the receiving team verifies identity and location. A vehicle-level receipt does not close every resident record automatically.

At the final exercise checkpoint, all 24 residents have a verified current location, and all on-duty staff are reconciled to onsite, escort, receiving-site or relieved status. The retained history explains the redirection and the delayed confirmation instead of hiding them behind a final “complete” label.

Send a usable care-information packet

Tie the record packet to the actual resident and departure context. Preserve the approved current clinical information needed by the receiver and evidence of how it was made available. If an updated order or other material information arrives after departure, use the clinical handoff process to communicate the change rather than assuming the original packet remains sufficient.

The location manifest should not become an unrestricted copy of the medical record. Define role-specific views and approved offline handling. Test readable exports and the reconciliation process when ordinary connectivity is unavailable; a live dashboard alone is an inadequate emergency dependency.

Carry tracking through return and reconciliation

The workflow continues after the last vehicle leaves. Record relocations from one receiving site to another, staff handovers, resident updates and eventual return or other disposition. Reconcile temporary paper records with electronic history using identifiable events, not a blanket import that duplicates departures.

The buyer's completed test is the 24-person reconciliation with evidence for every current location, a separate accounted-for staff roster and a recoverable event history. The platform must help staff find an unresolved arrival quickly and retain the facts needed for continuity. A polished route map is useful only after that accountability is established.