The EVV Compliance Guide for Home Care Agencies

EVV started as a federal mandate and turned into a daily operational grind. The rule itself is simple — prove electronically that each visit happened. The hard part is what happens in real homes with real caregivers: phones die, GPS drifts, schedules change at the last minute, and every one of those events creates an exception someone in your office has to resolve before the visit can be billed. Agencies rarely lose money because they ignored EVV. They lose it because exceptions pile up faster than anyone clears them.

This guide covers where the mandate came from, what it actually requires, where visits fail most often, and what a correction workflow looks like when it works.

Where did the EVV mandate come from?

Section 12006 of the 21st Century Cures Act, signed in December 2016, required every state to implement EVV for Medicaid-funded personal care services and home health care services. The statutory deadlines were January 1, 2020 for personal care and January 1, 2023 for home health, and many states received "good faith effort" extensions that pushed their personal care enforcement into 2021.

The enforcement mechanism matters: states that failed to comply faced reductions in their federal Medicaid match. That gave every state a financial reason to enforce EVV strictly — which they do by refusing to pay claims for visits that lack a matching verified record. In other words, the state's compliance problem became your billing problem.

What are the six data points every visit must capture?

Federal law sets a floor of six elements per visit:

• The type of service performed
• The individual receiving the service
• The individual providing the service
• The date of the service
• The location of service delivery
• The time the service begins and ends

States and managed care plans layer their own requirements on top — specific service code mappings, geofence tolerances, limits on manual edits, and deadlines for corrections. Your state's EVV policy manual, not the federal statute, is the document your office actually lives by.

How does your state's EVV model affect you?

States chose different implementation models, and yours dictates how much flexibility you have:

• Closed model: the state contracts one EVV system and every provider must use it.
• Open or provider-choice model: you may use your own EVV or agency-management system, as long as it meets state specs and feeds the state's data aggregator.
• MCO-driven variants: in some managed care states, each plan designates or approves systems, which can mean juggling more than one.

Common systems and aggregators you will encounter include HHAeXchange, Sandata, AuthentiCare, and Netsmart, alongside EVV modules built into agency scheduling platforms. The practical consequence of the model question: in open-model states, schedule data lives in your system and must transmit cleanly to the aggregator, so integration errors become their own category of exception.

SS Support Network is an independent company — not affiliated with or endorsed by any EVV vendor, aggregator, or state program named in this article. We work inside whatever system your state and agency already use.

Where do visits fail verification most often?

Across agencies, the same failure points account for most of the exception queue:

• Missed clock-ins and clock-outs. The caregiver forgot, the app crashed, or the phone was dead. The visit happened; the record says nothing.
• GPS and geofence mismatches. The check-in registers outside the allowed radius — rural properties, apartment complexes, and community visits are chronic offenders.
• Schedule mismatches. The visit does not line up with an authorized schedule or service code, often because a last-minute caregiver swap never made it into the system.
• Telephony from unregistered numbers. The caregiver called from a personal cell instead of the client's registered landline.
• Visits exceeding authorized units. The caregiver stayed longer than the authorization allows, or the authorization lapsed mid-week.
• Manual edits without reason codes. A fix that is not documented properly just creates a second, worse problem.

Each of these is fixable — but only inside your correction window, and only if someone is watching the queue every day.

What does a clean EVV correction workflow look like?

Agencies that stay compliant run some version of this loop:

1. 1
   Review exceptions daily. Every morning, someone works the previous day's failed visits while caregivers and clients still remember what happened. Exceptions older than a few days get dramatically harder to verify honestly.
2. 2
   Correct with reason codes and evidence. Every manual fix carries a state-approved reason code and a note — who confirmed the visit, how, and when. That documentation is what stands between a routine correction and an audit finding.
3. 3
   Clear the queue before the billing export. Set an internal deadline: no claim batch goes out with unresolved exceptions in it. Billing a flawed visit does not make the flaw disappear — it converts it into a future denial or recoupment.

Two metrics tell you whether the loop is healthy. First, exception rate: what share of visits fail verification each week, and is it trending down? Second, manual edit rate: states monitor providers whose edit percentages run high, because heavy editing is exactly what fraud looks like from a regulator's chair. If your edit rate is climbing, do not just keep fixing visits — root-cause them. A repeat offender usually points to something specific: a caregiver who needs retraining, a geofence radius set too tight for a rural address, or schedules being changed by phone but never in the system.

How do you keep EVV from consuming your office?

The work is not intellectually hard; it is relentless. Exception review, caregiver callbacks, schedule corrections, and aggregator troubleshooting eat one to several office hours every single day, and they compete directly with intake and scheduling for your coordinators' attention. The failure mode is predictable: exceptions get batched to Fridays, the correction window slips, and clean revenue quietly turns into write-offs.

You have three workable options: dedicate a trained in-house person to the daily queue, spread it across coordinators with a hard daily deadline and weekly reporting, or hand the loop to a dedicated EVV support desk that works exceptions every day inside your system. Many agencies pair that desk with wider home care back-office coverage so schedule changes get entered correctly in the first place — preventing the exception instead of correcting it. Whichever route you choose, compare the cost against what unbillable visits are already costing you; our ROI calculator makes that comparison straightforward.

Frequently asked questions

Is EVV required for private-pay home care?

No. The federal mandate applies to Medicaid-funded personal care services and home health services. Private-pay and most commercially funded visits are exempt, though many agencies run every visit through EVV anyway so caregivers follow one process and payroll pulls from one verified record.

What are the six data points EVV must capture?

Federal law requires each visit record to capture the type of service performed, the individual receiving the service, the individual providing it, the date of service, the location of service delivery, and the time the service begins and ends. States and payers layer their own rules on top of these six.

What happens if a visit fails EVV verification?

The visit lands in an exception queue instead of flowing to billing. Someone must correct it — with a documented reason code — before the claim goes out. Uncorrected exceptions become unbillable visits, and if a flawed visit is billed anyway, the payer can deny it or recoup the payment later in an audit.

Can caregivers clock in without cell service?

Yes. Most EVV apps have an offline mode that stores the check-in and syncs when coverage returns. States also allow telephony (the caregiver calls from the client's registered phone) and fixed-device verification, where a small unit in the home generates codes the caregiver records. Ask your vendor which fallbacks your state accepts.