---
name: sop-from-process-notes
description: Turns rough notes or a transcript of someone doing a task into a standard operating procedure with purpose, trigger, owner, steps, checks and exceptions, plus questions about gaps. Use when a process lives in one person's head.
---

# Write an SOP from rough process notes

## When to use

Use this skill when someone gives you rough notes, voice-note text or a transcript of a person doing a task, and wants a written standard operating procedure (SOP) that a new team member could follow. It suits routine work such as processing invoices, onboarding a client, handling a refund, dispatching an order or closing the month.

Do not use it to invent a process that does not exist yet. If there are no notes, first ask the user to talk through one real run of the task.

## What to ask for

Ask for each item below. If the user has not given one, ask for it before writing.

- The name of the task in plain words
- Who does the task, and who approves or backs it up
- The tools, systems and folders used
- What starts the task and how often it happens
- Rules, limits or deadlines that apply, such as approval limits or payment terms
- Known problems, workarounds and special cases
- The rough notes or transcript of someone doing the task

If the notes contain personal data such as customer names, phone numbers or bank details, tell the user to remove them or replace them with a role. Also tell them to use their company's approved AI workspace.

## Steps

1. Read all the notes once before writing anything. Note the order of the work, the tools named, and every point where a person makes a decision.
2. Separate what the notes say from what you would be guessing. Only what the notes say goes into the steps.
3. Write the SOP in the order the work happens. Use short sentences. Start every step with a verb, keep one action per step, and name the tool or screen.
4. Mark each step where a person decides or approves, and state what they check before deciding. Do not add an approval channel, timing or threshold the notes do not give.
5. Add checks after the stages that matter.
6. End the steps with a separate final check before the task is closed. If the notes do not give one, write a provisional check and mark it 'To be confirmed'.
7. Describe exceptions the notes mention. If the notes show two ways of doing the same step, write the more common way in the steps and raise the other as a question.
8. List every gap, contradiction or unclear point as a specific question for the person who does the work. Do not propose process changes in the questions.
9. List everything you inferred in a separate Assumptions section. This includes rules you worked out from a limit, such as what happens below it.
10. If the output is long, finish the SOP first, then the questions, then the assumptions, so nothing is lost if the answer is cut short.
11. When the user brings back answers, update the SOP and remove the questions that are now settled.

## Output format

Use this layout and these headings.

```text
SOP: <task name>
Version and date: <to be filled by the owner>

Purpose
Trigger
Owner and backup
Before you start
Steps (numbered, one action each, decision points marked)
Checks
Final check before closing
Exceptions
Records

Questions to resolve (numbered, each addressed to the person who does the work)
Assumptions (anything not stated in the notes)
```

Write 'To be confirmed' where the notes do not give an owner, a limit, a deadline or a final check. Keep each section short enough to read on one phone screen.

## Quality check

Before sending the result, check each point.

- Every step holds one action, starts with a verb and names the tool.
- Every name, limit, deadline and tool in the SOP appears in the notes or the user's details.
- No step contains an inference. Inferences sit in Assumptions.
- Every approval step says what the approver looks at.
- The owner, the backup and a separate final check are present, even if marked 'To be confirmed'.
- Each question is specific and can be answered in a sentence or two.
- No personal data appears in the SOP.

## Watch-outs

- Do not tidy a messy process into something that only sounds right. If the notes are inconsistent, say so in the questions.
- Do not invent approval limits, deadlines, legal requirements or safety rules. Ask the user, and tell them a responsible person should confirm them.
- Do not suggest automation or process improvements. If a step looks unstable or varies between runs, flag it, and say the process should be settled before anyone automates it.
- Remind the user that the person who does the task must read the final SOP, and that someone new to the task should try it once and report where they got stuck.
- Recommend a named owner and a review date, because an SOP that nobody owns goes out of date.
