---
title: "Write an SOP from rough process notes"
description: "AI prompt and skill that turn rough notes or a walkthrough transcript into a clear SOP with steps, checks, exceptions and an owner."
url: https://atulsingh.co.in/ai-playbooks/sop-from-process-notes
skill: https://atulsingh.co.in/ai-playbooks/sop-from-process-notes/SKILL.md
function: operations
roles: ["Operations manager", "Founder or business owner", "Team lead", "Office or admin manager"]
industries: ["manufacturing", "logistics", "professional-services"]
published: 2026-11-14T20:49:16.864+00:00
updated: 2026-11-15T15:16:16.966176+00:00
---

# Write an SOP from rough process notes

This playbook turns rough notes, or a transcript of someone doing a task, into a written standard operating procedure. You get a purpose, trigger, owner, numbered steps, checks and exceptions, plus a list of questions for the person who does the work. It suits operations managers and owners who need a process written down so a second person can run it.

**Time saved:** roughly an hour per procedure

## What to gather

- A rough record of the task as it is really done: typed notes, voice notes or a transcript of a recorded walkthrough
- The name or role of the person who does the task today, and who approves or backs it up
- The tools, systems and shared folders used in the task
- What starts the task and how often it happens
- Any rules or limits that apply, such as approval limits, deadlines or company policy
- Known problems, workarounds and special cases the person can remember

## Steps

1. Ask the person who does the task to talk through one real run while doing it. Record it on a phone, or write notes as they go. A real run shows more than a description from memory.
2. Get the notes or transcript into text. Remove customer names, bank details and other personal data, or replace them with a role such as 'the supplier' or 'the finance head'.
3. Fill in the fields below and paste the prompt into ChatGPT, Claude or Gemini. Paste the full notes, even if they are untidy. If the answer stops part-way, type 'continue' to get the rest.
4. Read the steps against your notes. Some steps may hold more than one action, or add a detail the notes never mention, such as when or how an approval happens. Ask the model to split those steps, and to move anything it inferred into Assumptions.
5. Check that the SOP ends with a separate final check before the task is closed. If it is missing, ask the model to add one and mark it 'To be confirmed'.
6. Send the 'Questions to resolve' list to the person who does the work. Paste their answers back into the same chat and ask the model to update the SOP.
7. Ask the person who does the task to read the SOP line by line and correct it. Then ask someone who has never done the task to follow it once and mark where they got stuck.
8. Name an owner, add the date and a review date, and save the final version in one shared place the team already uses.

## The prompt

```text
I need a standard operating procedure (SOP) written from rough notes. It will be used by a new team member who has never done this task, so write it plainly and in the order the work happens.

Process: {{process_name}}
Done by: {{who_does_it}}
Tools and systems used: {{tools_used}}
What starts it and how often: {{trigger_and_frequency}}
Rules or limits that apply: {{rules_and_limits}}
Known problems or exceptions: {{known_problems}}

Rough notes or transcript of someone doing the task:
{{process_notes}}

Write the SOP with these headings:
1. Purpose: one or two sentences on why the task exists and what a good result looks like.
2. Trigger: what starts the task and how often it happens.
3. Owner and backup: who is accountable and who does the work. If the notes do not say, write 'To be confirmed'.
4. Before you start: access, files and information needed.
5. Steps: numbered, one action per step, starting with a verb and naming the tool or screen used. Mark every step where a person must decide or approve, and say what they look at.
6. Checks: how the person knows each stage was done correctly, and the final check before the task is closed.
7. Exceptions: what to do when something does not fit the normal path, and who to ask.
8. Records: what to save, where, and for how long, if the notes say.

After the SOP, add a section called 'Questions to resolve'. List every gap, contradiction or unclear point in the notes, each as a specific question for the person who does the work. Then add a section called 'Assumptions' for anything you filled in yourself, so I can check it.

Rules: Use only what is in the notes and the details above. Do not invent steps, tools, names, limits or deadlines. If the notes show two ways of doing something, describe the more common one and put the other in Questions to resolve. Remove personal data such as customer names or bank details and use a role or placeholder instead. Keep sentences short and simple. Do not suggest automation. If a step looks unstable or inconsistent, flag it in Questions to resolve.
```

### Fill in

- `{{process_name}}`: Name of the task in plain words (for example: Paying a supplier invoice for raw material)
- `{{who_does_it}}`: Who does the task and who approves it (for example: Meena Iyer, accounts executive at a packaging unit in Pune. Approved by Rakesh Shah, finance head.)
- `{{tools_used}}`: Tools, systems and folders used (for example: Accounts email inbox, Tally Prime, company bank portal, shared Google Drive folder)
- `{{trigger_and_frequency}}`: What starts the task and how often it happens (for example: A supplier invoice arrives by email. Around a dozen a week. Payments go out in one run every Thursday.)
- `{{rules_and_limits}}`: Rules, limits or deadlines that apply (for example: Invoices above Rs 1,00,000 need Rakesh's approval. Pay within 30 days of invoice date. A goods receipt must exist before payment.)
- `{{known_problems}}`: Problems, workarounds or special cases you already know about (for example: Suppliers sometimes send invoices without a PO number. The stores team is sometimes late entering the goods receipt.)
- `{{process_notes}}`: Paste the rough notes or transcript of someone doing the task (for example: I open the invoice from the accounts inbox, check the PO number, then look in Tally for the goods receipt. If it matches I enter the bill in Tally. Amounts over a lakh I send to Rakesh on WhatsApp for his OK. On Thursday I make the payment list from Tally, upload it to the bank portal and Rakesh releases it. Then I save the invoice in the Drive folder under the supplier name. If stores has not entered the receipt I call Imran in stores.)

## Check the result

- Every step starts with a verb, holds one action and names the tool or screen used.
- Each trigger, limit, deadline and name in the SOP can be found in the notes or the details you supplied.
- No step adds a channel, a timing or an approval rule that the notes do not mention.
- Every step where a person decides or approves says what that person looks at before deciding.
- The SOP has an owner, a backup and a separate final check before the task is closed, even if marked 'To be confirmed'.
- Each item in Questions to resolve names a specific situation, such as 'What happens when the PO number is missing?'. A vague catch-all like 'Any other exceptions?' does not count.
- Anything the model filled in sits in the Assumptions section, outside the steps.
- A person who has never done the task can follow the SOP once without asking the original worker for help.

## Watch out for

- Personal and customer data: notes and transcripts often contain names, phone numbers or bank details. Remove or replace them before pasting, and use your company's approved AI workspace. This matters under India's DPDP Act and GDPR. This is general guidance and not legal advice.
- Invented steps: models tend to tidy a messy process into something that sounds right. They also slip their own guesses into the steps. Read every step against the notes, check the Assumptions section, and have the person who does the work correct the draft.
- Writing down the wrong process: if the notes come from what a manager believes happens, the SOP will be wrong. Base the notes on a real run, and watch the work being done at least once.
- Locking in a messy process: an SOP written from unstable work records the mess. Treat the exceptions and open questions as work to settle before you automate anything.
- Approvals and limits: money limits, customer promises and compliance steps need a named person to confirm them. Do not accept a limit or deadline the model has guessed.

## Industry notes

- **manufacturing:** Useful for shop-floor and back-office routines such as goods receipt, invoice payment, machine changeover and quality sign-off. Add safety rules yourself and have a supervisor confirm them.
- **logistics:** Works well for dispatch, proof of delivery, damage claims and driver onboarding. The questions list helps most with exceptions such as failed deliveries and missing paperwork.
- **professional-services:** Good for client onboarding, month-end tasks and file handover, where one person usually holds the knowledge. Remove client names and confidential details before pasting notes.

## Before and after

**Before:** The task lives in one person's head. When they are away, someone else guesses, and the manager writes a rough document from memory that misses the workarounds. It takes an afternoon and goes out of date quickly.

**After:** The person talks through one real run, and the model drafts the SOP and lists what is unclear. The person answers the questions, a newcomer tests the draft, and the owner signs it off. The gaps are found before the document is shared.

## FAQ

**Can I use a voice recording instead of typed notes?**

Yes. Record the person doing the task and talking aloud, then turn the recording into text with a transcription tool your company allows. Paste the transcript in. The model can ignore spoken filler.

**How long should the notes be?**

As long as one real run of the task takes. A few paragraphs is enough for a simple task, and a long transcript is fine for a complex one. If the process has many branches, write one SOP for the normal path and handle the branches under Exceptions.

**Should I automate the task once the SOP exists?**

Not straight away. First run the SOP with the team for a few weeks and settle the open questions and exceptions. Once the steps stay the same from one run to the next, you can decide whether any part is worth automating.

**Who should own the SOP?**

The person accountable for the result, usually the team lead or manager. That may be a different person from whoever wrote it up. The owner confirms it, sets a review date and updates it when the work changes.

## Atul's note

Teams often write an SOP from what the manager believes happens. I prefer to start from a real run of the task, written down as it happens, because the gaps and workarounds that show up are the useful part. I settle those with the team first, and only then look at whether any step is worth automating.

## Tested on

- GPT-6, 2026-11-14: pass
- Gemini 4, 2026-11-14: pass

[This page](https://atulsingh.co.in/ai-playbooks/sop-from-process-notes) · [Markdown copy](https://atulsingh.co.in/ai-playbooks/sop-from-process-notes.md) · [SKILL.md](https://atulsingh.co.in/ai-playbooks/sop-from-process-notes/SKILL.md)
