What is an SOP?
An SOP (standard operating procedure) is a maintained set of instructions for a repeatable task. It explains when the task starts, who is responsible, which actions and checks to follow, and what to do when something goes wrong.
In the fictional customer handoff below, the SOP ends when an available receiving owner accepts the next action and its due date. The instructions describe how to reach that result; the handoff record shows what happened in one case.
Define the outcome and the starting point
Before writing steps, describe the observable result and the event that starts the procedure. For a customer handoff, that might be a checked account, an assigned owner, and a recorded next action. Specify the access, information, and tools the person needs before beginning.
Write one useful action at a time
Use direct instructions and the labels people will see in the system. Explain what to check after saving or submitting, not only what to click. Group steps into phases when there is a meaningful handoff or change of responsibility.
A screenshot can clarify a screen, but it cannot explain every decision. Add the context a new colleague would otherwise need to ask about.
Name owners and exceptions
Identify the team that maintains the procedure and the roles that perform it. For each handoff, say what the receiving person needs. Include a clear stop or escalation instruction when a prerequisite is missing or a check fails. Configure workspace access to match those responsibilities.
Capture the browser work when it helps
SOP Recorder can provide a first draft from supported browser interactions and screenshots. Review the sequence, images, and proposed instructions, then import the useful steps. Use example data and check the captures before sharing. AI drafting uses the workspace’s available allowance.
You can also write the procedure yourself or bring existing text. Choose the starting point that needs the least correction for this particular task.
Test the instructions with a teammate
Ask someone who did not write the procedure to follow it in a suitable practice setting. Observe where the instructions are unclear. Give help when needed and record the gap; the goal is to improve the procedure, not test someone’s ability to guess. Validate completion against the intended outcome.
Review, publish, and keep it useful
Request review, publish the approved version, and show readers where to find it. Decide whether colleagues need assigned training or a procedure run. Set a review cadence and revisit the instructions when the tool, responsibilities, or process changes. Preserve the context of earlier work when publishing a revision.
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.
Compare four completed SOP examples to see how triggers, exception paths and completion records change between tasks.
Turn an SOP into a flowchart
Choose the structure around the task. Numbered steps show a sequence; a checklist helps verify required items; phases make a change of responsibility visible; a flowchart helps a reader choose between routes. Keep the current procedure easy to find when you combine them.
Build this map manually from the fictional customer handoff in the worked example below. Sales supplies the details, the Customer Success lead arranges an available owner, and the receiving owner confirms acceptance. The boundary is an accepted handoff with a recorded next action and due date; delivery of the customer's service belongs to a later procedure.
Map the decisions as well as the ordinary steps
- Mark the same start and finish as the SOP. Use an action box for a meaningful task. Keep detailed field instructions beside the procedure step they explain.
- Turn each condition into a question with labelled outcomes. Missing or unclear information keeps the case open and identifies who must resolve it.
- Keep availability, access and acceptance distinct. Check that the receiver is available and can open the record before recording their acceptance, next action and due date.
- Give every exception a visible destination. After the responsible person resolves it, repeat the relevant check before continuing.
Scroll horizontally to explore the diagram. The equivalent text follows.
Follow the same routes in text
Ordinary route
- Handoff request received
- Check organization, scope and contact
- Information complete? Yes
- Receiver available with access? Yes
- Record acceptance, next action and due date
- Handoff record complete? Yes
- Close the Sales task
- Information complete? No.
When: Required information is missing or unclear.
Action: Return the question to Sales and keep the handoff open while the missing details are resolved.
Before continuing, return to: Information complete? Compare the corrected record with the approved handoff request.
- Receiver available with access? No.
When: The receiver is unavailable or cannot open the relevant record.
Action: Ask the Customer Success lead to arrange an available, authorized owner. Keep the Sales task open.
Before continuing, return to: Receiver available with access? Check availability and actual access again; assigning a name does not establish acceptance.
- Handoff record complete? No.
When: Scope, contact, owner, acceptance, next action or due date is missing.
Action: Keep the handoff open and ask the responsible person to resolve the missing record.
Before continuing, return to: Handoff record complete? Check the summary again. If the scope, contact or receiver changed, repeat those earlier checks first.
Test the map against the procedure
- Walk the ordinary route with someone who performs the task. Check the result before treating the handoff as complete.
- Try missing information, an unavailable receiver and an incomplete confirmation. Each case must remain open until its issue is resolved.
- Keep field definitions, role authority, access requirements and record references in the maintained SOP. Give your map a procedure reference and revision note.
- Review the map and its links when the instructions change, while preserving earlier training and work records in their original context.
ASQ explains common flowchart symbols and walking through a draft with the people doing the work.
Turn rough notes into testable instructions
Use one customer handoff to test the writing. A useful step identifies an action, its object and the observable result. Add the decision where the reader encounters it; a warning at the end is easy to miss.
| Rough note | Usable instruction |
|---|---|
| Check the account. | Open the customer record and compare the organization name and primary contact with the approved handoff request. If either is missing, return it to Sales. |
| Send it to the right person. | Ask the Customer Success lead to assign an available owner. Record their acceptance before closing the Sales task. |
| Make sure everything is done. | Confirm scope, contact, owner, next action and due date are present. Leave the handoff open if any field is missing. |
Before using the example
- Give the draft and fictional account to a teammate who did not write it. Ask them to perform the task without verbal coaching.
- Record every clarification, skipped decision and missing prerequisite. Revise the instruction that caused the problem.
- Repeat the exception path. Review the corrected draft with the owner before approving it.
Continue with a related task
Want to know why we built SOPFlow? Read the founder’s story.