The Dental VA Job Description Is a Scope of Work

A dental VA job description should read like a scope of work, not a job ad. Its audience is the practice as much as the candidate: writing it forces the clarity that makes the engagement work.

This distinction matters in practice. A job ad is written to attract; a scope of work is written to align. Most dental VA job descriptions are written as job ads, which means the practice finishes the posting without having done the alignment work. The scope of work format reverses this: the practice writes the document and, in doing so, discovers whether the role is actually ready to hire for. If the nine sections below cannot be completed, the role definition is not finished.

The thirteen sections

Section 1: Role purpose

One sentence, outcome-oriented. The sentence names the result, not the activity.

• Weak: “Handle insurance tasks.”
• Strong: “Reduce AR over 90 days and increase clean claim rate by owning verification, claim follow-up, and denial management.”

If the role purpose cannot be stated in one outcome-oriented sentence, the scope is not clear enough to hire for. The exercise of writing this sentence is the practice’s first diagnostic: if it requires qualifiers, exceptions, or multiple rewrites, the problem definition needs more work before a candidate is ever contacted.

Section 2: Owned workflows

Specific, referenced to named workflows. Not “handle insurance” but “W29 verification (all appointments, 48 hours or more ahead), W32 claim submission (daily), W33 status follow-up (15/30/45-day intervals), W35 denial categorization and appeal preparation.”

The specificity here is what prevents scope confusion. A VA who knows they own W29 and W32 also knows they do not own everything else. The list of named workflows becomes the foundation of the next section.

Section 3: Not in scope

The most important and most often omitted section. Scope creep is the leading cause of quiet failure, and it is prevented in writing or not at all.

For an insurance VA, the not-in-scope list includes: final CDT code selection, write-off approval, patient clinical questions, treatment plan discussion, schedule changes, and payment plan authorization. Each of these is something that might plausibly come to a VA’s attention during insurance work. Writing them as explicit exclusions removes the ambiguity before it becomes a problem.

The test for whether an exclusion belongs on the list: if a staff member might reasonably ask the VA to handle it, and the answer should be no, it goes on the list.

Section 4: Success metrics

Two to three, with baseline and target. Not “improve efficiency” but “AR over 90 days from [current percentage] to under [target percentage] within 120 days; verification completion at 48 hours or more ahead from [current percentage] to 95% within 60 days.”

Without a baseline, nothing can be evaluated. Without a target, nothing can be achieved. Writing this section forces the practice to pull current numbers before posting the role, which also satisfies the prerequisite of recording a baseline before the engagement starts.

Section 5: Required experience

Dental-specific and honestly stated. For an insurance VA: “2 or more years of dental insurance experience, CDT code familiarity, experience with [PMS name], payer portal experience, and appeal writing.”

PMS specificity matters here. “PMS experience” is not equivalent to “[Dentrix/Eaglesoft/Curve] experience.” A candidate who knows one system may need significant ramp time to become productive in another. Name the system; screen for it explicitly.

Section 6: Tools

Named systems with specificity: PMS name, clearinghouse name, phone system, documentation platform. This tells candidates what access they need to demonstrate proficiency in, and it tells the practice what needs to be provisioned before day one.

Section 7: Schedule

Hours and time zone overlap requirement. “30 hours per week, minimum 4 hours overlapping practice hours for escalation.”

Without a time zone overlap specification, the escalation path does not work in real time. A VA who is asynchronous with the practice’s operating hours can handle back-office work effectively. But if escalation requires a real-time response, the overlap requirement must be written before the role is posted, not negotiated after a candidate is selected.

Section 8: Escalation

Who they go to, for what. “Office manager for process questions; Dr. [X] for anything clinical; no independent patient clinical communication.”

The escalation matrix must be explicit before the VA starts. Without it, every question routes to the owner by default, reproducing the original problem the VA was hired to solve.

Section 9: First 30 days

What will be learned versus produced. For an insurance VA: “Weeks 1 to 2, learn payer mix, fee schedules, and document current state. Weeks 3 to 4, take over verification fully and begin claim follow-up. Deliverable: a documented verification SOP and a plan library covering the top 10 payers.”

This section prevents the common experience of the first month as an undirected orientation period. When the first 30 days have a written deliverable, the VA and the practice share a definition of a successful ramp. Both parties know what week four looks like before week one starts.

Section 10: Communication and language

Name the reporting person and backup. Set one channel for routine communication, another for urgent issues, and a response-time expectation for escalations.

For phone roles, state the spoken-language requirement and test it in a live call. If the patient population regularly prefers another language, define whether the role needs conversational or professional fluency.

Section 11: Access and security

List each system, permission level, access method, and the person who provisions it. Use named individual accounts, multi-factor authentication, and minimum-necessary access. Confirm the managed device, private workspace, patient-data handling rules, and offboarding plan before the start date.

Section 12: Decision rights

Write three lists: what the VA can decide alone, what they can recommend but the practice must approve, and what always stays with the practice.

This prevents the VA from escalating every routine choice or making decisions involving clinical care, fees, write-offs, or policy exceptions without authority.

Section 13: Ramp and review points

Separate learning from expected output. State what should be true after two weeks, four weeks, and the full ramp period. Set a 30-day scope review and a 90-day decision-rights review.

Worked example: Insurance Support VA

Role purpose: Reduce AR over 90 days and increase clean claim rate by owning verification, claim follow-up, and denial management.

Owned workflows: W29 verification (all appointments, 48 hours or more ahead); W32 claim submission (daily); W33 status follow-up (15/30/45-day intervals); W35 denial categorization and appeal preparation; weekly AR report.

Not in scope: final CDT code selection; write-off approval; patient clinical questions; treatment plan discussion; schedule changes; payment plan authorization.

Success metrics: AR over 90 days from 22% to under 12% within 120 days; verification completion 48 hours or more ahead from 40% to 95% within 60 days; clean claim rate at 95% or above.

Required experience: 2 or more years of dental insurance; CDT familiarity; [PMS name]; payer portal experience; appeal writing.

Tools: [PMS]; [clearinghouse]; payer portals; [phone system]; [documentation platform].

Schedule: 30 hours per week, minimum 4 hours overlapping practice hours for escalation.

Escalation: Office manager for process questions; Dr. [X] for anything clinical; no independent patient clinical communication.

First 30 days: Weeks 1 to 2, learn payer mix, fee schedules, and document current state. Weeks 3 to 4, take over verification fully and begin claim follow-up. Deliverable: a documented verification SOP and a plan library covering the top 10 payers.

Why this works: the role purpose names the outcome, not the activities. The owned workflows are specific enough that a candidate can confirm they have done exactly this work before. The not-in-scope section removes the ambiguity that generates scope creep. The metrics have baselines, which means the engagement can be evaluated. The first 30 days section gives both parties a shared definition of success before the engagement starts.

Worked example: Scheduling VA (condensed)

Purpose: Reduce open chair time and increase hygiene reappointment rate.

Owns: W12 confirmations (including live escalation); W05 ASAP list; W04 cancellation recovery; W17 recall outreach; W06 forward gap review.

Not in scope: schedule design or block rules; emergency clinical triage; fee or treatment discussions; policy exceptions beyond defined thresholds.

Metrics: open chair time under 5%; same-day cancellation recovery above 40%; recall reappointment rate plus 15 points.

First 30 days: weeks 1 to 2, shadow and document; week 3, take confirmations; week 4, take the ASAP list.

Three exclusions in the scheduling VA’s not-in-scope section deserve specific attention. Emergency clinical triage is excluded because it requires clinical judgment about symptom severity, which is a clinical boundary rather than an administrative one. Schedule design and block rules are excluded because these are strategic decisions about how the practice allocates chair time, not execution of the schedule against existing rules. Fee and treatment discussions are excluded because they cross into clinical and financial authority that belongs to the practice, not to an administrative contractor.

Common job description failures

Six failure modes appear consistently in dental VA job descriptions that do not work:

“Other duties as assigned” produces scope collapse. Remove this phrase entirely from every dental VA job description. It is written permission for scope to expand to fill all available demand. No managed scope can survive this phrase.

No exclusions listed means everything becomes their job. The not-in-scope section is not optional; it is the mechanism that enforces scope discipline after hiring.

Vague metrics like “improve efficiency” make evaluation impossible. Nothing can be measured against a standard that has no number. When the engagement is difficult to evaluate, it is evaluated on feel, which is almost always unfavorable during a stressful month.

An unstated PMS produces the wrong candidate skill match. The candidate who knows Dentrix is not the same candidate as the one who knows Curve. Name the specific system and screen for it.

No time zone overlap defined makes real-time escalation impossible. If the VA’s working hours do not overlap with the practice’s operating hours, the escalation matrix written in section 8 becomes fictional.

See Also

• The Six Prerequisites Before Hiring a Dental VA, the six prerequisites that should be completed before writing the job description
• The Dental VA Interview Framework, the five-stage interview process to evaluate candidates against the written scope
• The Dental VA Role Library, the seven role definitions with owned workflows, metrics, and ramp expectations

No named escalation contact means every question routes to the owner. This reproduces the original problem and puts the practice owner back in the communication loop for every question, which is precisely what the engagement was supposed to change.