Delegation gives someone a defined outcome, appropriate decision authority, and the support to deliver it. Dumping work transfers a burden while leaving important expectations, resources, or decisions unresolved. The difference becomes visible in the handoff and the follow-through, not just in how politely the task is assigned.
A manager can delegate an unpopular task responsibly. A pleasant invitation to an “exciting opportunity” can still leave someone carrying work they cannot complete. Before judging the label, look at whether the person knows what they own, what they can decide, and where to go when the plan stops working.
This guide focuses on handing work to another person. It complements, rather than replaces, our guides to asking for help, setting limits, and escalating an issue. The examples are illustrative workplace situations, not reports of measured results.
Delegation vs. dumping: compare the handoff
| Handoff question | Delegation | Dumping work |
|---|---|---|
| What is the expected result? | A deliverable and an understandable completion standard | “Just handle it” with an undisclosed standard |
| What can the person decide? | Clear authority within stated limits | Responsibility without access to necessary decisions |
| What happens to existing work? | Priorities and capacity are reviewed | Everything remains urgent and unchanged |
| What support is available? | Relevant context, access, and a named contact | Missing information and no route to resolve it |
| When will progress be reviewed? | Checkpoints matched to uncertainty and risk | No contact until a surprise final judgment |
| What if circumstances change? | A clear trigger for asking for a decision | The person absorbs every new requirement |
| Who owns the wider commitment? | Management oversight remains explicit | The delegator disappears from the outcome |
1. Define the result before discussing the method
“Take over reporting” leaves too much open. Does that mean collecting figures, checking them, designing the report, or approving the final version? Name the deliverable and its audience.
A clearer assignment is: “Prepare Friday’s draft status report using the agreed source sheet. Flag missing figures rather than estimating them. I will approve the version sent to the client.” That defines a result and preserves an important boundary.
Do not prescribe every step simply because you would do the work differently. If a method is required, explain the reason, such as an existing review process or a dependency. If the person may choose the approach, say so.
2. Give decision authority that matches the task
Someone cannot own a delivery plan while being unable to obtain estimates or request a priority decision. Specify what they can decide, what they can recommend, and what requires approval.
For example: “You can rearrange the review sessions within this week. Any change to the client delivery date needs my approval.” This gives useful freedom without pretending that every decision has moved to the recipient.
The Center for Creative Leadership’s guidance on delegation emphasizes authority alongside resources and support. The practical implication is to check whether the person can actually act on the assignment. A title such as “owner” does not provide access or approval rights by itself.
3. Resolve the priority tradeoff
A task that fits someone’s skills may still exceed their available time. Review the work they already have, the effort the new assignment may require, and the consequence of moving another commitment.
Ask: “What would need to move for you to deliver this by Thursday?” If both tasks matter, the person with the relevant authority should choose the priority or adjust resources. Avoid describing the assignment as development while expecting someone to quietly absorb an unlimited workload.
If you receive the task, make the tradeoff concrete: “I can prepare this by Thursday if the dashboard update moves to Monday. Can you confirm that priority?” For changing requirements, use the separate guide to handling scope creep.
4. Transfer the context and arrange access
Useful context includes the reason for the task, existing commitments, source documents, relevant contacts, and known constraints. Give enough information to prevent avoidable guessing without burying the recipient in an unstructured archive.
For a recurring task, show a previous example and explain which parts still apply. Arrange access through the organization’s normal process. Do not ask someone to use another person’s credentials as a shortcut.
Finish with a check of understanding: “What do you see as the first step, and what is missing before you can start?” An unanswered access request is a dependency to resolve, not evidence that the person lacks initiative. Our knowledge transfer checklist covers the supporting documentation in more detail.
5. Match checkpoints to the uncertainty
A new assignment may need an early review of the proposed approach. A familiar, repeatable task may need only an exception update. Agree on the checkpoint instead of choosing between constant monitoring and total silence.
For instance: “Send the outline on Tuesday before you build the full report. After we agree the scope, update me only if an input is missing or the date is at risk.” This gives the person space to work and an opportunity to catch a misunderstanding early.
At the review, assess the agreed result. If you introduce a new requirement, acknowledge the change and revisit effort or timing. Do not treat a previously unstated preference as something the recipient should automatically have known.
6. Name the conditions that require a decision
“Let me know if anything happens” is less useful than identifying the issues that would change the plan. A missing approval, a conflicting instruction, or an estimate beyond the agreed capacity may need a decision from someone else.
Try: “If the data owner cannot confirm the figures by Wednesday noon, flag the gap to me. I will decide whether we send a partial report or move the date.” Keep the escalation route proportionate to the work.
The recipient should bring the issue, its impact, and the decision needed. They should not have to solve a problem outside their authority before mentioning it. For a fuller message structure, see how to escalate an issue without losing ownership.
7. Keep oversight and credit visible
Delegating execution does not make the manager disappear from staffing, competing priorities, or the wider promise made to stakeholders. State who approves the outcome and who communicates changes to that promise.
The person doing the task also has responsibilities: work within the agreed limits, raise relevant risks, and report progress honestly. If something goes wrong, review the assignment, the support provided, and the execution rather than automatically blaming either side.
When the work is complete, credit the contribution accurately. Ask what should be documented for the next handoff. A difficult first attempt can reveal a missing instruction or unrealistic workload, not just an individual performance issue.
A delegation note you can adapt
Use this as a short written confirmation after the conversation. Remove fields that do not help; a small task does not need a long form.
Outcome: Draft the weekly status report for review by Thursday afternoon. Completion standard: Use confirmed figures; list gaps and decisions separately. Authority: Choose the report layout. Bring changes to scope or delivery commitments to me. Priority: Move the internal dashboard refresh to Monday, as agreed. Support: Use the shared source sheet; I will arrange the missing folder access. Checkpoint: Review the outline Tuesday. Flag missing inputs by Wednesday noon. Approval and communication: I approve the client version and communicate any revised delivery date.
Frequently asked questions
Is an urgent assignment always dumping?
No. Genuine urgency may limit preparation time. Clarify the immediate outcome, decision owner, available support, and what can wait. An emergency does not make missing authority or conflicting priorities disappear.
Can a manager delegate a task the employee does not enjoy?
Yes. Enjoyment alone does not determine whether a work assignment is appropriate. Consider the role, skills, capacity, support, and applicable organizational process. Be honest about routine work rather than dressing every task up as a special opportunity.
How do I respond when the handoff is incomplete?
Identify the missing condition: “I can prepare the draft, but I need the source figures and confirmation of who approves it.” Ask for a priority decision when commitments conflict. Address the task setup before using a label such as “dumping.”
Is delegation the same as asking a colleague for help?
No. Delegation usually assigns defined responsibility within a management or project structure. A request for help may be narrower and leave the original owner in place. See how to ask for help at work when you need assistance rather than a transfer of responsibility.