The Dental VA Readiness Assessment

The commercial temptation is to design an assessment that always says yes. Resist it.

An assessment that reliably identifies unready practices, tells them so, and gives them a path is worth more as a trust asset than as a lead filter. It also protects against the failure cases that generate negative word of mouth in a profession that talks to itself constantly. A framework that can only produce the answer “proceed” is a framework that serves the vendor rather than the practice.

This one is built to produce all four honest outputs, including the ones that cost a sale.

The Five Readiness Dimensions

VA engagements that fail tend to fail in predictable ways. The five dimensions below are a preventive inversion of the observed failure list: each one maps directly to a failure mode that shows up repeatedly when practices launch before they are ready.

Dimension 1: Process Readiness (Highest Weight)

The question here is whether documented, transferable process exists for the function being delegated.

A practice that cannot describe how a workflow runs cannot hand it off. The VA will either invent a process (producing outputs that do not match how the practice actually wants things done), ask constant questions (consuming in-house time that the engagement was supposed to free up), or produce work that gets silently redone by whoever held the knowledge in their head. None of these outcomes produce value. All of them produce the conclusion that VA arrangements do not work.

The scoring scale:

• Score 0: Nothing documented; knowledge is tribal
• Score 1: A few checklists; mostly in people’s heads
• Score 2: Core workflows documented but stale or unused
• Score 3: Current, used SOPs for the target workflow

Threshold: Score 1 or above to proceed with a scoped execution role. Score 0 does not mean stop entirely. It means the first engagement must be SOP authoring itself, with documentation as the measured deliverable. This reframe converts the most common disqualifier into a legitimate first project: hire for documentation, not execution, and let the documentation become the prerequisite for what comes next. The engagement transitions from authoring to execution as the SOPs are completed and validated.

Dimension 2: Owner Readiness (High Weight)

The question here is whether the owner will actually delegate, which is distinct from whether they say they will.

Most owners believe they are ready to delegate. Most owners have not tested that belief against a real situation. The way to find out before the engagement starts is to ask four specific questions:

1. Name three things you did last week that someone else could have done. If you cannot name them, your capacity to identify delegation opportunities in practice is low.
2. When you delegated something recently, what happened? If the answer is “I ended up taking it back,” the pattern is already established and will repeat.
3. Who would this person report to? No answer here means no accountability structure, and accountability structures do not create themselves.
4. What would you do with the time this frees up? This last question is the most predictive and the least asked. An owner with no plan for the recovered time will refill it with low-value work and conclude the engagement produced nothing. The delegation succeeded technically; the practice did not improve. The recovered time was never invested, because there was no stated purpose for it.

If the recovered time has no destination, the engagement will not create value even when it succeeds.

The practice also needs a named onboarding owner with protected time in week one. “Nobody” is a stop signal. A strong candidate cannot compensate for missing access, unanswered questions, and absent feedback during the first days of the engagement.

Dimension 3: Technical Readiness (Hard Gate)

The question here is whether the work can physically be done remotely.

This is the one dimension that blocks regardless of how well every other dimension scores. Technical requirements are not culturally solvable. You cannot decide your way around a phone system that does not support remote extensions.

The checklist:

• Cloud-based practice management software, or secure remote access infrastructure confirmed and tested
• Role-based permissions with unique logins (not shared accounts across staff)
• Phone system that supports remote extensions with appropriate features
• Communication platform accessible remotely
• Document sharing method confirmed for the VA
• Payer portal access model established and verified
• Business Associate Agreement capability confirmed; BAA signed before any patient records are handled
• Managed device, private workspace, and minimum-necessary permission plan confirmed
• Same-day access revocation process written before the VA starts

Each of these requires verification per platform and vendor. There is no universal answer, and “it should work” is not the same as “it works.”

Threshold: A score of zero here is genuinely blocking regardless of all other scores. However, technical remediation is usually a solvable IT project rather than a cultural one. That makes it the easiest of the five blockers to clear, and the one most worth clearing first when it is the single disqualifier.

Dimension 4: Volume Readiness

The question here is whether there is enough work in one coherent function to justify dedicated capacity.

A very small practice may not have sufficient volume in any single function to support a dedicated VA for that function. The honest threshold is roughly 10 hours per week of real work in a coherent domain. Below that, part-time or shared arrangements are more appropriate, and the right answer is to say so rather than to push a full engagement that will underdeliver.

Estimation is straightforward for each function:

• Verification: Multiply appointments per week by average verification time per appointment
• Claims and AR: Estimate from weekly claim volume plus aged claim count and current resolution time
• Recall: Multiply due patients per month by the number of touches each patient requires
• Phone overflow: Multiply missed calls per week by average handling time per call

If the math does not produce 10 hours per week in the target function, the practice has two options: expand the scope to include a second related function, or start part-time. Both are legitimate. What is not legitimate is launching a full engagement into 6 hours of weekly work and then diagnosing the underperformance as a VA problem.

Dimension 5: Team Readiness

The question here is whether the existing team will cooperate.

Team resistance is the most under-diagnosed failure cause in VA engagements and, simultaneously, the most fixable one. It costs one conversation and is almost never had before the start date.

The risk signals to look for:

• A long-tenured staff member who controls the function being delegated and has not been consulted about the change
• Prior failed change initiatives that produced cynicism about new arrangements
• Staff members who were not told the plan before the VA was hired
• Unresolved performance issues in the same function where the VA will work

The most common form of team resistance is not overt. It is quiet: information withheld, access not fully provided, context not explained, questions not answered promptly. The VA reports that they “cannot get what they need.” The practice concludes the VA is not working out.

The fix is one conversation, early, that covers four things: here is what we are trying to accomplish, here is what changes about your role, here is what does not change, and here is how you can tell me directly if something is not working. That conversation changes the dynamic. It is almost never had.

The Scoring Model

Apply scores from 0 to 3 in each dimension, then apply weights:

Dimension	Weight	Your Score	Weighted Score
Process	x3
Owner	x3
Technical	x2 (hard gate)
Volume	x2
Team	x2
Total			/36

Scoring bands:

Total Score	Interpretation	Recommended Action
28 to 36	Ready	Proceed with a scoped role; first 30-day scope defined
20 to 27	Conditionally ready	Fix the lowest-scoring dimension first, then start narrow
12 to 19	Not yet ready	Documentation and owner-preparation project first
Below 12	Not ready	Operational foundations before any delegation
Technical = 0	Blocked	IT remediation required regardless of other scores

The Four Honest Outputs

The assessment must be capable of producing all four of the following outputs, including the two that do not result in an immediate engagement. An assessment that can only produce outputs 1 and 2 is an assessment that serves the vendor rather than the practice.

Output 1: “You are ready, start here.” This output includes a specific role recommendation and a defined first 30-day scope. The practice has scored above 28, cleared the technical gate, and has a plausible delegation plan. Proceed.

Output 2: “You are nearly ready, fix this one thing first.” One dimension is scoring low enough to create predictable risk. The path forward is a defined prerequisite: document the target workflow, establish the reporting structure, prepare the team, or clear the technical blocker. Then return.

Output 3: “You are not ready, and here is the 60-day path.” Multiple dimensions are weak. The 60-day path is usually documentation-first: engage for SOP authoring, build the foundational process, then reassess. This output is not a rejection. It is a sequenced plan.

Output 4: “A VA is not your answer.” The underlying problem is demand, clinical capacity, cost structure, or an unresolved personnel issue that delegation will not solve. Naming this output clearly is the credibility test of the entire framework.

The Paired Assessment Insight

The single most diagnostic improvement available to this framework is also the least used: having both the owner and the office manager complete the assessment independently, then comparing their scores before discussing results.

Divergence between the two assessments, particularly on owner readiness and team readiness, is likely more diagnostic than either score alone. The dimensions where they disagree most are the dimensions where the stated plan and the actual situation are farthest apart. An owner who scores their own readiness at 3 and whose office manager scores it at 1 has identified, without prompting, the central risk in the engagement.

No competing approach is doing this. It costs nothing to implement and produces a materially more honest starting picture.

Reassessment

Readiness is not static. A practice that was not ready in January may be ready in April. A practice that was ready when it hired may not be ready after a staff departure, a PMS migration, or a failed first engagement.

Reassess at 90 days from the start of any engagement, and after any of the following: a staff departure in the relevant function, a practice management software change, a location addition, an associate hire, or a failed VA engagement.

See Also

• Should My Dental Practice Hire a VA?, the five-gate decision framework that uses readiness as one of its inputs
• Which Dental VA Role Do I Need?, role selection, applied after readiness has been confirmed
• The Owner-Manager Readiness Gap, the paired assessment (why divergence between owner and manager answers is the most diagnostic signal)
• Why Dental VA Engagements Fail, the ten failure modes, most of which are readiness failures in disguise

The five dimensions that determined readiness at the start continue to determine success throughout. The assessment is not a one-time gate. It is a repeating check on whether the conditions that make delegation work are still in place.