How to Delegate Tasks: What to Hand Off and How to Follow Up

Knowing how to delegate tasks comes down to three things: choosing work that someone else can do well enough, handing it over with a clear result, deadline and level of authority, and agreeing up front when you will check in. Most delegation fails at the handoff, not in the choice of person.

Below you will find how to pick what to delegate, a quick payback test, a handoff checklist with a sample message, a follow-up schedule, and a simple way to track who owns what.

What Tasks to Delegate

Start with the Delegate box of an Eisenhower matrix: tasks that are urgent but do not need your judgment. Our Eisenhower matrix examples show what lands there for a manager, a freelancer, a student and a parent. The D in the ABCDE method marks the same kind of task, and how to prioritize tasks compares both methods. Then look further down your list with this table:

Delegate	Keep
Recurring admin: reports, bookings, ordering, data entry	Performance feedback and difficult conversations
Tasks that are someone else’s strength	Confidential or legally sensitive work
Research, first drafts and option lists	Final decisions on direction and budget
Stretch work for someone ready to grow	The first response to a crisis you are accountable for
Urgent tasks that do not need your judgment	Work you promised to do personally

Recurring tasks are the best place to start, because one good handoff pays off every week. If your routine work is scattered, how to manage recurring tasks shows how to list it with dates first.

The Payback Test

Delegating takes time up front: explaining, showing, reviewing. A quick sum tells you whether it is worth it.

Say a weekly report takes you 1.5 hours. Training someone takes 6 hours in total (a walkthrough, one report done together, and reviews of their first three), and afterwards you spend 15 minutes a week checking it. You save 1.25 hours a week, so the training pays for itself after 4.8 weeks, about five reports (6 ÷ 1.25). Over a year you get back 59 hours: 52 weeks × 1.25 hours, minus the 6 hours of training.

A one-off task that takes you 30 minutes and would take an hour to explain fails the test, unless the point is to teach the skill.

Choose the Person and the Level of Authority

Pick someone with the skill, or the ability to learn it, and the time. Ask what comes off their plate to make room, rather than assuming there is space. Then say out loud which of these levels you mean:

1. Do it as described. Follow the steps; check with me before changing anything.
2. Look into it. Gather the facts and options; I decide.
3. Recommend. Bring me your recommendation; I approve it.
4. Decide and tell me. Make the call, then let me know what you did.
5. Own it. Decide and act; we cover it at our usual check-in.

Many handoffs go wrong because the level was never said. The other person thinks they are at level 4, you meant level 2, and both of you end up frustrated. Start new people at 1 or 2 and move up as trust builds.

How to Delegate Tasks: The Handoff Checklist

Go through this delegation checklist every time, in writing, even for small tasks:

• The result. What done looks like, with an example if one exists.
• Why it matters. One sentence on who uses the result and for what.
• Deadline and milestones. A date and time, never “ASAP”, plus a checkpoint for longer work.
• Authority level. From the list above.
• Budget and resources. What they may spend, the hours it should take, the tools to use.
• Access. Logins, files and contacts, sent before the start date.
• Who to ask. You, or someone closer to the work.
• Check-in dates. Agreed now and put in both calendars.
• How to report. A status in the task list, a short email or a 10-minute call.
• What to do if blocked. When to stop and ask, and when to work around it.

Here is what that looks like as a message:

Can you take over the weekly analytics report, starting Friday, October 9? The result is the same one-page summary the director gets now; last week’s is in the shared folder as an example. It feeds her Monday planning, so it needs to reach her by 4 p.m. on Fridays, and it should take about 90 minutes. You decide what to highlight each week, but flag any figure that drops more than 10% to me before it goes out. I’ll walk you through the data sources on Tuesday and review your first three reports before they are sent. After that, we’ll check in for 10 minutes on the first Monday of each month. Mark it done in the task list once it’s sent, and if a data source is broken, message me rather than working around it.

That covers the result, the reason, the deadline, the time it should take, the authority, the check-ins, the reporting and what to do when blocked. Send the logins and files in the same message so nothing waits on you.

How Often to Follow Up

Agree the follow-up schedule at the handoff so check-ins feel planned, not suspicious. Base it on the length of the task and on how familiar the person is with it:

Task length	Experienced with this kind of task	New to it
Under a week	Once, at the halfway point	Day 1, then halfway
One to four weeks	Weekly	Twice in the first week, then weekly
Over a month	Every two weeks, plus each milestone	Weekly, plus each milestone
Recurring	After the first two runs, then monthly	Each of the first three runs, then monthly

For example, a 10-working-day task handed to someone new on Monday, October 5, would be checked on Tuesday, October 6 (questions and a confirmed start), Friday, October 9 (halfway), Wednesday, October 14 (the last stretch) and at the deadline on Friday, October 16.

In each check-in, ask questions instead of reviewing every detail: what is done, what is left, and is anything in the way? If you find yourself redoing their work, the problem is usually the description of done, and that is what to fix next time.

Delegating Tasks at Work: Track Owners in Your Task List

A delegated task you cannot see is a task you will chase from memory. Add an owner and a check-in date to your task list:

Task	Owner	Delegated on	Due	Next check-in	Status
Weekly analytics report	Priya	Oct 5	Oct 9	Oct 8	In progress
Book the workshop venue	Marco	Oct 5	Oct 16	Oct 9	Not started
Supplier price comparison	Priya	Sep 28	Oct 12	Oct 7	In progress
Update the onboarding checklist	Lena	Sep 21	Oct 2		Done

With column A for Task, B for Owner, E for Next check-in and F for Status, two formulas cover most needs.

Open tasks per person, the same in both apps: =COUNTIFS(B2:B100, "Priya", F2:F100, "<>Done"). For the table above it returns 2. Check this before you hand anyone something new.

Check-ins due today or earlier:

• Google Sheets: =IFERROR(FILTER(A2:B100, E2:E100<>"", E2:E100<=TODAY(), F2:F100<>"Done"), "No check-ins due")
• Excel (2021 or Microsoft 365): =FILTER(A2:B100, (E2:E100<>"")*(E2:E100<=TODAY())*(F2:F100<>"Done"), "No check-ins due")

The E2:E100<>"" condition matters, because an empty date counts as earlier than today and would fill the list with rows that have no check-in.

If you run projects in our project management spreadsheet, the Eisenhower matrix template fills its To Delegate box from tasks ticked urgent but not important, and each task’s owner field lets the task filter and Kanban board show one person’s list. For reporting on delegated work across a whole project, how to track project progress covers percent complete and status colors.

Common Delegation Mistakes

• Handing over the task but not the authority, so every small choice comes back to you.
• Setting “ASAP” instead of a date, which means a different deadline to each person.
• Taking the task back at the first mistake, which teaches everyone to wait for you.
• Delegating only the dull work. Mix in tasks that build skills, so a handoff feels like trust rather than a dumping ground.
• Checking in more often than agreed. Unplanned check-ins read as distrust, even when they are meant as help.

This week, pick one recurring task that passes the payback test, write the handoff with the checklist above, and put the first check-in in both calendars before you send it.