A manager asks an employee to prepare a client proposal, then chooses the wording, reads every email and finally rewrites the document. The task has formally been handed over, but the work still rests on the manager.

For delegation to work, the person needs a clear result and the right to make decisions. Here is an approach for a small team: what to hand over first, how to set boundaries and where to put checkpoints.

In short

Hand over an agreement along with the assignment: the result, deadline, materials, authority and review point. Check where a problem can still be fixed, not after the deadline has been missed.

How delegating differs from assigning

When you delegate, you hand over the work together with context, resources and agreed authority. The person owns the agreed result; you provide the conditions and review at points set in advance.

Test yourself with one question: what can the employee decide without me? If the answer is "nothing", you take part in every step, however neatly the assignment is written. You don't have to grant complete freedom, but you do have to name the boundaries up front.

What to hand over first

Start with work whose result you can describe and verify: research, a regular report, a draft, arranging a meeting, updating materials. Before handing it over, ask yourself five questions:

Question If the answer is no
Can you describe the finished result? Clarify expectations first
Does the person have time and the skills needed? Adjust workload, deadline or scope, or arrange training
Can you give access to the materials? Prepare access before work starts
Is the cost of an error acceptable with these checks? Add an early review or narrow independent authority
Is it clear which decisions the person makes alone? Write down the boundaries

It isn't only boring routine that can be delegated: a development task works too, if there is time for discussion and an interim review. Hand over high-risk work in stages and keep the critical decisions with the person authorized to make them.

What to write down before work starts

The basis is the same as in our task assignment template: the result, why it's needed, acceptance criteria and a due date. Delegation adds three items: resources (time, budget, access, help from colleagues), the boundaries of independence and an escalation rule, meaning when the person should report a problem without waiting for the review.

Example: a client proposal

Suppose a colleague is preparing their first proposal for a new client. "Get the proposal done by Friday" leaves too many decisions open. An agreement might look like this:

Field Agreement
Result A proposal PDF and the editable source in the shared folder
Why The client is comparing options and choosing a supplier
Done when Scope, cost, dates, assumptions and contacts are included
Materials Meeting recording, approved price list, document template
Decides alone Structure, wording, requests for missing information from colleagues
Needs approval Discounts, changes to scope, commitments outside the price list
Review Structure and calculations by Wednesday at 3 pm; final version by Friday at noon
Report sooner Source information is missing or the deadline no longer looks achievable

Ask the employee to say briefly what they are preparing and where they will start. If it turns out they are waiting for you to calculate the price, it's better to learn that today than on Wednesday.

Follow-up without checking every step

How often to check depends on how new the task is and how much a mistake costs. An experienced employee with a familiar report needs only a review of the finished result. New work needs an early version while the direction is still easy to change.

A checkpoint needs a subject: "we'll look at the structure and calculations", not just "let's have a call". The employee knows what to prepare, and you can give useful feedback.

A short written status is a convenient way to report progress, for example:

Done: collected the inputs and calculated the base price. Next: format the proposal options. Blocker: the supplier hasn't given a delivery date. Help needed: an answer from purchasing by 4 pm. Forecast: I can still make Wednesday's draft.

Send a status like this at the agreed checkpoint or when the forecast changes, not every hour.

What to do when the deadline is at risk

First establish what is finished, what remains, what information is missing and how long the next step will take. Then choose a solution together:

  • reduce the scope while keeping the necessary result;
  • reschedule the employee's less important work;
  • provide the missing access or bring in help;
  • agree on a new deadline with the person waiting for the result.

Record the change in the task. If you take back part of the work, name which part: otherwise two people do the same piece and a third has no owner.

What sends the work back to the manager

  • Handing over without access. The person looks for files and permissions instead of working.
  • Approving every small decision. The employee stops deciding alone, because everything gets checked again anyway.
  • Adding a task to a full workload. The day has no more hours than before, so revisit the queue.
  • Changing the criteria after submission. Call a new requirement a new requirement and discuss at once how it moves the deadline.
  • Quietly rewriting the result. Say which criterion wasn't met and let the person fix it, otherwise they never learn where their decision differed from your expectations.

Where to keep delegated tasks

The agreement should be available to both sides. A shared document or a tracker will do, and if there are several parallel assignments, a kanban board is convenient.

In iTasker you can create the assignment from a message in a linked Telegram chat by replying to it with /new. Then open the task, write the result, decision boundaries and checkpoint in the description, choose an assignee from the project members and set the due date. The status on the board shows where the work stands, and changes to the requirements are easy to record in the same card.

Launch the iTasker bot