Business
Closed-loop communication: how to check shared understanding

Stefan Weiss
Closed-loop communication means sending a message, asking the receiver to repeat their understanding, and confirming or correcting that response. The exchange ends with both people clear about what was meant. A nod, a read receipt or “OK” usually tells you less.
For a work request, the practical pattern is: make the request specific, hear it back, then confirm the details. If the response exposes a different deadline, owner or deliverable, correct it before anyone proceeds.
The American Hospital Association’s TeamSTEPPS teaching material describes this sequence for healthcare teams. The workplace examples below adapt the communication pattern to ordinary project work. They are fictional teaching examples, not clinical instructions or evidence of a measured productivity gain.
There is one distinction to keep throughout: confirming a request does not establish that the work has been completed. You can close the communication loop today while the agreed task remains due next week.
What the loop checks
Consider this request: “Can you send the pilot update before Friday?”
It sounds clear until you ask what each person heard. One may mean a draft for internal review on Thursday afternoon. Another may mean a final message to customers by Friday evening. Both can say “yes” while planning different work.
A check-back makes that difference visible. The receiver explains the request in their own words; the sender checks that explanation against their intention. The point is to expose important ambiguity while correction is still straightforward.
A useful exchange checks the recipient, the action, the expected output, the timing and any boundary that would materially change the work. It does not require repeating every word. A short request may need only a short response. A complicated handoff may need separate checks for several decisions.
Before you start: identify what matters
Use the pattern deliberately when a misunderstanding could change someone’s next action. Examples include handing over a customer issue, asking for an approval, moving a deadline, delegating an unfamiliar task or coordinating work across time zones.
Choose the detail that is easiest to misinterpret. “Friday” may need a date, a local time and a time zone. “Send the report” may need a version and a recipient. “Review” may mean checking accuracy, giving a recommendation or granting approval. If you cannot name the important distinction, improve the request before asking somebody to repeat it.
You also need the right person in the exchange. A message to a group does not establish that any particular individual has accepted responsibility. Direct the request to an owner, or explicitly ask who can take it. Do not interpret silence from everyone else as agreement.
Step 1: send a specific request
State the action and the output, then add the relevant timing and boundary. Keep the message short enough to check.
For example: “Maya, please send me the draft pilot update by 15:00 Amsterdam time on Thursday 12 November. Include the three open customer issues. I’ll approve it before it goes outside the team.”
This request distinguishes drafting from sending, identifies the reviewer and defines the deadline. It also makes the boundary explicit: the recipient is not being asked to contact customers yet.
If several actions have different owners, separate them. “Everyone sort out the launch preparation” is difficult to repeat meaningfully. “Maya drafts the update; Leo checks the issue list; I approve the external version” gives each person something concrete to confirm.
Avoid making an instruction more confident than the decision behind it. If the date is only proposed, say so. “Could you confirm whether Thursday is feasible?” asks for a commitment discussion. “Thursday is agreed” reports a decision that must already exist.
Step 2: ask for a check-back
Invite the receiver to explain what they will do. Use ordinary language: “Could you run through what you’re taking away?” or “Just so we catch anything I’ve explained badly, what will you send and when?”
The receiver might reply: “I’ll draft the update with the three open issues and send it to you by Thursday at 15:00 Amsterdam time. You’ll approve it before anyone sends it to customers.”
That response gives the sender something to verify. “Understood” does not reveal the same information. Neither does a reaction on the message, even if it is a useful acknowledgement that the request was seen.
The tone matters. Frame the check as a shared accuracy check rather than a test of the other person’s memory. If the response differs, the exchange has done useful work. Make it easy to say “I thought you meant something else” or “I cannot meet that date”.
Step 3: confirm or correct the response
The sender now verifies the receiver’s understanding. “Yes, that’s the draft I need, and the deadline is correct” closes this exchange clearly.
If the response contains an error, name the correction and check the revised understanding. Suppose the receiver says they will send the update directly to customers. The sender can reply: “One correction: send the draft to me first. Please hold the customer email until I approve it.” The receiver then confirms the changed boundary.
Do not skip this final step because the check-back sounded mostly right. A nearly correct answer can hide the detail that matters most. In the AHA teaching sequence, the sender’s verification is a distinct part of closing the loop.
If the receiver cannot accept the request, resolve that explicitly. “I can draft it by Friday, or send an outline on Thursday” is a proposed alternative. It becomes the agreed plan only after the sender accepts it. Record the revised plan rather than keeping the original deadline in the notes.
Three workplace examples
A customer handoff with an unclear owner
A weak exchange is: “Can someone call the customer about the revised dates?” followed by several nods.
A stronger exchange is: “Leo, can you call the customer after we approve the revised dates?” Leo replies: “I’ll call after your approval, explain the new dates and send you a short recap.” The sender confirms: “Yes. Please wait for my approval message first.”
The check identifies the owner and the dependency. It does not show that the call has happened. The task remains pending until there is evidence of the call and its outcome.
A deadline across countries
A weak exchange is: “Please have it ready by end of day Friday.” The team works in Toronto and Amsterdam.
A stronger exchange is: “Please send the draft by 16:00 Toronto time on Friday 13 November.” The receiver repeats the date and time zone, and the sender confirms them. If the team needs a local-time conversion, verify that separately rather than relying on an assumption about the time difference.
The important part is not the particular hour. It is that both people are using the same deadline, including which date the deadline belongs to.
A request that cannot be completed as stated
A weak exchange is: “Please approve the budget today.” The recipient says “OK” despite lacking the supporting figures.
A stronger reply is: “I can review the assumptions today, but I cannot approve the budget until finance confirms the figures. Is an assumptions review what you need first?” The sender accepts or changes that proposal.
This prevents an acknowledgement from turning into a false approval. A closed loop can end with a clear limitation or a revised request. It does not require pretending that the original request is feasible.

Keep understanding, commitment and completion separate
Use three questions when writing the follow-up: what did the person understand, what did they agree to do, and what evidence shows it is done?
“I understand that you want a draft on Thursday” establishes understanding. “I will send the draft on Thursday” adds a commitment. “Here is the draft I sent” provides evidence of a delivered output. Even then, the reviewer may still need to check whether the output meets the request.
These states can appear in one conversation, but they should not be collapsed into one status. A meeting summary that turns every clear request into “completed” will mislead the next person who reads it.
For project work, keep the resulting action somewhere the team actually reviews. The communication check creates shared understanding; the team’s follow-up process handles progress, exceptions and completion. If the plan changes later, close a new exchange around that change instead of assuming the original confirmation covers it.
Review a recorded exchange without inventing agreement
With permission to record and review the conversation, you can revisit the exact request and response. In Weeve’s chat with saved recordings, use a tightly scoped question such as: “Find the pilot-update request and the response. Separate the requested deadline, the accepted deadline and anything that remains unclear. Cite the passages.”
Read the cited source material before using the answer. Check who spoke, whether a reply refers to the same request and whether the sender actually confirmed it. If retained audio is available for that passage, listen when wording or timing is unclear. A generated summary is a draft interpretation of the recording, not a new agreement between the people involved.
The product source reader shown here uses approved synthetic demonstration content. It illustrates where to inspect evidence; it does not show a tested closed-loop exchange or prove that the pilot work was completed.

Turn an incomplete exchange into a useful follow-up
If the recording contains a request and a vague reply, send a clarification rather than rewriting the history. For example: “My notes say the update is due Thursday, but I don’t have a clear confirmation of the time or whether it goes to me first. Can we confirm those details?”
If two people remember different versions, state the discrepancy without choosing a winner from confidence alone. “I heard an internal draft; you understood a customer-ready version. Let’s agree which output we need now.” The next exchange can establish a clear plan even when the previous one remains ambiguous.
Weeve can also help prepare a follow-up meeting from saved conversations. Review any proposed agenda or clarification before sharing it. Do not let a suggested next step appear as a commitment somebody already made.
Where the pattern needs judgement
Repeating every casual message makes conversation cumbersome. Use a fuller check when the ambiguity matters; use a brief confirmation for a simple low-stakes request. If the exchange keeps failing, investigate the request itself, competing priorities, missing authority or an unrealistic deadline. Repetition cannot solve those problems on its own.
A person may correctly repeat a request and still disagree with it, lack the resources to act or discover a new obstacle. Ask about those conditions separately. Shared understanding makes disagreement clearer; it does not remove it.
In regulated or safety-critical settings, follow the organisation’s trained communication and escalation procedures. The office examples in this article are a practical adaptation of the basic pattern, not a replacement for those procedures.
Try it on one important request
Choose a request that is about to cross a person, team or time-zone boundary. State the output, owner and important timing. Ask the receiver to explain their understanding, then verify it. Save the agreed wording and keep the task’s completion status separate.
The useful result is modest and concrete: before work begins, both people can describe the same next action, and any remaining disagreement is visible.



