Blog

EVV troubleshooting starts with a fact most home care offices learn the hard way: the failure always shows up on the caregiver’s phone, but the cause only sometimes lives there. A clock-in that will not go through can fail in any of four layers: the device, the login, the EVV platform, or the schedule and setup data behind the visit. Each layer belongs to a different party, and each one looks nearly identical from a client’s doorstep.

This post is for owners, administrators, and schedulers at home care agencies across the San Francisco Bay Area who want to stop guessing. It covers what a failed clock-in actually costs, why the four layers produce the same symptom, and how to tell which one failed before anyone calls the wrong vendor. Phone configuration, offline capture, and escalation routing each have their own piece in this series, and this post links to them where they apply.

What Does It Cost When a Caregiver Can’t Clock In?

A caregiver who cannot clock in turns a routine visit into an exception the office has to repair after the fact. The care still happens. The record of it does not, so someone in the office rebuilds that visit later, usually from a text message and the caregiver’s memory, and usually days after anyone could check the details.

Picture 6:55 AM. A caregiver is at the client’s door for a 7 AM visit, the EVV app will not load, and the office line is not staffed for another hour. She goes in and delivers the visit, because the client is waiting. On the way out she texts the scheduler: “App wouldn’t work this morning.” By the time anyone reads it, that visit exists only as a text.

The usual fallback is a manual entry by the office after the visit. That fallback is permitted, and it is also the first thing an auditor counts.

What Did the OIG Audit Find About Manual Entries?

A July 2026 HHS Office of Inspector General audit of Colorado’s Medicaid personal care services found manually entered visits in 62 of 160 sampled claim lines, a 38 percent rate as the report states it. OIG treats manual entries as permitted but not real-time verification, and it recommended that the state limit how often they are used.

That is Colorado’s program rather than California’s, and personal care rather than home health, so the figure is a pattern rather than a prediction. The pattern is simple: every clock-in that fails in the field becomes a manual entry in the office, and a high manual-entry rate is exactly what program integrity reviewers go looking for. The office cost of a failed clock-in is not one phone call. It is a visit that has to be reconstructed, a record that is weaker than it should be, and a number that climbs every week the underlying cause goes undiagnosed.

Where Does an EVV Clock-In Failure Actually Come From?

An EVV clock-in failure comes from one of four layers, even though every one of them shows up as the same thing: a caregiver with a phone that will not let them start the visit. Naming the layer is the whole job of troubleshooting, because each layer has a different owner and a different fix.

• The device: the phone itself, its operating system, the app version installed, free storage, battery and background settings, and whether location permission was ever granted.
• The login: the caregiver’s credentials and account status in the EVV app, including whether the account is active and whether a password reset is pending.
• The EVV platform: the vendor’s app and servers, including outages, defects, and forced version changes.
• Schedule and setup data: the visit on the schedule, the client’s address on file, and the geofence around it. If any of those is wrong or missing, a perfectly good phone with a perfectly good login still cannot clock in.

Which Party Owns Each Layer?

The device and login layers belong to the agency’s IT provider. The EVV platform belongs to the vendor. Schedule and setup data belong to the agency office. That split is the reason a clear diagnosis matters: the same symptom has three possible phone numbers attached to it, and only one of them can fix the problem. How IT support for EVV divides across those parties is covered in the first post in this series.

Misdiagnosis wastes the narrow window before the visit. Calling the EVV vendor about a phone setting costs twenty minutes on hold and ends with “that’s not us.” Reinstalling the app over a missing schedule entry costs the reinstall, the re-login, and the realization that the visit still is not there. Neither gets the caregiver into the home any faster.

Why Do Device, Login, and Platform Problems Look the Same?

Device, login, and platform problems look the same because the EVV app reports a symptom, not a cause. The error on screen is whatever the app could detect at that moment, and the app cannot always tell the difference between a phone that is misconfigured and a server that is not answering. Two documented examples show how far the symptom can drift from the source.

A device problem that looked like connectivity. After an encryption certificate change in February 2024, HHAeXchange+ app versions below 24.1 could no longer connect, and the app displayed a “no internet connection detected” message. A caregiver with full signal bars would see an error that pointed at her carrier. The real fix was updating the app.

A platform problem that looked like a device. In its response to the OIG audit, Colorado traced missing GPS coordinates on mobile check-ins to a system logic defect, which it fixed with its vendor in July 2025. An agency troubleshooting those visits one phone at a time would have been checking location permissions on phones that were fine.

IT Total Care sees the same failure patterns across HHAeXchange, AxisCare, Axxess, and WellSky. The app differs. The layers do not.

Does It Matter Which EVV System a California Agency Uses?

For the device and login layers, no. In California, EVV data from Medi-Cal providers that are required to use EVV lands in the CalEVV Aggregator that Sandata operates for the Department of Health Care Services, whether the agency uses the state system or an alternate one. Which app a caregiver carries changes the icons on the screen; it does not change the four layers or who owns them. How CalEVV and alternate systems differ, and what happens at the aggregator, is its own topic.

Visit verification is one of several places where field technology shapes a home care agency’s day. The broader picture, from intake through billing, is laid out in IT for Home Care Agencies.

How Do You Tell Which Layer Failed?

Start with one question: is it one caregiver or many? The answer narrows four layers to one or two before anyone touches a phone, and it is the step most offices skip because the first report always sounds like a single broken app.

• Many caregivers on the same platform failing at once points to the EVV platform. Check the vendor’s status notices before anyone touches a phone. If the vendor has posted an outage or a forced update, every phone in the field is about to generate the same ticket.
• One caregiver failing at one client’s home points to schedule or setup data: the client address, the geofence, or a visit that never made it onto the schedule. The phone worked at the last home. It will work at the next one.
• One caregiver failing at every client points to the device or the login. Something about that phone or that account is wrong everywhere it goes.

What Does This Look Like on a Scheduler’s Screen?

Consider a scheduler managing 40 or more shifts a week who sees three different caregivers fail at the same client’s home over five days. Three tickets to IT about three phones would be the natural reaction. It would also be wrong. Three caregivers, three phones, one address: that is a setup-data problem, almost certainly the client’s address or geofence, and it lives in the agency’s own system.

“The EVV related call we get most often is ‘the app is broken.’ Sometimes it is. More often it’s a visit that never got built or a password that expired over the weekend. By the time someone looks, the caregiver has already reinstalled the app twice and lost a morning. Figuring out which layer you’re in before anyone touches the phone is the fastest fix most of the time.”

Brendan Duebner, President of IT Total Care

What Are the Signals for Each EVV Layer?

Each layer leaves its own signals, and most of them are visible on the caregiver’s screen or in the office’s own records without any technical investigation. Reading the signal correctly is what turns “the app is broken” into a ticket that reaches the right party the first time.

What Do Device Problems Look Like?

Device problems show up as the app failing to open or crashing on launch, a “no internet” message while the phone clearly has signal, a location prompt that never appeared when the app was installed, or an app that logs the caregiver out whenever it sits in the background. Each of these traces to a setting, a version, or a resource on the phone itself.

What Do EVV Login Problems Look Like?

EVV login problems show up as an invalid-credentials error, an inactive account message, a lockout after too many failed attempts, or a forced password reset the caregiver cannot complete from the field. The phone is fine. The account is not, and nothing done to the phone will change that.

What Do Schedule and Setup Problems Look Like?

Schedule and setup problems show up as today’s visit not appearing in the app, an out-of-area error while the caregiver is standing at the correct address, or a clock-in refused because it falls outside the allowed window. AxisCare’s caregiver resources list the same three causes as the common reasons a caregiver cannot clock in: too early or late, too far from the home, and no visit scheduled. All three live in the agency’s own data.

What Do Platform Problems Look Like?

Platform problems show up as the same error across multiple caregivers and phone models, sync failing for everyone at once, or a vendor-announced outage or defect. The tell is breadth: nothing about one phone or one account explains a failure that spans the whole field team.

Where Do EVV GPS Issues Belong?

EVV GPS issues can land in three different layers, which is why they generate so many misdirected calls. A location prompt that never appeared is a device problem. An out-of-area error at the correct address is a setup problem with the client’s address or geofence. Coordinates missing for every caregiver at once is a platform problem, as Colorado’s defect showed. If the phone simply has no service, that is a connectivity question rather than a troubleshooting one.

What Should the Office Do Before Escalating?

Before escalating, the office should check the app version, protect any visits that have not synced, and collect five facts. Those three steps take minutes, and they turn a vague report into a case that the right party can act on immediately.

Check the app version early. It is the fastest device-layer fix and the most common one IT Total Care sees. EVV vendors set minimum versions, and a phone that stopped updating can stop clocking in overnight without the caregiver changing anything.

Before anyone deletes or reinstalls the app, confirm no visits are waiting to sync. A reinstall can take unsynced visits with it, and a visit lost that way becomes a manual entry with nothing behind it.

Collect five things before the call goes anywhere:

1. The caregiver’s name.
2. The client and the visit time.
3. The exact error text, or a screenshot of it.
4. The phone model and operating system version.
5. The EVV app version.

Log each failure by layer. Repeat patterns only show up when someone writes them down: the same phone model failing after an OS update, the same client address generating out-of-area errors, or a cluster of failures in the same week an app update shipped. A simple log, kept by whoever already tracks visit exceptions, is enough.

Once the layer is identified, the failure needs to go to the party that owns it. How to escalate EVV issues to the right party walks through that routing.

How Does IT Total Care Handle EVV Troubleshooting for Home Care Agencies?

IT Total Care owns the device and login layers for its client agencies. The EVV vendor still owns its platform, and the agency office still owns schedules and client setup. That division is deliberate, because the agencies that struggle most are the ones where nobody is clearly responsible for the phone and the account, so every failure defaults to the vendor or to the scheduler.

What that looks like in practice:

• Layer first, then the call. When a caregiver cannot clock in, IT Total Care identifies the layer before anyone is called, so the ticket goes to the right party the first time.
• Coverage across the apps agencies actually run. IT Total Care supports agencies on HHAeXchange, AxisCare, Axxess, and WellSky, and recognizes each app’s common failure signals rather than starting from scratch with every report.
• Version and OS monitoring. IT Total Care tracks EVV app versions and vendor OS requirements, so a forced minimum version is a planned update rather than a Monday morning surprise.
• A documented case for the vendor. When the cause is the platform, the vendor receives the error text, the affected caregivers, the phone models, and the OS and app versions, which shortens the time to a fix.
• Clear boundaries. IT Total Care does not change EVV schedules, client addresses, or geofences. Those stay with the agency office and the vendor, where the authority and the context for them live.

This is part of the home-based care IT support that IT Total Care provides to home care, home health, and home hospice agencies, where field devices and the accounts on them are managed as a service rather than handled ticket by ticket.

Ready to Stop Guessing Which Layer Failed?

A failed clock-in should take one call to resolve, not three. IT Total Care works with home care agencies across the Bay Area, from the Peninsula to the East Bay, to keep caregiver phones and EVV logins working in the field and to make sure that when something does break, the diagnosis comes before the phone call. Learn more about EVV troubleshooting and field device support from IT Total Care.

Contact Us to talk through what your agency needs.