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.
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.
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. Gather your inputsHave the items above to hand.
- 2. Fill in the formYour prompt updates as you type.
- 3. Copy or open in your AIClaude, ChatGPT or Gemini.
- 4. Review before you sendCheck it against your notes.
Your prompt · 0 of 7 filled
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.
How to install
- Claude: download the zip and upload it as is under Settings, Capabilities, Skills.
- Other assistants: open SKILL.md, copy it, and paste it into the assistant's custom instructions or project.
- 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…
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. TriggerA 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.
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-
Open the supplier invoice in the accounts email inbox.
-
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. -
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. -
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. -
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. -
Enter the bill in Tally Prime.
-
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. -
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. -
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. -
Upload the payment list to the company bank portal.
-
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. -
Save the supplier invoice in the shared Google Drive folder under the supplier name after the payment release.
| 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.
- Who is accountable for the full process, and who is the backup?
- What are the exact Tally Prime screens and shared Drive folder path?
- What bank portal permissions does the accounts executive need?
- Is WhatsApp the approved channel for invoice approval, and which account should be used?
- Is the PO number checked only for presence, or must it be checked against a purchase order? Where is the purchase order held?
- What should happen when a PO number is missing, and who should be contacted?
- How is the correct goods receipt found in Tally Prime?
- Which invoice and goods receipt fields must match?
- What should happen if they do not match, and who resolves the difference?
- After calling the stores contact, when should the accounts executive check again? Who handles an unresolved delay?
- Can the bill be entered before the goods receipt exists, or must entry wait for the match?
- Which fields must be entered in Tally Prime, and how is the entry checked?
- Is there a check for an invoice that has already been entered or paid?
- Does the Rs 1,00,000 approval threshold apply to the invoice total including tax?
- What information must be sent to the finance head through WhatsApp, and what must the finance head review?
- How is the finance head’s OK linked to the correct invoice? Must proof of approval be saved?
- What happens if the finance head refuses approval, does not respond or is unavailable?
- Which invoices go into each Thursday payment list, and is there a cutoff for inclusion?
- 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?
- What upload format does the bank portal require, and how is the list produced from Tally Prime?
- Where do the supplier payment details come from, and who checks them?
- What checks does the finance head perform before releasing the bank payment run?
- How is successful payment confirmed, and what happens if an upload or payment fails?
- Must the payment be recorded against the bill in Tally Prime? If so, who does this and when?
- Is the invoice saved after bank release or only after payment success is confirmed?
- What file-naming rule should be used, and what happens if the supplier’s Drive folder does not exist?
- Which supporting records must be saved, where, and for how long?
- What exact conditions must be met before the task is closed?
- Personal names have been replaced with role labe
Standard Operating Procedure: Paying a Supplier Invoice for Raw Material
1. Purpose This procedure explains how to check, record, and pay supplier invoices for raw materials. A good result is that valid invoices with matching goods receipts are paid within 30 days of the invoice date and saved in the correct folder.
2. Trigger This task starts when a supplier invoice arrives in the accounts email inbox. Invoices arrive around a dozen times a week, and payments go out in one run every Thursday.
3. Owner and backup
- Accountable (Approver): Finance Head
- Performs the work (Owner): Accounts Executive (Packaging unit, Pune)
- Backup: To be confirmed
4. Before you start You need access to the following tools and information:
- Accounts email inbox
- Tally Prime
- WhatsApp (to contact the Finance Head)
- Company bank portal
- Shared Google Drive folder
- Contact details for the Stores Contact
- The supplier invoice (must include a PO number and invoice date)
- The goods receipt in Tally Prime
5. Steps Perform Steps 1 to 6 as invoices arrive during the week:
- Open the supplier invoice from the accounts email inbox.
- [DECISION] Check the invoice for a Purchase Order (PO) number. Look at the invoice document to see if the PO number is written on it.
- Look in Tally Prime for the matching goods receipt.
- [DECISION] Check if the goods receipt matches the invoice. Look at the invoice details and the goods receipt in Tally Prime to confirm a goods receipt exists and matches.
- Enter the bill in Tally Prime if the goods receipt matches.
- [DECISION / APPROVAL] Check the total amount on the invoice. If the amount is above Rs 1,00,000, send the invoice details to the Finance Head on WhatsApp and wait for their approval before paying. (The Finance Head will look at the invoice details and amount to approve).
Perform Steps 7 to 10 every Thursday for invoices due within 30 days of the invoice date:
- Make the payment list from Tally Prime.
- Upload the payment list to the company bank portal.
- [APPROVAL] Wait for the Finance Head to release the payment in the company bank portal. (The Finance Head will look at the uploaded payment list in the bank portal to approve and release it).
- Save the invoice in the shared Google Drive folder under the supplier name.
6. Checks
- PO Check: The invoice has a PO number on it.
- Goods Receipt Check: A goods receipt exists in Tally Prime and matches the invoice before the bill is entered.
- Approval Check: Any invoice above Rs 1,00,000 has received an OK on WhatsApp from the Finance Head.
- Payment Timing Check: The invoice is paid within 30 days of the invoice date.
- Final Check: The payment is released in the company bank portal by the Finance Head, and the invoice file is saved in the shared Google Drive folder under the supplier name.
7. Exceptions
- No goods receipt in Tally Prime: If the stores team is late and has not entered the goods receipt in Tally Prime, call the Stores Contact in the stores team. Do not enter the bill or pay the invoice until the goods receipt exists.
- Missing PO number: Suppliers sometimes send invoices without a PO number. (Who to ask and what to do: To be confirmed).
8. Records
- What to save: The supplier invoice and the entered bill.
- Where to save: Save the invoice in the shared Google Drive folder under the supplier name. Enter the bill in Tally Prime.
- How long to save: To be confirmed.
Questions to resolve
- Missing PO Number: What is the exact process when a supplier sends an invoice without a PO number, and who should the Accounts Executive contact to resolve it?
- Mismatched Goods Receipt: In Step 4, what should the Accounts Executive do if the goods receipt is in Tally Prime, but the quantities or prices do not match the invoice?
- Timing of Finance Head Approval: For invoices over Rs 1,00,000, should you get the Finance Head's WhatsApp approval before entering the bill into Tally Prime, or after entering it (just before adding it to the Thursday payment list)?
- Unstable Step – WhatsApp Approval: Approving invoices over Rs 1,00,000 via WhatsApp is informal and hard to track for audits. Should the screenshot of the WhatsApp approval be saved, or should approvals be moved to email or Tally Prime?
- Tools List Missing WhatsApp: WhatsApp is used for approvals in the rough notes, but it was not listed in the official "Tools and systems used" section. Is WhatsApp an approved company tool for this process?
- 30-Day Payment Rule vs. Weekly Run: Since payments go out every Thursday, do you pay all entered bills every Thursday, or do you select only the bills that are close to their 30-day deadline?
- Unstable Step – Filing Invoices Last: Currently, invoices are saved to Google Drive after the Thursday payment run. This means an email could be lost while waiting for Thursday. Should invoices be saved to Google Drive as soon as they are entered into Tally Prime?
- Updating Tally After Payment: After the Finance Head releases the payment in the bank portal, do you need to go back into Tally Prime to mark the bills as paid?
- Backup Person: Who is the backup person if the Accounts Executive or the Finance Head is on leave?
- Record Retention: How long must the invoices be kept in the Google Drive folder?
Assumptions
- Role Placeholders: Replaced personal names from the notes (Meena Iyer, Rakesh Shah, and Imran) with role titles (Accounts Executive, Finance Head, and Stores Contact) to follow the rule on removing personal data.
- Splitting Daily vs. Weekly Tasks: I assumed Steps 1 to 6 happen throughout the week as emails arrive, and Steps 7 to 10 happen only on Thursdays during the payment run.
- Supplier Name Placeholder: In Step 10, the phrase "supplier name" is kept as a general instruction for folder naming rather than personal data.
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 reviewReview before you send
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.
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.
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.
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.
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.
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.
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.
Last checked · Updated