The best way to learn how to write an SOP is to study real examples. This guide provides 18 SOP examples across 6 industries, each with a step-by-step outline you can adapt for your team.

For foundational SOP knowledge, start with our complete guide to standard operating procedures. For ready-to-use structures, see our SOP templates collection.

Jump to Industry

1. Technology / SaaS

Technology teams need SOPs for processes that are high-stakes (deployments, incidents) and high-frequency (code review, releases). Without documented procedures, institutional knowledge walks out the door when engineers leave.

Production Deployment SOP

Pre-deployment: Run automated test suite, verify staging environment matches production

Deployment window: Notify team in Slack, confirm rollback plan is ready

Deploy: Push to production via CI/CD pipeline, monitor error rates for 15 minutes

Verification: Run smoke tests, check key user flows, verify database migrations applied

Rollback criteria: If error rate exceeds 1% or P0 bug detected, execute rollback within 5 minutes

Post-deploy: Update deployment log, close related tickets, notify stakeholders

Incident Response SOP

Detection: Alert fires from monitoring (PagerDuty, Datadog) or user report

Assessment: Incident commander classifies severity (P1-P4), opens incident channel

Communication: Post status page update within 10 minutes for P1/P2

Resolution: Engineers investigate and fix, communicating progress every 30 minutes

Recovery: Verify fix in production, confirm metrics return to baseline

Post-mortem: Write blameless post-mortem within 48 hours, identify action items

Code Review SOP

PR requirements: Description, test coverage, screenshots for UI changes

Reviewer assignment: Auto-assign via CODEOWNERS or manual selection

Review checklist: Logic correctness, edge cases, security implications, performance

Feedback format: Distinguish blocking vs. non-blocking comments

Approval criteria: At least one approval from a maintainer, CI passing

Merge: Squash and merge, delete branch, verify deployment

Common Pitfalls in Technology / SaaS SOPs

Deployment SOPs that only cover the happy path — always document rollback procedures

Incident response without clear severity definitions — teams waste time debating priority

Code review SOPs that are too rigid — they slow down velocity without improving quality

2. Healthcare

Healthcare SOPs are not optional — they are mandated by regulations like HIPAA, OSHA, and Joint Commission standards. These procedures directly impact patient safety, and non-compliance can result in fines, lawsuits, or loss of accreditation.

Patient Intake SOP

Greeting: Greet patient, verify appointment, provide intake forms

Identification: Verify identity with two identifiers (name + DOB)

Insurance: Copy insurance card, verify coverage, collect copay

Medical history: Review and update medical history, allergies, current medications

Consent: Obtain signed consent forms for treatment and HIPAA acknowledgment

Triage: Measure vitals (BP, temp, weight), record in EHR, route to provider

Medication Administration SOP

Verify the 5 Rights: Right patient, right drug, right dose, right route, right time

Check allergies: Cross-reference patient allergy list in EHR

Prepare medication: Follow preparation guidelines, double-check dosage calculation

Administer: Follow route-specific protocol (oral, IV, injection)

Document: Record administration in EHR immediately with time and dose

Monitor: Observe patient for adverse reactions per drug-specific monitoring schedule

Equipment Sterilization SOP

Collection: Gather used instruments in designated contaminated bin

Pre-cleaning: Rinse instruments within 30 minutes of use to prevent biofilm

Cleaning: Run through ultrasonic cleaner or manual scrub per manufacturer specs

Inspection: Check each instrument for damage, corrosion, or residue

Sterilization: Load autoclave per capacity guidelines, run appropriate cycle

Storage: Store in sealed sterile packaging, label with sterilization date and expiry

Common Pitfalls in Healthcare SOPs

Assuming staff know the 5 Rights — new hires need explicit training on verification

Sterilization SOPs without manufacturer-specific parameters — generic cycles may not work

Missing documentation steps — if it is not documented, it did not happen (legally)

3. Manufacturing

Manufacturing SOPs ensure product consistency, worker safety, and regulatory compliance (ISO 9001, OSHA). They are essential for maintaining quality at scale and training operators on equipment they may not have used before.

Equipment Setup SOP

Safety check: Verify lockout/tagout completed, PPE worn, area clear

Materials: Confirm raw materials match production order specifications

Calibration: Verify equipment calibration is current (check calibration sticker)

Setup: Follow machine-specific setup sequence with parameter settings from spec sheet

First article: Run first piece, measure against quality spec, document results

Production: Begin run only after first article approval, monitor output every 30 minutes

Quality Inspection SOP

Sampling: Pull samples per AQL table (e.g., 5 units per 500-unit batch)

Visual inspection: Check for surface defects, color consistency, labeling accuracy

Dimensional: Measure critical dimensions with calibrated instruments

Functional: Test operation per product test specification

Documentation: Record results in inspection log, note any deviations

Disposition: Accept, reject, or quarantine batch based on results

Safety Protocol SOP

Daily safety briefing: Review hazards specific to today's production schedule

PPE verification: Confirm all operators have required PPE before entering production floor

Machine guarding: Verify all safety guards are in place and functional

Chemical handling: Follow SDS (Safety Data Sheet) for each chemical in use

Incident reporting: Report all incidents (including near-misses) within 1 hour

Emergency procedures: Post evacuation routes, review quarterly with all staff

Common Pitfalls in Manufacturing SOPs

Equipment setup SOPs without first-article inspection — catching defects early saves entire batches

Safety SOPs that live in a binder nobody reads — post visual SOPs at the work station

Skipping calibration checks — out-of-calibration equipment produces out-of-spec product silently

4. Retail / E-commerce

Retail and e-commerce SOPs ensure consistent customer experience across locations, shifts, and team members. They are critical for order accuracy, returns handling, and inventory management where mistakes directly impact customer satisfaction and margins.

Order Fulfillment SOP

Order receipt: System pulls new orders every 15 minutes, assigns to next available picker

Picking: Follow pick list, scan each item barcode to verify correct product and quantity

Packing: Select box size per packing guide, include packing slip and return label

Quality check: Verify item count, check for damage, confirm shipping label matches order

Shipping: Scan tracking barcode, place in carrier staging area, update order status

Exception handling: If item is out of stock, notify customer within 2 hours with options

Returns Processing SOP

Request intake: Customer submits return via portal or contacts support

Eligibility: Verify purchase within return window (30 days), check return policy exclusions

Authorization: Generate RMA number and prepaid return label

Receipt: Inspect returned item for damage, verify matches original order

Disposition: Restock (if sellable), send to refurbishment, or dispose

Refund: Process refund to original payment method within 48 hours of receipt

Inventory Count SOP

Preparation: Print count sheets organized by location, freeze inventory transactions

Counting: Two-person count — one counts, one records. Count each item twice.

Reconciliation: Compare physical count to system count, flag variances over 2%

Investigation: Research large variances (check receiving logs, transfer records, damage reports)

Adjustment: Enter approved adjustments in system with variance explanation

Reporting: Submit count summary to management with variance analysis

Common Pitfalls in Retail / E-commerce SOPs

Fulfillment SOPs without exception handling — stockouts happen, and the team needs a plan

Returns SOPs without clear disposition criteria — items pile up in limbo

Inventory counts without transaction freeze — new sales during counting create phantom variances

5. Finance

Finance SOPs are driven by accuracy requirements and regulatory compliance. Mistakes in financial processes can lead to audit findings, regulatory penalties, and material misstatements. SOPs provide the controls that auditors want to see.

Account Reconciliation SOP

Timing: Complete reconciliation within 5 business days of month-end close

Data gathering: Export GL balance and bank/sub-ledger statement for the period

Matching: Match transactions between GL and source, flag unmatched items

Investigation: Research unmatched items — timing differences, errors, or fraud indicators

Adjustments: Prepare journal entries for confirmed errors, get manager approval

Documentation: Sign and date reconciliation, attach supporting documents, file for audit

Audit Preparation SOP

Timeline: Begin preparation 30 days before audit start date

Document collection: Gather requested documents per auditor PBC (Prepared by Client) list

Reconciliations: Ensure all account reconciliations are current and signed

Access: Set up auditor workspace, system access, and point-of-contact list

Walkthrough prep: Prepare process narratives for key controls auditors will test

Issue tracking: Maintain log of auditor questions and responses with deadlines

Client Onboarding (Financial Services) SOP

KYC verification: Collect and verify identity documents per regulatory requirements

Risk assessment: Score client risk level (low/medium/high) using assessment matrix

Account setup: Create accounts in system, assign relationship manager

Agreement execution: Send engagement letter or account agreement for signature

System configuration: Set up reporting, access permissions, and billing

Welcome: Send welcome packet with key contacts, service schedule, and portal access

Common Pitfalls in Finance SOPs

Reconciliation SOPs without materiality thresholds — investigating every penny wastes time

Audit prep starting too late — 30 days is minimum; large organizations need 60+

KYC procedures that do not specify document types by jurisdiction — requirements vary significantly

6. Marketing

Marketing teams need SOPs to maintain brand consistency, meet publishing deadlines, and execute campaigns without dropping steps. This is especially important for agencies managing multiple client brands simultaneously.

Content Publishing SOP

Brief: Content manager assigns topic with target keyword, audience, and format spec

Draft: Writer produces first draft within 3 business days, following brand voice guide

Review: Editor reviews for accuracy, SEO optimization, and brand compliance

Design: Designer creates featured image and any in-article graphics

Final approval: Marketing manager approves content and scheduled publish date

Publish: Upload to CMS, verify formatting, add internal links, schedule social promotion

Campaign Launch SOP

Planning: Define goals, KPIs, budget, target audience, and timeline

Creative: Develop ad creative, landing pages, and email sequences

Technical setup: Configure tracking pixels, UTM parameters, and conversion events

QA: Test all links, forms, tracking, and mobile rendering before launch

Launch: Activate campaigns per channel, verify ads are serving, check initial metrics

Monitoring: Daily check for first week, weekly after that. Report against KPIs.

Brand Guidelines Enforcement SOP

Asset requests: All external-facing materials go through brand review before publishing

Review checklist: Verify logo usage, color palette, typography, tone of voice, and imagery

Approval levels: Minor pieces (social posts) need one approval; major pieces (website, ads) need two

Vendor management: Send brand kit to external vendors with usage guidelines and examples

Violation handling: Flag non-compliant materials, provide corrective guidance, track repeat issues

Quarterly audit: Review all active channels for brand consistency

Common Pitfalls in Marketing SOPs

Content SOPs without SEO requirements in the brief — retrofitting SEO is harder than building it in

Campaign launches without a QA checklist — broken tracking means you cannot measure results

Brand guidelines that are too restrictive — teams work around them instead of following them

Build SOPs your team actually follows

Turn any of these examples into trackable checklists with Pathalize. Assign steps, track completion, and identify where processes break down.

How to Adapt These Examples

Start with the closest match

Pick the example that most closely resembles your process. You will customize it, but the structure saves you from starting with a blank page.

Replace generic tools with yours

Where the example says "update in EHR" or "post in Slack," replace with your actual systems — Salesforce, Teams, Jira, or whatever your team uses.

Add your decision points

Real processes have branches. Add "if X, then Y" decision points where your process diverges based on situation, severity, or customer type.

Include time expectations

Each step should have a target time or deadline. "Respond within 2 hours" is better than "respond promptly." Measurable targets enable accountability.

Validate with practitioners

Before publishing, have someone who performs this task daily review the SOP. They will catch gaps, incorrect sequences, and missing edge cases.