To delegate a task, pick work that repeats and has a clear finish line, hand it to the right person or tool with a short written brief, agree how much freedom they have, and check the result instead of the method. Most people skip the brief and the freedom agreement, which is why delegated work comes back wrong and ends up done twice. This guide walks through the six steps, gives you a brief template you can copy, and shows which tasks you can now hand to an AI assistant.
Why is delegating tasks so hard?
Delegating feels slower at first. Writing instructions takes longer than doing a small task yourself, the first attempt rarely matches your standard, and checking someone else's work feels like a second job. So the task stays on your list, and so does the next one.
The cost shows up later. Every task you keep is time you aren't spending on the work only you can do. In a Gallup study of 143 CEOs on the Inc. 500 list, those with strong delegation talent generated 33% more revenue in 2013 than those with low or limited delegation talent ($8 million versus $6 million).
The good news is that delegation is a process, not a personality trait. The six steps below make it repeatable.
What tasks should you delegate?
Run each task through four questions. A task that passes all four is a safe first handoff.
| Question | Why it matters |
|---|---|
| Does it repeat? | Writing a brief once pays off every time the task comes back. |
| Does it have a clear finish line? | "Send the invoice reminders" can be checked. "Improve our marketing" can't. |
| Could someone else do it 80% as well? | If yes, the last 20% isn't worth your hour. |
| Is a mistake cheap to fix? | Start with work where an error costs minutes, not a client. |
Keep the work that depends on you: strategy, hiring and firing decisions, sensitive conversations, and relationships only you hold. You can still delegate the preparation for those, such as the research or a first draft.
Step 1: List everything you do for a week
Write down every task as you do it for five working days, including the small ones: replying to the same three questions, chasing an invoice, moving notes into the CRM, preparing for calls. Small tasks are the ones that disappear from memory and quietly eat the day.
Note roughly how long each one took. You'll want those numbers in Step 2.
Step 2: Sort each task into keep, delegate, automate or drop
Go down the list and give each task one label:
- Keep: only you can do it, or the stakes are too high to hand off.
- Delegate: it needs judgment or writing, but someone else can do it with a good brief.
- Automate: it's the same steps every time, so software can run it on a schedule.
- Drop: nobody would notice if it stopped. These are more common than you'd expect.
Then sort the delegate and automate piles by time saved per week. Start at the top.
Step 3: Pick the right owner
The owner can be a teammate, a human assistant or an AI tool. Match the owner to the task, not the other way round.
| Owner | Best for | Watch out for |
|---|---|---|
| A teammate | Work that builds their skills or sits in their area | Their existing workload; delegating isn't dumping |
| A human assistant | Calls, errands, judgment calls with people, anything in the physical world | Onboarding time and cost |
| An AI assistant or agent | Repetitive inbox, scheduling, research, reporting and follow-up work in your apps | It should ask before sending anything in your name |
If you hand a task to a person, check they have the time and the access they'll need before you write the brief.
Step 4: Write a handoff brief
A brief turns "can you handle this?" into work that comes back right. Answer five questions in writing, even if it's three lines in a chat message:
- Outcome: what should exist when this is done?
- Context: why does it matter, and who is it for?
- Done looks like: an example, a format or a checklist.
- Deadline: when you need it, and when you want a first look.
- Limits: what they shouldn't do, send or spend without checking with you.
Here's a filled-in example you can copy:
Task: Chase the overdue Northwind invoice.
Outcome: a polite reminder email sent to their accounts team.
Context: invoice #1042 for $2,400 was due on September 28 and they're a good long-term client, so keep it friendly.
Done looks like: a short email with the invoice number, amount and due date, offering to resend the PDF.
Deadline: today.
Limits: don't mention late fees, and show me the draft before it goes out.
The same brief works whether the owner is a person or an AI agent. That's the point: if you can describe it this clearly, you can hand it to either.
Step 5: Agree how much freedom they have
Most delegation goes wrong here. You expected a draft and they sent it, or you expected it done and they kept asking. Pick one of three levels before the work starts:
- Ask first: prepare it, then wait for my OK before acting. Use this for anything external or hard to undo.
- Do it, then tell me: go ahead and report back. Use this once you trust the result.
- Just do it: no report needed. Use this for routine work that has gone right several times.
Move a task up a level as it proves itself. A reminder email might start at "ask first" and reach "just do it" after a month.
Step 6: Check the result, then make it a habit
Review the output against the brief, not against how you would have done it. If it misses, fix the brief (usually the "done looks like" or the limits) rather than taking the task back.
Once a task has gone right a few times, make it recurring. A weekly invoice chase, a Friday status update or a morning inbox sort should run on a schedule, not wait for you to remember to hand it off again.
Which tasks can you hand to AI?
AI assistants and agents can now handle a lot of the delegate and automate piles, especially work that happens inside your apps. A rule of thumb: hand AI the preparation and the routine, keep the relationship and the decision.
| Hand to AI | Keep for a person |
|---|---|
| Sorting the inbox and drafting replies | Negotiating with a client |
| Meeting prep: who's attending, recent threads, talking points | Running the meeting |
| Research briefs on a company or topic | Deciding whether to pursue the deal |
| Overdue-invoice reminders | Handling a dispute over the invoice |
| Weekly reports and status updates | Explaining bad news to the team |
| Tagging and routing support tickets | Calling an upset customer |
On DeskFerry, delegating to AI follows the same six steps. You write the task in plain English, the way you would in a brief, and give it to your AI assistant or to a specialist AI agent built for that job. Anything that would go out in your name, like an email or a Slack message, waits on your Desk for approval, which is the "ask first" level from Step 5. Tasks you hand off every week can run on a schedule. For a closer look at how assistants compare with human help, see AI personal assistant vs virtual assistant.
Common delegation mistakes
- Delegating only what you hate. Hand off what someone else can do well, not just what's boring. Otherwise people learn that delegated work is the leftovers.
- Skipping the brief. A one-line request saves you two minutes and costs an hour of rework.
- Not agreeing the level of freedom. Most "they overstepped" and "they keep asking me" problems come from this.
- Taking the task back after one miss. Fix the brief and try again. The second attempt is almost always better.
- Checking the method instead of the result. If the outcome matches the brief, the approach was fine.
Start with one task this week
Pick the most repetitive task from your list, write a five-line brief, agree the level of freedom, and hand it off. Once that goes well, do the next one. Delegation compounds: every task that leaves your list for good gives you back time every week.
