guides 45 min read

50 SOP Examples by Industry (2026): Real Process Structures You Can Use Today

50 standard operating procedure examples across 11 industries — restaurants, healthcare, cleaning, construction, auto repair, daycare, and more. See the actual steps inside real SOPs.

CM
Chris McGennis

Most articles that promise “SOP examples” hand you a list of process names and call it a day. That’s not useful. Knowing you should have a “customer complaint SOP” doesn’t tell you what goes inside it.

This page is different. For each of the 50 examples below, I’ve included the actual process structure — the 5 to 8 steps that make up the backbone of that SOP. Not the full document, but enough that you can see what a real SOP looks like and whether yours covers the same ground.

I’ve organized examples by industry. Jump to what’s relevant to you.

One note before you start: these are reference structures, not finished SOPs. Your versions need your specific software, your supplier names, your room numbers, your dollar thresholds. The structure here gets you to first draft in a fraction of the time. If you want to build on these examples in a structured tool, What’s the Process For is free to start.


Table of Contents

  1. Restaurants and Food Service
  2. Healthcare and Medical Practices
  3. Cleaning and Janitorial
  4. Construction and Trades
  5. Office Administration
  6. Customer Support
  7. Ecommerce and Retail
  8. Churches and Nonprofits
  9. Auto Repair
  10. Daycare and Childcare
  11. Fitness and Salon
  12. What to Do With These Examples

Restaurants and Food Service {#restaurants-and-food-service}

Restaurants run on repetition. The same opening sequence, the same closing checklist, the same line setup — every single day. When those processes aren’t written down, you’re paying for the same training conversation over and over, and you’re trusting your health inspection score to whoever happens to be working that day.

The average restaurant turns over most of its hourly staff every year. If your processes live in your head or in the head of one long-tenured shift lead, you’re rebuilding from zero every time someone quits.

For a full breakdown of the 10 processes every restaurant should document, see the restaurant SOP template guide.


1. Restaurant Opening Checklist

What this SOP covers: The sequence of tasks a manager and kitchen staff complete before the restaurant is ready to serve its first customer of the day — from equipment power-on through final walk of the dining room.

Process structure:

  • Turn on all cooking equipment in sequence (fryers, flat top, ovens, steam tables) with warm-up times noted for each
  • Check walk-in cooler and freezer temperatures; log on the HACCP sheet with your initials and timestamp
  • Pull prep sheets from the night before; confirm what’s needed based on reservation count
  • Set up line stations — cutting boards, containers, utensils, and mise en place per station card
  • Turn on POS system; confirm menu pricing is current and printer paper is loaded
  • Review reservation list; adjust floor plan and table assignments for covers
  • Final manager walk: dining room set, bathrooms stocked, staff assignments confirmed, doors unlocked on time

2. Restaurant Closing Checklist

What this SOP covers: End-of-shift tasks that ensure the kitchen is safe, the cash is reconciled, and the next opening crew doesn’t walk into a disaster.

Process structure:

  • Break down all stations: cool and store hot food properly, label and date all containers
  • Clean and sanitize all prep surfaces, cutting boards, and cooking equipment
  • Mop floors in sequence (kitchen first, then dining room) using correct dilution ratios
  • Run the dishwasher final cycle; ensure all dishes are dry and stored
  • Close out POS, print the Z-report, and count the cash drawer against the report
  • Verify all gas equipment is off; walk the walk-in one final time to confirm temps
  • Log the closing in the manager’s notebook; set alarm and lock in sequence per post on back door

3. End-of-Shift Handoff

What this SOP covers: The structured transfer of information between a departing shift manager and the incoming one, so nothing falls through the gap between shifts.

Process structure:

  • Departing manager fills out the shift log: covers served, any 86’d items, equipment issues, staff incidents
  • Review reservation list for the incoming shift; flag any VIPs, large parties, or requests
  • Walk the line together and verbally confirm prep levels on all stations
  • Note any equipment that’s running slow or needs attention before next service
  • Hand off active customer complaints or pending issues (never drop an open loop at shift change)
  • Incoming manager confirms receipt and signs the log; departing manager is released

4. Cash Drop Procedure

What this SOP covers: How a bartender or server handles a cash drop to the safe mid-shift — a process that matters both for security and for reconciliation accuracy at close.

Process structure:

  • Count down the drawer to a set float ($100 or per your house rule) and place excess cash in an envelope
  • Record the drop amount, time, and your name on the envelope and the cash log sheet
  • Walk the envelope to the manager; manager verifies count and witnesses the drop
  • Manager places envelope in the safe; both parties sign the log
  • Safe log stays with the manager; do not leave cash sitting on a desk or back counter
  • At close, pull all drops and reconcile against the Z-report before counting the final drawer

5. Vendor Delivery Receiving

What this SOP covers: How your team receives a food or supply delivery — verifying quantities, checking temperatures, and rejecting product that doesn’t meet spec.

Process structure:

  • Confirm you have the purchase order before the truck arrives; know what’s coming
  • Inspect the truck and packaging before unloading — look for damaged boxes, wet cardboard, or condensation on frozen goods
  • Check temperatures of all refrigerated and frozen deliveries with your probe thermometer; log each reading
  • Count delivered quantities against the invoice line by line; note any shorts or substitutions on the invoice
  • Reject any product with broken seals, off temperatures, or signs of pest activity; document rejections in writing
  • Store product by FIFO (first in, first out): new product behind existing, labels facing out
  • Sign the invoice with any variances noted; give the driver their copy and file yours

6. Register Reconciliation

What this SOP covers: The daily process for counting cash registers, matching them against POS totals, and documenting variances — the backbone of honest cash management.

Process structure:

  • At close, remove drawer and bring to the counting area; do not count on the floor
  • Count all bills by denomination, then coins; record totals on the count sheet
  • Pull the POS Z-report for that drawer’s session; enter the expected totals
  • Calculate variance: actual count minus expected. Variances of +/- $2 are acceptable per your policy; anything larger triggers a review
  • Manager reviews the count and signs off; teller initials the sheet
  • Place cash in the bank deposit bag; log the bag number and total on the deposit record
  • File the count sheet and Z-report together; keep for 30 days minimum

7. Stockroom Restock

What this SOP covers: How your team moves inventory from the stockroom to the floor or line — a process that affects both product availability and shrink control.

Process structure:

  • Pull the par sheet or reorder list for your station or section; confirm what needs restocking before pulling anything
  • Pick items from the stockroom in FIFO order; rotate stock as you go
  • Log quantities removed from the stockroom on the inventory movement sheet
  • Stage product at the station before placing it — don’t just dump boxes on a shelf
  • Check expiration dates as you restock; pull any items within 3 days of expiration for manager review
  • Update the stockroom count sheet after the pull so the next person’s count is accurate
  • Notify manager if any item is running below the reorder point

Healthcare and Medical Practices {#healthcare-and-medical-practices}

Healthcare SOPs serve two purposes: consistency of patient care, and regulatory compliance. Every step in a clinical process carries liability, so the process needs to be written, reviewed, and followed in the same way every time.

For dental office SOPs specifically, see the dental office SOP template. For general medical practices, the medical practice SOP template covers the core processes.


8. New Patient Intake

What this SOP covers: The end-to-end process for registering a new patient — from the first call through confirmed appointment and completed paperwork.

Process structure:

  • Collect patient demographics, insurance information, and chief complaint during the initial call; enter directly into your EHR
  • Run insurance eligibility check (same-day, not morning-of); note deductible, copay, and any referral requirements
  • Send new patient packet via patient portal or mail: intake forms, HIPAA notice, insurance card request
  • Set intake form deadline (48 hours before appointment); call to confirm receipt if portal isn’t activated
  • Morning of appointment, confirm chart is complete: insurance verified, forms signed, referral on file if required
  • Flag any clinical notes from the referring provider or prior records; attach to the chart before the provider sees it
  • Day-of check-in: verify ID and insurance card against chart; collect copay before the visit

9. Patient Check-Out

What this SOP covers: The steps that happen after the provider exits the exam room — charge capture, follow-up scheduling, and any patient education or orders.

Process structure:

  • Pull charges from the visit: confirm CPT and ICD-10 codes match the provider’s note before submitting
  • Collect patient responsibility (copay, coinsurance, outstanding balance) before the patient leaves the building
  • Schedule any follow-up or referral appointments before the patient is released
  • Print or portal-send the After Visit Summary; walk the patient through any medication changes or orders
  • Route pending lab orders or imaging requests; give the patient the facility information and estimated turnaround
  • Document the visit as complete in your EHR; confirm no open orders are sitting in a “pending” state
  • Add to follow-up queue if the patient needs a callback for lab results

10. Medical Record Release

What this SOP covers: How your office responds to a patient’s request to release medical records — a process governed by HIPAA and your state’s laws.

Process structure:

  • Receive the request: patient must submit a signed, dated Authorization to Release Medical Information form
  • Verify patient identity — compare signature against the file; never release records on a verbal request alone
  • Check the authorization for completeness: specific records requested, recipient, and purpose must all be present
  • Log the request in the release log with date received and identity verification method
  • Process within the legal timeframe for your state (typically 30 days; 15 days in some states)
  • Release records through the authorized method only (portal, encrypted email, mail, or fax — per the authorization)
  • Document release date and method in the log; retain the signed authorization in the file for 6 years

11. Appointment Reminder and No-Show Protocol

What this SOP covers: The automated and manual process for reducing no-shows — and what to do when a patient doesn’t arrive.

Process structure:

  • Send automated reminder 72 hours before the appointment via patient-preferred channel (text, email, or portal)
  • Send secondary reminder 24 hours before; include date, time, provider name, and any prep instructions
  • At 10 minutes past the scheduled time, call the patient directly; document the call attempt in the chart
  • At 15 minutes, designate the appointment as a no-show in the EHR
  • If the slot cannot be backfilled, document the revenue impact in the daily report
  • No-show patients receive a rescheduling call from the front desk within 24 hours; document attempts
  • After 3 no-shows, flag the chart for manager review per your no-show policy

12. Equipment Sterilization and Maintenance Log

What this SOP covers: The daily and weekly process for sterilizing clinical instruments and maintaining sterilization equipment — required for any clinical or dental practice.

Process structure:

  • After each patient use, instruments go immediately into enzymatic solution; never dry-clean
  • Pre-clean instruments at the sink: scrub, rinse, inspect for residue
  • Package instruments in sealed pouches with chemical indicator strips; label with date and autoclave cycle number
  • Run autoclave cycle per manufacturer specs; log cycle number, temperature, time, and load contents in the sterilization log
  • Verify chemical indicator changed correctly before releasing instruments; failed indicators mean re-run, full stop
  • Weekly: run biological indicator (spore test); log result and keep records 3 years minimum per CDC guidelines
  • Monthly: check autoclave seals, gaskets, and drain for wear; document inspection in the maintenance log

13. End-of-Day Clinical Closing

What this SOP covers: The structured closing process for a clinical practice — covering both the front desk and the clinical areas.

Process structure:

  • Clinical staff: clean and disinfect all exam rooms; restock supplies to par level; verify no specimens are pending pickup
  • Pull all paper superbills or confirm all charges are entered in the EHR before the last provider leaves
  • Run the end-of-day batch in your clearinghouse; confirm claim count matches expected
  • Post any ERA payments received today; flag denied or rejected claims for follow-up tomorrow
  • Front desk: balance the day’s payments against charge report; prepare bank deposit if your policy is daily deposits
  • Lock medication sample cabinet; verify controlled substance log if applicable
  • Arm security, lock in sequence, and note building departure time in the manager’s log

14. New Staff Credential Verification

What this SOP covers: The HR and compliance process for confirming that a new clinical hire holds the licenses, certifications, and clearances required before their first patient contact.

Process structure:

  • Collect copies of all required credentials at offer stage: license number, expiration date, DEA number if applicable
  • Run primary source verification — check the state licensing board directly, not just the certificate on the wall
  • Run background check through your approved vendor; do not schedule first shift until cleared
  • Verify BLS/CPR and any specialty certifications specific to the role; document expiration dates
  • Complete I-9 and employment eligibility verification; store separately from the personnel file
  • Add credential expiration dates to your reminder calendar; flag 90 days before any expiration
  • Document all verification steps in the credentialing file; keep for the duration of employment plus 7 years

Cleaning and Janitorial {#cleaning-and-janitorial}

A cleaning business lives or dies on consistency. Your crew can’t call you every time they’re not sure what goes in a bathroom versus a kitchen, or which products to use where. Written processes are also your liability shield — if a client claims your crew damaged something, your job log and checklist are the first things your insurance carrier asks for.

The cleaning business SOP template covers the full list of processes to document.


15. Residential Cleaning Checklist (Room-by-Room)

What this SOP covers: The standard sequence and scope for a recurring residential cleaning — the exact tasks, in the correct order, for each room type.

Process structure:

  • Start with the kitchen: clear counters, wipe down surfaces, clean stovetop, microwave exterior and interior, sink, backsplash; sweep and mop last
  • Bathrooms: toilet bowl, exterior, and base; sink and faucet; mirror; tub and shower; restock toilet paper and hand soap; sweep and mop
  • Bedrooms: dust all surfaces including ceiling fans and baseboards; make beds per client instruction; vacuum and empty small trash cans
  • Living areas: dust shelving and electronics (not screens unless instructed); vacuum furniture; vacuum or mop floors per surface type
  • Walk through each room before moving on; use the checklist as your exit criteria, not your memory
  • Note any damage observed (pre-existing or new) on the job sheet before leaving the property
  • Lock up per client’s key/code instructions; log job-complete time in your scheduling software

16. Commercial Cleaning End-of-Night

What this SOP covers: The nightly routine for a commercial office cleaning crew — covering restrooms, common areas, and security steps.

Process structure:

  • Empty all trash and recycling bins; replace liners; transport to the dumpster or designated collection point
  • Restock all restrooms: toilet paper, paper towels, soap dispensers; clean toilets, urinals, sinks, and mirrors
  • Vacuum all carpeted areas; mop hard floors with correct product for the surface (no bleach on sealed concrete, no ammonia on natural stone)
  • Clean break room: wipe counters, clean microwave interior, wipe refrigerator exterior, empty and clean sink
  • Dust horizontal surfaces in open-plan areas; clean glass partitions and door handles
  • Log any damaged fixtures, burned-out bulbs, or security concerns on the nightly report; send to client contact before leaving
  • Lock and alarm per client’s documented procedure; time-stamp your exit in your job tracking app

17. Move-In / Move-Out Deep Clean

What this SOP covers: The checklist for a full deep clean of a vacant residential or commercial property — the most time-intensive and highest-stakes cleaning job type.

Process structure:

  • Walk the property first and note all damage, missing fixtures, and areas needing extra attention before starting
  • Start with ceilings and work down: ceiling fans, light fixtures, cobwebs in corners
  • Kitchen deep clean: clean inside all cabinets and drawers, refrigerator interior (remove shelves), oven interior with degreaser, range hood filter
  • Bathroom deep clean: remove shower head and soak in descaler; clean grout with brush; scrub drain covers; clean inside vanity cabinet
  • All windows: interior glass, frames, and window sills (add exterior windows to scope if included in quote)
  • Baseboards, door frames, and switch plates throughout
  • Final walk: document condition with photos before handing keys back to the property manager

18. Chemical Safety and Equipment Handling

What this SOP covers: The procedures for safely handling, diluting, storing, and disposing of cleaning chemicals — required for both regulatory compliance and team safety.

Process structure:

  • Maintain an SDS (Safety Data Sheet) binder in every vehicle; every chemical you use must have a current SDS on hand
  • Never mix chemicals: no bleach with ammonia, no bleach with vinegar, no acids with bases — post this list in every supply area
  • Dilute concentrates at the correct ratio using a measuring cup, not a pour; log the product, dilution rate, and batch date on the spray bottle label
  • Wear appropriate PPE for each chemical: gloves minimum; goggles and respirator for strong acids, degreasers, or enclosed-space disinfectants
  • Store chemicals in original containers or clearly labeled spray bottles; never in food containers
  • Dispose of chemical waste per local regulation — most residential diluted products can go down the drain with water; concentrated disposal varies
  • Report any chemical spills or exposure to the crew lead immediately; first aid steps are on the SDS

19. Post-Construction Cleaning Sequence

What this SOP covers: The structured approach to cleaning a construction site or freshly renovated space — dust and debris management before the standard cleaning begins.

Process structure:

  • Pre-clean sweep: remove all construction debris, leftover materials, and packaging before bringing in any cleaning equipment
  • HEPA vacuum all surfaces — walls, window sills, HVAC vents, cabinet interiors — to capture drywall dust before it becomes airborne again
  • Clean all windows inside; remove paint and adhesive residue with appropriate scraper or solvent per surface type
  • Wipe all cabinetry, counters, and fixtures with a damp cloth; drywall dust reactivates when wet, so work in order
  • Mop hard floors last, in sections, starting from the farthest point from the exit
  • Final inspection: check every room with a flashlight at a low angle to catch remaining dust on floors and ledges
  • Document and photograph the finished space; get client sign-off before leaving the site

Construction and Trades {#construction-and-trades}

Construction SOPs exist primarily for three reasons: job site safety, project consistency, and liability protection. An undocumented process on a job site is a OSHA citation waiting to happen and a disputed invoice with no paper trail to back you up.

For industry-specific templates, see the construction company SOP template, the electrician SOP template, the HVAC SOP template, and the roofing SOP template.


20. Job Site Safety Inspection (Morning Walk)

What this SOP covers: The daily safety inspection a foreman or site supervisor runs before any crew members begin work — the 15-minute walk that keeps OSHA and insurance carriers happy.

Process structure:

  • Inspect all access points: ladders secured, scaffolding stable, no trip hazards at entry points
  • Verify all required PPE is present and in condition: hard hats, safety glasses, high-visibility vests, and any task-specific gear (harnesses, respirators)
  • Check temporary electrical: GFCI protection on all outdoor circuits, no damaged cords, panel locked out if required
  • Inspect the work area for overhead hazards: ceiling conditions, structural elements that may shift, active utility lines
  • Confirm first aid kit and fire extinguisher are accessible and stocked
  • Brief the crew on the day’s tasks and any site-specific hazards; note attendance in the crew log
  • Sign and date the inspection checklist; file it in the site safety binder — this is your OSHA documentation

21. Subcontractor Coordination and Scheduling

What this SOP covers: The process for scheduling, confirming, and coordinating subcontractors on a project — one of the most common sources of delay and rework on construction projects.

Process structure:

  • Confirm all required subs are under signed contract before their trade is scheduled on the critical path
  • Issue a written schedule with each sub’s start date, duration, and milestones; get written confirmation back
  • Two days before each sub’s start: confirm crew size, equipment needs, and material deliveries are on track
  • Day before: confirm site access, parking, laydown area, and any permits they need to pull
  • At sub kickoff: walk the scope together; clarify any interface with other trades; note anything that could cause a change order
  • During the sub’s work: inspect at defined milestones before they cover work (framing before sheathing, rough-in before drywall)
  • At completion: punch-list walkthrough together; confirm all their permits are closed before final payment

22. Equipment Maintenance and Inspection Log

What this SOP covers: The recurring maintenance schedule for job site equipment — generators, compressors, lifts, and vehicles — to reduce breakdowns and document compliance.

Process structure:

  • Assign each piece of equipment a unique ID and a maintenance schedule card (manufacturer intervals or your company standard, whichever is more frequent)
  • Daily pre-use check: fluid levels, tire pressure, hydraulic lines, safety guards, warning lights — operator signs off before first use
  • Log each check with date, operator name, equipment ID, and any noted issues
  • Any defect found during pre-use: tag the equipment Out of Service; notify the foreman before using it regardless of timeline pressure
  • Scheduled service (oil change, filter, etc.): log the service date, work performed, and parts used; file the receipt
  • Annual third-party inspection for lifts and cranes per ANSI/OSHA requirements; maintain certificates on file
  • Review the maintenance log quarterly; identify any equipment approaching end of expected service life and flag for replacement planning

23. Customer Change Order Process

What this SOP covers: The process for documenting, pricing, and getting signed approval for any work that falls outside the original project scope — the process that protects your margin.

Process structure:

  • When a change request is identified, stop work on the affected area until scope is confirmed in writing
  • Prepare a written Change Order Request with: description of the change, reason for the change, cost impact (labor and materials), and schedule impact
  • Submit to the customer for review; do not begin the changed work until you have a signed CO
  • Log the approved CO in your project file and update the project schedule and budget accordingly
  • Never accept verbal authorization for scope changes; note in the CO form that verbal directions are not binding
  • Bill for change order work on a separate line item on the invoice — keep original scope and changes clearly separated
  • Close out the CO when the work is complete and the customer has inspected it

24. Project Closeout and Final Walkthrough

What this SOP covers: The structured process for completing a construction project — from punch-list through final documentation and payment.

Process structure:

  • Generate the punch list by walking the project with the customer or GC; document every outstanding item in writing, with photos
  • Assign each punch item an owner (your crew or a sub) and a completion date
  • Complete all punch items and re-walk with the customer; get written sign-off that punch is complete
  • Collect all close-out documentation: as-builts, warranties, permit inspection cards, equipment manuals, and the Manufacturer’s Certificate of Compliance if applicable
  • Submit final application for payment per your contract terms; include all required lien waivers (conditional or unconditional per your state)
  • Confirm all subcontractors and suppliers have been paid and have issued their lien waivers before the customer’s final check is deposited
  • Archive project documents for 7 years minimum; photograph the completed project for your portfolio

Office Administration {#office-administration}

Office admin SOPs are often the last to get written because they feel less urgent than the customer-facing ones. That’s backwards. An undocumented payroll process, an inconsistent invoice format, or an unclear expense reimbursement rule creates friction every month — and causes real money errors when the person who knows how it works is out sick.

For accounting firm SOPs, see the accounting firm SOP template. For law firms, see the law firm SOP template. For marketing agencies, see the marketing agency SOP template.


25. Invoice Generation and Delivery

What this SOP covers: The step-by-step process for generating an accurate invoice and delivering it to the client — the process that determines whether you get paid on time.

Process structure:

  • Pull the project or time tracking report for the billing period; verify all time and expenses are posted before generating the invoice
  • Create the invoice in your billing software (QuickBooks, FreshBooks, etc.); confirm: client name, address, invoice number, billing period, itemized services, rates, and total
  • Attach any required supporting documentation (timesheets, expense receipts, signed work orders) per the client’s contract
  • Review the invoice against the contract: correct rate, correct units, no duplicate line items, payment terms match the signed agreement
  • Deliver the invoice via the client’s preferred method (email, portal, or mail); log the delivery date in the project file
  • Set a follow-up reminder for 3 days before the due date; if unpaid, follow the collections escalation process
  • Post payment to the project record when received; match against the invoice and mark as closed

26. Expense Reimbursement Request

What this SOP covers: The process an employee follows to submit a business expense for reimbursement — and the process a manager follows to review and approve it.

Process structure:

  • Employee submits all receipts within 30 days of the expense (policy: no receipt, no reimbursement — no exceptions)
  • Complete the expense report form: date, vendor, amount, business purpose, project code, and receipt attached
  • Manager reviews: expense is within policy (see expense policy), receipt matches the amount, business purpose is legitimate
  • Approved reports are forwarded to Accounts Payable by the 15th of the month for inclusion in that month’s reimbursement run
  • Reimbursements are paid with the next payroll cycle or by standalone ACH — whichever your policy specifies
  • Denied or incomplete submissions are returned to the employee with a written note within 5 business days
  • All approved expense reports are filed by month and retained for 7 years per IRS recordkeeping requirements

27. Payroll Close

What this SOP covers: The end-of-period process for closing payroll — from verifying hours through submission and confirmation.

Process structure:

  • Two business days before the close deadline: notify all employees to submit final hours/timesheets and flag any corrections
  • Run a pre-close report: compare submitted hours to scheduled hours; flag variances greater than 2 hours for manager sign-off
  • Confirm any salary changes, new hires, or terminations effective this period are entered in the payroll system
  • Review deductions: confirm benefit deductions, garnishments, and tax withholding elections match the employee’s current authorization on file
  • Submit payroll to the processor by the required cut-off time; confirm submission receipt
  • After processing: run the payroll journal and reconcile to your general ledger; post the journal entry by payroll date
  • File the payroll register; retain all payroll records for 4 years minimum per FLSA and IRS requirements

28. New Client Onboarding

What this SOP covers: The structured process for converting a signed client into an active, fully set-up account — the process that sets the tone for the entire relationship.

Process structure:

  • Upon signed contract: send welcome email within 24 hours with your contact information, next steps, and the kickoff meeting invite
  • Kickoff meeting agenda: confirm scope, deliverables, timeline, and points of contact; document decisions and send a written summary within 24 hours
  • Set up the client in all required systems: CRM, project management, billing, and any client-specific portals
  • Complete the internal brief: client goals, preferences, known sensitivities, and anything discussed in the sales process that the delivery team needs to know
  • Deliver any required onboarding documentation (intake forms, access credentials, NDAs) within the first week
  • Schedule a 30-day check-in at the kickoff; calendar it with both parties before the call ends
  • Assign a primary contact and a backup; both names go in the client record and in the welcome email

29. Social Media Post Scheduling

What this SOP covers: The recurring process for creating, approving, and scheduling social media content — a process that often breaks down to ad-hoc posting with no consistency.

Process structure:

  • Content is drafted the week before publishing; all drafts go into the content calendar in your scheduling tool (Buffer, Hootsuite, Sprout, etc.)
  • Each draft includes: platform, post copy, image or video, link, hashtags (if applicable), and target publish date/time
  • All content is reviewed by the designated approver before scheduling; no post goes live without approval
  • Images are sized correctly for each platform per your asset spec sheet (dimensions are in the shared folder)
  • Schedule posts for your confirmed peak engagement windows; do not post in real-time unless it’s time-sensitive
  • Monitor comments and mentions for the first 2 hours after each post; respond to questions within 4 business hours
  • At month-end, pull analytics from each platform; log impressions, engagement rate, and follower change in the reporting sheet

30. Fire Drill and Emergency Evacuation

What this SOP covers: The structured process for conducting a fire drill — including the schedule, roles, and documentation required by most insurance carriers and many jurisdictions.

Process structure:

  • Schedule at least two drills per year (quarterly is best practice); notify leadership but not staff at least 24 hours prior
  • Designate a floor warden for each area; confirm wardens know their zone and the nearest two exits
  • Sound the alarm; all staff evacuate via the nearest safe exit to the designated assembly area
  • Floor wardens do a sweep of their zone (restrooms, conference rooms, storage) before leaving
  • At the assembly area, take a headcount against the office roster; account for all staff, visitors, and contractors
  • Record the time from alarm to full assembly; log any issues (blocked exits, slow evacuation, staff who didn’t know the assembly point)
  • Debrief within 24 hours: share the log with staff and correct any identified gaps before the next drill

31. Vendor Onboarding and Accounts Payable Setup

What this SOP covers: The internal process for adding a new vendor to your accounts payable system — a step that’s often skipped until you need to cut a check.

Process structure:

  • Collect a completed W-9 from all new vendors before any work begins or any payment is issued
  • Verify the vendor’s business name, EIN, and address match what they provided; run a basic reference or background check for vendors over $5,000 per year
  • Enter the vendor into your AP system with all required fields: name, address, payment terms, and 1099 flag if applicable
  • Route for manager approval before making the vendor “active” in the system
  • Store the W-9 in the vendor file; W-9s must be retained as long as you have a payment relationship plus 7 years
  • Confirm payment method preference (check, ACH, wire) and add banking information to the vendor record per your authorization process
  • Review all new vendors annually; deactivate vendors with no activity in the prior 12 months

Customer Support {#customer-support}

Customer support SOPs exist because every edge case that your best support rep handles intuitively becomes a disaster when your newest rep encounters it alone on a Saturday afternoon. Documenting the process transfers the judgment, not just the steps.

For a full template guide, see the customer support SOP template.


32. Customer Complaint Handling

What this SOP covers: The step-by-step process for receiving, documenting, and resolving a customer complaint — the process that determines whether an unhappy customer becomes a churn risk or a loyal one.

Process structure:

  • Acknowledge the complaint within 4 business hours (or your SLA); use a confirmed format that validates the customer’s experience without admitting fault
  • Open a ticket in your CRM with: customer name, account ID, issue category, channel received, and verbatim description of the complaint
  • Assess severity: Tier 1 (standard, rep handles), Tier 2 (requires supervisor), Tier 3 (potential legal, refund over threshold, or repeat complaint — escalate immediately)
  • For Tier 1: resolve and document resolution within 24 hours; confirm with the customer in writing
  • For Tier 2/3: escalate with all ticket context; the escalation owner takes it from here — no hand-off without context
  • After resolution, send a brief satisfaction check (one-question survey or direct reply); log the response in the ticket
  • Weekly: review all complaints by category; identify any pattern that signals a product or process issue

33. Refund Processing

What this SOP covers: The internal process for evaluating, approving, and executing a refund — with a documented decision framework so frontline staff aren’t making it up per customer.

Process structure:

  • Confirm the customer is eligible for a refund per your published policy (return window, condition of product, subscription status)
  • Document the reason for the refund in the ticket: customer’s stated reason and your assessment
  • Refunds under $[your threshold, e.g., $50] are approved at the rep level; above that threshold requires supervisor sign-off
  • Issue the refund in your payment processor; note the refund transaction ID in the ticket
  • Confirm the refund method: original payment method is default; alternative method requires written authorization from the customer
  • Send the customer a written confirmation with the refund amount, transaction ID, and expected timing (3–5 business days for cards, typical)
  • Log the refund in your refunds tracker with date, amount, reason code, and approver; use this data monthly to identify high-refund SKUs or issues

34. Support Ticket Triage

What this SOP covers: The process for categorizing and routing incoming support tickets so they get to the right person at the right priority without sitting in a queue for two days.

Process structure:

  • All incoming tickets are triaged within 2 business hours of receipt (or your SLA); assign a priority (P1/P2/P3) based on impact
  • P1 (service down, data loss, security issue): assign immediately to a senior rep and notify the team lead; response within 1 hour
  • P2 (functionality degraded, billing error, high-value customer): assign to appropriate rep; response within 4 hours
  • P3 (general question, feature request, low impact): route to the queue; response within 24 hours
  • Assign all tickets a category (technical, billing, product, account, other); this data feeds your weekly root-cause report
  • If a ticket is missing information needed to resolve it, send a one-response follow-up with specific questions; if no reply in 3 business days, close the ticket with a note
  • Review triage accuracy weekly: if more than 10% of tickets are re-prioritized after triage, the triage criteria need updating

35. Escalation to Engineering or Product

What this SOP covers: The handoff process from support to an internal technical or product team — the moment where most customer issues either get resolved or fall into a black hole.

Process structure:

  • Before escalating, confirm the issue is reproducible: you have a step-by-step reproduction, relevant account IDs, and screenshots or logs
  • Create an internal ticket in your bug/feature tracker with all context from the support ticket; link the two tickets to each other
  • Set customer expectation before escalating: “I’m looping in our technical team — here’s what you can expect in terms of timing and next steps”
  • Engineering or product team acknowledges the ticket within [your agreed SLA, e.g., 1 business day]; rep remains the customer’s point of contact
  • Rep provides status updates to the customer at each agreed interval; never let the customer chase for an update
  • When engineering resolves, they notify the rep with the fix or workaround; rep tests before confirming to the customer
  • Close the ticket only after the customer confirms the issue is resolved — not when engineering closes the internal ticket

Ecommerce and Retail {#ecommerce-and-retail}

Ecommerce SOPs protect two things: margin and reputation. Inconsistent fulfillment loses customers. Inconsistent returns processing loses money. For a full template, see the ecommerce SOP template.


36. Order Fulfillment and Shipping

What this SOP covers: The step-by-step process for picking, packing, and shipping a customer order — the process that determines whether your delivery promise is real or aspirational.

Process structure:

  • Pull orders at the start of each fulfillment shift (or as they arrive, per your volume); sort by ship date commitment
  • Pick items from the warehouse using the pick slip; verify item, SKU, and quantity against the order before moving to packing
  • Pack per your product’s requirements: appropriate box size, fill material, any required inserts (invoice, packing slip, return label)
  • Apply the correct shipping label for the service selected (ground, 2-day, international); verify the address matches the order
  • Scan the package out of inventory and into “shipped” status in your order management system before it leaves the building
  • End of day: confirm all orders committed for today’s cutoff were shipped; any missed cutoffs get flagged immediately to customer service for proactive notification
  • Log any packing errors, damaged items, or short picks in the fulfillment error log; use this data weekly to audit pick accuracy

37. Return and Exchange Processing

What this SOP covers: The inbound return process — from receiving the item through issuing the refund or exchange and updating inventory.

Process structure:

  • Receive return package; match the return to the original order using the packing slip or order number
  • Inspect returned item: condition (new/used/damaged), correct item (not a swap), and all original packaging and components present
  • Classify the return: restockable (goes back to inventory), non-restockable (damage not covered by policy), or defective (warranty claim)
  • For restockable returns: restock immediately; update inventory count in your system
  • For defective returns: log in the defect tracker; route to the vendor/manufacturer for credit if applicable
  • Issue refund or exchange per the customer’s request; refund goes to original payment method within your stated window
  • Confirm with the customer that the return was received and the refund/exchange is in process; close the ticket

38. Inventory Cycle Count

What this SOP covers: The rolling process for counting a portion of your inventory regularly — not a once-a-year full count, but a continuous accuracy check.

Process structure:

  • Divide your SKUs into weekly count zones (A, B, C by velocity); count A-zone items weekly, B monthly, C quarterly
  • Count team counts physically (no looking at the system first); record on the count sheet
  • After the count, compare to the system quantity; investigate any variance greater than 2% or $25 (whichever is less)
  • Adjustment variances require manager sign-off; post the adjustment to inventory in your system with a reason code
  • Review variance reasons monthly: if the same SKU shows repeated variances, investigate receiving, picking, or theft at that location
  • Full physical inventory at year-end to reconcile with financial records; coordinate with accounting on cut-off
  • Use the cycle count data to identify which SKUs need tighter location controls or more frequent counting

39. Price Change and Promotion Execution

What this SOP covers: The process for implementing a price change or promotional discount — a step that breaks down constantly without a checklist.

Process structure:

  • Price change or promotion is documented in a brief: what’s changing, when, which SKUs, and what the expected margin impact is
  • Update pricing in the ecommerce platform (Shopify, WooCommerce, etc.) at least 24 hours before the promotion goes live
  • Update any external price feeds (Google Shopping, Amazon, wholesale EDI) separately — they do not auto-sync in most setups
  • Verify the change on the live storefront before the promotion window opens; check the correct SKUs, correct discount, correct end date
  • If running a promotional code, test the code on a test order before sending it to customers
  • At promotion end: verify all discounts are removed from the platform and price feeds; check within 1 hour of expiration
  • After the promotion, pull revenue and margin for the period; compare to baseline and log in the promotions tracker

40. Product Listing Quality Check

What this SOP covers: The process for reviewing a new or updated product listing before it goes live — catching errors that cost you conversions or create customer service volume.

Process structure:

  • Confirm product title follows your naming convention: brand + model + key attribute + size/color (where applicable)
  • Verify all required fields are complete: title, description, price, weight, dimensions, category, and all required attributes for your platform
  • Images: minimum 3 images, white background for hero, alt text on all images, no watermarks or text overlaid
  • Description: includes key features in bullet points, dimensions in both metric and imperial if you ship internationally, and care/handling instructions if applicable
  • Check the product is mapped to the correct category and tags; confirm it will surface in the right search filters
  • Preview the listing on mobile — most shoppers see it on a phone first
  • Price check: confirm the price matches the approved pricing sheet and any active promotions are applied or excluded correctly

Churches and Nonprofits {#churches-and-nonprofits}

Nonprofits and churches often resist SOPs because the work feels personal, not procedural. But volunteer coordination, donation processing, and event management all have enough repetition to benefit from documentation — and enough at stake to require it. For full templates, see the church SOP template and the nonprofit SOP template.


41. Volunteer Onboarding

What this SOP covers: The process for moving a new volunteer from expressed interest through their first assignment — a process that determines whether people come back or quietly disappear.

Process structure:

  • Collect volunteer’s information, availability, skills, and area of interest via your intake form; enter in your volunteer management system
  • Conduct a brief orientation (in person, video, or written): mission, values, how decisions get made, and what volunteers can expect
  • Run any required background checks before assigning roles that involve children, finances, or vulnerable populations
  • Match the volunteer to a team and a team lead; introduce them by email or in person before their first shift
  • First assignment: have a team lead or experienced volunteer alongside them; this is not a solo-drop-in shift
  • At 30 days: brief check-in (5 minutes, in person or email) — are they in the right role? Are there barriers?
  • Add to volunteer communications list; confirm they’re receiving the correct digest or announcements for their team

42. Donation Processing and Acknowledgment

What this SOP covers: The process for receiving, recording, and acknowledging a charitable donation — with the accuracy required for IRS compliance and the warmth required for donor retention.

Process structure:

  • All donations (check, online, cash) are entered in the donor management system within 24 hours of receipt
  • Cash donations are counted by two people simultaneously; both sign the deposit record
  • Checks are endorsed with “For Deposit Only” and deposited within 3 business days
  • Each donation triggers an automated acknowledgment for amounts under $[your threshold]; personalized acknowledgments are sent for major gifts within 48 hours
  • IRS-required written acknowledgment (for donations over $250) is sent within 30 days; it must include: organization name, EIN, donation date, amount, and a statement that no goods or services were provided (or the fair market value of any goods/services received)
  • End-of-year statements are mailed or emailed by January 31 covering all donations in the prior calendar year
  • All donor records are reconciled to the bank deposit monthly; any variance is investigated before the books are closed

43. Event Planning and Day-Of Coordination

What this SOP covers: The process for planning a recurring or one-time event — from initial setup through day-of execution and teardown.

Process structure:

  • Create the event brief: date, purpose, expected attendance, venue, budget, and lead coordinator
  • Assign roles at least 2 weeks out: setup crew, greeters, A/V lead, childcare lead, cleanup crew — each role has a named person
  • One week before: confirm all vendors and equipment; walk the venue if possible; distribute the day-of run sheet to all role holders
  • Day before: final headcount estimate; confirm all supplies are on hand; brief the volunteer team
  • Day of, 90 minutes before start: setup complete and tested; all volunteers on station 30 minutes before doors open
  • During the event: one coordinator owns the timeline; no one makes timeline changes without going through them
  • Post-event: all setup broken down and venue returned to condition before your team leaves; debrief within 48 hours to capture what to improve next time

44. Background Check Process for Volunteers and Staff

What this SOP covers: The process for running a background check on a volunteer or staff member who will have contact with minors or access to finances — a process that most organizations handle inconsistently.

Process structure:

  • Any role involving unsupervised contact with minors, access to cash, or access to sensitive donor information requires a background check before the first assignment
  • Use an approved screening vendor (e.g., Checkr, Sterling, your denomination’s endorsed provider); do not rely on personal references alone
  • Obtain written authorization from the individual before running the check — FCRA requires signed consent
  • Review results against your written screening criteria; consult with legal counsel before making adverse decisions
  • All background check records are confidential; stored separately from the personnel or volunteer file; accessible only to the designated administrator
  • Background checks must be renewed every 2 years for anyone in a covered role; calendar the renewal dates at the time of initial screening
  • Document your process in writing; your insurance carrier may ask for it during renewal

Auto Repair {#auto-repair}

Auto repair SOPs aren’t about turning technicians into robots. They’re about ensuring the inspection, communication, and billing process is consistent — so customers aren’t surprised, and you’re not absorbing comebacks you didn’t cause. The auto repair shop SOP template covers the full list.


45. Vehicle Check-In and Write-Up

What this SOP covers: The process for receiving a vehicle and creating an accurate repair order — the step that determines whether the rest of the job goes smoothly.

Process structure:

  • Greet the customer within 3 minutes of arrival; listen before reaching for the keyboard
  • Walk around the vehicle with the customer; document all pre-existing damage on the repair order and get customer initials — this is your liability protection
  • Confirm the customer’s complaint in their words and enter it verbatim on the repair order; do not paraphrase the symptom as a diagnosis
  • Collect customer contact information, best callback time, and authorization for a diagnostic or not-to-exceed estimate amount
  • Confirm the customer’s expectations for completion: same-day, next-day, or in for a while — and note if a loaner or ride is needed
  • Assign the RO to a technician; note any parts that need to be ordered before diagnosis begins
  • Call the customer with the diagnosis and authorization before any repair work starts — no authorization, no work

46. Multipoint Vehicle Inspection

What this SOP covers: The structured inspection every vehicle receives when it comes in for any service — the process that drives additional service revenue and protects the shop from “you broke it” claims.

Process structure:

  • Technician completes the multipoint inspection form for every vehicle, every time — not just oil changes
  • Check all fluid levels: engine oil, coolant, brake fluid, power steering, washer fluid, transmission if dipstick accessible
  • Inspect tires: tread depth with gauge (record mm), sidewall condition, inflation pressure, uneven wear pattern
  • Test battery with a load tester; record CCA and state of charge
  • Visually inspect belts, hoses, brakes (where visible), lights, wipers, and any suspension components that can be observed on the rack
  • Document findings on the form with condition codes (good/monitor/recommend/urgent); attach photos for any urgent or recommended items
  • Present the inspection to the customer with photos — advisors who show the photo have a 3-4x higher approval rate on recommended work

47. Parts Ordering and Receiving

What this SOP covers: The process for ordering, receiving, and matching parts to a repair order — a process that causes shop delays when it runs on verbal communication.

Process structure:

  • Parts are ordered from the repair order — never ordered verbally without a written RO number attached
  • Parts person quotes and confirms availability before ordering; note ETA on the RO so the tech knows when to expect the part
  • When parts arrive, receiving staff matches the part number and quantity to the purchase order — not to memory
  • Any discrepancy (wrong part, wrong quantity, damaged) is flagged immediately to the parts person; the carrier’s delivery driver must sign the exception before leaving
  • Parts are tagged with the RO number and placed in the appropriate bay shelf or bin — not left in a pile
  • When the tech picks up parts, they initial the RO to confirm receipt; this closes the chain of custody
  • Return cores and warranties within 30 days per supplier terms; log all returns in the parts tracking sheet

48. Technician Time Clock and Flag Hour Recording

What this SOP covers: The process for recording technician time accurately — the process that determines flat-rate technician pay and shop efficiency reporting.

Process structure:

  • Tech clocks in to a specific RO and operation code when starting the job; clocks out when the job is complete or they move to another job
  • Any time the tech is off the clock (waiting on parts, at lunch, pulled to another vehicle) must be tracked — this is how you calculate productive hours vs. hours available
  • Tech completes the repair and notes any additional concerns found during the job on the RO before returning it to the advisor
  • Advisor reviews the time on the RO against the flag hours; any significant discrepancy (more than 20% over flat-rate book time) is discussed with the tech before the RO is closed
  • At the end of the day, the shop foreman reviews all open ROs; any job that’s been open for more than 1 day without movement needs a status note
  • Tech pay is calculated from flag hours on closed ROs; any disputes are resolved from the time records, not from memory
  • Weekly: report tech efficiency (flag hours earned / hours clocked in) by technician; use this data for coaching, not just accounting

Daycare and Childcare {#daycare-and-childcare}

Childcare is one of the most regulated SMB categories in the United States. Every licensing visit, health inspection, and incident audit hinges on documented processes. An undocumented practice is a liability in any industry; in childcare, it’s a licensing risk. See the full daycare SOP template for the complete list.


49. Child Drop-Off and Check-In

What this SOP covers: The structured arrival process for each child — a daily touchpoint that confirms custody authorization, health status, and any communication from the family.

Process structure:

  • Staff member greets each child and parent at the door; do not allow self-check-in without a staff member present
  • Health screen at arrival: observe for visible illness symptoms (runny nose, fever, vomiting); ask parent about any symptoms since yesterday
  • Confirm the child is on the authorized pickup list for today; check any custody or access restrictions in the child’s file
  • Sign-in entry: name, time, and which staff member checked the child in — most licensing boards require daily sign-in with times
  • Collect any medications being brought in; verify written authorization from the parent matches the medication
  • Note any communications from the parent (child didn’t sleep, had a hard morning, special schedule today) in the day log
  • Alert the classroom teacher to any health, behavioral, or schedule notes from the drop-off

50. Incident Report Completion

What this SOP covers: The process for documenting and reporting an incident (injury, behavioral event, or policy-reportable occurrence) involving a child in your care.

Process structure:

  • When an incident occurs, first ensure the child is safe and receives appropriate first aid or medical care
  • Complete the incident report form within 30 minutes of the incident, while details are fresh — include exact time, location, what happened, who witnessed it, and what action was taken
  • Notify the parent by phone before end of business — do not send the incident report as first notification; call first
  • Have the parent sign the incident report at pickup; provide them a copy
  • For any incident meeting your state’s mandatory reporting threshold (head injuries, suspected abuse, fractures, loss of consciousness), report to the appropriate state agency per your licensing requirements — your director should have the reporting hotline number posted
  • File the completed report in the child’s file and in the incident log; the incident log is a required record for most licensing boards
  • Debrief with staff within 24 hours: what happened, what was done, and whether any procedure needs to change to prevent recurrence

Fitness and Salon {#fitness-and-salon}

Fitness studios and salons share a challenge: they’re appointment-driven businesses with high cancellation rates, product inventory to manage, and staff whose inconsistency directly affects client retention. The fitness studio SOP template and salon SOP template cover the full process list.


51. Client Intake and Consultation (Salon)

What this SOP covers: The process for conducting a new client consultation before any service — the step that prevents surprises, protects you from liability, and increases retention.

Process structure:

  • Before any chemical service, every new client completes a health history card: medications, allergies, prior chemical treatments, scalp conditions
  • Consultation happens before the client is draped — looking at and touching the hair before discussing goals
  • Ask specifically about what they’ve had done in the last 12 months; document in the client card
  • Show examples (portfolio, lookbook, or their own reference photos) before verbally agreeing on a result; close the expectation gap before, not after
  • Price the service before it begins; no service should start without the client knowing the cost range
  • Conduct a strand test for any significant color change or chemical service on a new client; document the test result
  • Update the client card after every visit: formula used, processing time, result, and any notes for next time

52. Class Cancellation and Waitlist Management (Fitness Studio)

What this SOP covers: The process for managing class cancellations — both instructor-initiated and client-initiated — and maintaining a fair waitlist system.

Process structure:

  • Client-initiated cancellations: must cancel at least 12 hours before class start (or your policy window) to avoid a late-cancel fee; cancellation policy is confirmed at signup
  • Late cancellations or no-shows trigger the fee automatically through your booking system; do not manually waive without manager approval
  • When a spot opens, the booking system notifies the next person on the waitlist automatically; confirm your platform is configured to do this
  • Instructor-initiated cancellations: notify all registered students at minimum 4 hours before class; provide a makeup option or credit
  • If a sub instructor is needed: follow the substitute instructor communication process (see your sub list and the call-in script)
  • Class is cancelled due to low enrollment per your policy (e.g., fewer than 3 students): notify all registered students 2 hours before; offer credit
  • Log all cancellations and reasons in your class management system; review monthly to identify instructors or class times with recurring low enrollment

What to Do With These Examples {#what-to-do-with-these-examples}

Reading process structures is useful. Actually building them is where the value lives.

The most important thing is to start with the process that causes you the most pain right now — not the one that looks most impressive to have documented. If your cash drop is a source of recurring reconciliation errors, start there, not with the social media checklist. If new volunteers keep disappearing after their first shift, the onboarding process is the lever.

If you’re not sure which process to tackle first, this guide walks through exactly how to decide. If you’re building from scratch and wondering whether to use a template or start with a blank page, this comparison is worth 10 minutes.

Once you know what to write, you need somewhere to write it that your team will actually use. A Google Doc works for one process. It doesn’t work for 25. When your SOP library gets big enough that people stop looking things up because they can’t find what they need, it’s time for a purpose-built tool.

What’s the Process For is free to start. Build your first 5 processes, assign them to your team, and see whether people actually reference them. If they do — and they usually do, once the process is easy to find — you’ll know the investment is worth it.

For the deeper template by industry you need, the SOP template library has 26 categories with specific process lists. The complete guide to writing SOPs covers structure, format, and what makes a process document people actually follow.

The goal isn’t a perfect document. It’s a team that doesn’t need you in the room to do the job right.


Chris McGennis is the founder of What’s the Process For — process documentation software for small and medium businesses. He has spent 6+ years talking to operators across every industry about what makes documented processes stick.

Tagged sop examples standard operating procedure examples sop templates process documentation small business operations

Ready to document your processes?

Start creating SOPs your team will actually use. Free to get started.

Start Free Trial

Get templates like this in your inbox

We send practical SOP templates and process documentation tips. No fluff, no spam.