The reason most physician-owned practices don’t have SOPs isn’t that owners don’t believe in them. It’s that writing SOPs feels like the slowest possible thing to do when there are patients in the waiting room and a thousand small fires to put out. The work itself is urgent. Documentation feels like the opposite of work.
This is the trap, and almost every practice falls into it.
The reality is the opposite of what it feels like. SOPs are the fastest way to systematize a practice. They’re the bones of the business — without them, every process lives in someone’s head, every hand-off is a translation, every new hire is a six-month onboarding because there’s nothing for them to read. With them, training time collapses, mistakes go down, the owner stops being the bottleneck, and the practice becomes something that can run, scale, or eventually be sold.
The good news: in 2026, you don’t need a consultant to build them. You need a method, a few hours of focused work, and an AI tool that costs less per month than dinner.
Here’s how to do it.
Why SOPs matter more than they feel like they should
Before the method, the case.
SOPs unblock delegation. Most physician-owners are bottlenecks because they’re the only person who knows how things are supposed to be done. Every question routes to them. Every decision ladders up. The practice doesn’t grow past the owner’s available bandwidth, because there’s nothing for the team to follow without asking. SOPs externalize the knowledge in the owner’s head and put it where the team can actually use it.
SOPs make new hires productive in weeks instead of months. When a new MA, a new front desk, a new biller starts, the question that determines their ramp time is whether someone has to walk them through everything live, or whether they can read documents and ask questions only when they’re stuck. The first model takes six months. The second takes three to four weeks. Same person. Different infrastructure.
SOPs reduce mistakes. Most operational errors in a practice — billing problems, missed callbacks, supply runouts, charting gaps — are not skill failures. They’re memory failures. People forget the step. People skip the check. People assume someone else handled it. SOPs are external memory. The practice doesn’t depend on whether the front desk was paying attention on the day they were trained.
SOPs are what makes a practice sellable. A practice that exists entirely in the owner’s head is worth a fraction of what a documented, systematized version of the same practice is worth. Buyers pay for transferable systems, not for personal heroics. Even if you have no intention of selling, building toward sellability makes the practice easier to run, hire into, and step away from.
SOPs survive turnover. When a key team member leaves — and they will — a practice without documentation loses everything that team member knew. A documented practice loses a person but keeps the system. The first scenario is a crisis. The second is an inconvenience.
If you’re sitting at your desk thinking I know I should be doing this but I’m too busy — that feeling is exactly the symptom that says you should start tomorrow.
The Codie Sanchez rule
The simplest threshold for whether something deserves an SOP comes from entrepreneur Codie Sanchez:
If it has more than three steps and you do it more than three times, write an SOP.
That’s the whole rule. It’s clean, it’s testable, and it solves the most common SOP question, which is should I document this? If the task is more than three steps and you’ve done it (or someone has) more than three times, the answer is yes. Always.
In a medical practice, this rule alone identifies hundreds of SOPs you should have. Every recurring task in every department clears the threshold. Patient onboarding. New-hire training. Lab result follow-up. Refill protocols. Front desk check-in. Cash and check handling. Daily open and close. Equipment maintenance. Billing reconciliation. Vendor ordering. Every one of them.
You don’t have to write them all this month. But the rule tells you what’s eligible, which means you can stop debating and start documenting.
The method
Here’s the workflow we used to build out the SOP library for our flagship practice. It’s faster than hiring a consultant, and the quality is comparable for most operational documents.
Step 1: Pick one process. Start small. Pick a process you do often and feel some pain around — usually one where mistakes happen, training takes too long, or the work piles up when one specific person is out. Patient onboarding and new-hire training are usually high-leverage starting points because both pay back so quickly.
Step 2: Brain-dump every step you can think of. Open a blank document. Write down everything you do as part of that process, in any order, with no formatting. Don’t worry about completeness or sequence. Just empty the contents of your head onto the page. This usually takes 15 to 30 minutes and produces something messy and incomplete. That’s fine — that’s the raw material.
Step 3: Feed it to AI. Take your brain-dump and paste it into the AI tool of your choice (Claude, ChatGPT, Gemini — they all do this well). Ask it to:
- Reorganize the steps into a logical sequence
- Identify gaps or steps that are probably missing
- Format it as a standard SOP with sections (Purpose, When to Use, Steps, Owner, Notes)
- Flag anything that seems unclear or risky
What comes back is usually 80% of the way to a finished document. The AI fills in obvious steps you forgot to write down, organizes what you wrote into a clean sequence, and surfaces structural gaps you didn’t notice.
Step 4: Compare with a colleague’s version. This is the step that takes the SOP from good to excellent. If you have a peer in another practice running a similar process, ask if they’d share their version. Compare side by side. Their SOP will have steps yours doesn’t, and yours will have steps theirs doesn’t. Each version improves the other. (If you don’t have a peer to compare with, peer groups and practice-owner communities exist for exactly this reason.)
Step 5: Lock the framework, then scale. Once you have one SOP you’re happy with, the structure is reusable for everything else. Same template, same sections, same level of detail. Now you can run the same workflow — brain-dump, AI refinement, peer review — on every other process in the practice, and the cumulative time per SOP drops by half because you’ve already done the hard work of figuring out what good looks like.
What to document
When we built out our library at the practice level, the categories that earned SOPs were broader than people expect. Not just clinical. Operational, administrative, financial, and HR processes all qualify. Specifically, we built SOPs for:
- Clinical care. Initial visit workflow, follow-up structure, referrals out, lab review, controlled substance protocols
- Hiring. Job posting, screening, reference checks, offer letters
- Interviewing. Standard question sets by role, scoring rubric, who interviews when
- Onboarding. First day, first week, first 30 days for every role
- Training. Role-specific training plans, sign-off checklists, competency reviews
- Ordering. Supply reordering thresholds, vendor contacts, approval workflows
- Front desk processing. Patient check-in, schedule management, payment collection, answering common questions
- Cash and checks. Daily reconciliation, deposit procedure, who handles what
- Patient communication. Email templates, phone scripts, response time standards
- Marketing. Content calendar, social posting workflow, lead capture handling
- Compliance. HIPAA training, OSHA logs, board reporting, audit readiness
- Annual / quarterly. Strategy review, financial review, vendor review, staff review
If a process is happening in your practice and you’d be hosed if the person who does it left tomorrow, it needs an SOP.
What good looks like
A working SOP doesn’t need to be long or elegant. It needs to be usable. Most of ours are one to two pages and follow this structure:
- Title. Plain language. Patient Onboarding — First 30 Days.
- Purpose. Two sentences on what this SOP exists to do and why it matters.
- When to use. The trigger that starts this SOP.
- Steps. Numbered, sequential, specific. Each step short enough to be unambiguous.
- Owner. The role responsible for this SOP being followed and updated. Not a person — a role.
- Last reviewed. Date the SOP was last verified. Review every 12 months at minimum.
- Notes / variations. Edge cases, exceptions, links to related SOPs.
That’s the whole template. Once you’ve built one in this format, the rest follow easily.
The traps to avoid
A few patterns that wreck SOP libraries:
- Overengineering the format. A 14-page SOP for a 6-step process. Nobody reads it. Keep it the length the work demands and no longer.
- Building in a vacuum. SOPs written by the owner alone, without input from the people who actually do the work, miss the real workflow and produce documents the team doesn’t trust. Involve the staff who execute the process — they know things you don’t.
- Writing once and never updating. SOPs go stale. Software changes, vendors change, regulations change. A library that hasn’t been reviewed in three years is a liability, not an asset. Calendar a review cycle.
- Storing them where nobody can find them. SOPs in a Word file on the owner’s desktop are not SOPs. They have to live in a centralized, searchable system the whole team can access — Google Drive, Notion, a shared SharePoint, whatever fits your stack. Where doesn’t matter much. Findable does.
- Treating them as bureaucracy instead of infrastructure. SOPs are not about creating rules to enforce. They’re about removing friction so the work can happen consistently. If your team experiences the SOP library as a control mechanism, the culture is wrong, not the SOPs.
Why this is now a one-weekend project
Five years ago, building a comprehensive SOP library was the kind of thing that took six months of consultant time and $30,000. In 2026, with the AI tools widely available and the workflow above, a focused practice owner can build the foundational library in a weekend or two — covering the 15 to 25 processes that account for 80% of operational repetition.
That’s not exaggeration. We’ve watched physicians do it. The bottleneck isn’t time or budget anymore — it’s the willingness to sit down and actually start.
If you’ve been telling yourself you’ll get to SOPs next quarter, stop. Block one Saturday. Pick one process. Brain-dump it, feed it to AI, refine it, save it. You’ll have your first SOP by lunch. Pick another after lunch. By the end of the day you’ll have four. By the end of the weekend you’ll have eight or ten. You’ll be further along than 90% of practice owners, and you’ll have changed the trajectory of the next two years of your business.
The bones get built one process at a time. The work doesn’t get easier than this.
Maverick Medical Ventures helps physicians design and build practices outside the insurance system — across the four pillars of medicine, marketing, finance, and operations. [Learn more]
