SOPs, operations & owner independence

Free SOP template library

SOP templates and generator

Choose a useful template or turn your notes into an SOP.

Start the toolEstimated: 5 minutes

Built by Nick Horob · Updated

4 styles × 4 formats

Start with the format your team will actually edit.

All 16 blank templates are free. Google files are standards-based DOCX/XLSX imports. Open the download in Word or Excel, or import it into Google Docs or Sheets.

One owner, one trigger, and a short repeatable task.

Opens directly in Microsoft Word.

Browse 20 filled SOP examples

20 filled examples

Copy the control logic, not just the headings.

Every example names an owner, trigger, inputs, normal path, exceptions, checks, and review cadence. Adapt it; do not treat it as legal, safety, finance, or HR approval.

20 of 20 examples shown

Customers

New customer setup

Create one accurate customer record and a clear first handoff without asking the customer for the same information twice.

Owner
Customer operations coordinator
Trigger
A signed agreement and approved start date are recorded.

Inputs

  • Signed agreement
  • billing contact
  • service address
  • approved scope
  • start date

Procedure

  1. Confirm the agreement, scope, and start date match.
  2. Create the customer record using the legal or approved trading name.
  3. Add billing and day-to-day contacts in their correct roles.
  4. Assign the internal owner and first delivery task.
  5. Send the approved welcome message with the next action and date.

Exceptions

  • Hold setup when scope, price, or legal name conflicts across records.
  • Escalate requests for unapproved access, terms, or delivery commitments.

Quality checks

  • A second person checks the first invoice destination.
  • The customer receives one owner, one next step, and one date.
Customers

Customer intake and qualification

Collect the minimum facts needed to route a request without making a service, price, or schedule promise.

Owner
Intake coordinator
Trigger
A new phone, form, or email inquiry arrives.

Inputs

  • Contact preference
  • request summary
  • location
  • desired timing
  • consent or opt-out state

Procedure

  1. Confirm how the person wants to be contacted.
  2. Record the request in the customer's words.
  3. Ask only the approved routing questions.
  4. Select the correct service queue and urgency label.
  5. Send the approved receipt message and stated response window.

Exceptions

  • Route emergencies or safety concerns to the published emergency path immediately.
  • Do not qualify requests outside the approved service area; send the approved decline or referral language.

Quality checks

  • Required routing fields are complete.
  • No price, arrival, eligibility, or outcome was promised without approval.
Sales

Quote review and approval

Release quotes only after scope, assumptions, price, and approval evidence agree.

Owner
Sales manager
Trigger
A draft quote is marked ready for review.

Inputs

  • Draft quote
  • approved price list
  • scope notes
  • exceptions
  • customer deadline

Procedure

  1. Match every quoted item to the approved scope.
  2. Check quantities, taxes, discounts, and expiration date.
  3. List exclusions and customer responsibilities in plain language.
  4. Route discounts or nonstandard terms to the named approver.
  5. Record approval and send the locked customer version.

Exceptions

  • Return the quote when source notes and line items disagree.
  • Do not send a nonstandard term without written approval.

Quality checks

  • The sent file matches the approved version hash or timestamp.
  • The CRM records the amount, expiration, approver, and next follow-up date.
Sales

Lead follow-up after a quote

Follow up helpfully while stopping immediately after a reply, decline, or opt-out.

Owner
Account representative
Trigger
An approved quote is sent and no reply is recorded.

Inputs

  • Quote sent date
  • expiration date
  • approved contact channel
  • reply status
  • opt-out status

Procedure

  1. Verify there is no reply, decline, or opt-out.
  2. Send the approved first follow-up on the scheduled day.
  3. Record the touch without copying sensitive message content into analytics.
  4. Repeat only the approved cadence while the quote is valid.
  5. Close the sequence when the customer replies, declines, opts out, or the quote expires.

Exceptions

  • Pause when the quote or scope changes.
  • Escalate legal, price, complaint, or special-term questions to the responsible person.

Quality checks

  • Every touch uses the current approved quote and contact preference.
  • The stop reason is recorded once.
Operations

Daily opening procedure

Open the location safely and make it ready for the first customer and employee.

Owner
Opening lead
Trigger
The assigned opener arrives before operating hours.

Inputs

  • Keys or access credential
  • opening checklist
  • alarm instructions
  • staff schedule
  • issue log

Procedure

  1. Check the exterior for damage or an unsafe condition before entry.
  2. Disarm the approved alarm and record entry.
  3. Inspect public and staff areas using the opening checklist.
  4. Start only approved equipment and systems.
  5. Review staffing, bookings, and unresolved issues before unlocking for customers.

Exceptions

  • Do not enter after evidence of forced entry; move to safety and follow the emergency path.
  • Keep the affected area closed when a hazard cannot be corrected before opening.

Quality checks

  • Opening checklist is signed with time and initials.
  • Unresolved issues have an owner and customer-impact decision.
Operations

Daily closing procedure

Secure people, cash, data, and the location at the end of the operating day.

Owner
Closing lead
Trigger
The last customer leaves and the closing lead starts the checklist.

Inputs

  • Closing checklist
  • cash policy
  • equipment shutdown list
  • issue log
  • alarm instructions

Procedure

  1. Confirm all customers and non-closing staff have left.
  2. Reconcile cash or payment totals using the approved two-person rule.
  3. Shut down listed equipment and secure sensitive records.
  4. Walk every area and record maintenance or safety issues.
  5. Lock doors, arm the alarm, and confirm the system reports a successful close.

Exceptions

  • Use the cash variance path when totals do not reconcile.
  • Do not leave alone when the lock, alarm, or safety system fails; call the designated contact.

Quality checks

  • Two people sign any required cash control.
  • Alarm confirmation and closing time are recorded.
Finance

Create and send a customer invoice

Send an invoice that agrees with approved work, terms, tax treatment, and customer billing instructions.

Owner
Billing specialist
Trigger
A billable milestone is approved as complete.

Inputs

  • Approved scope
  • completion evidence
  • price and tax rules
  • purchase order
  • billing contact

Procedure

  1. Confirm the milestone and completion evidence are approved.
  2. Match line items and quantities to the contract or accepted change order.
  3. Apply approved tax, discount, deposit, and payment terms.
  4. Attach required purchase-order or completion references.
  5. Send through the approved channel and record the due date.

Exceptions

  • Hold invoices with a scope, tax, price, or purchase-order conflict.
  • Route credits and nonstandard payment terms to the finance approver.

Quality checks

  • Invoice total reconciles to its source documents.
  • Customer name, billing address, due date, and remittance details are correct.
Customers

Review a refund request

Apply the written refund policy consistently while preserving a clear escalation path.

Owner
Customer care lead
Trigger
A customer asks for money back or disputes a charge.

Inputs

  • Customer request
  • order or invoice
  • delivery evidence
  • refund policy
  • approval limits

Procedure

  1. Acknowledge the request without promising an outcome.
  2. Confirm the transaction and stated reason.
  3. Compare the facts with the current refund policy.
  4. Approve within the role limit or send a neutral summary to the named approver.
  5. Record the decision, amount, method, and customer message.

Exceptions

  • Escalate fraud, legal threats, safety claims, chargebacks, or exceptions to written policy.
  • Do not request full payment-card or identity documents through an unapproved channel.

Quality checks

  • Decision cites the policy version and approver when required.
  • Refund amount and destination match the original verified transaction.
Customers

Customer complaint handoff

Move a complaint to the right owner with the customer's facts, desired resolution, and next update intact.

Owner
Customer service lead
Trigger
A concern cannot be resolved within the first responder's authority.

Inputs

  • Customer's description
  • order or job record
  • prior contacts
  • requested remedy
  • escalation matrix

Procedure

  1. Reflect the concern and confirm the requested resolution.
  2. Separate observed facts from assumptions or internal conclusions.
  3. Choose the escalation owner using severity and remedy authority.
  4. Send the owner a concise handoff with evidence and a response deadline.
  5. Tell the customer who owns the next update and when to expect it.

Exceptions

  • Use emergency, legal, privacy, or safety escalation immediately when triggered.
  • Do not promise a remedy outside the first responder's limit.

Quality checks

  • The receiving owner accepts the handoff.
  • The customer is not asked to repeat information already captured.
Operations

Create and approve a vendor order

Order the correct item, quantity, price, and delivery terms from an approved vendor.

Owner
Purchasing coordinator
Trigger
An approved reorder point or project request is reached.

Inputs

  • Approved request
  • vendor record
  • current price
  • required-by date
  • approval threshold

Procedure

  1. Confirm the item specification, quantity, and required-by date.
  2. Check the approved vendor and current quoted terms.
  3. Create the purchase order with delivery and receiving instructions.
  4. Obtain approval when value or terms cross the role limit.
  5. Send the order and record confirmation and expected delivery.

Exceptions

  • Hold substitutions, changed bank details, or unapproved vendors for independent verification.
  • Escalate orders that cannot meet the required date before making a commitment.

Quality checks

  • Purchase order matches the approved request.
  • Vendor confirmation is attached to the order record.
Operations

Inventory reorder

Replenish stock from verified counts without hiding shortages, excess, or substitutions.

Owner
Inventory lead
Trigger
Available quantity reaches the approved reorder point.

Inputs

  • Verified count
  • open orders
  • reorder point
  • standard pack size
  • approved vendor

Procedure

  1. Recount the item and separate damaged or reserved units.
  2. Subtract confirmed inbound quantities from the reorder need.
  3. Calculate the order using the approved point and pack size.
  4. Create the purchase request with count evidence.
  5. Update the inventory record only after approval or receipt, as policy requires.

Exceptions

  • Escalate negative stock, unexplained shrinkage, or repeated emergency orders.
  • Do not substitute a different specification without the named approver.

Quality checks

  • Physical count, available quantity, and open orders reconcile.
  • The next count or review date is recorded.
People

New hire onboarding

Give a new employee the approved access, context, and first-week plan needed for their role.

Owner
Hiring manager
Trigger
A signed offer and confirmed start date are received.

Inputs

  • Approved role
  • start date
  • manager
  • equipment list
  • access matrix
  • training plan

Procedure

  1. Confirm role, manager, location, and start date.
  2. Request only role-approved accounts and equipment.
  3. Prepare the first-day schedule and required policy acknowledgments.
  4. Assign a role buddy and first meaningful task.
  5. Review access and training completion at the end of week one.

Exceptions

  • Do not create access before employment and identity checks are complete.
  • Escalate any requested permission outside the role matrix.

Quality checks

  • Manager verifies least-privilege access.
  • The employee knows how to request help and report a security or safety issue.
People

Employee offboarding

Remove access, return property, transfer approved work, and preserve required records on time.

Owner
People operations lead
Trigger
A verified separation date and authorization are received.

Inputs

  • Separation authorization
  • access inventory
  • company property list
  • work owner
  • record-retention policy

Procedure

  1. Confirm the effective time and responsible approver.
  2. Create the access-removal plan from the current inventory.
  3. Assign transfer owners for approved work and records.
  4. Collect company property and record its condition.
  5. Verify access removal and close the offboarding checklist.

Exceptions

  • Use the immediate security path for high-risk or involuntary separations.
  • Do not copy personal content or retain records outside policy.

Quality checks

  • A second person verifies critical access removal.
  • Property, records, payroll handoff, and ownership transfer are documented.
Finance

Payroll pre-submit review

Submit payroll only after roster, time, changes, and approval totals reconcile.

Owner
Payroll administrator
Trigger
The payroll period closes and all manager approvals are due.

Inputs

  • Active roster
  • approved time
  • pay changes
  • leave records
  • payroll register

Procedure

  1. Lock the period after the stated cutoff.
  2. Match paid people to the active approved roster.
  3. Review missing time, unusual hours, and pay changes against approvals.
  4. Compare gross payroll and headcount with the prior period and explain material changes.
  5. Obtain final approval and submit through the approved payroll system.

Exceptions

  • Hold unapproved pay or identity changes.
  • Escalate duplicate people, negative pay, or unexplained bank-detail changes before submission.

Quality checks

  • Two-person approval is recorded.
  • Register totals and exception explanations are retained under policy.
Operations

Weekly operating scorecard review

Turn a small set of agreed measures into named decisions and follow-up owners.

Owner
Operations manager
Trigger
The weekly reporting cutoff passes.

Inputs

  • Metric definitions
  • source reports
  • targets
  • prior actions
  • known data issues

Procedure

  1. Refresh each metric from its named source.
  2. Mark missing or provisional data instead of estimating silently.
  3. Compare actuals with target and prior period.
  4. Choose the few variances that need a decision or investigation.
  5. Assign one owner and date to every action.

Exceptions

  • Do not use a metric whose definition or source changed without labeling the break.
  • Escalate suspected data integrity issues before performance conclusions.

Quality checks

  • Every metric has one definition, source, owner, and refresh date.
  • Prior actions are closed, carried forward, or explicitly canceled.
Safety

System access request

Grant the least access needed after role, approver, and identity are verified.

Owner
System owner
Trigger
A person submits an access request through the approved channel.

Inputs

  • Requester identity
  • role
  • system
  • permission requested
  • manager approval
  • expiry when temporary

Procedure

  1. Verify the requester and employment or vendor status.
  2. Compare the requested permission with the role matrix.
  3. Obtain approval from the system or data owner.
  4. Grant the minimum approved permission and require supported authentication controls.
  5. Notify the requester and record the grant and next review date.

Exceptions

  • Reject credentials sent in tickets, chat, or documents.
  • Escalate administrator, financial, export, or sensitive-data access for enhanced approval.

Quality checks

  • A different person verifies privileged access.
  • Temporary access has an automatic or scheduled removal date.
Safety

Preventive equipment maintenance

Complete approved routine maintenance without bypassing safety, warranty, or technical limits.

Owner
Maintenance lead
Trigger
The equipment reaches its time, use, or condition-based maintenance interval.

Inputs

  • Equipment identifier
  • manufacturer procedure
  • maintenance interval
  • approved parts
  • lockout requirements

Procedure

  1. Verify the equipment and current approved procedure.
  2. Take it out of service and apply required energy-control steps.
  3. Inspect and complete only authorized maintenance items.
  4. Replace guards and perform the approved return-to-service check.
  5. Record work, parts, readings, and the next due date.

Exceptions

  • Stop for damage, unexpected energy, missing guards, or work outside authorization.
  • Use a qualified technician where the manufacturer or law requires one.

Quality checks

  • Safety controls are independently verified where required.
  • The equipment record includes measurements and return-to-service approval.
Safety

Operational incident escalation

Protect people and evidence, limit impact, and put one accountable person in charge.

Owner
Incident coordinator
Trigger
A safety, security, privacy, service, or financial incident threshold is met.

Inputs

  • Observed facts
  • time detected
  • affected people or systems
  • incident matrix
  • emergency contacts

Procedure

  1. Put immediate human safety first and call emergency services when appropriate.
  2. Stop or isolate the affected process within the responder's authority.
  3. Record observed facts, time, and actions without speculation.
  4. Notify the incident coordinator using the approved private channel.
  5. Preserve evidence and wait for authorized recovery instructions.

Exceptions

  • Do not investigate beyond training or enter an unsafe area.
  • Do not make public, legal, insurance, or customer statements without the named approver.

Quality checks

  • Incident owner, severity, next update, and decision log are recorded.
  • Recovery includes a check that the original hazard or failure is controlled.
Finance

Verify a vendor bank-detail change

Prevent payment diversion by verifying changed payment instructions through an independent channel.

Owner
Finance controller
Trigger
Any vendor asks to add or change bank or payment details.

Inputs

  • Existing vendor record
  • change request
  • approved callback contact
  • pending payments
  • dual approval policy

Procedure

  1. Pause changes and related payments.
  2. Open the existing vendor record without using links or numbers in the request.
  3. Call the previously approved contact and verify the change using the agreed challenge process.
  4. Record verification evidence and obtain dual approval.
  5. Update the record and release payment only after the change becomes effective.

Exceptions

  • Treat urgency, secrecy, changed email domains, or callback resistance as fraud indicators.
  • Escalate any mismatch; never negotiate around the verification control.

Quality checks

  • Verifier and approver are different people.
  • Audit log shows old value, new value, evidence, time, and approvals.
Operations

Turn a recording into an approved SOP

Convert observed work into a usable draft, then verify it with the person who performs and approves the process.

Owner
Process owner
Trigger
A process recording or transcript is ready for documentation.

Inputs

  • Recording or transcript
  • process owner
  • approver
  • screens or artifacts
  • known exceptions

Procedure

  1. Remove customer, employee, credential, and confidential details from the source.
  2. Break the normal path into one action per step.
  3. Separate decisions, approvals, exceptions, and proof from the normal path.
  4. Walk the draft with a performer and correct missing or out-of-order work.
  5. Run one observed test, obtain approval, and set a review date.

Exceptions

  • Do not document unsafe, unauthorized, or policy-breaking work as the standard.
  • Stop when credentials, regulated data, or customer records remain in screenshots or text.

Quality checks

  • Every source instruction is used or explicitly excluded with a reason.
  • The approved version names an owner, approver, effective date, and review cadence.
Free resourceKeep the whole operating library

Download the full template library

Get all 16 import-ready templates, 20 complete examples, the Excel/Google Sheets index, draft-only agent recipe, and your generated SOP exports when available. Source text stays out of capture.

  • Editable template library
  • Your generated SOP when ready
  • Searchable library index
Preview the result or example included in this kit
Template example: purpose → owner → procedure → exceptions → quality checks. Includes sample material; no personal inputs.

You'll also receive practical Nerd Out notes. Unsubscribe anytime. We never sell your email.

How this tool works

Four SOP styles and 20 real examples in. One process owner, normal path, exceptions, approvals, evidence, and review date out.

  1. Download any of the 16 blank templates without an email.
  2. Search 20 filled examples or structure one redacted process.
  3. Get the ZIP, index, agent recipe, and draft exports.

How to write an SOP people use

A template supplies the shape. A tested process supplies the truth.

A useful standard operating procedure names the outcome, trigger, owner, required inputs, normal path, exceptions, approvals, proof, and review date. Start with the smallest style your team will maintain. Use a checklist for frequent handoffs, a standard SOP for cross-team controls, and a visual SOP only when each frame shows a meaningful action or decision.

The assisted generator does not write from imagination. It classifies the lines in your approved redacted source, preserves them in a deterministic draft, and exposes missing exceptions, approvals, and checks as prompts for a person. Test the procedure once with the performer, correct the order and edge cases, name an approver, then set the review date.

Word and Notion files download directly. Google Docs and Sheets use import-ready DOCX and XLSX files so private process text stays in your browser instead of being uploaded by Nerd Out. Download a format your team can edit, then review the imported document before use.

Questions owners ask

SOP template and generator FAQ

What should an SOP template include?

Include the purpose and scope, trigger, process owner, required inputs and access, one observable action per step, exceptions, approvals, evidence or quality checks, effective version, and next review date. Add screenshots only when they clarify a real action or decision.

What is the difference between a simple SOP and a standard SOP?

A simple one-page SOP fits short work with one owner and a small number of exceptions. A standard SOP adds scope, multiple roles, inputs, controls, approvals, evidence, and a revision log for cross-team or higher-consequence work.

Can I use these SOP templates in Google Docs and Sheets?

Yes. Google Docs templates download as DOCX files and Google Sheets templates as XLSX files. Upload either file to Drive, open it with the matching Google app, and save it as a native file after reviewing the import. Nerd Out does not receive your edits.

Can I import an SOP template into Notion?

Yes. Each Notion version is a Markdown file. Import it into a Notion page, then confirm headings, checkboxes, links, permissions, owner, and review date before sharing it with the team.

Does the SOP generator store my transcript?

No. Raw source stays in your tab. You review an editable redacted preview before submission; the approved text is processed in session, excluded from analytics and logs, and not saved. The generated export is created in your browser.

Can an AI-generated SOP be approved automatically?

No. The generator structures source lines but cannot verify the real order, systems, permissions, safety, policy, exceptions, or evidence. A process owner must test the draft, and the named approver must accept it before use.

See all operations and owner independence resources →