Below is a complete sample standard operating procedure you can adapt, with a note under each section explaining why it is written that way, followed by a second, shorter sample SOP for a monthly task. The question this article answers is practical: what does a finished, usable procedure actually look like on the page, and what decision sits behind each line? Most standard operating procedure examples online are either a blank template or a laboratory protocol. Neither helps the owner of a 50-person firm who wants to see a real business process written down properly. The main sample covers handling a new enquiry, because almost every company has one and almost every company handles it inconsistently.
Why a worked sample beats a template
A template tells you which headings to use. It does not tell you how specific to be, how long each step should run, or what to do when the buyer does something unexpected. Those are the decisions that make a procedure work or fail, and you only learn them by seeing them made.
Business procedures fail most often at the level of the sentence. "Respond to the lead promptly" is a template sentence. "Reply within 15 minutes during office hours, using the first-reply snippet" is a procedure sentence. Both samples below are written at that level throughout.
Sample one: handling a new enquiry
What follows is the procedure as your team would see it. The annotations in note boxes are for you, the author, and would not appear in the live version.
Header
- Title: Handle a new enquiry
- Reference: SALES-001
- Owner: Head of sales
- Applies to: Anyone on enquiry duty, including reception when sales is unavailable
- Version: 1.2
- Last reviewed: date of last review
- Next review: six months after last review
The title is an instruction, so it matches how people describe the task when they search for it. The owner is a role, not a named person, so the procedure keeps an owner when people change jobs. The "applies to" line names reception because, in most firms, reception is who actually answers the phone at lunchtime.
Purpose
New enquiries are answered within 15 minutes during office hours and before 9:30 the next working day outside them, every enquiry is recorded in the CRM, and every qualified enquiry leaves the first conversation with a booked call.
The purpose is an outcome you can check, with a deadline, not a value statement. Anyone can look at last week's enquiries and see whether it was met. It is also the standard to test any proposed change against.
Scope
Covers enquiries from the website form, phone, email, live chat and referrals. Does not cover existing clients asking for more work, which follows SALES-004.
Before you start
- You are logged in to the levelpartner.ai platform and can open Conversations.
- You know who is on enquiry duty today. The rota is pinned at the top of the sales channel.
- You have the qualifying questions card open (SALES-001-A).
Procedure
- Open Conversations and open the contact's thread as soon as the notification arrives.
- Check the contact record for an existing client relationship, an open opportunity or a previous enquiry.
- If the contact is an existing client, assign the contact to their account manager and stop here.
- Click the Snippets icon in the message composer, choose the first-reply snippet, and add one sentence that refers to what they asked.
- Offer two specific call times, or send the calendar booking link if they prefer to choose.
- Ask the three qualifying questions on the card, by phone if they called and by message otherwise.
- Record the answers in the contact's qualifying fields.
- If the enquiry meets the qualifying rules, go to Opportunities, add an opportunity for the contact in the New enquiry stage and assign it to the rep on the rota.
- If it does not, add the tag for the disqualification reason to the contact and send the polite decline snippet.
- Confirm the booked call appears in the rep's calendar before you move on.
Each step is one action. Step 3 contains an explicit exit, which is the most common thing missing from small business procedures: the branch where the general rule does not apply. Step 10 is a check, not an action, because the most frequent failure in this process is a booking that never reached the rep's calendar.
Exceptions
- If the enquiry is from a journalist, forward it to the managing director and do not qualify it.
- If the enquirer is abusive or clearly spam, do not reply, and record it as spam.
- If nobody on the sales rota is available today, assign to the head of sales.
Records
The conversation, contact record, qualifying fields and opportunity are the records. Nothing is kept outside the platform.
Measures
Reviewed weekly by the head of sales: median first-reply time, share of enquiries with a booked call, and number of enquiries with no qualifying fields completed.
Measures belong in the procedure. Without them, the owner has no way to tell whether people follow it, and the review becomes a matter of opinion.
What makes sample one work
Three features carry most of the weight.
First, it states timings. Speed of first reply decides more enquiries than the quality of the reply, and a procedure that says "promptly" lets each person define prompt.
Second, it ends with a verification step. Procedures usually stop at the last action. Adding a check that the outcome actually happened catches silent failures, such as a calendar sync error, before the prospect does.
Third, it is short. Ten steps fit on one screen. If your draft runs past fifteen steps, it is almost certainly two procedures, and the right move is to split it.
Suppose the brokerage takes four hours on average to answer web enquiries, and about half are never logged as contacts. With an automated acknowledgement and a human reply inside 15 minutes, every enquiry would exist in the CRM from the first minute. Say that turned 60 enquiries a month into 18 booked calls before; if faster replies booked even one more call in every ten enquiries, that would be 24 a month on the same volume.
Sample two: a sample SOP for the monthly client report
The second sample SOP covers a task most service businesses run every month, so you can see the same shape applied to recurring delivery work. Agencies send monthly reports, consultants send progress updates, mortgage brokers send pipeline summaries to introducers and real estate firms send landlords or vendors activity reports. It is also a task where variation is expensive: one account manager sends a polished report on the third working day, another sends a raw export on the twelfth, and the second client starts to wonder what they are paying for.
Title: Prepare and send the monthly client report. Purpose: every retained client receives an accurate, readable report by the fifth working day of each month. Trigger: the first working day of the month. Owner: head of client services. Performed by: the account manager for each client. Version 3.
Steps: 1. Open the reporting dashboard and set the date range to the previous calendar month. 2. Export the five agreed metrics for the client into the report template. 3. Compare each metric with the previous month and with the target in the client plan. 4. Write three sentences of commentary: what went well, what did not, what you will change. 5. Add one recommendation the client can approve or reject. 6. Save the report as a draft and give a second account manager a review task. 7. The reviewer checks numbers against the dashboard and reads the commentary for clarity, then completes the task or returns it with comments. 8. Send the report to the client contact using the report email template. 9. Log the send date on the client record. 10. Book or confirm the monthly review call.
If a metric cannot be pulled: note the gap in the report, tell the client why and when it will be fixed, and raise an internal task for the data owner. Done when: the client has the report, the send date is logged and the review call is in the diary.
That is about 250 words, and a competent account manager can follow it on their first day. Three choices in it are worth copying.
The trigger, owner and performer are separate. The trigger is a date, so nobody has to remember to start. The performer is listed apart from the owner because the person who owns a procedure is rarely the one who runs it, and when the two are blurred, the performer notices a wrong step but assumes the document is not theirs to fix.
Step 4 constrains the commentary to three sentences in a fixed shape. Left open, commentary either disappears or becomes a page of filler the client skims. Step 6 adds a second pair of eyes, which does more for report quality than any writing guidance because it catches wrong date ranges and copied numbers before the client sees them.
The "done when" line lists three things a manager can verify in thirty seconds without asking anyone. If you cannot write a definition of done like that, the procedure has no clear end, and tasks without clear ends are the ones that drift.
Imagine 30 retained clients and six account managers, with reports going out anywhere from the third to the fifteenth working day. Say about 4 reports a month contain an error a client spots, each taking an hour to correct and apologise for. The peer review would add 15 minutes per report, 7.5 hours a month across the team. The trade is 7.5 predictable hours against four awkward client conversations, and a fifth-working-day deadline every client can rely on.
What most samples get wrong
Most published samples are written to look thorough. They have a revision table, a glossary, a responsibilities matrix, a references section and a list of related documents, all on page one, and the steps start on page three. Nobody in a 50-person firm reads to page three.
Put the steps where the eye lands. Push the governance detail to the end or into a separate register. Link to anything that changes faster than the procedure, such as the client's agreed metrics or an email template, instead of pasting it in. If you operate in a regulated setting where an auditor expects document-control fields, keep them, but still keep the steps near the top. Where you need recorded sign-off on top, SOP certification explains the two levels of approval.
Leaving out the exception path. Most samples show the happy path only. A real procedure has to say what happens when data is missing, a client contact has left or a system is down, because those are exactly the moments people improvise badly. One or two exception lines are enough.
Other procedures worth writing in the same shape
The same skeleton works for most processes in a service firm. Useful candidates, in rough order of the revenue they protect:
- Booking and confirming a first meeting, including reminders and what to do on a no-show.
- Sending a proposal and following it up.
- Onboarding a new client after signature.
- Requesting a review after a project closes.
- Raising and chasing an invoice.
Each gets the same header, purpose, scope, steps, exceptions, records and measures. The steps change; the skeleton does not. For a longer example built on the same skeleton, see the sales SOP.
Adapting the samples to your firm
Copy the shape, not the steps. Change the timings to what you can actually staff. Promising a 15-minute reply and achieving it half the time is worse than promising an hour and hitting it every time, because people learn to ignore a target that is never met.
Replace the qualifying questions with your own. Three is the right number for a first conversation; more than that turns a reply into an interrogation. Name the systems you really use. If enquiries arrive in three separate inboxes, the first improvement is getting them into one place. On the levelpartner.ai platform, Conversations brings email, SMS, WhatsApp, chat and call records into one view, so step one can name a single place to look.
Look for steps that do not need a person. In sample two, the first-of-month trigger, the review task and the send-date log can all run as workflow actions, leaving the account manager the steps that need judgement.
Then test your version. Give it to someone who has never done the task and watch them follow it. Our guide to SOP training covers how to bring staff onto the tested version, and the SOP for a virtual assistant shows how to write each step against the access the person actually has.
Frequently asked questions
Can I use this sample standard operating procedure as it is?
Use it as a starting point, not a finished document. Change the timings, the qualifying questions, the roles and the systems to match your firm, then test it by asking someone who has never handled an enquiry to follow it while you watch.
What should a sample SOP include?
A title written as an instruction, a one-line purpose with a deadline, the trigger, the owner, numbered single-action steps, what to do when something goes wrong and a checkable definition of done. Anything beyond that should earn its place.
What is the difference between a sample and a template?
A template gives you empty headings. A sample shows finished content, including how specific each step is and where the exceptions go. Most people learn more from a sample, because the hard decisions are about wording and detail, not headings.
Does every procedure need a review step like sample two?
Only where an error reaches a client or costs real money. Internal, low-risk tasks do not need a second reviewer. Client-facing outputs such as reports, proposals and invoices usually do.