How to write a medical office procedure manual people actually use
Every practice has a binder. The procedure people actually follow is in someone's head, and it leaves when they do.
Most practices have a procedure binder, and almost nobody follows it. The real procedure, the one that decides how a new patient gets booked or how a referral gets chased, lived with the senior medical assistant or the front-desk lead. On the day they were out, the practice ran differently. On the day they resigned, it ran differently for good.
That is not a rare event. In MGMA's 2025 poll of practice leaders, medical assistants and front-office staff were the turnover hotspots, and practices responded by extending orientation and training periods and improving onboarding (MGMA Stat). Onboarding is also where most organizations fall short: in Gallup's research, only 12% of employees strongly agree their organization does a great job of it (Gallup).
Why the binder goes stale
Procedures get written once, usually during a quiet week or after a mistake, and then the work changes and the document doesn't. Within a year the binder describes a practice that no longer exists, so new staff learn by shadowing, which means they learn whatever the person they shadow happens to do.
Who writes the procedure
The person who does the work should explain it, and someone else should write it down. That split matters. The people who know the procedure best are the busiest people in the practice, and a template handed to them on a Friday afternoon comes back as three bullet points.
So skip the template. Ask the person who does the work to explain it out loud, ideally while they do it, and record it. People explain far more than they would ever write down: the exception for a certain kind of patient, the reason one step happens before another, the check they do that isn't in any manual.
Then turn the recording into steps, with an owner for each step. Have the person who explained it read the draft. They'll catch what's missing in five minutes.
A medical office procedure template: new-patient insurance verification
Here is what one finished procedure looks like. Copy the shape, not the content: your payers, timings and owners will differ.
Verify insurance for a new-patient visit Owner: practice manager. Version 3. Last reviewed September 2026.
- When the appointment is booked (front desk). Take the payer, member ID, and the subscriber's name and date of birth. Ask the patient to bring the card, front and back.
- Two business days before the visit (billing coordinator). Check eligibility on the payer's portal or by phone. Note the copay, the deductible remaining, and whether a referral or prior authorization is needed.
- If coverage is inactive or a referral is missing (billing coordinator). Call the patient that day. If it can't be fixed before the visit, offer a new time.
- On the day (front desk). Ask whether anything has changed, scan the card, and collect the copay.
Changelog. Version 3 (September 2026): moved the eligibility check from one day to two business days before the visit, because same-day referral problems kept forcing reschedules. Approved by the practice manager.
That changelog line is the part most manuals skip, and it's the part that makes the rest trustworthy.
Version it, and change it on purpose
A procedure is only useful if people trust that it's current. Give every procedure a version, a last-reviewed date and a short changelog. When the process changes, change the document the same week, and say why. Review the rest at least once a year, even when nothing seems to have changed.
That turns the binder from a museum into a record of how the practice decided to work.
A 90-day plan for a new front-desk hire
The other place procedures pay off is onboarding. A written plan tells a new hire what to learn in what order and who to ask, and it tells you at day 30 whether it's working. Give each stage a milestone they can actually pass, not just a list of things to watch.
Before day one
- Logins ready, a desk, and the written procedures they'll use in their first week.
- One named person to ask, who isn't the busiest person at the desk.
Days 1 to 30
- Checks patients in and answers routine calls on their own.
- Verifies insurance from the written procedure, with a second check.
- Milestone: ten verifications in a row with no corrections.
Days 31 to 60
- Books every visit type, including the awkward ones.
- Handles a reschedule and a billing question without help.
- Milestone: covers the desk alone for a full morning.
Days 61 to 90
- Owns one procedure end to end.
- Suggests one change to it, with the reason.
- Milestone: their change goes into the manual as a new version.
Where Ted's name comes from
Years ago I was part of scaling Flux7, a fast-growing tech services startup. A colleague there named Ted started weekly sessions where the people running projects, sales and product mapped who had bandwidth, who knew what, and who was ready for more. Those conversations became a living map of what the company knew and who knew it, and that clarity became a competitive advantage. TalentOS's operations worker is named for that work: get what the practice knows out of people's heads and into something everyone can see, and keep it current.
How we handle it
AI works best with a human in the loop. Ted can turn a recorded walkthrough into clean, numbered steps in minutes, but only the person who does the work can confirm the steps are right, and only the practice manager should approve a new version.
This is the job Ted does in TalentOS. He records a walkthrough meeting in Chrome or Edge, or works from a transcript, notes or an old document, and turns it into a step-by-step procedure. When the process changes, you tell him what changed: he drafts the update with a changelog, and you approve it as a new version.
He writes onboarding plans for new hires, from before day one through the first 90 days, and turns a plan or a procedure into a checklist board your team works through and ticks off. He sends the finished document to Notion, Google Drive, Slack or email when you want it there. Nothing is published without your review. Ted is one worker at $500 a month.
Where to start
Pick the one procedure that would hurt most if the person who knows it left tomorrow. Record them explaining it this week.
See how Ted fits a medical practice, what each worker does, and what it costs.
Frequently asked questions
- What should be in an office procedures manual?
- One procedure for each task that would go wrong if the usual person were out: booking each visit type, verifying insurance, handling a reschedule, closing the day. Each needs numbered steps, an owner for each step, a version and a short changelog.
- Who should write the procedures?
- The person who does the work should explain it, and someone else should write it down. Doers rarely have time to write, and writers who don't do the work miss the exceptions. Name one owner per procedure who approves each new version.
- How do you get a procedure out of the person who does it?
- Record them explaining it out loud, ideally while they do it, then turn the recording into steps. Have them read the draft. They will catch what's missing in five minutes.
- How often should procedures be reviewed and updated?
- Whenever the process changes, the same week it changes, and at least once a year otherwise. A procedure with a named owner and a last-reviewed date gets reviewed. One without either doesn't.
- What is the difference between a policy and a procedure?
- A policy says what the practice does and why, such as verifying insurance before every new-patient visit. A procedure says how: the steps, in order, and who does each one.
- How do you train a new medical receptionist without just shadowing?
- Give them the written procedures for their first week before day one, then a 90-day plan with milestones they can pass, such as ten insurance verifications in a row with no corrections. Shadowing still helps, but as practice against the written version, not as the only source.
- What do you do when the one person who knows is out?
- This week, before it happens again, record them explaining the procedure that would hurt most without them. Then turn that recording into a written procedure the rest of the team can follow.