Closed loop communication is a three-step habit. The sender gives a specific message to a named person, the receiver repeats the key details back, and the sender confirms they are correct before anyone acts. The 5 Cs of communication (most often Clear, Concise, Correct, Complete and Courteous) describe what a good message looks like before it is sent. Neither one is software. Both work at the front desk and in the back office as well as at the bedside. This page explains each technique, gives phrasing you can copy, and shows how to apply both to everyday clinic operations. It is part of our healthcare communication guides.
- What closed loop communication in healthcare means
- The three steps of closed loop communication, with examples
- Closed loop communication in a healthcare team: when to use it
- The 5 Cs of communication in the medical field
- How the 5 Cs and closed loop communication work together
- Common barriers and how to fix them
- Putting it into practice in your clinic
- Closing the loop on operational work with a team chat
- FAQ
What closed loop communication in healthcare means
Definition: Closed loop communication is an exchange in which the sender gives a message, the receiver repeats it back, and the sender confirms it is correct, so both people know the message was received and understood as intended.
In healthcare team training, the term is closely tied to the check-back technique taught in AHRQ's TeamSTEPPS program. Many clinical teams, simulation programs and nursing curricula teach it as a core teamwork skill.
Why it matters: Verbal and written requests fail in predictable ways. People mishear a name or a number. They assume someone else is handling the task. A request lands with nobody in particular and quietly drops. A loop catches these problems at the moment the request is made, before they turn into errors or missed follow-ups. Communication failures are widely cited as a contributor to adverse events.
Scope note: In clinical care, closed loop communication follows your organization's own protocols and runs through its approved clinical systems. Verbal orders, critical results and handoffs are examples. This page uses clinical examples only to illustrate the technique. For the tools built for clinical messaging, see clinical communication platforms. The rest of the page focuses on how the same loop applies to operational and administrative work.
The three steps of closed loop communication, with examples
Step 1: Call-out. The sender addresses one named person and states the request specifically. "Can someone call the lab?" is not a call-out. "Priya, please call the reference lab about the missing courier pickup before noon" is.
Step 2: Check-back. The receiver repeats the key details back: who, what and when. Repeating only "Got it" or "Okay" does not count, because it shows the message was heard but not that it was understood.
Step 3: Confirmation. The sender says "Correct" or fixes what was wrong. Only then is the loop closed and the receiver free to act.
Clinical team example (illustrative only)
Provider: "Sam, please bring the vitals cart to room 4 now." Medical assistant: "Vitals cart to room 4, now." Provider: "Correct."
Real clinical exchanges follow your organization's protocols for verbal orders and read-back.
Operational example
Clinic manager: "Jordan, Dr. Patel is out Thursday afternoon. Please reschedule her 1:00 to 5:00 block and have the list of moved patients to me by end of day Wednesday." Front desk lead: "Reschedule Dr. Patel's Thursday 1:00 to 5:00 block, moved list to you by end of day Wednesday." Clinic manager: "Correct. And flag anyone you can't reach." Front desk lead: "Will flag anyone I can't reach."
The read-back covered the provider, the date, the time block and the deadline. If Jordan had heard "Friday," the error would have surfaced in seconds instead of on Thursday afternoon.
Closed loop communication in a healthcare team: when to use it
Training programs commonly emphasize closed loop communication for high-risk moments such as verbal orders, critical test results, patient handoffs and emergencies. These moments involve several roles at once, which is why the technique is a staple of interprofessional collaboration.
Everyday admin work benefits from the same habit, especially when a request has a deadline or crosses roles:
- Supply orders: "Order two cases of exam table paper for the north location, delivered by Friday."
- Coverage changes: who is covering which desk, at which site, for which hours.
- Patient callback lists: which list, who owns it, and when the calls must be done.
- IT requests: which workstation, what is broken, and how urgent it is.
- Facilities issues: "The waiting room thermostat at Elm Street needs a service call today."
Signs a loop is open
- No named owner ("Can someone…").
- No deadline ("When you get a chance").
- No confirmation. The sender never heard back, so nobody knows whether the receiver understood.
- The phrase "I thought you were doing it."
Common failure points
- Noise and interruptions: a request shouted across the front desk while the phones ring.
- Shift changes: the receiver acknowledges a request and then leaves for the day.
- Group messages with no named owner: a request posted to a group text that five people read and nobody takes.
- Multiple channels: half the request in email, half in a hallway conversation.
The 5 Cs of communication in the medical field
There is no single official list of the 5 Cs. A widely used version is below:
- Clear: One request, plain words, no ambiguity about what is being asked.
- Concise: Only what the receiver needs to act.
- Correct: Names, dates, numbers and locations are accurate.
- Complete: Who, what, where, when, and what "done" looks like.
- Courteous: Respectful and neutral in tone, so people feel safe to ask questions and read back.
Other versions swap in terms such as Consistent, Compassionate or Confident. Use whichever version your organization trains on. The point is a shared standard, not a particular acronym.
Before-and-after staff messages
| C | Before | After |
|---|---|---|
| Clear | "Can we look at the schedule thing for next week?" | "Maya, please block Dr. Kim's Tuesday 8:00 to 10:00 slots for her training." |
| Concise | A four-paragraph email about the supply room that ends with "so we need gloves." | "Leo, please order 10 boxes of medium nitrile gloves for the Oak Street site by Thursday." |
| Correct | "Move the Monday staff meeting to the 14th." (The 14th is a Wednesday.) | "Move the staff meeting from Monday the 12th to Wednesday the 14th, same time, 8:00." |
| Complete | "Please call back the patients from yesterday." | "Ana, please call the 12 patients on yesterday's no-show list by 3:00 today and mark each one rebooked or left a message." |
| Courteous | "Why isn't the fax machine fixed yet?" | "Chris, the fax machine at the front desk is still jammed. Could you look at it before 11:00? Thanks." |
How the 5 Cs and closed loop communication work together
The 5 Cs shape the message. The closed loop confirms it was received and understood. A clear, complete request still fails if the receiver mishears a date. A perfect read-back cannot fix a vague request.
Operations manager: "Dana, please update the after-hours voicemail at all three locations with the new holiday hours, Dec 24 to Jan 1, by Friday at noon." (clear, concise, correct, complete, courteous) Front desk lead: "Update after-hours voicemail at all three locations with holiday hours, Dec 24 to Jan 1, by Friday noon." Operations manager: "Correct."
Structured formats sit alongside both techniques. SBAR (Situation, Background, Assessment, Recommendation) organizes what to say when raising an issue. Closed loop communication confirms that what was said was understood. Teams often use SBAR to frame a message and check-back to close it. For more on these and related techniques, see communication strategies for healthcare teams.
Common barriers and how to fix them
Hierarchy and hesitation to speak up. Staff may feel awkward reading back a request from a physician or practice owner, or may worry it sounds like doubt. The fix is to make check-backs universal. Leaders read back requests from staff too, and "Let me repeat that back" becomes normal, not a sign of distrust.
Fragmented channels. Personal texts, sticky notes, email and hallway conversations each hold a piece of the work, and loops break in the gaps between them. Pick one place for operational requests so the call-out, the read-back and the confirmation all sit together.
Shift and location gaps. The person who received the request goes off shift, or the request was made at one site and needs action at another. Requests should carry a named owner and a deadline that survive the handover. The incoming person should be able to see what is still open.
For a deeper look at causes and fixes, read communication barriers in healthcare.
Putting it into practice in your clinic
- Train the phrasing in a 10-minute huddle. Walk through call-out, check-back and confirmation with two or three examples from your own week. Post a one-page script at the front desk and in the break room: "[Name], please [task] by [time]." / "[Task] by [time]." / "Correct."
- Agree on one channel for operational requests. When every request lives in the same place, open loops are visible. That matters most for loops that span shifts or sites.
- Make "owner plus deadline plus confirmation" the default. A request without all three is not finished being sent. Managers model this first.
- Review missed follow-ups monthly. Pull three or four things that slipped and trace where the loop stayed open. Was there no owner, no deadline, or no confirmation? Adjust the script or the channel.
For checklists and process guides you can adapt, see the operations library for practice managers.
Closing the loop on operational work with a team chat
A team chat can make the habit easier to keep for administrative work. In Chanty, staff can turn any chat message into a task with an owner and a deadline. The receiver replies in the thread to read back and confirm, and everyone can see when the task is done, across shifts and locations. Chanty does not automate or enforce read-back. The loop still depends on people using the phrasing.
Chanty is internal team communication for operational and administrative coordination, used alongside your clinical systems. It is not a clinical handoff, ordering or alerting tool, and it is not patient messaging or an EHR. Chanty supports HIPAA compliance for staff chat with a signed BAA on the Business and Enterprise plans. The Free plan does not include a BAA and should not be used for PHI. Learn more about team communication software for clinics, or sign up for Chanty.
Where Chanty fits. chanty.health is published by Chanty, a team chat for clinic staff with a signed BAA from the Business plan. If your team still coordinates in personal group chats, see how HIPAA-compliant staff chat works or start free.
FAQ
What is closed loop communication in healthcare?
It is a three-step exchange. The sender gives a specific message to a named person, the receiver repeats the key details back, and the sender confirms they are correct before anyone acts. It confirms that a message was understood, not just heard.
What are the three steps of closed loop communication?
Call-out, check-back and confirmation. The sender makes a specific request to one person. The receiver repeats who, what and when. The sender says "Correct" or fixes the error.
What is an example of closed loop communication in nursing or a clinic?
A clinic manager says, "Jordan, please reschedule Dr. Patel's Thursday 1:00 to 5:00 block by end of day Wednesday." Jordan repeats, "Reschedule Dr. Patel's Thursday 1:00 to 5:00 block by end of day Wednesday." The manager replies, "Correct." In nursing and other clinical settings, the same pattern applies under the organization's own protocols for orders and results.
What are the 5 Cs of communication in the medical field?
A widely used version is Clear, Concise, Correct, Complete and Courteous. Other versions include Consistent, Compassionate or Confident. No single list is the official standard.
Is closed loop communication the same as read-back or check-back?
They overlap. Check-back and read-back describe the receiver repeating the message. Closed loop communication is the whole cycle: call-out, check-back and the sender's confirmation.
How is SBAR different from closed loop communication?
SBAR structures the content of a message: Situation, Background, Assessment, Recommendation. Closed loop communication confirms the message was received and understood. Teams often use both together.
Can closed loop communication be used in written messages and chat?
Yes, for operational work. The receiver replies in writing with the key details ("Ordering 10 boxes of medium gloves for Oak Street by Thursday"), and the sender confirms. Assigning a named owner and deadline in the same thread keeps the loop visible. Clinical communication should follow your organization's approved protocols and systems.