SOP Template: How to Write Standard Operating Procedures

An SOP template gives you a consistent format for writing standard operating procedures: short, numbered instructions that tell someone exactly how to complete a routine task, who owns it and what "done" looks like. For a small business, SOPs are how you stop being the only person who knows how things work. They speed up training, cut errors and, eventually, make the business something a buyer will pay more for.

Below you will find a fill-in SOP template, the three most common SOP formats, a step-by-step method for writing them, a complete example SOP for sending invoices, and the mistakes that make SOPs gather dust.

What is a standard operating procedure?

A standard operating procedure documents one repeatable task. It is narrower than a process map (which shows a whole workflow, like quote to cash) and more practical than a policy (which states a rule). Think of it as the instructions you would give a capable new hire on their first day.

Document	Answers	Example
Policy	What is the rule, and why?	All invoices are sent within 2 business days of job completion.
Process	What stages does work go through?	Quote, job, invoice, reminder, payment, reconciliation
SOP	Exactly how do I do this task?	12 steps to create, check and send an invoice
Checklist	Did I do everything?	Month-end close checklist

SOP template

Copy these headings into a document:

1. Title and ID: e.g., "SOP-FIN-003: Create and send customer invoices."
2. Purpose: one sentence on why the task matters.
3. Scope: what the SOP covers and what it does not.
4. Owner and roles: who performs it, who approves, who is the backup.
5. Frequency and trigger: when it happens (daily, on job completion, the 1st of each month).
6. Tools and access: software, logins, templates, files.
7. Inputs: what you need before starting (signed quote, timesheet, completion photos).
8. Steps: numbered, one action per step, starting with a verb.
9. Quality checks: what to verify before finishing.
10. Exceptions: what to do when something does not fit.
11. Outputs and records: what is produced and where it is saved.
12. Related documents: links to policies, other SOPs, checklists.
13. Version control: version, date, author, approver, next review date, change log.

SOP formats: which one to use

Format	Best for	Example
Simple checklist	Short routine tasks experienced staff already understand	Opening and closing a shop
Numbered step list	Tasks with a fixed order	Sending an invoice, onboarding a client
Hierarchical steps	Longer tasks with sub-steps	Payroll run, month-end close
Flowchart	Tasks with decisions and branches	Handling a disputed invoice

How to write SOPs: step by step

1. List your recurring tasks. Spend a week noting everything you or your staff repeat. Group by area: sales, operations, finance, admin.
2. Prioritize. Start with tasks that are frequent, costly when done wrong, or done only by you. Billing, client onboarding and payroll usually top the list.
3. Capture the task as it is done. Record your screen or have someone shadow the person who does it best.
4. Draft the steps. One action per step, starting with a verb: "Open," "Select," "Enter," "Check."
5. Add checks and exceptions. Where do mistakes happen? What should the person do if a client is missing a PO number?
6. Test it. Have someone unfamiliar with the task follow the SOP exactly. Every question they ask is a missing step.
7. Approve and publish. Store SOPs in one shared place with a clear naming system.
8. Train and review. Walk staff through it, then review annually or when tools change.

Example SOP: create and send a customer invoice

SOP-FIN-003 | Version 2.1 | Owner: Office manager | Backup: Owner | Review: every January

Purpose: bill every completed job accurately within 2 business days so we get paid on time.

Trigger: job marked complete in the job tracker.

Inputs: signed quote or work order, technician's time and materials log, completion photos, client's PO number if required.

1. Open the completed job and confirm the technician attached the time log and photos.
2. Compare actual hours and materials with the quote. If the difference is more than 10%, check for an approved change order; if none exists, notify the owner before invoicing.
3. Open the invoice template and enter the next invoice number in sequence (format: INV-2026-0001; use the invoice number generator if starting a new series).
4. Enter the client's legal name, billing address and PO number.
5. Add line items: labor (hours x rate), materials (quantity x price), trip fee.
6. Apply sales tax where required, using the sales tax calculator for the job location.
7. Subtract any deposit already paid and show it as a separate line.
8. Set the due date per the client's terms (default net 15) and add the late fee wording from the payment terms policy.
9. Add payment instructions: card link, ACH details, check address.
10. Check: totals, client name spelling, PO number, tax, deposit credit.
11. Download as PDF, name it "INV-2026-0001_ClientName.pdf," and email it from the billing address with the standard message.
12. Log the invoice in the receivables tracker and set reminders for 3 days before and 3 days after the due date.

Exceptions: if the client requires a portal upload, follow SOP-FIN-004. If the client disputes the amount, follow SOP-FIN-007.

Worked example: a plumbing job quoted at $1,450 comes in at 7 labor hours at $95 ($665), $610 in parts and a $75 trip fee, totaling $1,350 before tax. Parts are taxable at 7% ($42.70), so the invoice totals $1,392.70. A $400 deposit was paid, leaving $992.70 due in 15 days. The SOP's step 2 check passes because actual cost was under the quote.

How many SOPs does a small business need?

Fewer than you might think. Most small businesses get most of the benefit from 10 to 20 well-maintained SOPs covering the tasks that bring in money, keep clients happy and keep the books straight. Write one per week and you will have the core set within a few months.

Which SOPs should a small business write first?

• Billing and collections: invoicing, payment reminders, recording payments. See our guides to invoice processing and the accounts payable process for the bills you pay.
• Client onboarding: contracts, deposits, kick-off; our client onboarding checklist is a ready starting point.
• Month-end: reconciliation and reports, using a month-end close checklist.
• Hiring and onboarding staff: paperwork, system access, training. Pair it with an employee handbook.
• Emergencies: data backup, power loss, key person absence, which feed into a business continuity plan.

Where to store SOPs

Option	Good for	Watch out for
Shared drive folders with documents	Small teams on a budget	Duplicate versions; enforce one master copy
Wiki or knowledge base tool	Teams that update often; searchable	Needs an owner to keep it tidy
Checklist or workflow app	Recurring tasks with sign-off	Steps can drift from the written SOP
Printed binder	Workshops and sites without devices	Hard to keep current; date every page

Whatever you choose, use a consistent naming scheme (area code, number, short title), link related SOPs to each other, and keep a simple index listing every SOP with its owner and next review date.

How to know your SOPs are working

Pick one or two measures per SOP and check them monthly. For the invoicing SOP above, track days from job completion to invoice sent (target: 2 or fewer), invoice error rate (credit notes or reissued invoices as a share of all invoices) and average days to get paid. If you used to send invoices a week after each job and now send them within two days, you will often see payments arrive several days sooner, because the client's payment clock starts earlier. Errors that keep recurring are a sign a step is missing or unclear, so update the SOP rather than retraining the person.

SOPs for a one-person business

Solo owners sometimes think SOPs are only for teams. They are not. Writing down how you invoice, chase late payments, back up files and do month-end bookkeeping means a virtual assistant, bookkeeper or family member can step in when you are sick or on holiday. It also makes it much easier to hire your first employee later, because training material already exists.

Writing tips that make SOPs usable

• Write at the level of a capable new hire, not an expert.
• Use the exact names of buttons, fields and folders as they appear on screen.
• Put warnings before the step they apply to, not after.
• Show one good example output, such as a correctly completed invoice, alongside the steps.
• Keep each step to one sentence where possible.

Common SOP mistakes

• Writing from memory instead of watching the task done. Steps get skipped.
• Paragraphs instead of numbered steps. People skim; steps get missed.
• No owner or review date, so SOPs go stale after a software update.
• Too much detail on obvious steps, not enough on judgment calls and exceptions.
• Scattered storage across email, desktops and paper binders.
• Never testing the SOP with someone new.

SOPs and the value of your business

Documented procedures reduce owner dependency, which buyers and lenders look at closely. If you plan to sell one day, SOPs are part of the evidence that the business can run without you; see how to sell a small business for what buyers review.

Your invoicing SOP works best with a consistent, professional template. Use our free invoice generator to create invoices in the same format every time, with no sign-up, and download each one as a PDF.