What a clear handoff does
Most problems with handing work to someone else come from a gap between what the giver pictured and what the receiver understood. The task gets done, but not the way it was imagined, or too late, or it stalls while the receiver waits for a decision nobody told them they could make.
Good task delegation closes that gap before work begins. It takes a few minutes, and it usually saves far more time than it costs. The sections below walk through the three things worth stating every time: the outcome, the deadline and the level of authority.
This applies at work, in volunteer groups and at home. Policies about who may assign work to whom vary by employer, so check your own workplace’s rules and reporting lines before handing off anything formal.
Start with the outcome, not the steps
Describe what “done” looks like. A result is easier to aim at than a list of instructions, and it leaves room for the other person to use their own judgment.
Compare two requests:
- “Update the spreadsheet with the new numbers.”
- “I need a one-page summary of last quarter’s costs that my manager can read in two minutes, with the three biggest changes highlighted.”
The second tells the person what the work is for, who will use it and roughly how big it should be. They can make sensible choices on their own, such as leaving out detail that would not help that reader.
A few things are worth including:
- The purpose. One sentence on why this matters helps people resolve small questions without asking you.
- The format. A document, a short message, a list, a finished form.
- What good looks like. If you have an earlier example, say so. If you have a quality bar, such as “numbers checked against the source”, name it.
- What is out of scope. Saying what you do not need prevents a lot of extra effort.
When a task has many moving parts, it can help to split it first, in the same way you would with project breakdown for your own large projects. Delegating a clear piece is easier than delegating a vague whole.
Set a deadline that is real
A deadline needs two parts: a date and a reason or context. “Friday” is clearer than “soon”, and “Friday at noon, because I send the report that afternoon” is clearer still.
Some practical points:
- Ask how long they think it will take. People often know their own workload and skills better than you do. Time estimates are notoriously optimistic for everyone, so treat the first answer as a starting point and be ready to adjust.
- Separate the hard deadline from the target. If you need it Friday but would like a draft Wednesday, say both.
- Check what else is on their plate. Someone juggling competing demands may need you to agree on what moves aside, or the new task will quietly slip.
- Leave a little slack. If you set the due date for the day you need the result, any delay becomes your problem.
If the other person says the date is not realistic, that is useful information, not resistance. Adjusting the scope or the date at the start is much cheaper than discovering the problem on the due date.
Say how much authority they have
This is the part people skip most often. When someone does not know what they are allowed to decide, they either ask about everything, which wastes both your time, or decide too much and surprise you.
A simple way to think about it is a few levels:
- Look into it and report back. They gather information; you decide.
- Recommend an option. They suggest what to do and why; you approve.
- Decide, then tell me. They act, and let you know afterward.
- Decide and handle it. They own it and only update you if something unusual happens.
You do not need these exact labels. What matters is naming the level out loud, such as “You can choose the vendor for anything under the amount we discussed, and just let me know. Anything above that, send me a recommendation first.”
Also mention constraints that cannot be changed, like a fixed budget, a required approval or a legal or policy requirement. Hidden constraints are a common reason finished work gets rejected.
If the level changes as trust builds, that is normal. Many people start new delegates at a lower level and move up as they both learn how the work goes.
Agree on how you will stay in touch
Decide before the work starts how and when you will connect, so that neither of you has to guess. The right rhythm depends on the size of the task and the person’s experience. Agreeing on progress check-ins at natural milestones is usually better than asking for updates at random moments, and regular one-on-one meetings can be a convenient place to cover them.
Also say how to reach you with questions and how quickly you can usually reply. If a small question can wait for the next check-in, tell them. If something is urgent, tell them what counts as urgent and which communication channels you prefer for it.
Confirm understanding without quizzing
After explaining, ask the other person to say back what they will do, in their own words. Phrase it as a check on your own explanation: “Just so I know I was clear, how are you planning to approach it?” That framing keeps it from sounding like a test.
Watch for questions you did not expect. They often point to a gap in how you described the work, not a gap in their ability.
A short checklist
Before you hand something off, see whether you can answer these in a sentence or two each:
- What is the finished result, and who will use it?
- When is it due, and why that date?
- What can they decide alone, and what needs my approval?
- What resources, files or contacts do they need?
- When will we next check in?
If you cannot answer one of them, that is the part to clarify before you delegate, not after.
When it does not go as planned
Sometimes the result comes back different from what you pictured. Start by asking whether the instructions allowed for the result you got. If they did, the fix is a clearer description next time, and some work feedback focused on the specific differences. If the person simply missed something, a calm conversation about what happened is usually more productive than redoing it quietly yourself.
Delegating well is a skill that improves with repetition, and there is no single correct method. Small, low-risk tasks are a sensible place to practice, and it is fine to adjust your approach as you learn what each person needs.