A 10-Minute Delegation Script That Actually Prevents Missed Handoffs

After this, you will have a repeatable ten-minute conversation that catches the four things that quietly wreck delegated work: unclear intent, invisible workload, fuzzy decision rights, and a moving target for "done." No theory first. Here is the script, why each part exists, and what to do when someone still drops the ball.

Most delegation fails long before the deadline. It fails in the handoff, in the sixty seconds where a task gets passed from one person to another with a vague nod and an "okay, sounds good." That nod feels like agreement. It is usually just politeness. Weeks later, the work comes back wrong, late, or half-finished, and both people are frustrated for reasons neither can quite name.

What the Delegation Handshake Actually Is

The Delegation Handshake is a short, structured conversation that happens at the moment work changes hands, not after. It runs about ten minutes and moves through five checkpoints in order: intent, capacity, decision rights, definition of done, and the next check-in. Skip one, and you have not delegated a task. You have transferred anxiety.

Think of it less like a meeting and more like a pressure test. You are not asking someone to prove they can do the work. You are confirming that both of you are picturing the same outcome, the same constraints, and the same timeline before either of you walks away and starts assuming.

Start With the Problem, Not the Task

Most delegation opens with an instruction: "Can you handle the client report by Friday." That sentence hands over a task without ever explaining the problem the task is meant to solve. The person receiving it now has to guess what "handle" means, and guessing under deadline pressure is where quality erodes fastest.

Open the handshake with questions instead of instructions. What outcome are we actually trying to produce here. Who is this for, and what will they do with it once it lands. What does a bad version of this look like, so we both know what to avoid. These are not soft, feel-good questions. They are the fastest way to surface a misunderstanding while it still costs ten minutes instead of ten hours.

Here is the part that gets missed constantly: intent changes the shape of the work. A report meant to inform a decision looks nothing like a report meant to defend one. If you skip this step, you get technically correct output that solves the wrong problem, and then you are redoing it anyway, just later and angrier.

Confirm Capacity Before You Confirm the Ask

This is the step almost everyone skips, and it is the one that causes the most resentment. You cannot responsibly hand someone new work without seeing what is already on their plate. Not what you think is on their plate. What is actually there, including the backlog nobody tracks, the rework from last week’s rushed job, and the three other "quick favors" that landed on them this month.

Ask directly: what does your current workload look like, and where would this new piece actually fit. Make the invisible visible for thirty seconds. If the honest answer is "I don’t really have room," that is not a failure of the person, it is useful information you needed before you committed either of you to something that was never realistic. That used to feel like a failure to admit. It isn’t.

Skipping this step is how good people quietly burn out while still technically saying yes to everything. The opposite mistake causes its own damage: managers who over-index on capacity checks turn every handoff into a negotiation, and the team learns that saying "I’m busy" is the fastest way to avoid ownership. Capacity checks work when they are honest inventories, not escape hatches.

Decision Rights: Who Decides, and When Do They Escalate

This is where delegation quietly becomes micromanagement, or quietly becomes chaos, depending on which mistake you make. If you never clarify decision rights, one of two things happens. Either the person escalates every small choice back to you, which defeats the point of delegating at all, or they make calls you never intended to hand over, and you find out after it is too late to redirect.

Name it out loud. What can this person decide on their own, no check-in needed. What requires a heads-up before they act. What is an automatic escalation, no judgment call required. That third category matters more than people think, because vague escalation triggers ("let me know if something big comes up") leave the definition of "big" entirely up to whoever is under the most stress at the time.

Then again, I’ve also seen the exact opposite happen when a manager tries to close every gap by spelling out decision rights in exhaustive detail up front. Instead of feeling trusted, the person feels boxed in, and starts treating every gray area as a rule violation rather than a judgment call they’re allowed to make. The goal isn’t maximum specificity. It’s enough clarity that the person can act without guessing, and still has room to think.

The cost of getting this wrong is not just wasted time. It is trust. Someone who gets overridden after making a reasonable call under unclear rights stops making calls at all. They start asking permission for everything, and now you have more meetings, not less delegation.

Define "Done" Before the Work Starts

A task without a defined "done" is not really delegated. It is deferred, because the real definition of finished will get negotiated later, usually at the worst possible moment, right when the deadline hits.

Agree on what done looks like in concrete terms. Not "a good report," but a report with three specific sections, reviewed by whom, delivered in what format, by what exact time. Then agree on how it will be reviewed. Will you read a draft first, or only the final version. Is there a checklist it needs to pass. Vague standards produce vague results, and vague results produce a review conversation that feels like a surprise test nobody studied for.

Lock the Next Check-In While You’re Still in the Room

The fifth checkpoint is the easiest to forget and the one that saves the most damage control later. Before you end the handshake, agree on exactly when you will talk again about this piece of work, and what that check-in will cover.

Not "I’ll check in soon." A specific day, a specific format, whether it is a two-line async update or a five-minute call. This single agreement turns a delegated task from something that silently drifts into something with a heartbeat. If the work is going to slip, you find out at the check-in, with time to adjust, instead of finding out at the deadline, with none.

The Script, Start to Finish (All Ten Minutes)

Here is the whole thing in order, so you can run it without flipping back through the reasoning behind each part.

1. Minutes 0–2, Intent. Ask: what outcome are we trying to produce, who is it for, and what does a bad version look like. Do not move on until the answer is specific.
2. Minutes 2–4, Capacity. Ask: what’s already on your plate, and where would this actually fit. Get an honest inventory, not a polite yes.
3. Minutes 4–6, Decision rights. Name three things out loud: what they can decide alone, what needs a heads-up first, and what triggers an automatic escalation.
4. Minutes 6–8, Definition of done. Agree on concrete deliverables, format, and who reviews what, before work starts, not after.
5. Minutes 8–10, Next check-in. Lock an exact day and format for the next conversation. Not "soon." A date.

Run it in this order, every time. Skipping a step doesn’t save time, it just moves the missing conversation to a worse moment later.

What Most People Get Wrong in the Handoff

Here is the sharp one. Most people think the handshake is where you solve problems. It is not. It is where you surface them and assign them, then get out of the way.

Borrow a rule from well-run team huddles: do not solve problems during the check-in itself. The check-in exists to validate what was decided, confirm who owns the next move, and flag risk early. The moment it turns into a live problem-solving session, it stops being ten minutes and starts eating the calendar, and the person you delegated to learns that bringing up a snag means losing an hour, so next time they just won’t mention it.

The fix is almost embarrassingly simple. When a problem surfaces, name it, name who owns solving it, and set a separate time to actually work it. That’s the whole move. The check-in stays short and honest. The problem still gets solved, just not at the expense of the one habit that keeps delegation from quietly falling apart, which is validating decisions out loud and noting, in plain language, who is taking responsibility for what happens next.

When Something Slips, Tighten the System, Don’t Blame the Person

Work will still slip sometimes. That is not proof the handshake failed. It is data about which checkpoint needs tightening.

If the deliverable missed the mark, go back to the intent questions, they were probably too vague or skipped entirely. If someone got buried, the capacity check was likely too soft or too rushed. If a decision caused friction, the decision rights were never actually named, just assumed. If "done" turned into a debate, the definition needed more specificity, not more trust. And if the whole thing quietly drifted off track, the check-in cadence was too far apart for how uncertain the work actually was.

Run this as a weekly habit, not a one-time fix. Each slip tells you exactly which of the five checkpoints needs a sharper question next time. Results vary by team and by how consistently the habit gets used, but the pattern holds: teams that treat missed handoffs as a signal to refine the script, rather than a reason to blame the person, tend to see fewer repeat surprises over time.

Delegation was never really about handing off a task. It was always about handing off clarity, and clarity either gets built in ten minutes up front, or it gets rebuilt later, under worse conditions, with more at stake. Skip the ten minutes enough times, and you won’t just lose a deadline — you’ll lose the person who stops volunteering for the next handoff, because they’ve learned that saying yes to you is a bet against their own time. That cost is already showing up on your team, whether you’re tracking it or not.