Onboarding Caregivers Onto a New EVV App: A Practical Guide

Caregiver software adoption fails for a predictable reason: too many taps, too much training, too little explanation of why it matters to them personally. It’s rarely a technology problem so much as a rollout problem. Here’s how to avoid the version that gets your caregivers grumbling in the group chat instead of just using the app.

Start With Why, Not How

Before showing anyone the app, explain the actual reason it exists: Minnesota requires GPS-verified visits for Medicaid billing, and this app is how the agency stays compliant without paperwork. Caregivers who understand the “why” trust the “how” faster, and they’re far more forgiving of a hiccup in week one if they already understand what the app is protecting: their hours getting paid correctly, and the agency staying eligible to keep serving its clients at all.

Skip this step and you’re introducing a mysterious new requirement with no context, which is exactly the kind of thing caregivers assume is there to check up on them rather than support them.

Keep the Training Under Five Minutes

If a clock-in flow takes more than two taps (select client, tap clock in), it’s too complicated for a caregiver standing in a doorway juggling a bag and a phone. A good EVV app should need almost no training at all. Walk through it once, live, on a real phone, with a real caregiver doing the tapping while you watch rather than narrate. If you find yourself needing a printed instruction sheet to explain the basic flow, that’s a signal about the app, not about your caregivers.

Keep the training session itself short and hands-on rather than a group presentation. Five caregivers each doing one practice clock-in on their own phone teaches more than twenty minutes of slides.

Roll Out in Waves, Not All at Once

Start with a small group of caregivers, five to ten, before rolling out agency-wide. This surfaces real-world issues (a caregiver’s phone with location services disabled, a client’s address that doesn’t geocode cleanly, an older phone that struggles with the app) while the group is small enough to troubleshoot individually rather than becoming a flood of support tickets on day one.

Pick your pilot group deliberately. A mix of your most tech-comfortable caregivers and a couple who are more hesitant gives you a realistic read on how the rollout will go for your whole roster, not just the easiest case.

Address the Trust Question Directly

Caregivers sometimes worry that GPS tracking means constant surveillance: being watched throughout an entire shift. Be direct, early, and repeat it more than once: the app only records location at clock-in and clock-out, not continuously throughout the visit. Saying this plainly, before anyone asks, heads off most of the resistance. Waiting for someone to raise it as a complaint means you’re now on the defensive about something you could have simply explained upfront.

It also helps to be honest about what the data is used for: verifying that a scheduled visit happened at the client’s home, which protects the caregiver as much as it protects the agency. A caregiver whose visit gets questioned has real evidence it happened, instead of it coming down to their word against a billing dispute months later.

Prepare for the Most Common Objections

A handful of concerns come up in nearly every rollout. Have a plain answer ready for each rather than improvising:

• “What if my phone dies mid-visit?” Clock the visit manually in the office that day, and flag it so the exception gets resolved before it ever reaches HHAeXchange.
• “What if I forget to clock out?” It happens to everyone in week one. It shows up as an exception, someone follows up, it gets corrected. It is not a disciplinary event.
• “Do I need a smartphone?” Yes, but nearly every caregiver already has one; this isn’t asking anyone to buy new hardware for the job.
• “Why do I need this if I’ve been doing this job for years?” Because DHS requires GPS-verified EVV for Medicaid-billed visits regardless of tenure. This isn’t a judgment on their reliability, it’s what keeps the agency paid.

Make the First Week Easy to Fix

Expect a higher exception rate in week one, mostly missed clock-outs and unfamiliar navigation, and treat it as normal, not a caregiver performance issue. Review the exception manager daily during rollout and follow up individually, by phone or text, rather than sending a group reminder that makes everyone feel scolded for a problem only a few people actually had.

Assign one person, a scheduler or office manager, as the point of contact for the first two weeks. Caregivers with a real person to text when something looks wrong will actually reach out; caregivers routed to a generic support inbox usually just stop using the feature that’s giving them trouble.

Materials Worth Having Ready

You don’t need a formal training manual, but prepare a few things before your rollout starts:

• A one-page cheat sheet with screenshots of the clock-in flow, for caregivers who want something to reference after the live walkthrough.
• A short list of who to contact for app problems, phone problems, and schedule problems, so caregivers don’t have to guess which one applies.
• A plain-language answer to “why now” if you’re mid-contract-year and this wasn’t part of anyone’s original onboarding. Caregivers notice when a new requirement shows up without explanation, and a short answer beats no answer.

None of this needs to be elaborate. The goal is removing friction for the caregiver who has a question at 7am before their first visit of the day, not producing documentation for its own sake.

Don’t Skip the Office Staff Side of Onboarding

It’s easy to focus entirely on caregivers and forget that your scheduler, office manager, and billing staff are also learning a new system at the same time, just from the other side of it. They need to know where the exception manager lives, what a normal daily exception count looks like versus a concerning one, and who’s responsible for following up on each type of flag.

A rollout that goes smoothly for caregivers but leaves office staff unsure how to use the tools on their end just moves the friction one step downstream: exceptions pile up unresolved, nobody’s clearly accountable for clearing them, and the compliance benefit of the whole system quietly erodes. Give office staff their own short walkthrough, separate from the caregiver training, focused specifically on what they’re responsible for checking and how often.

What Success Looks Like

By week two or three, clock-in should be routine enough that caregivers stop thinking about it, the same way they don’t think about unlocking their phone. Exception rates should drop sharply once the initial unfamiliarity wears off, settling into occasional, individually explainable incidents rather than a daily pattern.

If your team is still fighting the app after a month, the problem usually isn’t the caregivers, it’s the app itself, or a rollout that skipped the “why” and the wave-based pacing that makes adoption manageable. Diagnose which one directly rather than assuming it will resolve itself with more time.

Revisit the Rollout Once, a Month Later

Put a deliberate check-in on the calendar three to four weeks after go-live, rather than assuming silence means success. Pull the exception report and look at whether it’s trending down and whether it’s concentrated among a specific few caregivers rather than spread evenly. A caregiver who’s still struggling a month in usually needs a short one-on-one refresher, not another group reminder.

This is also the point to ask your office staff directly whether the rollout actually reduced their workload the way it was supposed to, or whether it just moved the same problems somewhere new. A rollout that looks finished from the outside can still have a handful of unresolved friction points that never surface unless someone asks.