# Closed Loop Communication: Say It, Repeat It, Confirm It

- Author: Bomb Appétit (https://bombappetit.com)
- Published: 2026-10-20
- Category: Communication
- Canonical: https://bombappetit.com/blog/closed-loop-communication-say-repeat-confirm

> Closed loop communication sends a message, hears it repeated and confirms it before anyone acts. Where the idea comes from and how its three steps fit a bomb.
Closed loop communication is a three-part exchange: one person sends a message, the receiver says it back in their own words, and the sender confirms it is right before anyone acts. The loop is closed only when the sender has heard the receiver's version. Until then, nobody knows the message arrived intact.

## What is closed loop communication?

Closed loop communication means a message is not finished when it is spoken. It is finished when the speaker has heard the listener restate it and has said "correct." The point is to compare two versions of one message, the sent one and the received one, while there is still time to fix a difference.

An open loop is the ordinary way people talk. Someone gives an instruction, the other person says "okay," and both walk away assuming they agree. Most of the time they do. The trouble is that the times they do not look exactly the same from the outside, and the mismatch only shows up when the action goes wrong.

The closed version adds one sentence and one word. The listener's sentence exposes what they understood. The speaker's word, "correct" or a fix, settles it. That small cost buys certainty on the messages where a mistake would hurt.

In Bomb Appétit the idea has an obvious home. The Defuser can see and touch the bomb but not the manual. The Experts have the manual but never see the bomb. Every cut, press and turn travels through speech, and a wrong action is a strike. The manual's own first page tells Experts to have instructions repeated back before the Defuser acts, which is a closed loop by another name.

## The three steps of a closed loop: call, read back, confirm

The three steps are the call, where the sender gives one clear message; the read back, where the receiver restates it including every number and direction; and the confirm, where the sender says "correct" or corrects it. Only after the confirm does anyone act. Each step has its own job and its own typical failure.

**The call.** One message, one action, said in a fixed order. At the bomb that order is usually the module, then the position with its direction, then the action. "Wires: cut the third wire from the top." A call that bundles two actions ("cut the third and then hold the button") makes the read back twice as long and twice as likely to drop half.

**The read back.** The receiver repeats the message and, ideally, adds one fact the sender could not see. A Defuser might say "Third from the top, that's the white one. Cutting?" The added color gives the Expert a second thing to check against their own picture. If the Expert expected blue, the loop has caught a problem before the wire is gone.

**The confirm.** The sender listens to the read back and answers with one word for yes or with the fix. "Correct" or "Yes, cut" is enough. If the read back was wrong, the sender gives the corrected call, and the loop starts again from the read back.

A sample exchange, invented for illustration:

> **Expert:** Glyph Keypad. Press the circle with a dot first.
>
> **Defuser:** Circle with a dot, the top-left key. Pressing first?
>
> **Expert:** Correct.

The manual names each glyph as an outer shape with a mark inside, so a name like "circle with a dot" is one both sides can read. That shared vocabulary is what makes a fast read back possible.

## Where closed loop communication comes from

Closed loop communication shows up wherever a misheard message can hurt someone. Healthcare teams and air traffic control both use it in named, written forms. Both put the weight on the same thing: the receiver says the message back so the sender can catch a mistake.

In US healthcare, the Agency for Healthcare Research and Quality teaches it as part of its TeamSTEPPS teamwork program. Its page on the [AHRQ TeamSTEPPS check-back tool](https://www.ahrq.gov/teamstepps-program/curriculum/communication/tools/checkback.html) describes the check-back, also called a repeat-back, as a closed-loop communication strategy to verify and validate exchanged information. Its examples follow the three steps exactly: a nurse reads a telephone medication order back to the physician, and the physician closes the loop by saying "Correct."

Aviation uses the same shape with a narrower focus. The Federal Aviation Administration's [Aeronautical Information Manual section on clearance readback](https://www.faa.gov/air_traffic/publications/atpubs/aim_html/chap4_section_4.html) asks pilots to read back the parts of an instruction that contain altitude assignments, vectors or runway assignments. It describes reading back the numbers as a double check between pilots and controllers, and asks pilots to read them back in the same order they were given.

The two sources agree on the core and differ in emphasis. The healthcare tool stresses that the sender must confirm. The aviation manual stresses which parts of the message deserve the read back. Both ideas transfer to a table of friends with a bomb and a manual.

## Which messages need a closed loop and which do not?

Close the loop on any message that leads straight to an action or that carries a number, a position or a name the listener will act on later. Skip it for chatter, encouragement and status that changes nothing. Closing every loop wastes the clock; closing none of them wastes the bomb.

The aviation manual's focus on numbers is a useful filter. Counts, positions and orders are where hearing goes wrong, and they are also where the bomb punishes mistakes. Feelings and plans can stay open.

The ten messages below are invented examples from a round. Your own team's list will differ, but the reasons should look familiar.

| Example message                           | Loop?       | Why                                                                  |
| ----------------------------------------- | ----------- | -------------------------------------------------------------------- |
| "Cut the fourth wire from the top."       | Loop needed | Leads straight to an action that cannot be undone.                   |
| "Serial number is K, 7, 4, R, 2, 9."      | Loop needed | Many later rules read it; a wrong digit poisons several modules.     |
| "There are three batteries."              | Loop needed | A count that rules check, often more than once.                      |
| "Hold the button, don't tap it."          | Loop needed | Tap and hold lead to different outcomes on the Big Button.           |
| "Press blue, then green, then blue."      | Loop needed | Order matters and sequences are easy to scramble.                    |
| "We have one strike now."                 | Loop needed | Some pages, such as Color Echo, change their answer by strike count. |
| "Nice, that one's green."                 | No loop     | Status the Defuser can already see; nothing follows from it.         |
| "I'm on the Passcode page."               | No loop     | Tells the table who is busy; nobody acts on it.                      |
| "Take your time, we've got four minutes." | No loop     | Encouragement, not an instruction.                                   |
| "I think the next one is easier."         | No loop     | An opinion, not a fact to act on.                                    |

A rule of thumb: if the message could be wrong in a way that costs a strike, close it. If it could only be wrong in a way that costs a moment of confusion, let it go.

## How does closed loop communication work with three Experts?

With three Experts, closed loop communication works when the loop has exactly two ends: the Expert who owns the module and the Defuser. The other two Experts stay silent during that loop, even if they know the answer. A loop with three voices in it is not a loop, because nobody knows whose message was confirmed.

The aviation manual has a detail that fits here. It asks pilots to include their aircraft identification in every read back, because several aircraft may share one radio frequency. At a bomb with three Experts, the equivalent is naming the module, or the Expert, in the read back. "Keypad, for Jo: circle with a dot first?" tells the whole table which loop this is.

Splitting the manual makes this easier. When each Expert owns a few modules, the owner of each loop is obvious before anyone speaks. The manual itself suggests splitting pages between Experts so that two people never search for the same thing. The guide to [one voice at a time when several Experts know the answer](/blog/how-to-be-a-better-communicator-lessons-from-a-bomb#one-voice-at-a-time-when-several-experts-know-the-answer) covers how a group decides who speaks in that moment.

A second Expert can still help without breaking the loop. If they hear a read back that sounds wrong, they say "hold" and wait for the owner. One word stops the action. A whole competing instruction would only open a second loop on top of the first.

Experts should close loops with the Defuser in the other direction too. When the Defuser reads out edgework, the Expert who will use it says it back. That catches a misheard serial number before it ruins three rules at once.

## The open-loop mistake: confirming with yeah

"Yeah" is not a confirmation, because it carries no content. The sender cannot tell from "yeah" what the listener heard, so the loop stays open even though it sounds closed. The fix is to replace every "yeah" in the read back slot with the message itself.

The mistake shows up in both directions. A Defuser says "yeah, got it" instead of reading the instruction back. An Expert says "yeah" to a read back without actually listening to it, because they were already reading the next rule. Either way, two different versions of the message survive.

The second version is the sneakier one. A read back only helps if the sender compares it with what they meant. An Expert who hears "fourth from the bottom" and says "yeah" because they expected agreement has turned a good loop into an expensive one. The [listener's half of a bomb round](/blog/how-to-be-a-good-listener-in-communication) covers how to hear a read back properly instead of waiting for it to end.

The [miscommunication examples from a bomb, and what fixed them](/blog/miscommunication-examples-from-a-bomb) show what slips through an open loop: mirrored left and right, wires counted from the wrong end, one nickname stretched over two symbols. Each of those would have surfaced in an honest read back.

If your team wants to build the habit deliberately, [active listening games that make you repeat it back](/blog/active-listening-games-repeat-it-back) treat it as practice. Its section on [the repeat-it-back drill with a bomb](/blog/active-listening-games-repeat-it-back#the-repeat-it-back-drill-with-a-bomb) walks through a slow first round built around that one habit.

To try the loop yourself, open [the standard manual](/manual/1) on one device and a bomb on another, and play one round where nothing gets cut, pressed or turned until the word "correct" has been said.