The state wants proof the visit happened.

Electronic visit verification captures where and when, from the same clock in your technician already does. It works with no signal and sorts itself out when the phone reconnects.

Captured at the clock in

Your technician starts the session the way they already do. ABAVault™ records the time, the coordinates and the location type at check in and again at check out, from the app your staff already have open. Nobody types a visit up afterwards from memory.

  • Works with no signal: the visit queues on the phone and goes up when it reconnects
  • Replaying a queued visit cannot create a duplicate, because the phone generates the visit's own id
  • A check in with no usable coordinates is flagged on the visit, so billing can see it
Check in and check out on the phone
The exceptions queue, with rejection codes

When the times were wrong

Correct a visit from the exceptions queue, or through a session time correction, and ABAVault puts it back in the submission queue rather than only updating your screen. That matters more than it sounds. The aggregator already holds the original times, and a system that showed you the fix while the state kept the old record would be worse than one that showed you nothing.

  • Every correction carries a reason code and a full audit trail
  • A corrected visit is sent again, so the state's copy agrees with yours
  • A late check in is flagged with its own exception code and lands in the queue
EVV is off until you turn it on. A practice with no EVV configuration is never touched by any of this, which matters because electronic visit verification applies to some services in some states and to none of the rest. Every query is scoped to your practice, and the credentials for the connection are encrypted at rest the same way your clearinghouse credentials are.

The exceptions queue is the work list

Rejected visits arrive carrying the codes the aggregator sent back, in a queue somebody can actually work through. Every session shows the status of the visits behind it, and you can run a submission for your practice on demand.

How this reaches a claim →

Consent, recorded per person and per version

Each staff member acknowledges location capture against the version of the notice they were shown, and the record keeps which version that was. Declining at clock in cancels the clock in.

How we handle PHI →

Which aggregator, and what it will take

States use different aggregators, and they differ in what they accept and in how they want a correction expressed. Which one applies to you, and what it will want from your sessions, is the first thing we work out together, before go live rather than after it.

Ask us about your state →

The visit is the session

What gets verified is the session your team already scheduled, staffed and wrote a note against. A separate verification tool means keeping a second roster and a second client list current, and reconciling the two at the end of every month. That work does not exist here because there is only one record.

All features →

Tell us which state you bill in.

We will walk through what its EVV rules would mean for your sessions.

Apply for beta access Next: Billing & RCM →