An SOP Template With a Filled-In Example

Every business has a few tasks that only one person knows how to do properly: opening the shop, issuing a refund, onboarding a client, closing the month. An SOP template turns that knowledge into a page anyone on the team can follow, so the task gets done the same way when that person is on holiday or has moved on. Below is a standard operating procedure template with each section explained, a filled-in example for a common task, three formats to choose from, and a faster way to draft the first version.

Direct answer. An SOP template is a standard document layout for recording how a recurring task is done. It covers the title and ID, purpose, scope, roles and responsibilities, materials, the numbered procedure steps, quality checks, and revision history. Fill in one section at a time, write each step as a single action, and test it with someone new.

The SOP Template

Copy this SOP template skeleton into any document editor. Each heading is a section; the notes under each one explain what goes there.

STANDARD OPERATING PROCEDURE
Title: [Task name]          SOP ID: [e.g. CS-004]       Version: [1.0]
Owner: [Role]               Approved by: [Name]          Effective date: [Date]

1. Purpose
2. Scope
3. Roles and responsibilities
4. Definitions
5. Materials, tools and access
6. Procedure
7. Quality checks
8. Related documents
9. Revision history

Title block

The task name, a unique ID, version number, owner, approver and effective date. The ID matters once you have more than ten SOPs; a simple department-plus-number scheme like CS-004 is enough.

1. Purpose

One or two sentences on why the procedure exists and what goes wrong without it. "Ensure refunds are issued within two business days and recorded correctly for accounting" is a purpose. "To describe the refund process" isn't.

2. Scope

What the SOP covers and what it doesn't. Name the situations, products or locations it applies to, and the edge cases handled elsewhere.

3. Roles and responsibilities

Who does each part of the procedure, by role rather than by name, so the SOP survives staff changes. Include who approves exceptions.

4. Definitions

Any acronym, internal term or system name a new hire wouldn't know. Skip it if there are none.

5. Materials, tools and access

Everything needed before starting: software logins, permission levels, forms, equipment. A step that fails because someone lacks access is a template problem, not a people problem.

6. Procedure

The numbered steps. One action per step, each starting with a verb, written in the order they happen. Put warnings directly before the step they apply to, not in a separate section at the top.

7. Quality checks

How the person confirms the task was done correctly, and what record proves it. This is the section auditors and managers read first.

8. Related documents

Linked SOPs, work instructions, forms and policies.

9. Revision history

A small table: version, date, what changed, who approved it. It answers "is this the current version?" at a glance.

A Filled-In SOP Example

Here's the SOP template completed for a fictional online store. It's short on purpose; most good business SOPs fit on one or two pages.

SOP CS-004: Processing a customer refund — Fernway Goods (fictional sample) Version 1.2 · Owner: Customer Support Lead · Approved by: Operations Manager · Effective: October 1

1. Purpose. Issue approved refunds within two business days and record them so accounting can reconcile them at month-end.

2. Scope. Refunds for online orders paid by card or PayPal, up to $500. Refunds over $500, wholesale orders and store credit follow SOP CS-005.

3. Roles. Support agent: checks eligibility and issues the refund. Support lead: approves exceptions outside the 30-day window.

4. Definitions. RMA: return merchandise authorization number, generated by the helpdesk.

5. Materials. Helpdesk access, store admin with "Refunds" permission, the Refund Log spreadsheet.

6. Procedure.

1. Open the ticket and confirm the order number and RMA are present.
2. Check the order date. If more than 30 days ago, assign the ticket to the support lead and stop here.
3. Confirm the returned item has been marked "received" in the warehouse system.
4. In store admin, open the order and select Refund.
5. Enter the item amount. Caution: refund shipping only if the item arrived damaged.
6. Add the RMA number to the refund note and submit.
7. Reply to the customer using the "Refund issued" saved reply.
8. Add a row to the Refund Log with the date, order number, amount and agent initials.

7. Quality checks. The support lead compares ten random Refund Log rows with store admin each Friday. Any mismatch is corrected the same day.

8. Related documents. CS-005 Large and wholesale refunds; Returns policy (customer-facing).

9. Revision history. 1.0, March: first version. 1.1, June: added PayPal. 1.2, October: shipping refund rule.

Two details make this example work. Step 2 has a clear exit, so the agent knows exactly when to stop and hand off. And the caution sits on step 5, the one place where a mistake costs money, rather than in a list of warnings nobody rereads.

Three SOP Formats and When to Use Each

The same SOP template can hold the procedure in three different shapes. Pick by how many decisions the task contains.

Simple step list. A numbered list of single actions. Best for short, linear tasks with no branching: opening a register, publishing a blog post, running a weekly backup. If the task has fewer than about ten steps and no "if", use this.

Hierarchical steps. Main steps with numbered sub-steps (4, 4.1, 4.2). Best for longer procedures where each main step involves several actions, like onboarding a new client or closing the month in accounting. The main steps give the overview; the sub-steps give the detail.

Flowchart. Boxes and arrows with decision diamonds. Best for tasks with branches: handling a complaint, triaging a support ticket, approving an expense. A flowchart shows at a glance which path applies, and it pairs well with a short step list underneath for the detail.

The U.S. Environmental Protection Agency's guidance on preparing SOPs (EPA QA/G-6) recommends a concise, step-by-step format in the active voice and present tense, and suggests using a flow chart to illustrate the process. It also lists five elements for a technical SOP: title page, table of contents, procedures, quality assurance and quality control, and references.

How to Write an SOP That People Actually Follow

Write from observation, not memory. Sit with the person who does the task best and write down what they actually do, including the workarounds. The steps people skip when describing a task from memory are exactly the ones a new hire gets wrong.

One action per step, verb first. "Open the order and select Refund" is one step. "Open the order, check the date and, if eligible, issue the refund" is three steps and a decision hiding in one line.

Test it with someone new. Hand the draft to a colleague who has never done the task and watch them follow it. Every place they pause or ask a question is a step to rewrite.

Keep it where the work happens. An SOP buried in a shared drive folder rarely gets opened. Link it from the tool, the ticket template or the checklist where the task starts. The EPA guidance makes the same point: current copies should be readily accessible in the work areas of the people performing the activity.

Review it on a schedule. Processes drift as tools change. The EPA document suggests a periodic review every one to two years, and business processes tied to software usually need checking more often than that. Put the next review date in the title block.

Once a process has been running for a while, an SOP library also helps when proposing changes. A project proposal template is a natural next step when an SOP review shows the process itself needs fixing.

Drafting an SOP With an AI Document Generator

The slowest part of writing an SOP is turning rough notes into a clean, consistently formatted document. That's where AI saves the most time.

In Playyy, describe the task, who does it, the tools involved, and paste your rough notes or a list of steps. The AI document generator writes a formatted SOP that follows the SOP template above, with headings for each section, numbered steps, a highlight callout for warnings, and a table for the revision history. A prompt as simple as "Write an SOP for processing customer refunds under $500, for support agents, using these notes" is enough for a first draft.

Then refine it by chat: "split step 4 into sub-steps", "turn the procedure into a hierarchical format", "add a caution before the shipping refund step", "translate this SOP into Spanish for the warehouse team". The formatting holds while the content changes. To match your company's look, the brand kit generator pulls your logo, colors and fonts from your website and applies them to every document, so a library of fifty SOPs looks like one set.

Already have SOPs in Word? Import the .docx files and update them in the same editor. When the SOP is final, export it as a PDF for printing and binders, or share a view link so the team always opens the current version. For training sessions, the same content can become a short slide deck with the presentation maker.

Read every AI draft against the real process before approving it. The AI writes from what you describe, and the steps only become a standard once someone who does the work has checked them.

Conclusion

A good SOP template does three jobs: it records how the task is done, it makes the person responsible clear, and it shows how to confirm the work was done right. Start with the skeleton above, fill it in from watching the task, choose the format that fits the number of decisions involved, and test it with someone new before it goes live. To get from rough notes to a formatted first draft in minutes, try Playyy's AI document generator.

Keep Reading

• A Project Proposal Template With a Full Example — propose the process change your SOP review uncovered.
• Executive Summary Examples and Why They Work — summarize an SOP audit or process report for leadership.
• Free AI Report Generator — turn quality-check results into a structured monthly report.
• What Is a One Pager, and When Should You Send One? — condense a procedure into a single quick-reference page.