Reducing EVV Exceptions: Why Minnesota Agencies Rack Up Missed Clock-Ins

An EVV exception is any visit that didn’t cleanly capture all six required data points at the time of service: a missed clock-out, a GPS coordinate that doesn’t match the client’s address, a visit that got entered manually after the fact. Every agency has some. The agencies that struggle are the ones where exceptions pile up faster than the office can clear them, because an unresolved exception doesn’t just sit there quietly. It becomes a denied claim weeks later, at exactly the moment it’s hardest to fix.

Here’s where exceptions actually come from, and what to do about each one.

The Usual Suspects

A dead or degraded phone battery. This is the single most common cause of a missed clock-out, and it’s rarely a caregiver problem so much as a device-hygiene problem. An older phone with a worn battery can die mid-shift without warning, taking the clock-out with it.

Spotty cell or GPS signal at the client’s home. Rural service areas, older apartment buildings with poor reception, and basements all cause the same failure: the app can’t get a location fix at the moment the caregiver tries to clock in, so it either times out or logs a coordinate that’s off by enough to trip a mismatch flag.

Multi-unit buildings and shared addresses. GPS doesn’t know which unit in a building the caregiver is actually in. A visit correctly performed at apartment 4B can still throw a location exception if the GPS fix lands closer to the building’s leasing office or a neighboring unit.

Caregivers clocking in under the wrong client profile. More common than it should be when one caregiver serves multiple clients back-to-back, especially with a rushed handoff between visits and an app that doesn’t make the active client obviously visible.

Manual entry becoming a habit rather than an exception. Once an office gets used to “just typing in the times after the fact” for one caregiver, it tends to spread, because it’s easier in the moment than fixing the underlying device or connectivity issue.

Fixing the Device Problem Before It Becomes an Exception

Most exception-reduction work isn’t glamorous; it’s device hygiene, done consistently. A few things worth building into onboarding and periodic check-ins rather than treating as one-time setup:

• Confirm each caregiver’s phone holds a charge through a full shift, and flag anyone on an old device for a check-in. A phone that dies by mid-afternoon is a predictable, recurring exception source, not a one-off.
• Make sure the app is current and the phone has enough free storage. A near-full phone slows everything down, including GPS acquisition.
• Where the app supports offline capture, make sure caregivers know how to use it and trust it, so a dead zone doesn’t turn into a skipped clock-in instead of a queued one that syncs later.

Fixing the Location Problem

For multi-unit buildings and known dead zones, the fix usually isn’t technical, it’s documentation. Flag known problem addresses in your scheduling notes so the office isn’t surprised by a location exception it’s seen a dozen times before, and so the exception gets cleared with context instead of treated as a fresh investigation every time. If your EVV app supports a manual address-verification or geofence-adjustment feature for a specific client location, use it once, rather than absorbing the same flag on every visit to that address indefinitely.

Fixing the Habit Problem

The manual-entry creep is the hardest one to fix because it’s a behavior problem, not a technology problem. It usually takes a direct conversation: same-day correction is expected, and next-day-or-later entry gets flagged for a reason, not just a formality. Agencies that get ahead of this build a same-day correction window into their caregiver expectations from day one of onboarding, so it’s never treated as optional.

Making Exception Review a Weekly Habit, Not a Monthly Scramble

The offices that keep exception rates low almost all share one practice: someone owns the exception queue and clears it on a fixed cadence, ideally weekly, rather than letting it accumulate until a billing deadline or an audit forces the issue. A weekly quarter-hour spent clearing five exceptions is a completely different experience than a pre-deadline scramble clearing forty, and it catches patterns (the same caregiver, the same address, the same time of day) while they’re still small enough to fix instead of after they’ve become a recurring revenue problem.

Why This Is a Revenue Problem, Not Just a Compliance One

It’s worth being blunt about the stakes here. An exception that never gets resolved doesn’t just sit in a queue looking untidy; it’s a visit that can’t be billed cleanly, and a pattern of unresolved exceptions is exactly what shows up during a DHS review as evidence of a compliance gap. The office time spent chasing down exceptions after the fact, and the revenue lost to denied claims that trace back to them, is almost always more expensive than the device hygiene and weekly review habits that would have prevented them in the first place.

The Short Version

Most EVV exceptions trace back to one of a handful of predictable causes: a dying phone, a dead zone, a multi-unit address, or a habit that’s drifted toward manual entry. None of them require a new app to fix. They require device hygiene at onboarding, documented context for known problem addresses, a clear expectation around same-day correction, and someone who owns the exception queue on a weekly cadence instead of letting it become a monthly emergency.