The Ten SOPs a Small Therapy Practice Actually Needs

Ask the owner of a three-person therapy practice how insurance verification works and you will get a confident, complete answer. Ask the person covering the front desk during the owner’s first real vacation in two years and you will get a different answer — or a phone call to the beach. That gap has a name: the procedure lives in someone’s head instead of on a page. It costs nothing on an ordinary Tuesday, and then it costs a missed authorization, a mishandled records request, or a week of unsubmitted claims the moment the one person who knows is sick, on leave, or gone.

The standard prescription is an operations manual, and it is a bad one. Owners buy a template, spend a painful weekend filling in forty pages, and produce a binder that describes an idealized practice nobody works at. It is opened twice: once to admire, once during the emergency it turns out not to cover. What a small practice actually needs is smaller and harder: roughly ten standard operating procedures, each one page, each owned by a role, each stored where the task happens. This article names the ten, gives the one-page format, and lays out a writing plan that takes one week per SOP instead of one lost weekend for the binder.

Start with the distinction the binder blurs. A policy states a rule: cancellations inside twenty-four hours incur a fee; records are released only with a valid authorization. An SOP states how this practice executes a recurring task: what starts it, who does it, the steps in order, when to stop and ask, and what finished looks like. Policies answer “what do we allow?” and change rarely. SOPs answer “what do I do right now?” and change whenever the workflow does. Binding them into one long document guarantees that neither is findable at the moment it is needed.

The moment of need is the whole design problem. Nobody reads procedures at their desk with coffee; they read them mid-task, often while a phone is ringing, and usually because the person who normally does the task is not there. That reader gives the page thirty seconds to prove it will help. A one-page SOP survives that test because reading it fits inside doing it. A ten-page procedure does not — the reader abandons it, calls the owner, or improvises, and each improvisation quietly becomes the new undocumented procedure.

One page is also an editorial forcing function for the writer. It leaves no room to document what the screen already shows, so every surviving line has to carry a decision: the step order that is not obvious, the rule for the fork in the road, the name of the person to interrupt when the case does not fit. If a task genuinely cannot fit on a page, that is almost always a sign it is two tasks — split the SOP, not the margin.

These ten cover the recurring administrative work of nearly any outpatient therapy practice — speech, occupational, or physical, solo or small group. They are ordered roughly by how often their absence causes damage, which is also a sensible writing order. Treat each line as the working scope of one one-page SOP: if your draft covers less, it will not carry a handoff; if it covers much more, it is probably two SOPs.

Notice what is deliberately not on the list. Clinical decision-making is not an SOP — evaluation and treatment run on clinical judgment and documentation standards, and a procedure page cannot substitute for either. The practice’s written HIPAA privacy and security policies are not on the list either, for the opposite reason: they are required formal documents, not optional operational aids, and they answer to regulatory requirements rather than to the one-page rule. And a task that does not recur does not need an SOP at all — write those down once as a decision log entry and move on.

Every SOP in the library uses the same skeleton, because a reader under pressure should never have to learn a new layout. Six fields: a header with version and owner, a purpose, a trigger, the steps, an escalation rule, and a definition of done. The escalation line and the definition of done are the two most often skipped and the two that matter most — the first tells a first-timer where their authority ends, and the second tells them when they are allowed to stop.

Two writing rules keep the skeleton honest. Steps start with verbs and name the actual system — “open the eligibility portal,” not “verify benefits.” And nothing goes on the page that the screen already says: an SOP that repeats every field label of the EHR form is documentation theater, and it goes stale the first time the vendor ships a redesign.

“

“An SOP is not a description of how work should happen. It is the shortest set of words that lets the work happen without you.”

The binder fails partly because it is written in one heroic sitting, from memory, far from the work it describes. The alternative is a ten-week cadence: one SOP per week, each written while the task is actually being done. Ten weeks sounds slow until you compare it with the usual outcome of the weekend approach, which is zero usable SOPs and a bad mood.

1. 01

   Pick by pain, not by list order

   Start with the task that most recently went wrong in someone’s absence, or the one only a single person can do. Urgency recruits the team to the project far better than an announcement about operational excellence.

2. 02

   Narrate a real occurrence

   The next time the task happens, the person who does it writes down what they actually do, step by step, as they do it — real screens, real field names, real decisions. Reconstruction from memory produces the idealized version; narration produces the true one, including the workaround everybody forgot was a workaround.

3. 03

   Cut the narration to one page

   The owner or a second reader edits: strip anything the screen already says, keep every decision rule, and make the escalation line and the definition of done explicit. This is where “verify benefits” becomes the six questions actually asked and the field where each answer is recorded.

4. 04

   Test it with a handoff

   The real test is not review, it is use: someone who has never done the task follows the page end to end while the usual owner watches in silence. Every question the tester asks marks a missing line; every hesitation marks an unclear one. Edit and, if the changes were substantial, test once more.

5. 05

   Store it where the work happens

   The finished page lives at the point of use — linked from the desk the task is done at, pinned in the system it starts in — not in a binder or a deep folder. A perfect SOP nobody can find during the actual emergency rounds to zero.

An SOP that no longer matches reality is worse than none, because it trains the team to ignore the whole library. The maintenance rule that works for a small practice is event-driven, not calendar-driven: the version number and date in the header change whenever the workflow does — a new payer joins, the EHR ships a redesign, a rejection pattern forces a new pre-submission check. The person who changes the workflow changes the page, in the same week. A calendar-only annual review, by contrast, mostly certifies pages nobody has compared with reality since the last annual review.

One part of the paperwork does run on formal rules, and it is worth stating plainly because it is where operational habit meets legal obligation. HIPAA requires covered entities to maintain written privacy and security policies and procedures, to train workforce members on them, to review and update security documentation periodically, and to retain these documents for six years from the later of their creation date or the last date they were in effect. Those requirements attach to the compliance policy set, not to your cancellation-call SOP — but a practice that has built the one-page habit usually finds the formal set far less painful to maintain, because “the document matches what we actually do” has become the house standard.