How to delegate work clearly with AI

Decide what done looks like before you write anything

Most delegation problems start before the handover. You know roughly what you want, you explain it in a hallway conversation, and a week later the result answers a slightly different question. Before asking AI for help, write one sentence describing the result you will accept: what it contains, who it is for, and how you will judge it.

This sentence is the most important input you give the model. A vague assignment produces a polished but vague brief, and polish makes the vagueness harder to notice. If you cannot describe the outcome yet, the work is not ready to delegate; it may need a short scoping conversation first.

Vague: "Look into venues for the offsite."
Clear: "Three venues compared on price, capacity, travel time, and accessibility, with a recommendation I can approve in one meeting."

Say which decisions are theirs

A person who has to check every choice with you has not really been given the work. A person who was never told the limits will either freeze or overstep. Sort the decisions into three groups: what they can decide alone, what they should discuss with you first, and what you keep. Budget commitments, anything signed, and anything visible to clients usually belong in the last group.

The delegation brief template asks for these levels explicitly, along with constraints and non-goals. Paste the real limits, such as a budget ceiling or a rule that no deposit is paid without approval. If a limit is not decided yet, say so; the brief should show it as an open question rather than as a rule the AI made up.

Plan checkpoints in proportion to the risk

A deadline alone tells you whether the work is late, not whether it is heading the wrong way. Add one checkpoint early, when a misunderstanding is still cheap to correct, and others only where a decision needs your approval. For a small task, a single check-in after the first day of work may be enough.

For larger assignments, give the person the project plan template as a starting point and let them draft the milestones themselves. Their plan shows you how they understood the brief. If their milestones do not lead to the outcome you described, discuss it now rather than at the deadline.

Hand over the brief in a conversation

Do not send an AI-written brief and consider the task delegated. Walk through it together, ideally in a short call. Ask questions that check understanding without asking for a restatement, such as what they would do first or which part they expect to be hardest. The brief template suggests some, but the answers matter more than the wording.

Before pasting anything into an AI tool, remove details you would not share outside your team: salaries, performance concerns, or client information. A delegation brief rarely needs them, and they do not belong in a third-party tool unless your company has approved it for that data.

Follow up on decisions, not on activity

At each checkpoint, focus on what has been decided, what is blocked, and what needs your input. If you take notes during these check-ins, the meeting notes template can turn them into a short list of decisions, owners, and open questions to send afterward. Check the list against your notes before sharing it, because a summary can attribute a decision to the wrong person.

When the work is done, compare the result with the outcome sentence you wrote at the start. If something was missing, ask whether the brief was unclear before concluding that the person was. Then update your saved brief so the next handover starts from a better version.