Most EVV feature pages recycle the same buzzwords - GPS, scheduling, billing, reporting. But the features that actually determine whether your agency runs smoothly are the ones that prevent daily operational chaos: exception handling, edit controls with a real audit trail, offline reliability, role-based workflows, aggregator visibility, and billing readiness. Use the scorecard in this guide to compare vendors based on what actually reduces denials and coordinator burnout. At Ankota, we know that the details matter and Ankota's EVV software handles the tricky parts of EVV.
If you've spent any time evaluating EVV software, you've seen the same feature page over and over. GPS check-in. Electronic scheduling. Automated billing. Reporting dashboards. Every vendor has them, and every vendor describes them in roughly the same language.
The problem is that those feature lists tell you almost nothing about how the software will perform on a Monday morning when 22 visits have exceptions, three caregivers forgot to clock out, and two claims are flagged before they've even been submitted.
What we've learned from working with home care agencies is that the features that win evaluations are rarely the features that determine operational success. So here's our version of the list - the features that actually matter and the questions you should be asking before you sign.
EVV compliance isn't just about capturing the right data points. It's about being able to prove you captured them - accurately, with appropriate controls - if a state auditor or payer ever asks.
The required data elements are well established: visit start and end time, service type, caregiver identity, client identity, and location methodology. Most EVV systems capture all of these. Where they diverge is in edit governance.
A vendor can tell you their system is "compliant" while still allowing coordinators to freely edit visit records without any approval workflow, audit trail, or reason code. That's a compliance posture, not a compliance system. What you want to understand is: who can change visit data, what approvals are required to do so, and what evidence is recorded when it happens.
Ask in the demo: "Walk me through what happens when a coordinator needs to correct a clock-out time after the visit is complete."
Your EVV platform should maintain a clear, searchable history of every visit modification - not a freeform notes field where someone typed "fixed the time."
A proper audit trail captures who created or edited a visit, what changed (the actual field values before and after), when the change occurred, why it changed via standardized reason codes, and whether a supervisor sign-off was required. This is the difference between "we fixed it" and "we can defend it."
Ask in the demo: "Show me a visit that was edited after the fact. I want to see the full before/after, timestamp, user, reason, and any approvals." If the vendor can't pull that up cleanly, that tells you something important.
An audit moment: At Ankota, we've been told be many customers that when the auditors see our audit sheet, they say that it's the best they've ever seen and they wish that all agencies have it. One "pro-tip" is to give the auditor printed sheets or online access for the recommended clients and time frames, but then at the same time make a set of the sheets for the agency owner that include the internal comments.
Here's something we hear from agency directors regularly: they didn't drown in EVV because of scheduling. They drowned because of exceptions.
Clock-out forgotten. GPS didn't register at a client's apartment building. Caregiver arrived 22 minutes late. Visit duration outside the authorized range. Each of these is an exception, and without a structured workflow to route, resolve, and document them, your coordinators spend their days working through a spreadsheet instead of supporting caregivers and clients.
What you need isn't just an exceptions list. You need an exceptions engine - a dashboard that surfaces exceptions by team, coordinator, or supervisor; routing rules that distinguish between what a caregiver should fix vs. what the office needs to handle; reason codes with supporting documentation; and resolution tracking so you can see time-to-clear and identify repeat patterns.
If you only buy "GPS + clock-in/out," you'll pay for the missing piece in coordinator hours.
The caregiver app is where EVV either works or doesn't. A sophisticated backend doesn't help much if caregivers can't - or won't - use the mobile experience consistently.
The right category of features includes one-touch clock-in/out, task and documentation workflows, client signature capture, multilingual support, and offline capability. But features on a spec sheet and features that work reliably in the field are two different things.
Offline mode is the one we'd push hardest on. Caregivers visit clients in rural areas with spotty coverage, basement apartments, and facilities with signal issues. If the app can't handle offline gracefully - capturing the visit locally and syncing without data loss when connectivity returns - you'll see exceptions created by the technology itself, not by caregiver error.
Field reality test: Ask the vendor to complete a visit with the phone in airplane mode, then sync it back. If they can't demonstrate that smoothly, you have your answer.
Offline mode in the real world: In the early days of EVV we had a customer where a clever caregiver went to a clients home, clocked in, turned off mobile access, then changed the clock on their phone to the end time of their visit, clocked out offline, and then sync'd. We caught them quickly because they sync'd before the time that their shift was supposed to end. But then we added additional safeguards to remove the possibility to change their phone clock and get away with it.
GPS sounds straightforward until you encounter the real-world conditions your caregivers work in: apartment buildings with GPS drift, dense urban areas, rural dead zones, community-based outings, or multi-entrance facilities where a caregiver enters through a side door 200 feet from the address on file.
Perfect GPS isn't a realistic bar. What matters is how the system handles imperfect location data - clear exception workflows when location is questionable, reasonable tolerance rules, and the ability to document and defend location methodology when a payer asks. That's a stronger compliance posture than a system that claims GPS precision it can't always deliver.
EVV data that doesn't flow cleanly into billing - or at least into a clean, reconcilable export - creates a specific kind of operational pain. You'll see delayed invoicing, manual rework between systems, denials from data mismatches, and payroll headaches when delivered hours don't line up with what was scheduled.
Many vendors advertise "automated billing and payroll" as a feature. The capability we'd look for is more specific: visit-to-billing reconciliation that compares what was scheduled, what was delivered, and what's been billed - and surfaces visits that are at risk of denial before you submit them. Catching a problem in the system is always faster and cheaper than fixing a rejected claim.
In states that use an aggregator model for EVV data submission, your software's relationship with that aggregator is operationally critical. You need to see submission status and rejection reasons without leaving your system, and you need to be able to fix and resubmit quickly with an auditable trail.
Beyond aggregators, consider your broader integration picture. If you run payroll or billing through a separate platform, does your EVV system have open APIs or standard connectors? If your agency operates across multiple payer types, does the system handle the translation cleanly?
This is where "EVV software" becomes "EVV operations." The data model matters as much as the features.
An aggregator blindside: A lot of states, in fact most of them, started their EVV program in parallel to their billing, so it was "Send EVV to Sandata and send your claim to Medicaid," but they weren't correlated. Georgia (with Tellus/Netsmart), North Carolina (for Sandata programs) and Colorado (also Sandata) have been correlating and denying claims for a long time, whereas other like New Hampshire (with Authenticare) and Kentucky (with Therap) just started in 2026. This is a cautionary tale, because agencies that don't pay attention to their EVV percentages have a rude awakening when the correlation goes live.
EVV systems touch protected health information and sensitive operational data. It's worth evaluating security as rigorously as you'd evaluate any clinical tool, even if it rarely makes the top of feature comparison lists.
At minimum, you should expect role-based permissions that limit data access to what each role actually needs, audit logging for sensitive actions, secure messaging if the platform includes that capability, and clear data retention and export policies. These aren't exotic requirements - they're the baseline of a HIPAA-aligned security posture.
Rather than comparing vendors feature-by-feature, we'd suggest a weighted scorecard that keeps attention on what matters most operationally.
| Category | Weight |
|---|---|
| Compliance integrity + audit trail | 25% |
| Exceptions workflow | 20% |
| Caregiver app usability + offline reliability | 20% |
| Billing readiness + reconciliation | 15% |
| Integrations + aggregator visibility | 15% |
| Security + role-based access | 5% |
Score each vendor 1-5 in each category, multiply by the weight, and add the totals. It won't make the decision for you, but it will stop a polished demo from carrying more weight than it deserves
Here's a scenario worth stress-testing with any vendor you're evaluating.
Monday morning. You have 22 exceptions from the weekend. A well-designed EVV system routes 14 of them back to caregivers - missing clock-out prompts they can address directly from the app. It escalates 6 to supervisors for review because location mismatches require a judgment call and documentation. It flags 2 as billing-risk before they reach the submission queue. By noon, the exceptions are resolved and the visits are billing-ready - without a spreadsheet, without a coordinator making 22 phone calls.
That's not a marketing scenario. That's what the right exceptions engine, routing logic, and caregiver app combination can do for an agency's Monday morning.
The Monday morning scenario (highest priority).
Mondays are always the craziest day in home care. Not only do you have to review all of the visits from Friday, Saturday, and Sunday from an EVV perspective, but it's also the day when new employees are starting and there's always some crises to deal with. For example, a client who was taken to the hospital on the weekend or even worse. One of the agencies that we work with in Kentucky told me that before they had the Ankota EVV system, and especially the approval assistant, that they would have three people whose dedicated job was to go through all of the EVV cleanup and that sometimes it would take them to lunchtime on Tuesday to get them finished. Now with the approval assistant, they can work through everything in under an hour. One specific lesson learned with the approval assistant is that we, as the vendor, provide it to agencies with rules for every possible exception, but when the start using our software to its full capability, it becomes impossible for 87% of the exceptions to occur.
We built Ankota for home and community-based care organizations operating in real complexity. EVV in that context isn't an isolated feature - it's connected to scheduling, compliance workflows, and Medicaid billing operations. An exception doesn't just affect a visit; it affects a claim, a caregiver's record, and potentially a payer relationship.
What differentiates our approach isn't "we have EVV." It's how EVV fits into end-to-end operations - so coordinators aren't reconciling exceptions against a separate billing system, caregivers aren't working around a mobile app that loses data in the field, and supervisors have the visibility they need without digging through exports.
For agencies managing multiple HCBS programs - home care alongside I/DD services, or self-direction programs alongside traditional shift-based care - that connected architecture matters even more. The EVV requirements differ by program, but the operational overhead of managing exceptions, audits, and billing shouldn't multiply with every program you add.
Don't evaluate EVV based on a feature page or a polished demo alone. The essential features are the ones that keep you audit-ready, drive real caregiver adoption in real field conditions, reduce exception workload on your coordinators, and produce billing-ready visits without manual heroics.
Ask for a workflow-first demo that shows you exception handling from creation to resolution, edit governance and the audit trail it produces, offline visit capture and sync, and visit-to-billing reconciliation. That's the demo that tells you what you're actually buying.
To see how Ankota handles EVV as part of connected home care operations, visit our EVV software page or request a workflow demo.
What is the most important EVV feature for home care agencies? Exception handling is the feature that most directly determines coordinator workload. GPS and clock-in/out are table stakes. The question is what happens when those features produce imperfect data - which they will.
What should I ask in an EVV demo? Ask to see an edited visit with its full audit trail. Ask for a demonstration of offline mode. Ask how the system surfaces billing-risk visits before submission. Ask how exceptions are routed between caregivers and the office.
Does EVV software need to connect to our billing system? Not always, but you need a clear reconciliation path. Whether that's a native integration or a clean export, visit data and billing data need to stay aligned or you'll create manual work and denial risk.
What's the difference between EVV software and EVV operations? EVV software captures visit data. EVV operations is the full workflow - exceptions, edits, aggregator submission, reconciliation, and audit defense. The software is only as valuable as the operational workflows built around it.
How does state aggregator compliance affect my EVV choice? If your state uses an aggregator model, your EVV system needs real-time submission visibility and the ability to fix and resubmit with an auditable record. Confirm this capability explicitly - not all EVV platforms handle aggregator-model states equally well.
Ankota's mission is to enable the Heroes who keep older and disabled people living at home to focus on care because we take care of the tech. If you need software for home care, EVV, I/DD Services, Self-Direction FMS, Adult Day Care centers, or Caregiver Recruiting, please Contact Ankota.
And if you're ready to see how the most innovative agencies are using AI to empower their caregivers and automate the rest, meet your new companion at www.kota.care.