Set a delegation brief that names the next decision

On this page
  1. How to approach: Set a delegation brief that names the next decision
  2. State the outcome and the definition of done
  3. Name the source and the boundary
  4. Name the decision owner
  5. Set the review rhythm
  6. Update the brief without losing history
Delegation Operations

Published November 8, 2026

Cover image for article: Set a delegation brief that names the next decision

Set a delegation brief that names the next decision

How to approach: Set a delegation brief that names the next decision

A delegation brief is useful when it names the next decision, not just the task. The assistant needs to know what outcome is expected, which source to use, and who decides if the work changes. A brief that stops at the task description leaves the hard questions unanswered. Keep the original note beside the corrected version.

Keep the brief to one page. A long brief is usually a sign that the work has not been defined. If the brief needs a meeting to explain, the task may need to be split. Update the template when the same question appears twice.

State the outcome and the definition of done

Write the outcome in one sentence that a reviewer can test. Then write what done looks like, including the format and the audience. A brief that says prepare a report without a format or audience invites rework. A short note with four fields is easier to use than a long narrative.

Include an example of acceptable work if one exists. An example is faster than a paragraph of description. Remove any confidential detail before sharing the example. Record the exception and the person who approved it.

Name the source and the boundary

Record the system of record and the approved sources. Name what the assistant may change and what requires approval. A boundary that is only in a policy file will be missed under pressure. A control that depends on memory is not yet a control.

Include the escalation path for missing information. If the source is unavailable, the assistant should know who to ask and how quickly. Escalation is a normal step, not a failure. Separate what was observed from what was assumed.

Name the decision owner

State who decides if the work changes scope, cost, or timing. A named role is better than a department. The assistant should not have to guess who can approve a change. If the source is unclear, route the question instead of guessing.

Record the decision owner in the brief and in the task system. If the owner changes, update both. A brief that names a person who has left is worse than no name. Use the same format for every handover so the next reader can scan it.

Set the review rhythm

Decide how the work will be reviewed and how often. A first draft review is different from a final approval. The brief should say which one applies and who attends. Keep the original note beside the corrected version.

Keep the review short and focused on the definition of done. A review that expands the scope every time is a sign that the brief is incomplete. Keep the original note beside the corrected version. Test the rule on one real task before applying it to the queue.

Update the brief without losing history

When the brief changes, add a dated version rather than overwriting the original. Record what changed and who approved it. The history shows whether the work drifted or the instructions did. Use the same format for every handover so the next reader can scan it.

Review the brief after the first completed task. Ask the assistant what was unclear and update the template. A brief that improves after each use is more valuable than a perfect template nobody follows. Record the date and the source so the next reviewer can repeat the check.

Ready to delegate this kind of work?

A free consultation takes 30 minutes. Leave with a clear delegation plan.

Get Free Consultation
Set a delegation brief that names the next decision | Delegation Assistant