SOP stands for Standard Operating Procedure.
An SOP is a short, written document that explains how to complete a specific task — the same way, with the same result — no matter who’s doing it.
That’s the textbook answer. It’s correct.
It also leaves out the part that decides whether anybody follows yours.
To get there, we have to go back to a runway in Ohio.
The First Famous SOP Was Written After a Plane Crash
On October 30, 1935, the U.S. Army Air Corps gathered at Wright Field in Dayton, Ohio to watch the future of aviation take off.
The plane was Boeing’s Model 299.
- Four engines
- Retractable landing gear
- Electric trim tabs, adjustable propellers, wing flaps — more switches and controls than any bomber before it. Boeing was betting the company on winning the Army contract
The pilot was Major Ployer P. Hill, chief of the Air Corps’ flying branch at Wright Field. One of the most experienced test pilots in the country.
The plane rolled down the runway, lifted off, climbed a few hundred feet…
Then stalled, and crashed into the field.
Hill died from his injuries, along with Boeing’s own chief test pilot.
Investigators went through the wreckage looking for a mechanical failure. There wasn’t one.
The crew had forgotten to release the gust lock — a device that holds the control surfaces in place while the plane is parked. One step. Missed by the most qualified man they could put in the seat.
The press said the plane was too complex for one man to fly. Boeing lost the contract.
The Checklist That Changed Everything
A group of Boeing engineers and test pilots disagreed. The plane wasn’t too complex to fly. It was too complex to fly from memory.
So they wrote the pilot’s checklist. Taxi, takeoff, landing. Every critical step, in order, every time.
The Model 299 went on to become the B-17 Flying Fortress. Boeing built 12,730 of them.
Notice what that checklist covered. Taxi. Takeoff. Landing.
It didn’t tell the pilot how to fly.
An SOP is a set of guardrails. It locks down the steps you can’t afford to miss and leaves the judgment to the person doing the work.
Most SOPs get this backwards. They try to script everything, run 30 pages, and nobody reads them.
What Does SOP Stand For?
SOP stands for Standard Operating Procedure. Each word does a job:
- Standard: It’s the agreed way. Not Kevin’s way, not Karen’s shortcut, not “however the last person did it.”
- Operating: It covers the day-to-day work of running the business. Real tasks that repeat.
- Procedure: It’s a sequence of steps.
In business, the SOP meaning is always this one. (If you’re applying to grad school, you want a Statement of Purpose — different document, different article.)
You’ll also see people write SOPs or SOP’s, or talk about “an SOP document.” Same thing. One SOP covers one task.
A company’s collection of SOPs is usually called an operations manual or a playbook.
An SOP Should Be Two Pages. Maximum.
Flying a B-17 needs more pages. So does running a pharmaceutical line or a nuclear plant, where a regulator audits every word.
Your business isn’t flying a bomber.
For the companies we work with — founders, agencies, service businesses, ecommerce brands — a single SOP should be no more than two pages.
If it runs longer, one of two things is happening:
Either it’s actually three processes stapled together, or it’s trying to script decisions that belong to the person doing the work.
Every SOP needs the same parts:
- Title: The name of the task, written the way your team actually talks about it.
- Purpose: One or two sentences on why this task exists.
- Owner: The one person responsible for keeping the SOP accurate.
- Trigger: What kicks the task off. A new client signs. An invoice goes overdue. It’s Monday at 9am.
- Steps: The critical ones, in order. Not every click.
- Definition of Done: What finished looks like. “Call the vendor” is a task. “Vendor confirms the replacement ships by Friday, in writing” is done.
- Video and links: A screen recording, logins, templates.
- Last updated: A date. An SOP with no date is an SOP nobody trusts.
That’s your SOP template. A Google Doc is plenty.
Guardrails, Not Scripts
Here’s where most SOPs go wrong.
A founder sits down to write an SOP and tries to capture everything.
Every step, every exception, every “if the client says this, you say that.” It feels thorough. It’s a disaster.
Take a cold sales call.
The opening matters. Who you are, why you’re calling, and the question that gets them talking.
Get those first few seconds wrong and the call is over. That part should be written down, word for word, and practiced.
The ask at the end matters too. Booking the next meeting has a right way and a wrong way.
The middle? It can go a million different ways.
- The prospect has a question you didn’t expect
- They mention a competitor
- They tell you about their kid’s soccer game
You can’t write an SOP for that, and if you try, you get a rep reading a flowchart out loud to a human being.
So you script the open and the ask. The middle is freestyle.
Our hiring discovery calls work on the same idea, just looser.
There’s no word-for-word script. There’s a list of questions our reps are supposed to cover — enough to understand the role, the urgency, and the key points of what the client actually needs.
The Sales Rep doesn’t have to ask them in order. They don’t have to ask every single one. It should feel like a natural conversation, not an intake form read out loud.
The Rule Is This:
By the end of the call, they should have asked 80% of those questions. Hit 80% and we have everything we need to run the search — and the client has had a real conversation about their hire instead of an interrogation.
That’s a guardrail.
The rep has room to think, listen, and follow the conversation where it goes. They just can’t finish the call without the information that matters.
Speaking of those discovery calls — if you want to talk through a role you’re hiring for, book one here.
Why You Need SOPs: Judgment Doesn’t Survive the Handoff
When a business is small, it runs on the founder’s judgment. That works, because the founder is in every decision.
Then the company grows.
At HireUA, I used to be in every interview. Then I trained an Operations Manager, who trained a Head of Recruiting, who trained the Recruiters.
Each handoff was reasonable. Each person was good at their job.
One day I randomly opened up a batch of recent interviews.
Why the hell were these people being approved? It made no sense.
Nobody had done anything wrong. My judgment had just been passed down three times by word of mouth, and it didn’t survive the trip.
Every layer added a little of their own taste and lost a little of mine.
That’s the moment every growing company hits.
The founder’s standard lives in the founder’s head. The further the work gets from that head, the less it looks like what the founder would have done.
So we pulled the decision out of everyone’s head — including mine.
We built a scored hiring matrix.
Every candidate gets scored on the same fixed set of criteria, no matter which recruiter screens them. There’s a hard cutoff.
Below it, the candidate doesn’t go to a client, no matter how much the recruiter liked them. And there’s a narrow middle band where the recruiter can’t decide alone — a second person has to weigh in.
That’s an SOP. It’s also a guardrail. It doesn’t pretend recruiters don’t need judgment.
It tells them exactly where their judgment applies.
SOP vs. Policy vs. Process vs. Checklist
These four words get mixed up constantly:
| Term | What It Answers | Example |
| Policy | What’s the rule? | “All client invoices are due within 14 days.” |
| Process | What happens, start to finish, across the company? | Sale closes → onboarding → delivery → invoicing → renewal |
| SOP | How do I do this one task? | The steps for chasing an overdue invoice |
| Checklist | Did I do every critical step? | The tick-box version used every time the task runs |
A policy tells people what the rule is. An SOP tells them what to do about it on a Tuesday afternoon.
A process is the whole map. SOPs cover each stop on it.
And a checklist is what the B-17 pilots carried — the shortest possible SOP, built for someone who already knows the job and can’t afford to skip a step.
Why Most SOPs Never Get Followed
Plenty of companies write SOPs. They spend a month on it.
Build a beautiful folder. Announce it in a team meeting.
Six months later, nobody opens them.
Four reasons, over and over:
1. They’re too long.
Thirty pages for a process that takes twenty minutes. Nobody reads it, so everybody goes back to asking the one person who knows.
2. They script judgment.
The SOP tries to cover every possible situation, which means it covers none of them well.
The first time reality doesn’t match the flowchart, the team decides the whole document is useless.
3. They document the ideal, not the reality.
The founder writes down how the task should go, from memory, in one sitting. It doesn’t match what actually happens.
4. Nobody owns them.
Tools change. Clients change.
An SOP with no owner goes stale in a few months, and the first time someone follows an outdated step and gets burned, they stop trusting every SOP in the folder.
How to Write an SOP in 2026
Forget sitting down with a blank document.
The fastest way to write a good SOP now is to record it.
- Turn on your screen recorder and do the task while you talk through it.
- Explain why you do each step, not just what you’re clicking.
- Add voice notes with all the context that never makes it into a document — the client who always pays late, the step that breaks if you skip it, what a good result looks like.
Lots of video. Lots of voice notes. And a lot of context.
Then hand all of it to an AI.
But don’t type “write an SOP.” That gets you a clean, generic document that could belong to any company on earth.
Tell the AI to review everything as if it’s a new employee on their first day.
Have it list every question it would need answered to do the task alone — the missing steps, the unclear decisions, the tools it doesn’t have access to, what “finished” means.
Answer those questions. Then have it write the SOP, under two pages, with the critical steps locked in and the judgment calls clearly marked.
That’s the difference between an AI writing a document and an AI stress-testing your process before a real new hire ever touches it.
[GATED CTA — Dorka: “Download our free 3-page guide to writing an SOP your team will actually follow, including the exact AI prompt we use.” Email capture.]
Your Hiring Process Needs an SOP More Than Anything Else
Most companies have SOPs for invoicing, onboarding, maybe customer support.
Almost none have one for hiring.
The most expensive decision a business makes — who gets a seat — comes down to whoever happened to run the interview and how they felt that day.
One manager loves confident talkers.
Another weighs the resume.
A third decides in the first 30 seconds and spends the rest of the call confirming it.
That’s the same drift we hit when our own judgment went through three handoffs. Now picture it with no matrix to catch it.
Every candidate we submit has been through the same scored process.
Same criteria, same cutoff, same second opinion in the gray zone — whether the search is for an Executive Assistant, a Developer, or a sales rep. It’s how we’ve placed 1,100+ people across 35 countries without the quality depending on which recruiter picked up the search.
You don’t have to build that system yourself. We already did.
Frequently Asked Questions About SOPs
What does SOP mean in business?
SOP means Standard Operating Procedure — a written document that explains how to complete a specific repeating task the same way every time.
What is an SOP document?
It’s the written SOP itself: A title, purpose, owner, trigger, critical steps, Definition of Done, supporting video or links, and a last-updated date.
How long should an SOP be?
For most businesses, no more than two pages.
Highly regulated work like aviation or pharmaceuticals runs longer.
If yours is longer than two pages, it’s likely more than one process or it’s trying to script decisions.
Should an SOP cover every situation?
No. An SOP should lock down the steps that can’t be missed and leave room for judgment everywhere else.
A sales call script covers the opening and the ask, not the conversation in between.
Can AI write SOPs?
AI can draft them well if you give it real material.
Record the task on video, add voice notes with context, and have the AI review it as a new employee on day one before it writes anything.
How often should SOPs be updated?
Any time the task changes, and reviewed at least once a quarter. Every SOP should have one named owner.
Back to Wright Field one more time.
The checklist that came out of that crash covered taxi, takeoff, and landing. The moments where one missed step kills everyone on board.
Everything in between, the pilot flew.
That’s the job of your SOPs. Lock down the moments you can’t afford to miss. Hire people good enough to handle the rest.
That second part is what we do. Book a hiring discovery call — we’ll ask our questions, and you’ll see the guardrails for yourself.
Tell Us Who You Need.
Tell us what needs to get off your plate. We’ll help define the role, tell you what it should cost, and recruit in the talent market where that role is strongest.