It's 0230 and your patient delivered forty minutes ago. Her fundus keeps going boggy between massages, you've swapped the chux twice, and the QBL you just totaled crossed 900 mL. The provider is at the bedside with a hand on the fundus, and there are now six people in the room — you, the charge nurse, a second RN, a tech, the provider, and the baby nurse. The provider says, to no one in particular, "Let's get some methergine going, and somebody grab a second line." And for about eight seconds, nothing happens. Everyone heard it. No one owns it.
Those eight seconds are where closed-loop communication lives or dies. Every skill you bring to a hemorrhage — your assessment, your IV hands, your knowledge of the staged response — runs through one narrow channel: whether words spoken in that room actually turn into actions. Closed-loop communication is the tool that makes sure they do, and it's the one most of us saw once on a TeamSTEPPS slide and never practiced out loud.
Recognize: what the loop is, and the three places it breaks
The loop has three beats. The sender directs an order or a piece of information to a named person. The receiver repeats it back — drug, dose, route, or the specific task. The sender closes it with a plain "correct," or fixes it on the spot. AHRQ's TeamSTEPPS curriculum calls that middle step the check-back; the whole sequence is closed-loop communication. It costs about four seconds, which is less time than the silence that follows an unclaimed order.
In a labor room the loop breaks in three predictable places, and it helps to be able to name them while they're happening.
The order goes to the room instead of a person. "Somebody call anesthesia" is not an order; it's a hope. OB emergencies are always crowded — the baby brings its own team — and a crowded room is exactly where diffusion of responsibility thrives. Three people assume someone else is calling, and anesthesia finds out about your hemorrhage when the blood bank calls them first.
The receiver acknowledges instead of repeating. "Got it" and a nod feel like closure, but they confirm nothing. The repeat-back is the only moment the content of an order is spoken twice by two different people, which makes it the only moment a misheard drug or a wrong-by-a-decimal dose can surface before it reaches the patient. In a loud room, over a delivery table, through a mask, "got it" protects nobody.
Nobody closes the loop. The repeat-back happens and the sender — already focused on the next problem — never says "correct." Now the receiver is acting on an order that was never verified, and if the repeat-back contained an error, it just became the plan. The close is the sender's job, but you can pull it out of them: end your repeat-back with "confirm?" and wait for the word.
There's one more thing the repeat-back buys you that the slide decks undersell: it's your safety screen. The classic OB example is exactly the drug from the scenario above. Methylergonovine is generally avoided in patients with hypertension — so the nurse who repeats back "methergine 0.2 milligrams IM — her last pressure was 158 over 94, do you still want this one?" isn't slowing the emergency down. She's the reason the error dies in the air instead of in the chart. The loop isn't a courtesy ritual. It's the last filter between a verbal order and the patient.
Escalate: scripts that close the loop
Start with the unclaimed order, because you'll meet one this week. When an order is thrown to the room, close it yourself by claiming it out loud with the content attached: "I've got the methergine — methylergonovine 0.2 milligrams IM, her last pressure was 128 over 82, drawing it up now." In one sentence you converted a hope into an order, performed the read-back, and flagged the one contraindication that matters. If the provider meant something different, this is when you'll hear it.
When you're the one sending — to a tech, a student, a float nurse who doesn't know your unit — use a name first, then the task, then the detail they need to relay: "Sam, call anesthesia. Tell them postpartum hemorrhage, room 4, QBL 900 and climbing." And listen for Sam's loop: "Calling anesthesia — PPH, room 4." If you don't hear it, ask for it: "Say it back to me." That sentence feels blunt the first few times. It feels normal by the third emergency, and the people you work with will start doing it to each other.
The phone version matters just as much, because a verbal order taken over the phone at 0230 is the highest-risk order in the hospital: no face, no shared view of the patient, and a provider who was asleep ninety seconds ago. Here's the whole call, with the loop built in. Notice it opens like SBAR and ends like a read-back, because they're two halves of the same tool:
"Dr. Reyes, this is Maloree on labor and delivery, calling about Ana Flores in room 4. She delivered vaginally at 0152. Her fundus won't stay firm with massage, oxytocin is running, and QBL just crossed 900 mL. This is a hemorrhage and I need you at the bedside now. While you're on your way — are you ordering a second-line uterotonic?"
The provider gives the order. You write it, then read it from what you wrote — not from memory:
"Reading that back: methylergonovine, 0.2 milligrams, IM, one dose now. Her last blood pressure is 128 over 82 with no hypertensive history, so no contraindication on my end. Confirm?"
"Correct."
"Thank you. Giving it now — I'll have fresh vitals and an updated QBL when you walk in."
Three details in that script do the real work. You read back from what you wrote, because the transcription is where phone orders go wrong, not the hearing. You attached the safety screen — the blood pressure — to the read-back, so verifying the order and verifying its safety happened in the same breath. And you ended with what the provider will find on arrival, which tells them you're still assessing, not just medicating. If the provider brushes past your read-back with "yeah, yeah, just give it," hold the line gently: "I need to verify — methylergonovine, 0.2 milligrams, IM, once. Yes?" You're not being difficult. You're being the nurse whose chart will say the order was verified, because it was.
And if the call itself doesn't get you what the patient needs — the provider won't come, won't order, won't engage — the loop you close next is the chain of command, and that's its own skill.
Document: the chart should show the loop closed
Here's the documentation habit that separates a defensible emergency record from a vague one: chart the loop, not just the order. A verbal or telephone order entered per your facility's process should reflect that it was read back and verified — most systems have a read-back attestation built into the verbal-order workflow, and in a true emergency where you're charting after the fact, your late entry should say so in words. Then your narrative ties the order to the time, the verification, the action, and the response, in that sequence:
0234 — Telephone order received from Dr. Reyes: methylergonovine 0.2 mg IM x1. Order read back and verified. BP 128/82 prior to administration, no history of hypertension.
0236 — Methylergonovine 0.2 mg given IM, left thigh.
0245 — Fundus firm at umbilicus with massage. Cumulative QBL 940 mL. Dr. Reyes at bedside.
Read that back as a reviewer would, months later: the order has a source, a verification, a safety check, a timestamp for the action, and a measured response. Nothing in it is editorial, and nothing is missing. If you want the fuller pattern for charting the conversation itself — what you reported, what the provider said, what you did when the response fell short — that's covered in how to document a provider notification, and the two patterns stack together cleanly.
One more habit worth stealing from the units that run hemorrhages well: in the debrief, ask one communication question — "did every order in that room get claimed and repeated back?" Not to assign blame. Because the answer is usually "almost," and the almost is where your next near-miss is hiding.
Closed-loop communication is not a personality trait. Loud nurses don't do it naturally and quiet nurses aren't excluded from it — it's a script, which means it's learnable, and it works precisely because it doesn't depend on confidence. It gives the newest nurse in the room the same sentence structure as the most senior physician: name, content, repeat, confirm. Practice it on the boring stuff — routine med pulls, lunch relief handoffs — so it's already in your mouth when the room gets loud.
This is education, not medical advice — your facility's policy, provider orders, and clinical judgment always come first.