Delegate So It Comes Back Right

When to use it

The user has a piece of work to hand to someone else (a report, an analysis, a supplier search, a customer reply, an event, a hiring round) and wants it to come back right the first time. They describe the task in a few lines and get a brief the person can start from.

Also for fixing a brief the user already wrote, or for diagnosing why a delegated task came back wrong: the same eight parts show where the gap was.

Not for: planning the user's own week (the Weekly Planner pack does that), writing a job description, or a standing process document (that is an SOP).

What it asks you

Ask in one message, numbered. Work from what comes back.

1. What is the task, in one or two lines, and who is it for in the end (a client, a boss, a team)?
2. Who is doing it, and how often have they done something like this before: never, once or twice, many times?
3. When is it needed, and is that date fixed or your preference?
4. What would make you say "yes, that is it" when you see the result? Describe the finished thing: format, length, audience, the question it must answer.
5. What must they not do, spend, promise, send or change without asking you?
6. Which decisions are theirs to make alone?
7. What do you already know that they do not: past attempts, people to speak to, files, traps?
8. How much of your time can this take: minutes per week for checkpoints?

A vague answer to 4 gets one follow-up: "If two versions came back, what would make you pick one over the other?" If they still cannot say, write the done test from the audience and the question the work must answer, mark it "done test: draft, confirm", and tell the user the brief will fail without it.

Never invent a deadline, a budget, a name or a past event. Write "not given" where a fact is missing and the brief needs it.

What comes back

Plain text, ready to paste into a message or document.

DELEGATION BRIEF: task name To: name From: name Needed by: date, and what it is for

Outcome Done test Why it matters Your decisions: Decide alone / Decide and tell me / Ask me first (three short lists) Limits What I already know Checkpoints (date, what you show me, how) Questions to ask me before you start (with answers where I have them) How to reach me when stuck

(N words; range 250 to 500, or under 150 for the short form) Gaps: each "not given" item in one line, with why the brief needs it (only if any). Next: one line naming the single most useful next step.

For a brief the user wrote: the fixed brief first, then "What changed:" in at most five lines, the missing part first.

For a post-mortem on work that came back wrong: the eight parts as a table with "present", "weak" or "missing" against each, then the two lines that would have prevented it.

• 00_START_HERE.pdf: the two-minute set-up for each AI.
• 1 - Skill: delegate-so-it-comes-back-right.zip, one upload to Claude, ChatGPT, Gemini, Grok or Microsoft 365 Copilot. It switches on by itself when this job comes up.
• 2 - Text file for any AI: the same Move as one .txt. Attach it to any chat, on any plan, and type "Follow this file".

It drafts, you read and send. It never contacts anyone for you and never invents a fact, a number or proof.

A Move is a single play. The whole function in a box is Weekly Planner, an agent pack with up to 8 skills.