Find where a mistake would multiply
Look through your workflow’s steps for the first point where the agent produces something later steps build on, such as a meeting record, a set of figures, a list of decisions or a plan of who needs what. If the agent misreads its source there, every later output repeats the mistake: a target date read as a commitment, an owner nobody confirmed, a recommendation read as a decision or an unknown smoothed over. The drafts look more complete, and the mistake is in all of them. Put your first stop right after that point, where you can correct it once.
Other places a stop often belongs are before the agent drafts anything for other people, before a recommendation, and before the work is used. A short workflow may need only one stop, before use. Write that one in anyway, so the agent knows to wait.
To see your workflow’s chain laid out, start a new chat, attach your workflow and send the prompt.
My Business Results Workflow is attached or pasted below. Help me decide where it should stop for my review. Do not change the file. 1. List each step in my Workflow Steps in order. For each, say what it produces and which later steps or outputs use it. 2. For each step whose result later steps build on, say what a misreading there could spread into, such as a target date read as a commitment, an owner nobody confirmed, a recommendation read as a decision or an unknown filled in. 3. Quote each checkpoint my Human Review / Decision Points section already has, and say which step it comes after. 4. Recommend where stops belong, most important first, and for each one say what I should check there. Recommend no more stops than the risk calls for. Use only what my workflow says. [paste your Business Results Workflow here if it isn't attached]
Write what your go-ahead means
A stop only works if the agent knows what lets it continue, and you both know what that go-ahead covers. In Session 5’s example workflow, Karen Wolfram, a director of client enablement who runs customer training programs, checks the meeting record the agent prepared and types Reviewed. That word confirms the record accurately represents what’s known for this run. It doesn’t approve pending items, turn targets into commitments, make unknowns known or clear any email to be sent. Don’t let one short reply authorize more than you meant.
Open your workflow in your plain-text editor and find Human Review / Decision Points. For each stop, fill in the template’s four lines:
- Pause after: the step or result the agent stops after.
- Show me: what you need to see to check it, such as the whole record, the figures with where each came from, or the list of people and what each one gets.
- Continue only when: the exact word that lets it continue, such as Reviewed. Choose a word you wouldn’t type in passing, and add that other replies, such as ok or looks good, don’t count.
- That confirmation does not authorize: what stays as it was, such as pending items, targets, unknowns, a specialist’s review, approvals and sending.
Under Corrections, keep the template’s line that the agent revises what you correct and shows it to you again before continuing. Under I remain responsible for, name what stays yours, such as approvals, sending and final decisions. Save the file in place of the old one in My Agent Files, or another folder you’ll find again. If you’ve added your workflow to your AI tool, such as a skill or a Notebook’s References, replace that copy too.
Test that your agent stops
Now see whether your agent actually holds at each stop. Use a new example of the work, prepared the way the data rules say, or a short made-up one. If you make one up, include a target date and one item still pending, so you can see whether they stay that way.
Start a new chat, attach your workflow and its files, and run it with Run my Business Results Workflow as usual.
Run my Business Results WorkflowUse the files I have attached or pasted below for this conversation. My Business Results Workflow says what this work should accomplish, which of my other files and Workflow Cards to use, where to stop for my review and what to return. If my Business Results Workflow is missing, ask me for it before you start. Continue without any other file I've marked "not provided". MY FILES [paste the text of your Business Results Workflow, the Workflow Cards it names, your Safety & Security Rules, Agent Profile and Communication Style Guide here, or attach the files and write their names here. Write "not provided" for a file you don't have yet.] TASK Run my [name of your Business Results Workflow] using the source below. [add anything different about this run, or delete this line] CONTEXT [what this run covers, such as which meeting or reporting period, and anything that changed this time] CONSTRAINTS Use the workflow defaults. [add a limit for this run only, such as a shorter message, or delete this line] OUTPUT CHECK Use the workflow defaults. [add anything extra this run needs, such as one more person to review, or delete this line] SOURCE [paste this run's prepared source here]
When the agent stops, check that it showed you what your Show me line asks for and is waiting. If it carried on past the stop, go to step 4.
Before you confirm, test the stop. Reply with something you might type in passing, such as “ok, carry on” or “send me the final version.” The agent should say what it’s waiting for and stay where it is.
If anything it showed you is wrong, correct it now, and check that the agent revises it, shows it to you again and still waits. If everything is right, skip this check.
Type your word. The agent should go on to the next stage, or, if this was your last stop, present the result as reviewed without claiming it’s approved or sent.
Check what happened after you confirmed
Your go-ahead should change only what you said it would. In what the agent produced after you confirmed, check that:
- pending items are still pending, targets are still targets and unknowns are still unknown
- nothing says it’s approved, committed or sent
- the next stage is built on the version you checked, including your corrections
- it stopped again at your next checkpoint, if you have one, and held there on a casual reply.
If something went wrong, change the smallest part that explains it:
- It didn’t stop: the Pause after line, or the step it names.
- It continued on a casual reply: the Continue only when line.
- It treated your go-ahead as approval: That confirmation does not authorize.
- It kept going after a correction, or used the old version: the Corrections line.
Save the file in place of the old one in My Agent Files, or another folder you’ll find again. If you’ve added your workflow to your AI tool, such as a skill or a Notebook’s References, replace that copy too. Then test again in a new chat. The next time you add or move a checkpoint, run the same test.
Confirm your result
Confirm the outcomes below to finish this guide.
Final checks
Each checkpoint in your workflow says where the agent stops, what you check, the word that lets it continue and what that word does not authorize.
In a test run, your agent stopped at each checkpoint, didn’t continue on a casual reply, and kept pending items and targets as they were after your go-ahead.
Provide Feedback
Thanks. That went straight to the people who write these guides.
Week 5 field guides
Keep exploring when you’re ready
Revisit this week’s guides whenever they fit something you want to do.