The short answer.
To hand a piece of your work to AI, write down five things: what it starts from, the steps in the order you do them, what to check and what to do when something is missing or odd, what the finished thing looks like, with one good example, and what you decide yourself. With those five written down, an AI assistant prepares the work the same way every time. Without them, the output changes from week to week, because the five live in your head and the assistant is guessing.
The five things fit on one page. You write the page once, save it where your assistant keeps standing instructions, and run the work from it every week in the ChatGPT, Claude, Copilot or Gemini your company already pays for. A page like that is a workflow: the assistant prepares, and you decide.
Why does it come out different every time?
AI output comes out different every time because a short request leaves the assistant to fill in everything you did not say. When you type “prepare this week’s report”, you know which file to open, which order to work in, which rows to worry about and what the page should look like. The assistant knows none of it, so it makes a reasonable guess, and next week it makes a different one.
Rewording the request changes the guess. Writing down the five things removes it: they are the decisions you make every week without noticing.
One piece of weekly work, start to finish.
Illustrative example.
Take a 30-person insurance brokerage. Every Monday, an account manager prepares the renewals list for the brokerage’s three producers: every policy renewing in the next two months, where each renewal quote stands and which clients need a call this week. She wants the assistant to prepare the draft, so she starts Monday by reviewing it.
One: what it starts from.
Write down the exact records the work starts from: the file, the export or the folder, by name, and how fresh each one has to be. “The client data” is a guess waiting to happen. “The renewals export from the policy system, run this morning” is an instruction.
The account manager’s list starts from three records:
- The renewals export.Every policy renewing in the next two months, from the brokerage’s policy system, run on Monday morning.
- The carrier quotes.Each quote received, saved in the client’s folder.
- The account notes.The last note on each client, from the same system.
Anything the work never uses goes on the page too, as a line that says so. The account manager writes: ignore marketing emails from carriers in the client folder.
Two: the steps, in the order you do them.
Write the steps of the work in the order you actually do them, one line each, starting with a verb. The order matters because each step uses what the one before it found.
- Sort the export by renewal date.Earliest first.
- Match each policy to its quote.Find the carrier quote in the client’s folder.
- Compare the quote with the expiring policy.Note any change in cover, limits or exclusions.
- Read the last account note.Pick up anything the client asked for or worried about.
- Group the policies by producer.One section per producer.
If you are writing down work a colleague does better than you, ask them to walk through three recent cases and write their order, not yours. When the know-how sits with one person covers that conversation.
Three: what to check, and what to do when something is missing or odd.
Write down every check you make and the exact action for each problem, because the checks are where an assistant guesses most. An assistant that meets a missing quote with no instruction will skip the policy, or describe a quote that does not exist.
The account manager’s checks:
- A renewal within three weeks with no quote.Put it at the top of the producer’s section, marked “quote outstanding”.
- A quote that changes cover or adds an exclusion.Flag it and quote the changed line word for word.
- A policy that was not on last week’s list.Mark it “new this week”.
- An export not run today.Stop and ask for a fresh one before preparing anything.
Add one rule that covers everything else: when a figure is missing or a record looks wrong, say so in the draft and never fill the gap.
Four: what the finished thing looks like.
Describe the finished output in a few lines, then paste one good example under the description. An example settles length, order and tone faster than any description.
The account manager writes: one page per producer, in three parts, “call this week”, “quotes in hand” and “waiting on carriers”, with one line per client giving the policy, the renewal date and what changed. Under that she pastes last month’s list, the one the producers liked best, with client names removed.
Five: what you decide yourself.
Write down the decisions that stay with you, so the assistant prepares them and never makes them. Naming them is what lets you trust the draft: you know which parts wait for you.
The account manager keeps three decisions: which clients the producers call first, whether a renewal is shopped to another carrier, and what anyone tells a client. The assistant never contacts a client or a carrier. What work should you not give to AI? sets out the work that stays with people in every workflow.
The five headings, as a blank sheet to copy.
Copy these headings into a document, fill them in for one piece of your weekly work, and save the page as your assistant’s standing instructions for that work.
- What it starts from.The exact records, by name, and how fresh each must be. What to ignore.
- The steps.In the order you do them, one line each, starting with a verb.
- What to check.Each check, and the exact action when something is missing or odd. Never fill a gap.
- What the finished thing looks like.A few lines of description, then one good example pasted in full.
- What I decide myself.The decisions the assistant prepares and never makes.
Run the sheet on last week’s work first, where you already know the right answer. Every difference between the draft and what you did points to a line on the sheet to sharpen. For work many companies do the same way, a free workflow template in the Workflows Directory gives you a filled-in sheet to start from; Are AI workflow templates enough? covers what to change in one.
What is different in a company of under 200 people.
In a company of under 200 people, the person who does the work writes the sheet, runs it and improves it, with no project around it. Most published advice assumes a central team that collects requirements and builds for everyone else. In a smaller company, nobody can write your five things as well as you can.
- Your records are already exportable.Your accounting system, your policy or order system and your shared folders export what the sheet starts from.
- Your assistant is already paid for.The sheet runs in your company’s ChatGPT, Claude, Copilot or Gemini, on the company’s account.
- Your sheet helps the next person.When you hand the work to a colleague or a new hire, the five things are already written down.
From one piece of work to the company’s plan.
One person handing one piece of work to AI is where a company’s plan starts, and the plan decides which work across every team gets written down next. How organizations plan their use of AI sets out the method: plan it, develop the workflows, deploy them. We have a plan. How do we build the first AI workflow? covers the same work from the company’s side, and From SOP to AI workflow shows a written procedure turned into one.
FullyPowered Planner is where the plan lives: your teams, their roles, the work between them, and what to build first. When you want a workflow built with you and tested on your own cases, a 3-Day Workflow Sprint does that for one piece of work.