Iron Goo
A woman reads a clipped procedure at a warehouse desk while a colleague watches beside shelves of rental equipment.

How to Write Standard Operating Procedures

Atamyrat Hangeldiyev
Atamyrat Hangeldiyev
Systems Architect
March 25, 2026
On this page
Business

At the openly hypothetical Ridgeline Event Rentals, a 24-person company renting tents, tables, chairs, linens, and lighting for weddings and corporate events, Dana is the only person who closes out events. She is on a two-week vacation in peak season, 38 finished events await a final invoice or deposit refund, and the operations manager cannot tell from the spreadsheet which damage charges apply or when to waive them.

Here is how to write standard operating procedures: score candidate processes, map one as people actually perform it, write the steps and decision rules in a fixed template, and accept the SOP only when someone else can run it from the page. All Ridgeline figures, policies, and thresholds in the examples are hypothetical.

Procedure 1: Score the processes and pick one

A process with a lot of hours and consequential errors deserves attention before a process that is merely easy to describe. Our rule of thumb multiplies monthly hours by an error weight, then gives a tie to the process fewer people can run.

Calculate runs per month × minutes per run ÷ 60 for each candidate. Use the following classes from choosing your first AI use case, with our rule of thumb weights:

  • A, weight 1: A mistake stays inside the company and can be undone in minutes.
  • B, weight 2: A mistake reaches a supplier, customer, or ledger but is reversible before financial loss.
  • C, weight 3: A mistake is irreversible or regulated. Use AI only as an assist, with human approval on every item.
ProcessRuns/moMin/runHours/moClassScorePeople who can run it
Event close-out invoice722530.0B60.01
Wedding quote363018.0C54.02
Delivery route sheet881217.6A17.63
Damage photo filing7267.2A7.24
Linen reorder4453.0B6.01

Event close-out scores 30.0 × 2 = 60.0, the highest of the five. Its 30.0 hours per month are about 6.9 hours per week using 30 ÷ 4.33, above the first-build guide's rule of 5 human hours a week. The wedding quote scores 54.0, but its class C status still limits AI to an assist with approval on every item.

Count the people who can perform the full process without the usual operator. A person who can find the spreadsheet but cannot decide a waiver does not count as a cover for Dana. The score is a selection aid, not a permission to automate a high-risk step.

Good result

Close-out ranks first at 60.0, and the table shows that only Dana can run it.

Bad result

The team picks photo filing because it looks easy, while the close-out backlog and its single-person dependency remain.

Procedure 2: Map the close-out as it actually happens

A process map exposes handoffs and missing knowledge before those gaps become instructions in an SOP. Start with the boundaries and an as-is SIPOC+CM, then trace the work in enough detail to see who hands what to whom.

ASQ defines a SIPOC diagram as "a data collection tool used by Six Sigma process improvement teams to assist in gathering information about all relevant elements, including suppliers, inputs, processes, outputs, and customers of a process." The +C adds constraints and +M adds measures. ASQ places this as-is view before a flowchart and describes the process block as “a high-level flowchart of the key five to seven core activities,” a “35,000-foot” view.

SIPOC+CM elementRidgeline close-out
SuppliersReturns crew, event client, order system, damage fee list
InputsOriginal order, check-in sheet with counts, damage photos, deposit amount, fee list
ProcessReceive check-in sheet; match counts to order; price damage and missing items; decide waivers; net against deposit; send invoice or refund
OutputsFinal invoice or refund, item status updates
CustomersEvent client, outside accountant, warehouse lead
ConstraintsRefund deposits within seven days of the event under Ridgeline policy
MeasuresElapsed time from check-in to invoice; corrections after sending

The boundary begins when the returns crew supplies a check-in sheet and ends when the final invoice or refund is sent and the item status is updated. Confirm those boundaries with the people involved. If refunds can be sent without an item status update, the team needs to resolve that difference before calling the map complete.

Next, draw a swimlane process map with one lane per role. A crossing arrow is a handoff. For Ridgeline, use these lanes and trace each transfer:

Returns crew       -> Accounts coordinator: check-in sheet and photos
Accounts coordinator: match counts, check driver notes, price damage
Accounts coordinator -> Operations manager: charge over $500 or dispute
Operations manager -> Accounts coordinator: decision
Accounts coordinator -> Operations manager: refund for approval
Operations manager -> Accounts coordinator: refund approval
Accounts coordinator -> Client: invoice or refund
Client             -> Accounts coordinator: dispute or payment

Use a box for an action and a diamond for a decision, with labeled paths out of the diamond. The map should show where the coordinator waits for the operations manager and where a client dispute returns work to accounts. It should also show the refund path, including the approval before money leaves.

During the walkthrough, Dana reveals a step on no existing document: she checks the delivery driver's notes for “damaged on arrival at venue” before charging. Add the note's location to the SOP and make its consequence explicit in the decision table. Otherwise, a new operator can follow every visible spreadsheet instruction and still charge for damage that preceded the event.

Close-out swimlanes show role handoffs and Dana's check of the driver's damage note

Follow the handoffs between the returns crew, accounts coordinator, operations manager, and client. The driver-note check is the step Dana performed without a written instruction.

ASQ's flowchart instructions are direct: “People who perform the process should draw it.” “Chart the current state.” “Walk through the process after completing the first draft to ensure it's accurate.” Have the returns crew and coordinator trace an actual completed event through the map, including a hold or dispute if that is what happened.

Good result

The map has four lanes, labeled handoffs, the actual start and end, and the driver-note check in the coordinator's lane.

Bad result

The map says “process damage” in one box and skips the driver's note, the manager's decision, and the return path for a dispute.

Procedure 3: Fill a fixed SOP template

A map shows the route; an SOP gives a person enough instruction to perform the work and leave evidence. A fixed template makes missing inputs, authority, and records visible before the document gets called finished.

The following example is a draft for Ridgeline. The locations and dates are hypothetical, so replace them with the actual locations and approved dates for your process. The named owner is accountable for the SOP; the role named on each step is accountable for that step.

ID and title: SOP-ACC-004 Event close-out
Revision: 1.0
Effective date: 1 November 2026
Page: 1 of 3
Accountable owner: Dana, accounts coordinator

Purpose:
  Complete an event invoice or deposit refund with supported
  counts, damage decisions, and records.

Trigger:
  The returns crew submits the event check-in sheet.

Scope:
  Starts at receipt of the check-in sheet.
  Ends when the invoice or approved refund is sent and
  the event item status is updated.

Inputs and locations:
  Original order: order system, event record.
  Check-in sheet and damage photos: event record, returns folder.
  Driver notes: event record, delivery notes.
  Deposit amount: order system, event payment record.
  Current damage fee list: shared operations folder, approved fees.

Steps:
  1. Returns crew lead: Attach the check-in sheet to the
     event record.
  2. Accounts coordinator: Match returned counts to the
     original order.
  3. Accounts coordinator: Check the delivery driver's notes
     for damage recorded on arrival.
  4. Accounts coordinator: Check that damage photos are attached.
  5. Accounts coordinator: Price damage and missing items
     against the approved fee list.
  6. Accounts coordinator: Apply the damage decision table
     in SOP-ACC-004, page 2.
  7. Operations manager: Decide any charge over $500 or
     client dispute referred under rule 3.
  8. Accounts coordinator: Net the approved charges against
     the deposit.
  9. Operations manager: Approve any deposit refund before
     it is sent.
  10. Accounts coordinator: Send the final invoice or the
      approved refund.
  11. Accounts coordinator: Update the event item status.
  12. Accounts coordinator: File the close-out evidence.

Decision rules:
  Apply the damage table on page 2 from rule 1 downward.
  Stop at the first matching rule.

Outputs and definition of done:
  Invoice or approved refund sent; item status updated;
  decision and supporting evidence filed in the event record.

Exceptions and escalation:
  Missing photos: crew lead supplies them within two working days.
  Charge over $500 or client dispute: refer to operations manager.
  Record the referral and decision in the event record.

Records:
  File the check-in sheet, photos, driver note, fee calculation,
  decision, approval, and invoice or refund in the event record.

Review date: 1 May 2027
Change log:
  Rev 1.0 | 1 November 2026 | Initial approved procedure |
  Approved by operations manager

Before adopting the example, give the operations manager a named identity in the live SOP and specify how a referral is made and how quickly that manager must respond. The two-working-day deadline applies to the request for missing photos in the decision table; it does not supply an unrecorded deadline for every other exception. If the seven-day refund promise requires a faster escalation, set and approve that timing explicitly.

The fields correspond to administrative SOP topics in the EPA's April 2007 QA/G-6 guidance, document EPA/600/B-07/001: purpose, applicability and scope, responsibilities, procedure, criteria, records, and quality oversight. It is a free public model written for environmental data organizations, not a legal requirement for a rental company. The EPA's style instruction is “The active voice and present verb tense should be used.”

Give the document one named Accountable owner and each step one Accountable person. The org and roles guide explains how to spot a step nobody else can cover; name a trained backup without assigning two people joint accountability for the same step. A tool can perform an action, but a person remains accountable for it.

The checklist at the end of an SOP helps an operator verify completion. It cannot replace the locations, decision rules, and exception instructions needed to perform the work. As EPA puts it, “Remember that the checklist is not the SOP, but a part of the SOP.”

Good result

A new coordinator can locate the driver notes, apply the table, identify the refund approver, and file the evidence for an event.

Bad result

The document says “close the event as usual,” names a team as owner, and leaves the fee list and approval location unspecified.

Procedure 4: Put damage judgments in a decision table

A decision table makes the conditions behind a charge visible enough to test. It also separates a rule a system can apply from a decision that needs a person with authority.

Read Ridgeline's hypothetical table from top to bottom and stop at the first matching row. The dispute condition in rule 3 is an additional condition on the damage total field.

#Check-in photos attachedDriver note says damaged on arrivalDamage totalRepeat client (3+ events in 12 months)ActionHuman?
1NoanyanyanyHold; request photos from crew within 2 working daysyes (crew lead)
2YesYesanyanyNo charge; log against the venue deliveryno
3YesNoover $500, or client disputesanyOps manager decidesyes
4YesNo$75.01 to $500anyCharge at fee list; coordinator approves before sendyes
5YesNo$0.01 to $75YesWaive; log waiverno
6YesNo$0.01 to $75NoCharge at fee listno
7YesNo$0anyNo chargeno

For example, a repeat client with $60 of damage has the charge waived under rule 5, provided photos are attached and the driver did not record the damage on arrival. If photos are missing, rule 1 holds the case even if the other facts would otherwise match another row. A dispute goes to the operations manager under rule 3.

This ordering uses the FIRST hit policy. In Camunda's decision table documentation, FIRST returns the output of the first satisfied rule. Camunda is one implementation of the OMG Decision Model and Notation standard; its default UNIQUE policy fails when more than one rule matches.

Rule 3 can overlap the later rules because a client can dispute a charge of $500 or less. A disputed $60 charge from a repeat client matches both rule 3 and rule 5, so an implementation using UNIQUE would fail on that case. Keep FIRST and test the order, or redesign the conditions to be mutually exclusive before using UNIQUE.

The crew lead must obtain missing evidence in rule 1, the operations manager decides rule 3, and the coordinator approves rule 4 before sending. A refund is a separate money-out action and retains named human approval as a class B control. Use the human oversight guide to design approval queues, seed known-wrong items, and provide stop controls for those human steps.

Rule 3 sends the recurring decision to the operations manager, not the company owner. That allocation follows the approach in owner time and decision making: give a named role authority for a defined decision and reserve an escalation for cases outside that authority.

Good result

A $60 damage case with missing photos stops at rule 1; once evidence arrives, the coordinator can apply the correct later row.

Bad result

The coordinator guesses whether to waive $60, or a UNIQUE table fails because overlapping rules match.

Procedure 5: Test the SOP with a new operator

An SOP passes when another person can use it to produce the right result without the author filling gaps aloud. A polished document can fail that test in the first minute.

Our rule of thumb is to have someone who has never closed out an event run 10 past close-outs with known correct results using the SOP alone. The author sits silently and logs every question. Pass only when all 10 outputs match their known results and no question needed the author; turn every question into an edit, then rerun the test on 10 different items.

Test set: 10 past close-outs with known correct results
Operator: Person who has never closed out an event
Available: SOP and the inputs named in it
Author: Silent; records questions and deviations

Pass:
  10 of 10 outputs match the known results
  No question requires the author

Fail and retest:
  Record each question and wrong or incomplete output
  Edit the SOP
  Run 10 different past close-outs

Include cases that exercise the decision table: missing photos, damage recorded on arrival, a small repeat-client waiver, a charge needing approval, and a dispute. The known result should include the decision and required record, not only the final dollar amount. Otherwise, an operator could arrive at the right total while skipping the evidence or approval.

A failed run may sound ordinary: “Which fee list is current?” or “Where do the driver notes live?” Those questions identify missing instructions. Add the precise location or selection rule, then give the revised SOP to the tester with a different set of items.

EPA's test for sufficient detail is that “someone with limited experience with or knowledge of the procedure, but with a basic understanding, can successfully reproduce the procedure when unsupervised”. Its guidance also says, “It is especially helpful if draft SOPs are actually tested by individuals other than the original writer before the SOPs are finalized.” The Ridgeline 10-item pass bar is our rule of thumb, not an EPA requirement.

Checklist results depend on what happens around the document. In the Haynes et al. study, a 19-item WHO Surgical Safety Checklist was associated with changes across eight hospitals in eight cities from October 2007 to September 2008. The before-and-after study included 3,733 patients before and 3,955 after, all at least 16 years old and undergoing noncardiac surgery; death changed from 1.5% to 0.8% and inpatient complications from 11.0% to 7.0%.

The Urbach et al. Ontario study examined 101 hospitals over three-month periods before and after adoption, with 109,341 and 106,370 procedures respectively. Adjusted mortality changed from 0.71% to 0.65% and complications from 3.86% to 3.82%, with no statistically significant reductions. Our reading is that a procedure people test and use is different from a document imposed by policy; neither study establishes what a rental company's checklist will achieve.

Good result

The tester completes 10 close-outs with matching decisions and records, without asking Dana where the driver notes live.

Bad result

The tester gets nine totals right but asks Dana which fee list applies and sends one case without its required approval.

Procedure 6: Measure clean completion and elapsed time

Measurement tells you whether the documented process works under normal volume, including the waiting that a list of actions can hide. Define each measure before collecting it so a faster-looking number does not conceal rework or customer corrections.

The Lean Enterprise Institute's lexicon defines cycle time as “the time required to produce a part or complete a process, as timed by actual measurement.” Production lead time runs from start to finish through the process or value stream and is usually longer. For Ridgeline, record hands-on touch time separately from the elapsed time between check-in and invoice.

In a hypothetical month, median touch time is 25 minutes and median elapsed time is 3.1 days. The latter includes waiting between actions. A seven-day refund promise can be threatened by that elapsed time even when the coordinator spends less than half an hour working on an event.

First-pass yield counts items that pass every step without rework or correction, divided by items entering the process. Say 72 close-outs start: 49 pass cleanly, 14 need rework before sending, and nine are corrected after sending. The categories total 72.

Ridgeline first-pass yield

FPY = 49 / 72 = 68.1%

Define Ridgeline's error rate after sending as close-outs corrected after the customer or ledger saw them, divided by completed close-outs in the period. If all 72 in the example were completed, that rate is 9 / 72 = 12.5%. It is not 100% - 68.1%: the 14 cases fixed before sending reduce first-pass yield without becoming after-send corrections.

Record a reason for each failure, such as wrong count, wrong fee, or missing photo. Keep the original timestamp and the correction timestamp so the team can distinguish a slow approval queue from repeated work on the same event.

Good result

The monthly record shows 49 clean cases, 14 reworked before sending, nine corrected after sending, and a 3.1-day median elapsed time.

Bad result

The report calls all 23 non-clean cases customer errors, or treats 25 minutes of touch time as the customer's total wait.

Procedure 7: Assign each step to automate, assist, or manual

A process does not need one automation label for every action. Assign each step according to its rule, the consequence of a mistake, and the human authority already specified in the SOP.

Use this hypothetical assignment only after the SOP passes the new operator test. A rule-based calculation still needs the inputs and hold conditions defined in the process.

Close-out stepAssignmentCheck or retained control
Match countsAutomateClass A comparison inside the company; flag a mismatch for review
Price from fee listAutomateUse the approved fee list; hold under rule 1 when photos are missing
Decide waiversAutomate rules 2, 5, 6, and 7; assist rules 3 and 4Draft the human rows; a named human decides or approves
Net against depositAutomateCalculate from the approved charge and recorded deposit
Send refundKeep manual approvalA named human approves before money leaves
Send invoiceAssistPrepare the invoice for a person to check and send

Test the proposed automate and assist steps on 20 to 30 past items before committing, using the test in choosing your first AI use case. Include missing evidence, a disputed charge, and the boundary amounts in the test set. Compare the proposed action and required human handoff with the known result for each item.

Close-out steps sorted into automate, assist, and manual trays

Each close-out step gets its own assignment. The refund approval stays manual while matching and arithmetic can move to automation.

Use the build versus buy guide to choose who should build the automate and assist rows. If your SOP has passed and you want those rows built and run, Iron Goo operations offers audit, build, and operate work: chatbots for repeat inbound questions and an agentic operations layer for internal operations, with scoped credentials and audit logging.

Good result

Count matching and deposit arithmetic are automated, the $75.01 to $500 charge reaches a named approver, and a refund waits for approval.

Bad result

A single “automate close-out” rule sends a refund and an unreviewed charge because the process was given one label.

Procedure 8: Control revisions and review triggers

An SOP becomes unreliable when a fee list, tool, or policy changes and the instructions continue to describe the old process. Version control gives the operator one current document and lets the team identify which rules an automation is running.

Put the short title or ID, revision, date, and page number on every page, using Page 1 of N so a reader can see whether the document is complete. Maintain a master list with SOP number, version number, issuance date, title, author, status, and the history of past versions. Withdraw and archive superseded versions so they are not available as current instructions.

SOP-ACC-004 | Rev 1.1 | 15 November 2026 | Page 1 of 3

Master list:
SOP-ACC-004 | Rev 1.1 | 15 November 2026 |
Event close-out | Dana | Current

Change log:
Rev 1.1 | 15 November 2026 | Updated approved fee list location |
Approved by operations manager

Update and reapprove the SOP whenever the procedure changes. EPA QA/G-6 also recommends review “on a periodic basis, e.g. every 1-2 years”. Our rule of thumb is a scheduled review every six months for any process with an automated step, plus an unscheduled review when any of these observable triggers occurs:

  • The fee list or policy changes.
  • A tool or automation changes.
  • The same unlisted exception appears three times.
  • First-pass yield falls 10 percentage points below its baseline.

For a baseline FPY of 68.1%, the last trigger is 58.1% or lower. Record the period and item count used for both measurements so the comparison is visible. The automation's configuration or prompt must record the SOP revision it implements; check that revision against the master list after each approved change.

Good result

The master list identifies Rev 1.1 as current, the old revision is archived, and the automation records Rev 1.1.

Bad result

The fee list moves, the SOP still points to the old folder, and the automation has no recorded SOP revision.

Close-out SOP acceptance checklist

Use these checks on the actual SOP and its supporting records. Each answer should be observable without asking the author what they intended.

  • The priority table shows monthly runs, minutes per run, calculated hours, error class, score, and the number of people who can perform each candidate process.
  • The selected process has a defined start and end, a SIPOC+CM with five to seven core activities, and a current-state map reviewed by the people who perform it.
  • The swimlane map names each role, shows handoffs and decision paths, and includes checks discovered during the walkthrough.
  • The SOP has an ID, revision, effective date, one named Accountable owner, a purpose, trigger, scope, input locations, numbered steps, decision rules, outputs, exceptions, records, and a review date.
  • Each step has one Accountable person, and the SOP identifies a trained cover for any person who is otherwise the only operator.
  • The decision table states its hit policy, defines each condition and action, and identifies the rows that require a named human decision or approval.
  • A person who has never performed the process has completed 10 past items from the SOP alone, with 10 matching outputs and no question requiring the author.
  • The measurement record separates touch time from elapsed time and shows the counts used for first-pass yield and corrections after sending.
  • Each proposed automated or assisted step has been tested on 20 to 30 past items, including exceptions, and retains the approvals specified in the SOP.
  • Every page identifies the SOP, revision, date, and page number; the master list identifies the current version; withdrawn versions are archived.
  • The review schedule and change triggers are recorded, and each automation identifies the SOP revision it implements.
Free ebook

Put your next steps in order

Build on what you have just read with a free ebook on semantic SEO and AI visibility. Get worked examples, decision rules, checklists and a do-this-week action in every chapter, plus a six-week plan for your site.

By signing up and confirming your address, you consent to receive the free ebook plus one email every two weeks with 3 or 4 new Iron Goo videos, guides and articles, and nothing else; unsubscribe any time with one click.

Related in Business

Ready to move?

Tell us where your business is today. A written assessment lands in your inbox within two business days.

Talk to us