How to Document a Dental Practice SOP in 20 Minutes

Most dental practices know what their workflows are. The people who do the work can describe them accurately when asked. The barrier to documentation is not knowledge. It is that writing a process down from scratch feels like a different kind of work, more formal and more time-consuming than the task itself.

The result is a practice that runs on tribal knowledge. When the person who knows the workflow is absent or leaves, the knowledge goes with them. When a VA is hired, there is nothing to hand them.

The talk-it-through method removes the writing barrier by converting what you already know into a document without requiring you to switch into formal writing mode.

The Talk-It-Through Method

1. Open a screen recording tool that captures audio and screen simultaneously.

2. Perform the task at normal pace while narrating everything you are doing and why. Speak every step aloud. Name every decision point. Describe what you would do if something looked wrong or a common exception occurred. Do not slow down for the recording.

3. Stop the recording when the task is complete.

4. Transcribe the audio. AI transcription tools produce a working transcript in minutes. The transcript does not need to be clean; it needs to be complete.

5. Fill the SOP template from the transcript. The transcript already contains every step and decision. The template work is organizing and clarifying, not creating. Move each narrated step into the corresponding field and add context that was implicit in what you said but would need to be explicit for someone new.

The barrier is writing, not knowing. This method converts expertise that already exists in the person’s hands into a document without requiring them to switch into formal writing mode. A team member who cannot write a process from scratch can almost always narrate one fluently, because narrating matches how they already think about the task.

The same method works for a VA documenting their own learned process. After executing a workflow consistently, the VA records and narrates their performance and submits the transcript for review. The office manager’s review both improves the SOP and confirms the VA’s process is correct. Documentation and quality check happen in the same step.

The Four Mandatory Fields

An SOP can include many fields: workflow name, purpose, trigger, steps, decision rules, exceptions, systems and access. Four are mandatory in a way the others are not. An SOP missing any of these four is incomplete regardless of how detailed the steps are.

Escalation criteria. What triggers an escalation? Who does the person go to, and how quickly? Without this field, an SOP creates one of two failure modes: constant questions routed to the owner because the VA has no guidance on when to decide independently, or incorrect independent decisions because there is no signal defining the boundary of their authority.

An SOP without escalation criteria is a common cause of VA engagements that produce more owner involvement after hiring, not less. The escalation criteria field does not need to be exhaustive. It needs to define the threshold clearly: if X happens, stop and contact the owner; if Y happens, contact the billing manager; if the situation does not match any step in this document, do not proceed without authorization.

Definition of done. What does “finished” look like? What has been updated, confirmed, logged, or sent? Without this field, the same workflow can be considered done at different stages by different people. One person considers a claim submitted when it has been entered. Another considers it done when the confirmation number is recorded and the charge is posted. Both are executing the same SOP. Only one is finishing correctly.

Owner. The owner is the named individual responsible for this SOP being accurate and current. Without a named owner, no one notices when the document becomes outdated. One SOP, one owner. The owner does not need to perform the workflow; they need to be accountable for the document being correct.

Review date. SOPs decay as systems change, payer rules shift, and workflows evolve. A review date converts a document that gradually becomes misleading into one that stays accurate because someone is scheduled to check it.

An SOP without a review date will eventually be wrong. A wrong SOP is not neutral. It is worse than absent, because it gives the person performing the task false confidence that their incorrect method is correct. The review itself takes 15 minutes if the SOP was written clearly: compare the current process to what the document says, update any changed steps, and reset the review date. The six-month review cycle is the minimum for any active workflow; workflows tied to payer rules or technology platforms should be reviewed quarterly.

The Length Constraint

Keep every SOP to one or two pages. Long SOPs are not read and not maintained.

A 12-page SOP for a 20-minute task signals that the author tried to cover every exception in the main document body rather than resolving exceptions through the escalation criteria field. The escalation criteria field exists precisely so the main body can stay short. When every exception lives in the body, the document is both too long to read and too brittle to maintain.

If the workflow genuinely cannot fit in two pages, examine whether it is one workflow or two distinct workflows written as one. Splitting them usually produces two cleaner, more maintainable documents.

Starting From a Draft, Not a Blank Page

The most useful thing a documentation system can do for a practice that has never documented anything is to provide the most common administrative SOPs in draft form. A practice starting from a blank page faces a writing task. A practice starting from a draft faces a review-and-correct task. The second is faster and produces better results because it prompts the reviewer to notice specific discrepancies rather than generate from memory.

The 15 highest-value starting points for a general dental practice, in roughly the order they should be documented:

Benefits verification; claim submission; claim status follow-up; denial categorization; morning huddle preparation; recall outreach; lapsed patient reactivation; unscheduled treatment follow-up; new patient intake; appointment confirmation; cancellation and same-day gap fill; end-of-day financial reconciliation; payment plan setup; referral management; new patient call handling.

These represent the workflows where documentation produces the most immediate operational improvement, where undocumented variation causes the most measurable downstream problems, and where a VA is most likely to be assigned work in the first 90 days of an engagement. Benefits verification leads the list because undocumented benefits verification is the most common source of claim errors in practices of any size. New patient call handling closes it because the stakes of that interaction are high and the variance in execution without documentation is wide.

Cross-reference: The AI-assisted SOP generation guide, available separately, covers using AI transcription and drafting tools to accelerate this process further. The talk-it-through method works without AI; AI accelerates the transcription and initial structuring step for practices that want to move faster.