Which action should a team leader take when input from a team member alerts them about a potential oversight during a resuscitation event? The leader should acknowledge the concern out loud, pause or slow the code for a brief reassessment, verify the claim directly against the patient and monitor, and then close the loop by telling the reporter what was found and what changes. That sequence converts a warning into a correction instead of a dismissed distraction.
The instinct to act fast during a code is right, but speed without verification is how teams repeat errors. A resuscitation event compresses time: compressions, rhythm checks, drugs, and airway moves overlap, and any one of them can drift. The member who speaks up is often the only sensor that catches the drift before it reaches the patient. The leader's job is to make speaking up cheap and acting on it systematic.
This matters because resuscitation error is well documented. The Institute of Medicine's 1999 report on patient safety estimated that medical errors contributed to between 44,000 and 98,000 deaths per year in US hospitals. Modern reviews of in-hospital cardiac arrest consistently find that CPR quality metrics—rate, depth, and peri-shock pause—fall outside guideline targets during a meaningful share of events. A team member's warning is a leading indicator of one of those gaps. The leader's action determines whether the indicator is used.
Mechanism: why the leader's action is the conversion step
A potential oversight travels through three states: an observation by one person, a spoken concern, and a change in team behavior. Most failures happen between the second and third states, not at the observation. Human factors research on speaking up describes a "gradient" between what a clinician notices and what they say, driven by hierarchy, timing, and uncertainty about being wrong. Even when the concern is voiced, the leader can truncate it by responding with reassurance, indifference, or a question that shifts the burden back to the reporter.
The leader's action matters because it manages two costs at once. The first is the cost of the oversight itself—a missed rhythm check, a misplaced tube, a wrong medication. The second is the cost of the interruption—a code that stops for a debate nobody needed. A closed-loop response controls both. Acknowledgment tells every observer the channel is open. Verification checks the claim against evidence rather than authority. Closure tells the team the concern was resolved and re-establishes the leader's plan.
Three mechanisms explain why closure, not acknowledgment alone, drives outcomes. First, verbalization creates an external record team members can act on; an unspoken "I heard you" is indistinguishable from being ignored. Second, verification forces the leader to look at the same data the reporter saw, which catches the case where both were partly right. Third, closure prevents the same concern from being re-raised repeatedly, which fragments the code's focus.
A useful frame is the two-challenge rule from crew resource management. Any team member should be able to state a concern once, and state it again more firmly if the first is not addressed. The leader's responsibility is to make the first challenge sufficient. If a concern requires a second, louder attempt, the leader has already failed one coordination step.
Plain language: a warning only helps if the person who warns sees the team respond to it.
Quantified context: how often input is correct, missed, or ignored
Exact figures vary by setting, so treat these as ranges and directions rather than a precise error budget. What is consistent across studies is that (a) team members frequently hold back concerns, and (b) when voiced, concerns have a meaningful hit rate.
| Layer | What it measures | Typical direction | What the leader can do |
|---|---|---|---|
| Speaking up | Share of observed concerns actually voiced | Commonly under half; hierarchy suppresses upward communication | Invite dissent by name; flatten the channel |
| Hit rate | Share of voiced concerns that identify a real issue | Often high enough that false positives are the cheaper error | Verify fast rather than debate first |
| CPR quality | Share of events with rate/depth outside guidelines | Frequently out of target during parts of the event | Re-check after any warning |
| Pause time | Perishock and rhythm-check pause duration | Often exceeds guideline targets | Use the warning as a pause audit |
| In-hospital cardiac arrest survival | Survival to discharge after IHCA | Roughly 1 in 5 or lower in many registries | Minor corrections compound over minutes |
The practical reading: the expected value of stopping to check is positive when the claim is plausible and the check is fast. You do not need the warning to be right most of the time. You need the verification to be cheap and the correction to be quick. That combination is why leaders should default toward verification, not toward dismissal.
Age and team experience shift these numbers. Trainee-led or night-shift teams often have wider authority gradients, so the same warning is less likely to be spoken. Experienced leaders get more false alarms because their teams self-correct less. Neither pattern changes the correct response; both change how much the leader should actively solicit input.
Edge cases: when the default sequence must be modified
The closed-loop protocol is a default, not a script. Four situations require modification, and the leader needs to recognize them in seconds rather than minutes.
During active compressions, a full pause is not always warranted. If the concern is "we may have missed a rhythm check," the leader can ask the compressor to keep going while a second team member confirms the last rhythm and the clock. If the concern is "the tube may be in the esophagus," continuing compressions is the right call while the airway operator re-verifies with waveform capnography and a second look. The rule is: verify without stopping when verification is possible without stopping; stop when the oversight cannot be evaluated in motion.
When the reporter is uncertain, the leader should not treat uncertainty as unreliability. The right action is to ask a clarifying question that turns the vague into verifiable: "What did you see, and when?" Vague concerns often resolve into a specific, checkable fact within one exchange. A leader who requires confidence before verification gets only confident reports, which is a bad filter.
When two reports conflict, the leader should name the conflict and use the patient as arbiter. "I have one report of X and one of Y; we check the monitor and the patient." This avoids a personal contest and keeps the conflict focused on evidence.
When the oversight is already past, the sequence continues after the code. The leader should record the concern, the verification, and the outcome in the event documentation, and should close the loop with the reporter afterward. Unresolved warnings become defensive silences on the next code.
Red flags that demand immediate stop-and-check rather than a deferred review: A mismatch between clinical signs and the monitor (pulseless but the monitor shows a rhythm). A concern that a drug or dose was swapped with another medication. An airway concern with falling or absent end-tidal CO2. A report that compressions have not paused for the scheduled check, or that a pause has run long. A report that a reversible cause has not been assessed.
Each of these can be checked in under a minute and each has a large downside if wrong.
Misconceptions: what leaders get wrong about team input
The most common misconception is that acknowledging a concern is the same as acting on it. Acknowledgment without verification and closure leaves the reporter believing they were heard but unheeded. Over time, that experience teaches the team to stop reporting. The code gets quieter, not safer.
A second misconception is that a leader must adjudicate immediately. Leaders are not required to decide whether the concern is correct before responding; they are required to launch a check. The decision and the verification are separate steps, and conflating them turns every warning into an argument.
A third misconception is that interruptions are inherently dangerous. Interruptions during resuscitation are a quality problem, but the fix is a structured interruption, not a ban on input. A five-to-ten second verification with the compressor continuing is not the same as a minute-long debate. The leader's response determines which one occurs.
A fourth misconception is that the leader is the only source of truth. Resuscitation is distributed: the monitor, the drug labels, the clock, and the team's eyes all carry information. A leader who sources truth only from their own view discounts the rest of the room.
Counterintuitive detail: leaders overestimate how often their teams speak up. In debriefs, team members consistently report concerns they withheld, while leaders report an open climate. The gap is the leader's blind spot, and it is best closed by specific invitations before the event rather than general assurances during it.
Practical actions: the leader's correction sequence, step by step
The following sequence is usable in real time and in any resusucitation setting where team input is possible. Each step is designed to take seconds, not minutes, and each step leaves a trace the team can see.
Acknowledge out loud and by name. "I hear you, [role]; say it again while we keep compressions." Naming the reporter signals to the whole team that the channel is open and that the concern is being taken seriously. Restate the concern in one sentence. "You think we may have missed a rhythm check." Restating catches mishearing and forces the concern into a shared, checkable form. Launch a specific verification, not a general discussion. Assign a named person to check a named thing: the last rhythm and its time, the tube position with capnography, the medication label, the compression start time. Verification should use the patient and the monitor, not memory. Decide with a threshold, not a debate. If the verification confirms the concern, correct it now. If it does not confirm, say so out loud and state what you did find. Either way, name the decision. Close the loop to the reporter and the team. "Confirmed; we correct X." Or "Not confirmed; we are continuing, good catch to raise it." Closure prevents re-raising and preserves the channel for the next concern. Log and debrief after the event. Record the concern, verification result, and action in the documentation, and revisit it in the post-event debrief.
These steps reconcile the two competing thresholds in resuscitation practice: the guideline threshold for pausing compressions, and the operational threshold for acting on a team member's warning. The pause threshold is set by the patient's need for continuous flow; the warning threshold is set by the cost of being wrong. In practice, the leader resolves the conflict in favor of verifying wherever verification is possible, and in favor of a structured brief pause where it is not. Both thresholds live inside the same sequence, and neither is a reason to ignore the other.
Plain language: treat every warning as a checkable fact, not as a challenge to the leader's authority.
Limitations: what this protocol cannot do and where judgment remains
This approach does not eliminate error, and it should not be sold as a guarantee. A team member can be wrong, silent, or late, and a verification can be ambiguous. A code can be so unstable that no check is possible without unacceptable interruption. The protocol improves the expected outcome of a team's coordination; it does not make coordination free.
The protocol also depends on a climate that exists before the code. If a team has never practiced speaking up, the first attempt during a code is unlikely to be heard. Simulation-based training in which the leader explicitly invites dissent is the strongest available preparation for the first challenge during a real event. Teams that rehearse the two-challenge rule perform it more reliably under stress.
A final limit is documentation. Concerns that are raised and resolved but never recorded are invisible to quality review, so the same pattern can recur without being recognized. Leaders who log concerns create the data that training and system change depend on.
This article is general educational information, not a diagnosis, a treatment plan, or a substitute for clinical judgment. Resuscitation protocols and drug dosing vary by setting and are governed by local guidelines; consult a qualified clinician and your institution's policies for patient-specific decisions. For an active emergency, contact local emergency services immediately.