The VA Engagement That Was Launched Before the Practice Was Ready

The Failure Sequence

A VA engagement launches. The VA shows up with login credentials, a general description of what they will be doing, and a starting date. There are no SOPs. The practice management software access takes two weeks to provision. The VA asks a question and the answer goes through three people before it comes back four hours later. After 30 days, the practice owner concludes that the engagement is not working and ends it.

The conclusion: VA arrangements do not work for dental practices.

The actual conclusion: the engagement was launched without the prerequisites that make any delegation arrangement work. The VA did not fail. The setup failed.

This failure sequence plays out with remarkable consistency, across practices of different sizes, different staff configurations, and different functions. It is not random. The gaps are diagnosable before hiring and correctable before launching, if the practice is willing to apply the assessment honestly before setting a start date.

Prerequisite 1: Documented Process

Process readiness is the highest-weight dimension in the readiness framework, and its absence is the most common cause of early failure. A practice that cannot describe how a workflow runs cannot hand it off to anyone, whether that person works on-site or remotely.

Without documented process, the VA faces three options, all of them bad. She can invent a process, producing outputs that do not match how the practice actually wants things done. She can ask constant questions, consuming the in-house time that the engagement was supposed to free up. Or she can produce work that gets silently redone by whoever held the knowledge in their head, generating the impression that the VA’s work is not usable.

The correct response when process readiness is zero is not to delay the engagement indefinitely. It is to start the engagement with documentation as the deliverable. A VA who shadows in-house staff, asks why things are done the way they are done, and writes the answers down is creating the prerequisite rather than waiting for it. The engagement begins with SOP authoring and transitions to execution as the documentation is completed and validated by the staff who know the workflow. This reframe converts the most common disqualifier into a legitimate first project with a measurable output.

Prerequisite 2: Technical Setup Confirmed Before the Start Date

Technical readiness is the one hard gate in the readiness framework: it blocks engagement regardless of how well everything else is positioned. Remote access to the practice management software, role-based unique-login permissions rather than shared accounts, a phone system that supports remote extensions, and a signed Business Associate Agreement before any patient records are handled, all of these must be confirmed before a start date is set, not discovered during the first week while the VA waits.

The most common technical gap is not a complex infrastructure problem. It is that nobody checked. The PMS access was assumed. The BAA was not discussed. The phone system was not tested for remote use. Two weeks into the engagement, the VA is operating at partial capacity or not at all, and the practice has already formed a negative impression of the arrangement.

Technical remediation is often faster than it looks. It is usually a solvable IT project rather than a cultural or structural problem. But it cannot be solved after the VA has started and is waiting for access. Confirm the technical prerequisites, test them, and sign the required agreements before the start date is finalized.

Prerequisite 3: Owner Delegation Tested Before Committing

Owner delegation failure is the most common and least discussed disqualifier in VA engagements. An owner who cannot let go of a function will override the VA’s work, generate a stream of corrections, or simply not route work to them in the first place. The engagement fails not because the VA was incapable but because the system was designed to bypass her. The owner retained the function while also paying for someone to hold the title.

The test is simple and can be run before any hiring decision is made. Name three things you did last week that someone else could have done. If you cannot name them, you have not yet developed the habit of identifying delegation opportunities. Describe the last time you delegated something and what happened. If the answer is that you eventually took it back, the pattern is established. Who would this person report to? If there is no answer, there is no accountability structure. What will you do with the time this frees up? If there is no answer, the recovered time has no destination, and it will be refilled with low-value work. The engagement will succeed technically and produce no observable improvement.

An owner who cannot answer these questions clearly is not ready to hire, regardless of how strong the business case appears on paper.

Prerequisite 4: Volume Sufficient for the Role

A practice with very low patient volume or a low-activity target function may not have enough work in that function to justify dedicated capacity. Roughly 10 hours per week of real work in a coherent function is the minimum that makes a dedicated arrangement sensible. Below that, part-time or shared arrangements are more appropriate.

Launching a dedicated VA into a function that generates 6 hours of weekly work produces underutilization, scope creep (tasks are added to fill the hours, pulling the VA across functions without clear accountability), and a confused engagement where neither the practice nor the VA is clear on what success looks like. The practice eventually concludes that the VA “wasn’t busy enough to justify the cost,” which is accurate but diagnoses the symptom rather than the cause. The cause was the decision to launch a dedicated arrangement without confirming that the volume supported it.

For verification roles, multiply appointments per week by average verification time. For claims and AR, estimate from weekly claim volume and aged claim count. For recall, multiply due patients per month by required touches. For phone work, multiply missed calls by average handling time. If the math does not support 10 hours per week, the right arrangement is different, not the wrong VA.

Prerequisite 5: Team Informed and Consulted

A staff member who learns about the VA on the VA’s start date has had no time to process the change. Their concern, whether or not it is reasonable, is more likely to surface as passive resistance: information withheld, access not fully set up, context not provided, questions not answered promptly. The most common form of team resistance is not overt. It is quiet and nearly invisible until the VA reports that she cannot get the information she needs to do the work.

The practice reads this as a VA performance problem. The actual problem is a team communication failure that predates the VA’s start date by months.

One conversation, held before the engagement launches, changes this reliably. The conversation 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 us directly if something is not working. That is the whole conversation. It costs one meeting and almost never happens before the VA starts.

Long-tenured staff members who control the function being delegated are the highest-risk cohort. They have established workflows, established authority, and the most to feel uncertain about. Consulting them before the engagement launches, not informing them after, is the difference between an ally and a passive blocker.

What to Do Before Launching

Score all five dimensions honestly, before a start date is discussed.

If process readiness is zero, start with SOP authoring as the engagement structure. Document the target workflows first, then transition to execution.

If technical prerequisites are missing, clear them before setting a start date. Test the remote access. Confirm the BAA. Verify the phone system. A start date set before these are confirmed is a date that will slip.

If owner delegation is untested, test it with a smaller internal delegation before bringing in an outside resource. The pattern the owner has established with internal delegation is the pattern that will repeat with the VA.

If volume in the target function is below threshold, consider a part-time or multi-function arrangement. The engagement structure should match the work volume, not the ideal structure.

If the team has not been prepared, prepare them first. The conversation that takes 30 minutes before the engagement launches is the conversation that takes months to have after resistance has calcified.

The readiness assessment is not a delay tactic. It is a setup for a first engagement that succeeds, rather than a first engagement that produces the conclusion that VA arrangements do not work for dental practices. That conclusion, once formed, is hard to walk back. The team saw it fail. The owner spent money and time on something that did not deliver. A second attempt requires overcoming not just the original gaps but also the skepticism the first attempt created.

Getting it right the first time is not about being cautious. It is about not manufacturing the resistance that makes every attempt harder.