A template for one repeatable task
Use this structure to explain what needs to happen, who is responsible, and how to check the result. Adapt the editable template to a real workflow, then test it with the people doing the work.
Blank SOP template
Free downloads. Choose Word for a document, Excel for steps in rows, PDF for printing or Markdown for plain text.
1. Purpose, scope, and trigger
State the expected outcome and when the procedure begins. Explain what is included and what needs a separate procedure. For a supplier request, a useful result is a complete request sent to the correct reviewer, with missing information routed back to its owner.
2. Owners and responsibilities
Name the team that maintains the procedure, the roles doing each phase, and the people authorized to review and approve changes. Include the receiving role at each handoff. Configure permissions separately; a written responsibility does not grant system access.
3. Prerequisites and materials
List the systems, access, information, tools, and reference documents needed before the first step. Explain what to do when a prerequisite is missing. Link to maintained references rather than copying instructions that another team owns.
4. Steps and decisions
Write direct actions in a logical order. Group related steps into phases and show where responsibility changes. Include decision points and the expected result of important actions. Use screenshots where they clarify the task, with example data and a review for sensitive content.
5. Checks and exceptions
Define how the person verifies the result, what evidence they should record, and when they should stop or ask for help. In SOPFlow, a run can hold responses and evidence for work carried out from the procedure. The authoring board itself is not a completion record.
6. Version, review, and maintenance
Identify the current version, review decision, effective date, and maintenance owner. Write useful change notes and choose a review cadence based on the process. SOPFlow records version and review activity, but people still need to supply accurate context and follow the configured policy.
Try the template before expanding
Fill it in for one task. Ask a teammate to follow it, note the unclear steps, and revise before publication. A template organizes instructions; it does not establish that a procedure is complete, safe, or suitable for every setting.
To maintain the instructions with your team, explore SOPFlow’s free SOP software. The plan includes AI tools and PDF export, with limits on users, procedures and weekly AI usage. Check what is included before expanding your library.
Use SOPFlow AI to turn your process notes into a structured first draft or review an existing SOP for possible gaps. Have the process owner verify the steps, responsibilities and exceptions before publishing.
Choose Word, Excel, PDF or Markdown
Download the blank template in Word, Excel, PDF or Markdown without registering. Use Word for document editing, Excel for steps in rows, PDF for printing or Markdown for plain text. The completed customer-handoff example below is available in Word, PDF and Markdown.
You can upload the Word file to your own Google Drive and open it with Google Docs. There is no published native Google Docs template to copy from this page. Check the resulting layout after import, especially checkboxes and page breaks. Keep one maintained source rather than separate Word and Google Docs copies that drift apart.
In Excel, complete the SOP sheet with purpose, scope, control and review fields. Use Steps for actions, responsible roles, expected results, evidence and exceptions. Add rows as needed, test the draft and record review decisions manually.
Fill the control fields for the customer handoff
The worked example below is CS-001, version 1.0, owned by Customer Success. Its trigger is Sales marking a fictional account ready for onboarding. Its finish condition is the receiving owner's acceptance of a next action, not merely an outgoing message. These are example choices to adapt, not a released policy for your business.
Before using the example, add the actual reviewer, effective date and procedure reference. Define whether Sales or Customer Success can accept an exception, which record holds the evidence, and who covers an absent receiving owner. An instruction that says 'assign an owner' is incomplete if the reader cannot tell which role can receive the work.
Write the ordinary case first, then a missing-contact case and an unavailable-owner case. In each exception, state where the work stops, who gets the question and what evidence to keep. Avoid placing real customer details in a public or shared sample.
Test the template before treating it as a procedure
Ask someone who did not write the draft to follow it in a suitable practice environment. Give them the starting information, access and expected result, then observe where they need clarification. Record the draft version and each correction so the owner can see what changed.
For the handoff, check that the receiving person can open the record, explain the scope and identify the next action and due date. Repeat the test with a missing contact and an absent owner. A ticked box is useful only when its acceptance criterion explains what was actually checked. Close the test when the owner has resolved the open questions, rather than when every field happens to be filled.
Set a review trigger and retain the change decision
The first review date should reflect how the task can change. A new CRM field, a changed receiving role or a failed handoff can require an earlier review. Decide who watches for those changes and who can approve the correction. A calendar reminder alone cannot make the instructions accurate.
Record the procedure and version, the reason for review, findings, decision, reviewer and next action. If a change affects the task, decide which people need updated instructions or practice. Keep previous work references available under your organization's retention policy.
Bring the checked text into SOPFlow
Create a free workspace when you want a maintained place for the instructions. Copy the relevant text from the template into the existing AI text importer, or build the procedure manually. Check headings, steps, links, screenshots and responsibilities afterward; document layout and complete source history do not transfer just because the words do.
Free includes three users, five SOPs, PDF export and 50,000 shared weekly AI tokens. Drafting and recorder processing use the same workspace allowance. Review and publication remain separate from creating or importing a draft. The download is usable without signup, and this page does not offer a one-click template-opening integration.
Need filled-in instructions before adapting the blank template? See four SOP examples with steps, exceptions and completed records.
Completed example: customer handoff
Illustrative procedure CS-001, version 1.0. Customer Success owns this process. Start when Sales marks a fictional account ready for onboarding. Finish only when the receiving owner confirms the next action. This example contains no customer results.
| Step and role | Action | Evidence or exception |
|---|---|---|
| 1. Sales coordinator | Check the organization, primary contact, agreed scope and open commitments. | Record the source record ID. Missing contact or scope: return to Sales before handoff. |
| 2. Customer Success lead | Choose an available receiving owner and confirm they accept the handoff. | Record the owner and acceptance. If unavailable, keep the handoff open and escalate to the lead. |
| 3. Receiving owner | Record the next action, due date and unresolved questions in the shared record. | Example: Demo Account 104; owner CS lead; next action welcome call; due September 18. |
| 4. Sales coordinator | Read back the handoff summary and confirm the receiving owner can access it. | Close only when scope, contact, owner and next action are present. A sent message alone is not acceptance. |
Before using the example
- Prerequisites: access to the customer record and agreed scope; use fictional data when testing.
- Change record: v1.0 establishes the acceptance check. The process owner sets the effective date and reviewer before use.
- Test the missing-contact and unavailable-owner cases as well as the ordinary path.
Completed customer handoff example
Free downloads. Edit the Word file in Word or import it into Google Docs.
Blank SOP template
Free downloads. Choose Word for a document, Excel for steps in rows, PDF for printing or Markdown for plain text.
Continue with a related task
Want to know why we built SOPFlow? Read the founder’s story.