How to assign a task to an employee: a template and examples

"Prepare the sales report, it's urgent." Three days later the employee brings a report for the wrong period in the wrong format, and each side is sure they explained everything. Deadlines usually slip because of a task that two people understood differently.
In short
A good task answers six questions: what to deliver, why, how to tell it's done, by when, who owns it and what already exists. Below you'll find a template with these fields, one worked example and a way to check that you were understood.
Six questions every task should answer
If one of them has no answer, the assignee fills the gap themselves, and not always the way you wanted.
- What to deliver. A concrete result, not a process: not "work on the presentation" but "a 10-slide presentation for the client meeting".
- Why. One sentence is enough. When people know the goal, they settle the small things you didn't describe.
- How to tell it's done. Acceptance criteria: what exactly you'll check when you accept the work.
- By when. A date and a time instead of "soon" or "whenever you're ready".
- Who owns it. One assignee. A task assigned to two people, in practice, belongs to no one.
- What already exists. Links, files and the person to ask for details.
A template
Copy it and fill it in. Three or four lines are enough for a small task; a big one needs every field.
Task: <verb + result, in one line>
Why: <the goal in one sentence>
Result: <what should come out, in what form and where it lives>
Done when:
- <checkable criterion 1>
- <checkable criterion 2>
Due: <date and time>
Assignee: <name>
Materials: <links, files, contacts>
Constraints: <budget, format, what not to do>
Start the title with a verb: "Prepare", "Approve", "Check". The action is visible at once, and titles in a task list make sense without explanation.
One report, two ways to assign it
Bad:
Andrew, prepare a sales report, it's urgent.
It's unclear which period, what format, who it's for and what "urgent" means.
Good:
| Field | Value |
|---|---|
| Task | Prepare the September sales report |
| Why | We'll discuss it at Thursday's meeting and decide where to move the ad budget |
| Result | A spreadsheet in the shared "Reports" folder, one sheet: sales by channel compared with August |
| Done when | • revenue and order count for every channel • the change vs August in percent • three takeaways at the bottom: what grew, what fell, and why |
| Due | Wednesday, 6 pm |
| Assignee | Andrew |
| Materials | The September CRM export, last month's report in the same folder |
The second version takes a couple of minutes longer to write. In return Andrew won't need to ask questions halfway through, and you won't need to ask for a redo.

How to check you were understood
Almost everyone answers "yes" to "Is that clear?". Ask for a retelling instead:
- "Tell me in your own words what you'll do and what you'll deliver."
- "Where will you start?"
- "What could go wrong?"
If the retelling doesn't match what you meant, it's better to find out in the first minute than on the due date.
Due dates, stages and priority
One due date is enough for a short task. If the work takes more than two or three days, split it into stages with checkpoints: a draft, a first version, the final. Set the first checkpoint early, while changing course is still cheap. The assignee then sees their progress, and you see where things stalled without asking "so, how's it going?".
If the person already has work, a new task has to arrive with a priority: "This is more important than what you're doing, put that aside" or "Pick it up after the report". Otherwise they'll choose for themselves, and you'll find out from a missed deadline. A simple rule helps too: no more than two or three tasks in progress per person, with the rest waiting in an ordered queue.
Control without micromanagement
Check the result and the checkpoints, not every step. Agree in advance:
- where the assignee updates the status, in the tracker or the chat, so you don't have to ask;
- when they should message you themselves: the task is blocked, the due date is at risk, questions came up;
- when you'll look at the intermediate result.
If you ask "How's it going?" every day, your status system isn't working. Fix the system rather than the frequency of the questions.
Mistakes the template doesn't catch
The template covers the due date, the criteria and the assignee. The rest happens after the task is assigned:
- A task disguised as a hint. "It would be great if…" may not register as a task at all.
- Several tasks in one message. A week later nobody remembers the second point. One task, one record.
- Assigning in a private chat with no record. A week later you and the employee will remember the conversation differently. The task should live where both of you can see it.
- Changing the requirements without saying so. If they change, update the task and tell the assignee directly.
- Taking the task back silently. If the result doesn't fit, say what exactly to fix instead of redoing it yourself.
How this looks in iTasker
The template fields exist in the task card: a title, a description (put the done criteria there), an assignee, a date and time, a priority, a reminder and a checklist for stages. The task's status shows on the board, so "in progress" and "waiting for review" don't have to be found out by asking. In the web version the card also has a change history, which settles a "but we agreed differently" argument.
You can create the task right in the work chat. In a group linked to a project, write /new Prepare the September sales report, Andrew, by Wednesday 6 pm or reply to the message with the agreement using /new. The AI parses the date; check the assignee in the card afterwards, because a name in the text is not the same as an assignment, and only a project member can be chosen.





