The five things every good delegation contains

You hand off a task. Three days later it comes back technically done, and also not what you meant at all. Not lazy-wrong, not incompetent-wrong: wrong in the specific way that happens when someone had to guess what you meant and guessed differently than you would have. So you rewrite half of it yourself, quietly decide delegation takes longer than doing it, and pull the task back onto your own plate for good.

That is not a people problem. It is a brief problem, and it is fixable with the same five ingredients every time, whether you are handing the work to a freelancer, a new hire, or an AI operator.

The five things a brief needs

Goal: what done means. Not “write the newsletter,” but “a newsletter under 400 words that gets a client to book a call, out by 9am Thursday.” A goal without a finish line invites a guess, and the guess is rarely the one you had in your head.

Examples: what good looks like, in your voice. Say you run a copywriting studio and every brief you send says “write it in our voice.” That sentence has never once produced work in your voice, because your voice is not a sentence, it is a pattern, and patterns need samples. Attach three emails you actually sent. The examples do the explaining the adjectives cannot.

Checklist: the steps that never get skipped. Every recurring task has two or three non-negotiables buried in your head that never make it into the instructions, because they feel too obvious to write down. Always reattach the invoice. Always tag the account manager. Always check the discount code still works before the newsletter goes out. Write them down once and nobody has to hold them in memory again, including you.

Tools: what the person is allowed to touch. A brief without a clear boundary either gets nothing done, because whoever is doing the work is too nervous to act without checking in, or gets too much done, because nobody said where to stop. Say which accounts, which folders, which spend limits are in bounds, and the rest of the anxiety resolves itself.

Skills: the know-how the job pulls in. Some tasks need more than instructions; they need expertise applied at the right moment. A refund policy, a tone guide, a pricing table. You do not want to re-explain your cancellation policy inside every single support reply brief. You want it sitting somewhere the work can reach for it exactly when it is relevant, and nowhere else.

Why this works on anyone you delegate to

Notice none of that is specific to software. A new hire needs the same five things in their first week, usually delivered badly, over a rushed onboarding call and a scattered doc nobody rereads. A freelancer needs them in the kickoff brief, or you get three rounds of revisions that were really just you filling in the gaps you left the first time. Good delegation was never about finding someone reliable enough to read your mind. It was about writing the five things down so nobody has to.

This is also, not coincidentally, close to how an AI operator approaches a task. Amber runs on the same five layers: a goal that defines done, examples that carry your voice, a checklist for the steps that cannot slip, a clear line on what she is allowed to touch, and the skills she pulls in when a job calls for them. Say you run a small studio and hand her the Thursday newsletter. The goal states what it needs to accomplish. The examples are three newsletters you already sent. The checklist has the two things you always forget to check. The tools list says which email account and which discount codes are fair game. None of that is exotic. It is just delegation, written down instead of left in your head, so the work can run on it consistently.

Why it usually stays undone

Because writing a real brief takes ten minutes the first time and feels like overhead, while a two-line instruction feels efficient. So we send the two-line version, and the ten minutes gets spent later anyway, on revisions and re-explanations and rewriting the draft yourself late at night, except now it is scattered across every handoff and none of it is written down for next time.

The fix is not more diligence. It is treating the brief as a one-time asset instead of a one-time message. Once the goal, examples, checklist, tools, and skills exist for a task, they exist for every future instance of that task. That is the real difference between delegating a task and delegating a role.

Write the five layers once

Pick one task you keep re-explaining: the newsletter, the invoice chase, the lead reply. Write its five layers down today, even if you have nobody to hand it to yet. You will use it the next time you delegate, and you will use it again if you decide to stop doing that task by hand at all. It is the same document either way, and if you want to see what a full brief looks like once all five layers are in place and running on their own, the anatomy is laid out here.