OperationsSaves roughly an hour per procedureTested on GPT-6 and Gemini 4, Nov 2026

Write an SOP from rough process notes

What this does

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.

Fill in your detailsDownload skill
On this page

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.

Saves roughly an hour per procedure

From my practice

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.
· AI workflow and adoption consultant

What to have ready

  • 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

Build your prompt

  1. 1. Gather your inputsHave the items above to hand.
  2. 2. Fill in the formYour prompt updates as you type.
  3. 3. Copy or open in your AIClaude, ChatGPT or Gemini.
  4. 4. Review before you sendCheck it against your notes.
Fill in your details

Fill these in. Your prompt updates as you type, and stays in this browser tab.

Your prompt · 0 of 7 filled

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: Name of the task in plain words Done by: Who does the task and who approves it Tools and systems used: Tools, systems and folders used What starts it and how often: What starts the task and how often it happens Rules or limits that apply: Rules, limits or deadlines that apply Known problems or exceptions: Problems, workarounds or special cases you already know about Rough notes or transcript of someone doing the task: Paste the rough notes or transcript of someone doing the task 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.
Open in
Open in Claude (opens in a new tab)Open in ChatGPT (opens in a new tab)

Gemini cannot be filled from a link, so the prompt is copied first. Paste it with Ctrl+V or Cmd+V.

Use it as a skill

Add this playbook to your assistant once, then ask for it by name.

Download skill for ClaudeView SKILL.md (opens in a new tab)
How to install
  1. Claude: download the zip and upload it as is under Settings, Capabilities, Skills.
  2. Other assistants: open SKILL.md, copy it, and paste it into the assistant's custom instructions or project.
  3. Ask for the playbook by its task, and give it your details when it asks.

The skill is plain text with no scripts, links or commands. Read SKILL.md before you install it, and use a company-approved AI workspace. Need help setting it up? Book a call.

See a real result

Sample input: Paying a supplier invoice for raw material · Meena Iyer, accounts executive at a packaging unit in… · Accounts email inbox, Tally Prime…

Sample output from GPT-6, run 14 Nov 2026
SOP: Paying a Supplier Invoice for Raw Material 1. Purpose

Pay supplier invoices within 30 days of the invoice date. A good result is a payment supported by a matching goods receipt and the required approval, with the invoice saved in the shared Google Drive folder.

2. Trigger

A supplier invoice arrives in the accounts email inbox. Around a dozen invoices arrive each week. Payments are made in one run every Thursday.

3. Owner and backup
  • Person doing the work: Accounts executive.
  • Accountable owner: To be confirmed.
  • Approver: Finance head approves invoices above Rs 1,00,000 and releases the Thursday bank payment run.
  • Backup: To be confirmed.
4. Before you start

You need:

  • Access to the accounts email inbox.
  • Access to Tally Prime.
  • Access to WhatsApp to request approval from the finance head.
  • Access to the company bank portal.
  • Access to the shared Google Drive folder.
  • The supplier invoice, including its date, amount and PO number.
  • A goods receipt in Tally Prime.
  • Contact details for the finance head and the stores contact.

The exact Tally Prime screens, bank upload requirements and Drive folder path are not given in the notes.

5. Steps
  1. Open the supplier invoice in the accounts email inbox.

  2. Check the invoice in the accounts email inbox for a PO number.
    [DECISION] Is a PO number present? If it is missing, refer to Exceptions. The notes do not explain how to proceed.

  3. Find the goods receipt in Tally Prime.
    [DECISION] Does the goods receipt exist? If not, follow Step 4. Do not pay without a goods receipt.

  4. Call the stores contact if the goods receipt is missing from Tally Prime.
    This step applies only when the receipt is missing. The notes do not state when to check again or how to escalate a delay.

  5. Compare the goods receipt in Tally Prime with the supplier invoice.
    [DECISION] Do they match? Enter the bill only if they match. The fields to compare and the action for a mismatch are to be confirmed.

  6. Enter the bill in Tally Prime.

  7. Check the invoice amount in Tally Prime against Rs 1,00,000.
    [DECISION] Is the amount above Rs 1,00,000? If yes, follow Step 8. The stated rule does not require this separate approval for amounts of Rs 1,00,000 or less.

  8. Request the finance head’s approval through WhatsApp for an invoice above Rs 1,00,000.
    [APPROVAL — FINANCE HEAD] The finance head reviews the invoice approval request and gives an OK. The notes do not specify what details must be sent or reviewed.

  9. Prepare the payment list from Tally Prime on Thursday.
    [DECISION] Select invoices for the payment run. A goods receipt must exist, invoices above Rs 1,00,000 need approval, and payment must be within 30 days of the invoice date. The exact selection method is to be confirmed.

  10. Upload the payment list to the company bank portal.

  11. Release the uploaded payment run in the company bank portal — finance head only.
    [APPROVAL — FINANCE HEAD] The finance head releases the uploaded payment run. The checks required before release are not specified.

  12. Save the supplier invoice in the shared Google Drive folder under the supplier name after the payment release.

6. Checks

| Stage | Check | |---|---| | Invoice review | The invoice contains a PO number. The handling of a missing PO number is unresolved. | | Goods receipt | A goods receipt exists in Tally Prime and matches the invoice. Match criteria are to be confirmed. | | Bill entry | The bill has been entered in Tally Prime. Detailed entry checks are not specified. | | Invoice approval | The finance head has given an OK through WhatsApp for invoices above Rs 1,00,000. | | Payment timing | Payment is within 30 days of the invoice date. How this is managed alongside Thursday-only runs is unresolved. | | Bank release | The finance head has released the payment run in the company bank portal. | | Filing | The invoice is saved under the supplier name in the shared Google Drive folder. |

Final check before closure: Bank release and invoice filing are the last recorded stages. The notes do not explain how to confirm successful payment or when to mark the task closed.

7. Exceptions

| Exception | Action and contact | |---|---| | Invoice has no PO number | The action and person to contact are To be confirmed. | | Goods receipt is missing or late | Call the stores contact. Do not pay without a goods receipt. Follow-up timing and escalation are To be confirmed. | | Goods receipt does not match | The notes only describe proceeding when it matches. The correction process and person to contact are To be confirmed. | | Approval is missing or refused for an invoice above Rs 1,00,000 | Approval must come from the finance head. Follow-up and refusal handling are To be confirmed. | | A Thursday run would cause payment after 30 days | The action and person to contact are To be confirmed. |

8. Records
  • Bill entry: Recorded in Tally Prime.
  • Invoice approval: Given through WhatsApp for invoices above Rs 1,00,000. Whether a separate copy must be saved is not stated.
  • Supplier invoice: Saved in the shared Google Drive folder under the supplier name.
  • Retention period: Not stated.
  • Other records: Requirements for saving the payment list, bank confirmation or goods receipt are not stated.
Questions to resolve
  1. Who is accountable for the full process, and who is the backup?
  2. What are the exact Tally Prime screens and shared Drive folder path?
  3. What bank portal permissions does the accounts executive need?
  4. Is WhatsApp the approved channel for invoice approval, and which account should be used?
  5. Is the PO number checked only for presence, or must it be checked against a purchase order? Where is the purchase order held?
  6. What should happen when a PO number is missing, and who should be contacted?
  7. How is the correct goods receipt found in Tally Prime?
  8. Which invoice and goods receipt fields must match?
  9. What should happen if they do not match, and who resolves the difference?
  10. After calling the stores contact, when should the accounts executive check again? Who handles an unresolved delay?
  11. Can the bill be entered before the goods receipt exists, or must entry wait for the match?
  12. Which fields must be entered in Tally Prime, and how is the entry checked?
  13. Is there a check for an invoice that has already been entered or paid?
  14. Does the Rs 1,00,000 approval threshold apply to the invoice total including tax?
  15. What information must be sent to the finance head through WhatsApp, and what must the finance head review?
  16. How is the finance head’s OK linked to the correct invoice? Must proof of approval be saved?
  17. What happens if the finance head refuses approval, does not respond or is unavailable?
  18. Which invoices go into each Thursday payment list, and is there a cutoff for inclusion?
  19. How is the 30-day payment deadline tracked? What happens if the next Thursday run would be too late or Thursday is a bank holiday?
  20. What upload format does the bank portal require, and how is the list produced from Tally Prime?
  21. Where do the supplier payment details come from, and who checks them?
  22. What checks does the finance head perform before releasing the bank payment run?
  23. How is successful payment confirmed, and what happens if an upload or payment fails?
  24. Must the payment be recorded against the bill in Tally Prime? If so, who does this and when?
  25. Is the invoice saved after bank release or only after payment success is confirmed?
  26. What file-naming rule should be used, and what happens if the supplier’s Drive folder does not exist?
  27. Which supporting records must be saved, where, and for how long?
  28. What exact conditions must be met before the task is closed?
Assumptions
  • Personal names have been replaced with role labe

Was this playbook helpful?

Want this set up for your team?

I can fit this playbook into your CRM, helpdesk or inbox and train your team to use it.

Book a 30-minute review

Review before you send

Check the result

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.

Tips for your industry

This playbook works for any business. These notes help you adapt it.

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.

Questions people ask

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.

Last checked · Updated