Why electronic visit verification programs fail audits and what operations leaders should ask about their EVV controls
Electronic visit verification (EVV) programs are an operational discipline, not a one-time IT checkbox. When states and providers treat EVV as a data collection tool without hard rules and clear exception workflows, documentation gaps and billing anomalies follow. Recent reporting that Colorado faced an $8 million repayment demand after a federal Medicaid audit is a reminder that even established EVV programs can leave audit exposure if the deployment lacks certain guardrails.
The practical risk is simple: auditors don’t need to prove fraud to find problems that require repayment. Missing location data, manual entries without review, background-screening records that aren’t verifiable, and the absence of edits to stop obviously impossible claims are all things an audit can point to. For an operations leader, the question is not whether to have EVV, but whether the EVV implementation is defensible when a reviewer asks for evidence.
Where EVV compliance breaks down in practice
There are a handful of recurring failure modes that show up across states and programs. System edits are often too permissive. If the billing system will accept implausible units or rates without flags, the downstream payment system can legitimately overpay. Exception workflows are weak: a location or phone exception gets filed but never reviewed or resolved, leaving the visit record incomplete. Supporting documentation for attendant eligibility or background checks is kept in disparate places or depends on manual confirmation rather than a consistent process.
Those problems are operational, not theoretical. They come from a mix of policy ambiguity, local provider practices, and technical gaps. Fixing them usually requires aligning policy, the EVV capture method, and the review process so that an auditor can trace a claim from the record in the EVV system back to a reviewed exception or an approved policy decision.
What operations teams should ask their vendors and program staff
Executives do not need to dictate technical designs, but they should ask specific, concrete questions that reveal whether the program is audit-defensible. Does the payment path include edits that block obviously impossible claims, such as more than 24 billed hours in a day or per-visit units that exceed approved limits? How are manual entries and exceptions routed for review, who reviews them, and is there a documented outcome retained with the record? Where and how are background-screening records stored, and can the program consistently demonstrate that required checks were completed before payment?
Those questions get you away from vague assurances and toward tangible evidence. If the answers are hand-wavy, a remediation cycle after an audit will be expensive and time consuming.
A measured path to audit-defensible EVV
There is no single magic change that removes audit risk. The practical path is a small set of disciplined steps that tie the capture method to consistent downstream controls. Start by aligning the policies that define allowable units and rates with the edits in the payment process. Make exception handling an auditable workflow: an exception should not be a note in a file cabinet but a recorded review with an outcome that can be queried later.
Automated edits do not replace judgment. They reduce obvious errors so staff focus on real exceptions. Likewise, retain a clear chain of documentation for background screenings: who requested the check, when it was completed, and where the verification is kept. We see this pattern often in Medicaid programs and provider networks: the technical system exists, but the human workflows around exceptions and documentation are inconsistent.
The operational habits matter more than the engineering. Teams planning changes to an EVV deployment should focus on the basics: edits that stop impossible claims, exception review that produces an auditable record, and background checks that are linked to the attendant’s record in a way that can be verified months later.
More on operational EVV workflows and verification methods is at /innovative-ivr-solutions-healthcare-services/electronic-visit-verification-tools-evv-system.
Related coverage: Colorado faces $8M repayment demand after federal Medicaid audit — Colorado Politics