How to Give Feedback When a Handoff Is Missed

How should you give corrective feedback when you are angry about a missed handoff?

Wait only until you can describe the shared handoff, what did not arrive, and how the gap affected the work without deciding what your colleague intended. Then speak privately and promptly. State the facts you have, ask what happened, and agree on a concrete rule for the next transfer. If anger still turns the issue into a character judgment, send only the message needed to protect urgent work and arrange a near-term conversation.

A short pause is for checking your account and choosing words; it should not become silent punishment or indefinite delay. In a randomized study of 102 adults with elevated trait anger after provocation, instructed reappraisal was associated with short-term decreases in reported anger and systolic blood pressure. “Trait anger symptoms and emotion regulation” examined laboratory responses, not workplace feedback, so it supports reconsidering an assumption rather than promising calm or agreement. Acas’s “Challenging conversations and how to manage them” advises preparing facts and meeting one-to-one; it is written for line managers. “The effects of feedback interventions on performance” reported average improvement across varied interventions, while more than one-third reduced performance. This is indirect guidance for a peer handoff, not a tested script.

Sources: Trait anger symptoms and emotion regulation: The effectiveness of reappraisal, acceptance and suppression strategies in regulating anger; The Effects of Feedback Interventions on Performance: A Historical Review, a Meta-Analysis, and a Preliminary Feedback Intervention Theory; Challenging conversations and how to manage them

First decide whether you can speak fairly

Before you speak, separate three things that can feel fused together: the event, your reaction, and your explanation of why it happened. The event might be that the agreed file was not in the shared folder by noon. Your reaction is anger because the delay held up your work. “They do not respect my time” is an explanation; the missing file alone cannot establish it. Readiness means you can state the first two clearly and leave the third open long enough to ask. That pause is not a requirement to become cheerful or to pretend the impact was small. Anger can alert you to disruption, but its intensity does not reveal whether the cause was disregard, a blocked dependency, or confusion about ownership. Reappraisal means deliberately checking how you are interpreting an event. In this case, ask what else could account for the delay and what record would help distinguish those explanations. You are testing a conclusion, not talking yourself out of the operational problem. A 2015 randomized study, “Trait anger symptoms and emotion regulation: the effectiveness of reappraisal, acceptance and suppression strategies in regulating anger,” assigned 102 adults with elevated trait anger to instructed reappraisal, acceptance, or suppression after provocation. The university abstract reports short-term declines in state anger and systolic blood pressure in the reappraisal and suppression groups; the acceptance group did not show a substantial decline. This was a selected sample facing provocation, with immediate outcomes. It says nothing about a colleague’s response to feedback or whether concealing anger is useful at work. Your framing can affect anger in the moment; check the story before presenting it as fact. Do not use a pause to rehearse an accusation or suppress the impact. Note the observable gap, the work it affected, and the question you need answered. Words such as “always” or “obviously,” and claims about intent, are cues to verify or remove. The Acas guide “Challenging conversations and how to manage them” is written for line managers, so its advice is guidance rather than a tested peer-feedback method. It recommends establishing relevant facts and allowing enough time for a break to gather thoughts or information. Apply that modestly here: check the message or tracker, take a short pause, and choose a private time soon. If work cannot wait, send a separate factual note about what is needed now and when you will discuss the handoff. A pause becomes avoidance when the operational issue is left unresolved and no return time is set. Use this readiness check: can you say, “The figures we expected by noon were not in the shared folder; I had to hold the review. What got in the way?” If you can say that without adding a verdict, arrange the conversation. If not, protect the work, check the record, and set a near-term time to talk.

Sources: Trait anger symptoms and emotion regulation: The effectiveness of reappraisal, acceptance and suppression strategies in regulating anger; Challenging conversations and how to manage them

What exactly was supposed to cross the handoff?

Before you correct a colleague, establish what the handoff actually required. A timestamp can show when something was sent or expected, but by itself it cannot show that both people agreed on the same task, deadline, or destination. First identify who owned the transfer, what the receiving person needed, when it was due, and where it was supposed to arrive. If the agreement changed after the initial plan, include the change. This check keeps a real work problem visible while leaving its cause open.

Look only at records relevant to this transfer: the task message, project tracker, calendar, or version history. Find the instruction or confirmation that established the due point and receiving location. Was the expected item a draft, final file, decision, or status update? Did the recipient need a particular version or information complete enough to continue? If the record names a deadline but not a channel, or names a file without saying who would post it, the missing detail matters. Do not treat silence in one folder as proof that nothing was sent if the agreed channel is uncertain.

Acas’s *Challenging conversations and how to manage them* advises managers preparing for performance or conduct discussions to establish relevant facts, check records, and consider circumstances that could affect expectations. Its guidance is written for line managers speaking with employees, so it is practical preparation advice rather than a tested peer-handoff method. The useful application here is narrow: bring the specific agreement and the observable gap into the conversation, not a summary of what you think the colleague is like. The guide’s example of a manager with records also shows why accurate notes alone may not settle how an event should be interpreted; the other person may add information that changes the picture.

Keep the description close to what the record can establish. “We agreed the revised figures would be in the shared folder by noon; I could not use them for the afternoon update” names an agreement, a gap, and a consequence. “You always leave me to clean this up” adds a pattern claim that this one handoff cannot prove. If there have been earlier failures, raise them with their own dates and consequences, or handle the pattern through the appropriate process. Do not let accumulated frustration make the current record seem clearer than it is.

This check may show that a correction is warranted, or that the first conversation needs to clarify the agreement. If ownership, destination, or completeness was never settled, say which detail was unclear and agree how to specify it next time. If the record shows a clear commitment, keep it available and ask the colleague to explain what happened before deciding why it was missed. Either way, the aim is a shared account of the transfer that failed and a usable basis for the next step, not a case built from an ambiguous timestamp.

Sources: Challenging conversations and how to manage them

Why character judgments can derail a useful correction

Task-focused feedback means information about a specific performance gap and a feasible next action. That focus matters when anger is present because a missed transfer is something both colleagues can inspect; a claim about character asks the other person to defend an identity. Compare: “The figures were due at noon and were not in the shared folder. I could not finish the client summary. Can we agree how you will flag a delay?” with “You don't care about the team.” The first statement is firm about the gap and its effect, while leaving room to learn why it happened. The second converts one event into a verdict about motive, which the record alone cannot establish.

The broad evidence gives a reason to prefer the first kind of message, though it cannot certify a script. In “The Effects of Feedback Interventions on Performance: A Historical Review, a Meta-Analysis, and a Preliminary Feedback Intervention Theory,” a meta-analysis of 607 effect sizes and 23,663 observations found that feedback interventions improved performance on average (d = .41), while more than one-third decreased performance. The authors proposed that feedback can shift attention among task learning, task motivation, and self-related processes; effectiveness tended to fall as attention moved away from the task and toward the self. They also reported that task characteristics remained poorly understood. Those findings cover varied interventions and tasks, not angry peer conversations or handoffs. They warn against assuming that any correction helps simply because it is accurate.

A 2021 review, “A Review of Feedback Models and Theories: Descriptions, Definitions, and Conclusions,” selected 14 publications through a systematic three-step approach and compared how their models describe feedback. Its subject is student learning, so applying it to a workplace exchange requires care. Still, it reinforces that feedback is not a uniform ingredient with a guaranteed effect: models give different accounts of message, recipient, context, and response. Here, specificity is a practical design choice, not a proven cure for defensiveness. Keep the correction anchored to what was expected, what was missing, and what should happen next. Avoid adding labels such as careless, unreliable, or selfish. Even if a pattern eventually needs to be discussed, begin with the behavior and evidence that can be checked. That lets the colleague respond to the work problem instead of first contesting an identity judgment. It also gives you a clearer basis for deciding whether the next step is a changed handoff rule, a blocker signal, or follow-up on a commitment. A specific request does not require gentle euphemism: state the deadline, the dependency, and the consequence plainly. If the colleague disputes a fact, compare the relevant record before widening the discussion. The aim is a correction the two people can examine together, not a polished sentence that guarantees agreement.

Sources: The Effects of Feedback Interventions on Performance: A Historical Review, a Meta-Analysis, and a Preliminary Feedback Intervention Theory; A Review of Feedback Models and Theories: Descriptions, Definitions, and Conclusions

Ask what happened before choosing the correction

Once you have stated the gap and its consequence, ask a question that leaves room for an answer: “What got in the way of the transfer?” Then listen for details that could change what the agreement meant or what was possible. Perhaps ownership shifted after the plan was made; a dependency arrived late; the shared folder was inaccessible; two deadlines collided; or the colleague missed a clear commitment. These possibilities are not excuses to list before the conversation. They are distinctions to hear before deciding which correction fits. You remain direct about the missing work and its effect while postponing the conclusion about why it happened. Keep the question bounded to this handoff. “What happened between our agreement and the file being ready?” invites a sequence of events. “Why are you always unreliable?” already supplies a verdict and asks the colleague to defend their character. A useful follow-up is concrete: “When did you first know the figures might be late?” or “Who had the final version after the ownership changed?” Ask one question, allow an answer, and check what you heard before moving to the next. If the explanation identifies a blocker, find out whether it was visible early enough to signal. If the account confirms a clear, feasible commitment was missed, say so plainly and discuss the needed change. Listening does not cancel corrective feedback; it helps you aim it at the failure that occurred. The guide “Challenging conversations and how to manage them” advises managers to establish what they know, use open questions and listen, while noting that a record of events may omit circumstances that matter. Its examples are practical guidance for manager-to-employee conversations, not evidence that a peer’s question will produce candor or agreement. Still, the advice fits this narrow problem: a tracker can show when a file appeared, but it may not show that access changed or a dependency was reassigned. Treat the record as a starting point for inquiry, then compare it with the colleague’s account and any relevant messages. There is a reason to make that room for information, though the research does not test this script. “Psychological Safety and Learning Behavior in Work Teams” reports a multimethod field study of 51 work teams in one manufacturing company. Team psychological safety, a shared belief that interpersonal risk-taking is safe, was associated with learning behavior; the study also reported that learning behavior mediated the association between psychological safety and team performance. This was team-level, associational evidence from one company. It cannot show that one private conversation creates safety or improves one handoff. It does make a useful caution visible: when people expect a question to become an accusation, they may have less room to raise the process information needed to prevent a repeat. Ask to understand the sequence, not to stage a trial. The answer may lead to a clearer protocol, an earlier blocker signal, or a specific correction to the colleague’s follow-through.

Sources: Psychological Safety and Learning Behavior in Work Teams; Challenging conversations and how to manage them

Three causes call for three different repairs

An empty folder can point to three problems, each calling for a different repair. Treat these as explanations to check, not labels. | Explanation | Clues | Repair | | --- | --- | --- | | Vague agreement | No clear owner, due point, destination, or definition of “ready” | Set terms before the next transfer | | Blocked dependency | An input, access, decision, or priority changed; no warning reached the recipient | Agree who flags a blocker, when, and to whom | | Clear commitment missed | Owner, item, due point, and feasible route were understood, with no intervening change | Name the missed action and how completion will be checked | This comparison is a practical synthesis, not a finding from one trial. Acas’s *Challenging conversations and how to manage them* advises managers to establish facts and consider circumstances that may change a target. Its guide concerns manager-employee conversations; applying that habit to peers is an adaptation. Check the ownership message, changed deadline, missing prerequisite, or confirmation. A tracker date alone may not settle what both people agreed. When the agreement was vague, a reprimand cannot supply the missing specification. Say what the transfer needs to contain, who owns it, where it belongs, and when it is due. If a dependency blocked delivery, agree on an early warning: “If approval is still pending by 10, can you tell me and copy the project lead?” That addresses coordination without assuming every delay was avoidable. When the commitment was clear and feasible, keep the correction specific. Name the agreed action and what failed, then ask for a change visible in the next transfer: “The signed figures were due in the shared folder at noon, and the review had to wait. Please post them there by noon Thursday or tell me earlier if that deadline is at risk.” This makes the expectation discussable without inferring carelessness from one event. Task-focused wording has a rationale, not a guarantee. *The effects of feedback interventions on performance: A historical review, a meta-analysis, and a preliminary feedback intervention theory* combined 607 effect sizes and 23,663 observations across varied interventions and tasks. Performance improved on average (d = .41), while more than one-third of interventions reduced it. The authors’ preliminary theory proposes that feedback may shift attention from task learning toward self-related concerns; task characteristics also moderated effects and remained poorly understood. The review does not test this peer conversation. It gives a reason to correct transfer behavior rather than deliver a character verdict. If the colleague’s account reveals both a missed action and a process flaw, name the action to change and repair the handoff conditions that disrupted the work.

Sources: Challenging conversations and how to manage them; The Effects of Feedback Interventions on Performance: A Historical Review, a Meta-Analysis, and a Preliminary Feedback Intervention Theory

State the impact without making the colleague responsible for your whole reaction

Once you have described what was expected and what arrived, name the work consequence someone else could check. The review may have started late because figures were missing. That explains why the handoff matters; it does not establish why it was missed. Anger can make those claims feel like one: the delay caused strain, therefore the colleague must have ignored the agreement. Keep the first claim and ask before relying on the second.

A useful correction has three parts: the observable gap, its operational impact, and a request. For example: “The draft was due in the shared folder before the review. It was not there at the start, so I could not check the figures and the review moved back. Can we agree what you’ll send and when, and how you’ll flag a delay?” It does not label the colleague careless or disrespectful. Those words make a claim about character or motive that the missed transfer alone cannot prove.

Impact matters because a colleague needs to understand what the gap disrupted and why the next step matters. Keep it proportionate: name the delayed decision, extra task, or missed dependency, rather than turning one event into a sweeping account. The Acas guide, written for line managers preparing challenging conversations with employees, advises establishing relevant facts, considering the effect on the team, and focusing on the issue rather than the person. This is practical guidance, not a study of which sentence changes a response.

Own the emotion in a separate sentence if it helps explain your timing or tone: “I’m frustrated, and I want to talk about the handoff clearly.” You need not pretend to be calm, but anger’s intensity is not evidence of intent. The HSE page Helping someone who is angry or upset addresses a person receiving feedback who becomes angry; it advises the feedback giver to stay calm, listen, acknowledge feelings, focus on the issue, and agree next steps. The roles differ here, so the page offers a conversational boundary, not direct evidence about an angry colleague giving feedback.

A boundary belongs in the conversation when work repeatedly shifts onto you. State what you can no longer absorb and identify the process that needs attention: “I can cover today’s review, but I can’t keep taking over this check at the last minute. We need to agree who owns it, and if we cannot, I’ll ask our manager to clarify the handoff.” This limits your workload and routes ownership for resolution; it is not a verdict about the colleague. If a workplace procedure applies, use it rather than trying to settle the matter through an improvised peer correction. The request should specify what will change in the next transfer, not demand that the colleague manage your feelings or promise never to make another mistake.

Sources: Challenging conversations and how to manage them; Helping someone who is angry or upset

End with a handoff rule both people can check

Once you understand what happened, bring the conversation back to the next transfer. A useful agreement names who owns the next step, what they will deliver, where it belongs, and when it must be available. Add an early signal for trouble: if a dependency or deadline puts delivery at risk, the owner alerts the receiver and says what is blocked. This turns “please communicate better” into something both colleagues can recognize. The receiver should confirm the arrangement in their own words; a nod can conceal different assumptions about completion.

For example, if a colleague owns final figures, identify the shared folder, required version, and time they must arrive. Also agree where to post an update if a source file is late, and who decides whether a partial transfer is usable. Keep the rule proportionate. A routine handoff may need only an owner, destination, and due time; a transfer with dependencies may need an earlier warning point. Specify what the receiver should do after that signal, such as acknowledge the blocker or agree a revised time. Settle the uncertainty that caused this exchange so neither person has to infer completion from silence before the next transfer begins.

The 1996 meta-analysis “The Effects of Feedback Interventions on Performance” covered 607 effect sizes and 23,663 observations. Feedback interventions improved performance on average (d = .41), while more than one-third reduced it. Its proposed theory suggests feedback can lose effectiveness when attention moves from task learning toward self-related processes; the authors also said task characteristics were poorly understood. A 2021 review, “A Review of Feedback Models and Theories,” describes forward-looking feedback as asking what comes next. These sources give a rationale for agreeing on a clear action. They did not test peer handoff conversations, so this rule is an application, not an established effect.

Acas’s “Challenging Conversations and How to Manage Them” advises managers to agree a way forward, arrange follow-up, and document outcomes with dates and standards. Its scope is employer-employee conversations, so it is practical guidance rather than evidence that a note improves peer coordination. Keep any record brief: owner, deliverable, location, timing, and the signal for a delay. It records what both people understood at the end; it does not prove fault or settle disputed history.

An apology may acknowledge the effect of a missed transfer, and the person affected can say what repair would help. The operational repair is whether the next transfer has a workable rule both colleagues understand. If you remember the discussion differently, compare the messages, tracker, or version history together, then clarify the protocol before assigning meaning. Close by asking, “Can you confirm what you’ll send, where it will go, and when you’ll flag a delay?” The answer gives both people a behavior to check without demanding a promise that nothing will ever go wrong again.

Sources: The Effects of Feedback Interventions on Performance: A Historical Review, a Meta-Analysis, and a Preliminary Feedback Intervention Theory; A Review of Feedback Models and Theories: Descriptions, Definitions, and Conclusions; Challenging conversations and how to manage them

When should you pause, stop or escalate?

A pause is useful when it has a return point. If either of you is speaking over the other, repeating accusations, or no longer able to discuss the transfer itself, stop the conversation for now. You might say, “I want to resolve the handoff, and I’m too angry to do that fairly at this moment. Let’s take a break and talk again at 2.” Acas’s guide to challenging conversations recommends allowing time for a break to gather thoughts or obtain more information. The same useful principle applies here: make the pause explicit and set a time to resume. Keep time-sensitive work separate from the dispute. If a client deadline, dependent task or safety check cannot wait, send a neutral operational note naming what is needed, who can provide it, and by when. For example: “The review is waiting on the figures. Please send the current version to the shared folder by noon, or tell me now if that is blocked so I can arrange coverage.” Then return to the corrective conversation once the immediate dependency is under control. If no safe workaround exists, or the handoff affects a safety-critical step, use the relevant supervisor or incident process promptly; an angry peer discussion is not a substitute for operational safeguards. Set a boundary if the exchange becomes abusive or threatening. The Health Service Executive’s “Helping someone who is angry or upset” guidance is written for a feedback giver whose recipient is angry. It advises staying calm and focused on the issue, but says not to tolerate unreasonable behavior; it identifies aggressive or threatening tone and abusive or inappropriate language, and recommends ending the conversation and reporting the behavior to a manager or authorities where appropriate if the conduct continues. Here it supports a narrow safety boundary: you can say you will continue when the language is respectful, then leave and seek help if it is not. Follow local policy for threats, harassment, or other serious conduct. A repeated missed handoff may also call for escalation when prior agreements have failed, the impact is serious, or workplace policy assigns the issue to a manager. Acas advises checking relevant procedures and getting management support when a policy breach is established; that advice concerns formal management responsibilities, not every peer disagreement. First record the concrete events and the operational effect, then ask the appropriate person to clarify ownership and next steps. Use it when safety, authority, recurrence, or the work itself requires a process beyond the two colleagues.

Sources: Helping someone who is angry or upset; Challenging conversations and how to manage them

Choose one skill to practice in your next difficult handoff

After the conversation, choose the moment in your own response that needs the most practice. Perhaps you treated a late transfer as proof that your colleague did not care; perhaps you asked what happened but filled the silence before hearing the answer; perhaps you explained the problem clearly and then left the next step vague. Pick one behavior you can observe next time. For example: before raising a missed commitment, write down the agreed delivery point and one alternative explanation you still need to check.

The goal is a clearer handoff and a more deliberate response from you. In the study described in the university record “Trait anger symptoms and emotion regulation: The effectiveness of reappraisal, acceptance, and suppression,” 102 adults selected for elevated trait anger were provoked and randomly assigned to regulation instructions. The abstract reports short-term reductions in state anger and systolic blood pressure for participants instructed to reappraise or suppress; it does not test workplace feedback, a handoff conversation, or whether any technique improves the relationship. Reappraisal is therefore a reason to check the story attached to the anger, not a guarantee that a difficult discussion will go well.

If you want structured help noticing your own habits, the [Emotional Skills Profile](/assessment) is a private 32-item reflection tool about recent behavior and authored emotional situations. It can give you material to consider when choosing a practice, such as pausing before inferring intent or making a more specific request. It has no validated norms and does not rate your colleague or establish that a particular feedback method works. The next useful conversation is the one where you can name what must arrive, by when, and what signal you need if it is at risk.

Sources: Trait anger symptoms and emotion regulation: The effectiveness of reappraisal, acceptance and suppression strategies in regulating anger

Questions readers ask