How to Build an Operating Manual Your Clinicians Actually Use

By Emelie Douglas, LPC, MBA · Founder, Sprout Your Practice

An operating manual is your practice's how-to: step-by-step processes for the work that happens every week. It isn't your employee handbook, which covers HR and compliance, and it isn't your policy set, which holds the rules. Keep the three separate. Have the manual link to policies instead of repeating them, and it stays usable at any size.

At Sprout Therapy PDX we keep all three in different places, on purpose. That decision has saved us more confusion than almost any other systems choice we've made. This post is about the operating manual. I'll come back to the employee handbook in a future post.

What's the difference between an operating manual, an employee handbook, and a policy set?

The policy set says what the rule is. The handbook covers the employment relationship. The operating manual says how we do the work. Each has a different job, owner, and pace of change.

•    Policy set: the rules and the reasons for them, like confidentiality, mandated reporting, documentation standards, and risk. Leadership approves them, they often get legal review, and they change rarely and deliberately.

•    Employee handbook: the employment relationship, like pay, leave, conduct, and HR compliance. Whoever’s responsible for HR owns it, and it changes when employment law or benefits change.

•    Operating manual: the processes, like how to complete an intake, transfer a client, file a report, or close a chart. Operations owns it, and it changes whenever your tools or workflow change.

Mandated reporting is a good example. The policy defines the obligation and your practice's expectations. The operating manual gives the steps: what to do first, where to document, who to notify. The first line of that process page links to the policy. The policy isn't pasted in.

Why keep them separate?

Because they change at different speeds, and mixing them breaks one or the other. When processes live inside policies, a software switch turns into a policy revision. When policies live inside processes, rules get quietly edited along with a workflow tweak.

•    One source of truth. A policy pasted into three documents becomes three versions within a year. Linking keeps a single version.

•    Usability at any size. A small practice's manual may be a few pages. Ours, at 40+ clinicians, is not short, and that's fine. What matters is that each page does one job and is easy to find. Copying policies in adds bulk without adding clarity.

•    Audit readiness. When a payer, a board, or an OHA Certificate of Approval reviewer asks for your policies, you hand over a clean policy set. The COA review specifically includes policy and procedure review.

•    Clear ownership. Each document has one owner and one approval path.

What belongs in an operating manual?

The recurring processes someone needs to do correctly without having to ask. If a task happens more than a few times a year and getting it wrong affects clients, billing, or compliance, it gets a page.

•    Client lifecycle: intake and scheduling, first-session paperwork, transfers, discharge, and closing a chart.

•    Documentation workflow: where notes go, supervisor sign-off, and late-note follow-up. Link to the documentation policy for the standards themselves.

•    Risk and safety: crisis response steps, mandated reporting steps, and recording a safety plan, each linked to its policy.

•    Billing touchpoints for clinicians: no-shows, superbills, and what to do when a claim bounces back. Only the clinician's part, not the whole billing operation.

•    Supervision and consultation logistics: scheduling, documentation, and what to bring.

•    Technology: EHR how-tos, telehealth setup, and secure messaging.

•    Who owns what, by role: the billing lead, the operations manager, the clinical director. Roles stay put when people change.

How do you write a process people will follow?

One task per section, numbered steps, the governing policy linked at the top, and an owner and review date at the bottom. Write it with the people who actually do the work, not for them. Encourage your staff to used CTRL-F to search the doc for the topic they’re looking for!

Here's what a section skeleton might look like. This is an illustrative example, not a substitute for your own policy:

•    Title: How to make a mandated child abuse report

•    When to use: any time you have reasonable cause to believe a child has been abused

•    Steps: (1) Address immediate safety. (2) Call the Oregon Child Abuse Hotline, 1-855-503-SAFE (7233), yourself. Consultation is welcome but doesn't replace your own report. (3) Document in the EHR using the template linked here. (4) Notify the clinical director role.

•    Governing policy: [link to your Mandated Reporting Policy]

Start each page with a sentence or two on why the process exists. Clinicians are trained to reason from purpose. Give them the purpose and they'll handle the edge cases you didn't write down.

How do you keep it from growing out of control?

Link instead of copying, retire what's stale, and give your manual an owner and a review date. Size isn't the problem. Manually go stale if they are not updated frequently.

•    When the same question comes up twice, write it to the manual. When a process goes a year without anyone using it, retire it.

•    Review it when something changes, like new software, a rule change, or an incident, and on a set annual cycle.

•    Keep it digital, searchable, and permissioned. The tool matters far less than having someone own it.

•    Track the changes in a short log so people can see what's new.

FAQ

Do I need all three documents if I'm still small?

My recommendation is to separate them from the start, even if each is just one folder. Keeping them apart early is much easier than untangling one combined document later. A small practice's manual can start as a handful of pages and grow as you do. You'll need the handbook once you have employees.

What tool should I use for an operating manual?

Anything searchable, linkable, and permission-controlled: a shared drive, an internal wiki, or the knowledge base in your practice software. We use a Google Doc. Clear ownership and review dates matter more than the platform.

About the author
Emelie Douglas is a Licensed Professional Counselor, MBA, and the founder of Sprout Your Practice. She built Sprout Therapy PDX from a solo private practice into a group of 40+ clinicians with ~90% annual retention, and served as president of the Oregon Counseling Association. She helps therapists and group practice owners grow businesses that are profitable, ethical, and sustainable — without burnout. Book a free consultation.