Code Pink: Building an Infant Abduction Response Plan That Actually Works Under Pressure

By the MGM Solutions team — life-safety RTLS specialists since 2002.

Infant abduction from a hospital is rare. That is exactly what makes it dangerous to plan for.
Staff will execute a Code Pink once or twice in a career, under the worst emotional
conditions imaginable, using a procedure most of them last read during onboarding. Whatever the plan
says on paper is not what matters. What matters is what a night-shift nurse, a lone security officer,
and a front-desk volunteer will actually do in the first ninety seconds.

This article is about that ninety seconds: how to write a response plan that survives contact with
a real event, how to drill it so the drill finds problems instead of confirming comfort, and where
electronic infant security fits into the procedure — and where it does not.

If you are still evaluating the technology itself, our companion guide on
how to choose a hospital
baby tag system covers tags, receivers, and vendor selection. This article assumes you have or are
buying a system and need the human procedure around it.

Why Plans Fail: The Four Recurring Gaps

When we help facilities review an existing Code Pink procedure, the same four weaknesses turn up
regardless of hospital size.

The plan assumes someone will notice. Many procedures begin with “upon discovery
of a missing infant.” Discovery is the slowest step in the entire chain. If the first indication is a
parent asking where their baby went, minutes have already passed. A plan that starts at discovery is a
plan that starts late.

Nobody owns the exits. The announcement goes out, staff are told to monitor doors
— and no document says which person covers which door. In the moment, three people converge on
the main lobby and the stairwell by the loading dock is uncovered.

The description never arrives. Responders are asked to watch for someone carrying
an infant while the only physical description sits with the charge nurse on the unit. Anyone posted at
a door is looking for nothing in particular.

The plan stops at the building. Coverage is defined by the doors of the maternity
unit. Once someone is in a stairwell, a parking garage, or the courtyard between buildings, the
procedure has nothing to say.

The First Ninety Seconds, Written as a Sequence

A usable Code Pink plan reads as a sequence with named owners, not as a policy narrative. The
structure below is the one we see work in practice.

Two entries in that table deserve emphasis. The first row decides everything downstream: an
electronic tag that trips at the door removes the discovery delay entirely, which is the single
largest variable in the whole sequence. And the last row is where most plans quietly end —
which is why we build for campus coverage rather than door coverage.

Where the Technology Belongs in the Procedure

An infant security system should do three specific jobs inside a Code Pink, and it should be
written into the plan by those jobs rather than by product name.

• Detect at the boundary, not after the fact. A low-frequency field at the doorway
  detects the tag the instant it enters, independent of how often the tag transmits. That is the
  difference between an alert at the door and an alert after a room check.
• Act, not just announce. The detection event should hold the maglock, deny the
  elevator call, and pull the door camera automatically. We cover the mechanics of this in
  RTLS integration
  with access control, elevators, and CCTV.
• Keep locating after the boundary. If someone does get outside, the plan needs
  position data in the parking area and between buildings — not a dark map.

It should also be honest about what technology cannot do. A tag cannot tell you whether the person
carrying the infant is authorized. It cannot stop a staff-impersonation abduction that walks out
through an unmonitored construction corridor. It cannot replace the mother-infant identification
procedure, the banding protocol, or the practice of never handing an infant to anyone who has not been
identified. Those remain human controls, and drills are how you keep them sharp.

Drills That Find Problems Instead of Confirming Comfort

A drill announced a week in advance, run at 10 a.m. on a Tuesday with full staffing, tests almost
nothing. The gaps that matter appear under the conditions you have not tested.

1. Drill on off-shifts. Nights, weekends, and holidays are when staffing is thinnest
   and when the plan is most likely to be exercised for real.
2. Use an unannounced or minimally announced format at least annually, with
   leadership and local law enforcement aware but unit staff not pre-briefed. Coordinate carefully so no
   one believes an actual abduction is in progress.
3. Use a doll with a live tag. Test the actual detection path, not a verbal
   scenario. This is also how you discover that a receiver has drifted or a door interface was left
   disabled after a maintenance visit.
4. Vary the exit. Do not always use the main stairwell. Use the loading dock, the
   service elevator, the connector to the medical office building.
5. Time three things and write them down: alarm to first responder posted at the
   correct exit; alarm to physical description in responders’ hands; alarm to law enforcement
   notification.
6. Debrief within twenty-four hours, with the people who were actually on the
   floor, and assign every finding an owner and a date.

The measurable output of a drill program is not a completion checkbox. It is a shrinking set of
time intervals and a shrinking list of repeat findings. If your last three drills produced the same
finding, the drill is working and the follow-up is not.

Documentation, Survey Readiness, and Liability

Accreditation and regulatory reviewers do not ask whether you own an infant security system. They
ask how you identified the risk, what you did about it, whether staff were trained, and whether you
tested it. Keep a durable record of the risk assessment, the written plan with named roles, training
completion, every drill with its timings and findings, and the corrective actions closed out.

The same record is what protects the organization afterward. A timestamped log showing the alarm
fired, the door held, the camera was bookmarked, and staff were posted within a defined interval is a
fundamentally different position than a narrative reconstruction written days later. We discuss that
dynamic in how hospitals
reduce liability and lawsuits with RTLS, and the broader survey angle in
RTLS and
Joint Commission compliance.

One Infrastructure, Whole Campus

SecurTRAK delivers infant security, patient elopement prevention, wireless staff duress,
and asset tracking on a single infrastructure — indoors and outdoors. The same tags and
receivers that protect the maternity unit protect the behavioral health unit, the staff walking to
their cars, and the ground between buildings. One map, one alerting pipeline, one vendor to call.

For a Code Pink specifically, that matters at exactly the moment plans usually go quiet: after the
exit. See why
indoor-only systems leave patients at risk for the full argument.

Frequently Asked Questions

Related reading:
How to Choose a Hospital
Baby Tag System  • 
How to Prevent Patient
Elopement in Hospitals  • 
RTLS for Hospital Security Leaders