Turn an expert’s notes into a procedure you have tested
The one person who knows how the job is done is going on leave, and their notes say things like “booklet, cards, slip, then seal it”. Claude can turn that into a procedure a new colleague could follow, as long as you test it on paper before anyone relies on it.

What you'll make
a one-page draft procedure with clear steps, stop points and a short list of questions for the process owner, checked against five paper test cases.
What you'll need
Claude (the same method works in ChatGPT, Gemini or Copilot), the expert’s notes and the current official rules for the task, both cleared for use in your work account, and about 30 minutes, including the walkthrough.
Example result.
3. Check the pack holds one v3 booklet, two sample cards and one
feedback slip, all undamaged.
If anything is missing, damaged or the wrong version: stop. Hold
the pack and tell the shift lead. Do not substitute.
Question for the process owner: who orders more booklets?
1. Collect the notes and the rules
Choose one small task, such as preparing a sample pack or checking a routine request. In a new Claude chat, paste the expert’s notes or attach them as a file, and do the same with the current procedure or checklist if one exists.
Label which document sets the rules and which holds informal notes. An experienced person’s shortcut is useful evidence of how the work really happens, but it isn’t automatically an allowed way of working.
To practise first, use our fictional sample-pack standard and rough expert notes. The task ends at a dispatch-review tray; nothing goes to customers.
Why this works: the label tells Claude which source wins when they disagree. Without it, the most recent or most detailed text tends to win, and that is usually the notes.
What you should see: two clearly labelled sources in one chat, with nothing sent yet.
2. Ask for a short, usable procedure
Turn these notes into a one-page draft how-to guide for [reader].
The official standard takes priority over the informal expert notes.
Use clear numbered steps. Say what someone needs, what to do, when
to stop and ask for help, and how to know the task is finished.
Flag conflicting shortcuts and missing details separately. Don't
invent policy, owners or deadlines. Point to the source for each
important rule. Keep this a draft for the process owner to review.
[reader] is who will follow it, such as “a new starter in their first week”. A new starter needs explanations that someone covering for an afternoon may already know.
Why this works: asking for conflicts and gaps as separate lists keeps a shortcut from quietly becoming a step, and keeps a missing rule from being filled with a plausible guess.
What you should see: numbered steps with a stop point wherever the standard says to hold, plus a list of conflicts and a list of questions.
3. Make vague steps concrete
Read the draft as if you’ve never done the job. Every check should say what to look at, what “good” looks like and what to do if it fails. “Check the pack” is too vague. “Check for one v3 booklet, two sample cards and one feedback slip, all undamaged” is something a new person can do.
Clarify these steps in the draft: [steps and what is unclear].
For each, say what to look at, the acceptable result and what to do
if it fails, using the official standard. Don't invent a missing rule;
list a question for the process owner instead. Keep the rest of the
procedure unchanged.
[steps and what is unclear] is the step numbers and the question you’d ask, such as “Step 4: check what, exactly?”
If the notes don’t say who orders replacement stock, leave it as a question. AI doesn’t know who has the cupboard key either.
Why this works: naming the unclear steps gets a targeted fix instead of a rewrite that may lose rules you’ve already checked.
What you should see: only the named steps changed, each with a pass condition and a failure route.
4. Walk through it on paper
Print the draft and walk through it with paper tokens. Don’t run an unsigned draft in live work to test it. For the practice pack, the five cases and their expected results are:
- Correct contents, second checker and complete log: seal and place in the dispatch-review tray.
- One sample card missing: hold and notify the shift lead. Don’t seal.
- Only a v2 booklet available: hold; no substitution.
- Correct contents but no second checker: leave unsealed.
- Second checker finds only one sample card: go back to the failed-contents path and recheck before sealing.
Ask a colleague who doesn’t know the task to talk through each case. Note where they hesitate and what they assume. Then give Claude the notes, without personal details:
Revise only the wording identified as unclear in this walkthrough log.
Show each changed step, the reason and the source that supports it.
If a fix needs a new policy decision, leave a question for the process
owner instead. Return a change log and the cases that must be rerun.
[walkthrough log]
Why this works: an unfamiliar reader finds the gaps the expert can’t see, because the expert fills them from memory.
What you should see: a short change log and a list of cases to rerun. Don’t write “tested” on the procedure until the walkthrough has happened and its findings are recorded.
Check the result
- Every mandatory rule survived: the contents, the log, the second check and the no-substitution rule.
- Each exception case ends in a hold or a question, never a sealed pack.
- The procedure stops at the dispatch-review tray and doesn’t add dispatch.
- The open questions are listed for the process owner, not answered by Claude.
The usual failure: the expert’s shortcut becomes an official step. Look for a line that sounds helpful and practical, such as “If v3 has run out, use a v2 booklet”. Compare every “if … then” line with the standard; a shortcut usually appears in the notes and nowhere in the rules.
Step [number] follows the informal notes, not the official standard.
The standard says: "[quoted rule]". Rewrite only that step to follow
the standard and move the shortcut to the conflicts list. Keep every
other step unchanged.
[number] is the step, and [quoted rule] is the exact line from the standard.
The process owner resolves the questions and signs off the procedure before anyone uses it in live work. Safety-critical or regulated procedures also need the relevant specialist review.
Worked example: the v2 booklet
Fictional example. The expert’s notes include:
N2. Booklet, cards, slip. I count the cards separately.
N3. If v3 has run out, I sometimes use a v2 booklet.
N4. Someone else looks at the contents, then I seal it.
N5. The log gets forgotten when we are busy.
The first draft read well, and step 3 said: “If v3 is missing, use a v2 booklet and continue.” Walkthrough case 3 (only v2 available) ended in a sealed pack, so the draft failed.
After the repair prompt with standard rule S2, step 3 read: “If a required item is missing, damaged or the wrong version, stop. Hold the pack and tell the shift lead. Do not substitute.” The v2 habit moved to the conflicts list for the process owner.
What mattered:
- The source label. Because the standard was marked as the rule, Claude could see the conflict once it was pointed out, rather than weighing two equal sources.
- The forgotten log stayed. N5 is a problem to fix, not permission to drop logging, so the draft kept the log and added it to the case 1 check.
- One question stayed open. Nobody in the notes orders stock, so “Who orders more booklets?” went to the owner rather than into a step.
Task kit for this job: Download (ZIP) · Reusable instructions
Go deeper
Rerun the old cases whenever the procedure changes
This is regression testing for procedures. When you edit a step, rerun all five cases, not only the one the change was for. A shorter, cleaner sentence can quietly remove a stop condition that an older case relied on.
Keep the procedure in your normal document system with an owner, a version and a review date. Store the walkthrough notes and any open questions alongside it, so the next editor knows why each stop point exists.
Measure a real trial honestly
During a real trial that the process owner has agreed, note where people hesitate, the questions they ask and any stop conditions they miss. Compare the time spent preparing, reviewing and correcting with your previous approach before you claim the new procedure is quicker. A neat document can still be slower to follow.