# SOP (standard operating procedure): what it is, how to write one, and five sales SOP examples

https://salesbond.app/blog/sop-sales-team/
Published: 2026-10-31 · Updated: 2026-11-12

SOP stands for standard operating procedure: a written, step-by-step guide for a task or workflow, so that whoever does the job completes it in the right order and to the same standard ( [Outsource Accelerator: standard operating procedure](https://www.outsourceaccelerator.com/glossary/standard-operating-procedure-sop/)). In a sales team, an SOP covers the few moves that repeat every week, such as qualifying a lead or changing a deal stage, and ties each step to a field or rule in the CRM so the manager can check it without asking.

SOPs are written wherever a task repeats and the result has to match every time: production lines, billing and collections, patient records, food handling, IT backups and patch installs ( [TechTarget: what is a standard operating procedure](https://www.techtarget.com/news/What-is-a-standard-operating-procedure-SOP/842435/)). A sales SOP that lives only in a document gets forgotten, so each of its steps should leave something the CRM can show.

## What a standard operating procedure (SOP) is, and when a small team needs one

A five-person sales team needs from an SOP what a cook needs from a recipe: the order of steps and what “done” looks like, written so a new rep can follow it on day three.

The purpose is the same on a factory floor, in a clinic and in a sales team: the task comes out the same whoever does it. Wikipedia lists what SOPs are for as uniformity of performance, quality output and fewer failures to follow the rules the business is subject to, with less miscommunication along the way ( [Wikipedia: standard operating procedure](https://en.wikipedia.org/wiki/Standard_operating_procedure)). For a small sales team that comes down to three things. A new rep reads the procedure instead of interrupting the manager with the same question for the fourth time; the same page notes that this is how new employees use an SOP. The method stays when the person who invented it leaves. And the pipeline report means one thing, because every deal went through the same steps. Compliance matters less for five people selling software than for a lab, unless you sell into a regulated industry.

You need one the first time two reps do the same thing differently and the pipeline report stops meaning anything. One rep moves a deal to Proposal after sending a price by email; another waits for the meeting where the price was discussed. Same stage name, two realities, and the conversion number between those stages is now noise. That is the moment to write it, well before “when we grow”, and the second trigger is a rep leaving with a method nobody wrote down.

A playbook is a different document. It holds what reps say; we wrote ours as [one page built from the pipeline stages](https://salesbond.app/blog/sales-playbook-small-teams-pipedrive/). The SOP holds what reps do in the system when a thing happens. Keep the two apart or both get long. Policies and process documents sit on either side of it. A policy states the standard (“every inbound lead gets a reply within one business day”) and, as TechTarget puts it, is the foundation SOPs are built on; the SOP holds the steps that meet it ( [TechTarget](https://www.techtarget.com/news/What-is-a-standard-operating-procedure-SOP/842435/)). A process document covers the whole flow from lead to invoice, and one process may need one SOP or several, depending on how many variants it has ( [Wikipedia](https://en.wikipedia.org/wiki/Standard_operating_procedure)). In a small sales team the flow from lead to won usually needs five.

## What goes into an SOP: the classic parts

Open any SOP template from a quality department and you will find the same skeleton. A title and an ID number, so one procedure can point to another and one version can be told from the next. A purpose: a sentence on why the procedure exists and what result it protects. A scope: which situations, teams or products it covers, and which it does not. Responsibilities: which role does which step, and who approves an exception. The procedure itself: numbered steps in the order they happen, each one action. References: the forms, systems, other SOPs or regulations the steps point to. And the housekeeping: who wrote it, who approved it, the effective date and the date of the last revision. TechTarget’s component list puts the ID, the audience and the names of the people who prepared and approved the procedure on a title page, and adds a table of contents, a glossary and appendices for long procedures ( [TechTarget](https://www.techtarget.com/news/What-is-a-standard-operating-procedure-SOP/842435/)). Penn State’s writing guide treats a descriptive title, the person responsible and the effective date as the minimum every SOP carries, whatever its format ( [Penn State Extension: Standard Operating Procedures, a writing guide](https://extension.psu.edu/standard-operating-procedures-a-writing-guide)).

Each part answers a question the reader would otherwise have to ask the author: why do we do this, does it apply to me, who does it and how, what else do I need. In a factory or a lab every part earns its place because the reader may be a new hire, an auditor or someone covering a shift in another building.

For a five-person sales team the reader sits next to the manager, the purpose is obvious and the scope is the pipeline. So we cut the skeleton to a name and four lines, and add one line the classic layouts leave out: what the CRM shows when the procedure is done. The result is a [half-page template](#a-half-page-sop-template-trigger-steps-owner-result) that fits next to the CRM.

## How to write an SOP in seven steps

The order matters more than the template, because most SOPs that fail start with the steps and never say what result they protect.

1. Pick a task that repeats and goes wrong in different ways. Not “selling”; “moving a deal to Proposal”. If two reps do it two ways and it costs something, that is the task. In sales, start with lead intake and stage change: they happen daily and feed every report.
2. Ask the person who does it for the first draft. Penn State’s method starts by watching someone perform the task as it exists today and writing down everything they do ( [Penn State Extension](https://extension.psu.edu/standard-operating-procedures-a-writing-guide) ). The rep drafts, the manager edits. A rep who writes “I check the deal has a next activity, then I move it” has just handed you step three of the stage-change procedure.
3. Write the trigger and the result before the steps. “A new lead arrives” and “a deal with a source, an owner and a dated next activity”. If you cannot say what the CRM looks like when the procedure is done, what you have is still advice.
4. Write the steps, one action per line, in the order they happen. Verb first: “Set the lead source from the list”, not “The source should be set appropriately.” Three to six lines. If you need ten, you have two procedures.
5. Name the owner as a role. “Deal owner”, “whoever creates the record”, “the SDR”. Maria leaves in March and a document with her name in it is wrong the same day.
6. Test it on someone who has never done the task. Penn State’s test is a person unfamiliar with the work performing each step exactly as written while the writer watches ( [Penn State Extension](https://extension.psu.edu/standard-operating-procedures-a-writing-guide) ). Every pause is a missing step or an unclear one. In sales the pause usually comes at “move the deal only if the exit criterion is met”, because nobody wrote down the criterion.
7. Set a review date and write it on the page. TechTarget suggests every six to twelve months ( [TechTarget](https://www.techtarget.com/news/What-is-a-standard-operating-procedure-SOP/842435/) ); for a sales pipeline we prefer a quarter, because stages and fields change faster than lab equipment. A procedure with no review date ends up in a binder nobody opens.

A word on format. Penn State names four: simple numbered steps; hierarchical steps, where a main step carries substeps; a graphic format that breaks a long job into short sub-procedures of a few steps each; and a flowchart for procedures with many decisions. The choice depends on how many decisions the user makes and whether there are more than ten steps ( [Penn State Extension](https://extension.psu.edu/standard-operating-procedures-a-writing-guide)). A checklist is simple steps with boxes, and some teams record a screen video instead. Sales procedures are short with few branches, so simple steps are enough, and the decisions that do exist (is this deal qualified or not) belong in the CRM as a required field or a stage rule. The flowchart for “deal handover” would be three boxes, so write the three lines instead.

## A half-page SOP template: trigger, steps, owner, result

The classic skeleton above shrinks to a name and four lines:

```
Procedure: <name, two or three words>
Trigger: <the event that starts it>
Steps: <three to six lines, each one action>
Owner: <the role, not the person>
Result: <what the CRM shows when it is done>
```

The last line is the one most templates lack, and it is the one that makes the procedure checkable. “Result: the deal has a dated next activity and a lost reason if it was closed” can be turned into a filter. “Result: the lead has been handled properly” cannot.

Skip the exceptions, because the SOP is for the common case.

## Five sales SOP examples worth writing first

The five are lead intake, qualification, stage change, handover, and closing with a reason. In a small team these are where the same mistake repeats, and each fits on half a page. Unless a procedure says otherwise, the owner is the deal owner.

### Lead intake

Trigger: a new lead arrives, by form, referral, inbound call or a rep’s own prospecting. Steps: create the person and the organization before the deal; set the lead source from a fixed list, not free text; assign an owner the same day; schedule the first activity. Owner: whoever creates the record. Result in the CRM: a deal with a source, an owner and a dated next activity, nothing blank.

The part teams skip is the fixed source list. “Website”, “web” and “inbound” are three values for one thing, and the source report will show three thin bars instead of one honest one.

### Qualification

Trigger: the first real conversation has happened. Steps: fill the qualification fields your team agreed on (budget known or not, decision maker reached or not, timeline named or not); move the deal to Qualified only if the agreed minimum is met; otherwise keep a next step scheduled or mark the deal lost with a reason. Result: every deal in Qualified has those fields filled.

Which fields? Pick three that a rep can fill straight after the first conversation.

### Stage change

Trigger: the rep wants to move a deal forward. Steps: check the exit criterion for the current stage (a sent proposal, a confirmed meeting, a verbal yes), update the expected close date and value if they changed, and schedule the next activity before moving. Result: no deal sits in any stage without a next activity.

Write the exit criterion as one sentence per stage where the rep sees it; the simplest place is the stage name itself, “Proposal (sent)”. Moving a deal back when the criterion was not met is part of the procedure, and nobody should treat it as a penalty.

### Handover

Trigger: a deal changes hands, from SDR to AE, from sales to delivery, or between reps when someone is away. Steps: the giver writes a three-line note on the deal (where it is, what was promised, what happens next), reassigns the owner in the CRM rather than in Slack, and the receiver confirms by scheduling thier first activity. Owner: the giver, until that activity exists. Result: the owner field matches the person actually working the deal.

### Closing with a reason

Trigger: the deal is won or lost. Steps: mark the outcome the same day; for lost, choose a reason from a short fixed list and add one line of free text; for won, confirm the final value and close date. Result: no open deals that are secretly dead, and a lost-reason report a manager can read.

If your lost reasons are free text today, fix the list first. We went through that cleanup for [Pipedrive lost reasons](https://salesbond.app/blog/pipedrive-lost-reasons/) and the [HubSpot closed lost reason property](https://salesbond.app/blog/hubspot-closed-lost-reason/) separately.

## Every step becomes a field, a stage rule or a task

Our rule is that an SOP step the CRM cannot show counts as not done, because memory is a poor record even for honest reps. So go through each procedure line by line and decide what the CRM should enforce and what it should only record.

![Three-column diagram: five SOP steps, the CRM object each becomes, and the report or filter that checks it](https://salesbond.app/wp-content/uploads/2026/11/sop-sales-team-2.png)

Take the five procedures in order. The lead source becomes a dropdown with a fixed list, and you check it with deals by source; if “Other” holds more than a handful, the list is wrong. The qualification fields become required on entering Qualified. In Pipedrive a deal field can be made required for chosen pipelines and stages, so the deal cannot move on until it is filled ( [Pipedrive: required fields](https://support.pipedrive.com/en/article/required-fields)), and HubSpot can show chosen properties when a deal is moved into a stage ( [HubSpot: set up pipelines](https://knowledge.hubspot.com/object-settings/set-up-and-customize-pipelines)). The check is any deal in Qualified or later with a blank in one of the three.

“Schedule the next activity before moving” becomes a saved filter: open deals with no next activity, by owner. Handover lives in the owner field, and the check is deals whose new owner has logged nothing since the handover date. Lost reasons become a fixed list with free text as an addition, never the only option, read as lost deals by reason for the quarter.

Enforce as few of these as you can, one at a time, two weeks apart. Required fields on a stage are the strongest tool and the most annoying one when overused; we described the trade-off for Pipedrive in [required fields in Pipedrive](https://salesbond.app/blog/required-fields-pipedrive/) and for Salesforce in [opportunity stage exit criteria](https://salesbond.app/blog/salesforce-opportunity-stage-exit-criteria/). Our rule of thumb is three required fields at most on the whole pipeline, all of them at the move into Qualified; everything else is a saved view.

A task created for the receiver on handover turns a courtesy into a step you can see. Automate carefully, though: a deal that moves itself when an email is sent teaches the rep to stop looking at the stage, which is why we keep some moves manual ( [what not to automate in your sales process](https://salesbond.app/blog/what-not-to-automate-sales-process/)).

## One report tells you whether anyone follows it

Skip the compliance dashboard and build one list to read on Monday.

The list is open deals with a problem the SOP should have prevented: no next activity, a blank required field, an owner who has not touched the deal since the handover, a close date in the past. It is one saved filter on open deals, sorted by owner. With twelve deals on it, the SOP is holding. With eighty, the stages need work before the rules do, and a look at [your pipeline stages](https://salesbond.app/blog/sales-pipeline-stages/) comes first.

Read it together with the rep. “These four have no next step, what is going on?” is a ten-minute talk that teaches the procedure faster than the the document.

A disclosure, since we are at the “one list” point: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. If you want the list before you have built the filters, the free CRM audit produces a version of it: SalesBond reads the last 30 days of the connected CRM and sends a PDF with deal health, the pipeline bottleneck and what to fix, then a second PDF a week later with what changed. [Check your CRM with SalesBond](https://salesbond.app/). For a team of five, a saved filter does the job most weeks, and that is where we would start.

## The binder nobody opens, and other ways an SOP dies

The classic failure is the binder: a full manual written over a weekend and opened once during onboarding. It is wrong a month later, and nobody notices.

The second failure is a step the CRM cannot show. “Research the account before the first call” does not work as an SOP step, because nothing in the system changes when it is done or skipped. Give it a visible result (a filled field, a note with a fixed heading) or move it to the playbook.

The third is writing it from the manager’s chair, which is why step two hands the first draft to the rep.

The fourth is quiet: someone renamed a field or deleted a stage, and the procedure broke without anyone deciding to break it. That is what the quarterly review from step seven catches, and a step nobody has followed for three months gets deleted.

Keep the page count fixed at five half-pages, one per procedure. If you write only one this week, make it the stage change, and build the “no next activity” filter the same afternoon.
