EVV-Compliant Scheduling: How Your Schedule Feeds the Aggregators

If you run a Medicaid-funded home care agency, you've learned that a visit isn't really "done" until it's verified electronically and accepted by your state's system. That's where a lot of agencies get tripped up: their scheduling lives in one place — a whiteboard, a spreadsheet, a legacy tool — and their Electronic Visit Verification (EVV) lives in another, and the two never quite agree. The result is rejected visits, claim delays, and a compliance coordinator spending Fridays reconciling records by hand.

EVV-compliant scheduling closes that gap. The idea is simple: the system you use to build schedules should also hand clean, structured visit data to the system that verifies them. This post explains how that hand-off works, what your EVV aggregator actually needs, and where scheduling software's job ends and the certified EVV vendor's job begins.

Key takeaways

• EVV and scheduling are two different systems. Scheduling plans the visit; EVV captures proof that it happened. Good software connects them rather than pretending to be both.
• The federal requirement is narrow but strict. The 21st Century Cures Act mandates EVV for Medicaid personal care and home health services, and it defines exactly six data points every visit must capture.
• States implement EVV differently. Some mandate a single vendor like Sandata; others let you choose and route data through an aggregator such as HHAeXchange or AuthentiCare. Your model determines the integration.
• Scheduling software's role is to export accurate data — authorizations, assigned caregiver, service type, and planned times — so your EVV records match what was authorized.

What "EVV-compliant scheduling" actually means

It's worth being precise, because the phrase gets used loosely. EVV-compliant scheduling does not mean the scheduling tool is itself a certified EVV vendor. It means the scheduling system is built to work with EVV: it captures the data your aggregator requires, structures it correctly, and exports it so the verified visit lines up with the authorization it was billed against.

SchedulerPro is a scheduling platform, not an EVV aggregator. Caregivers still verify visits through your state-approved EVV method — a mobile app, telephony, or fixed device — and that verified record flows to the aggregator. SchedulerPro's job is upstream: it holds the authorization, assigns the right caregiver, plans the visit, and exports that plan so the EVV record has something accurate to reconcile against. Keeping those responsibilities distinct is what keeps you out of trouble.

The six data points every EVV visit must capture

Under Section 12006 of the 21st Century Cures Act, states are required to implement EVV for Medicaid-funded personal care services and home health services. The law is specific about what "verification" means. Every EVV record must capture six elements:

1. The type of service performed
2. The individual receiving the service
3. The date of the service
4. The location of service delivery
5. The individual providing the service
6. The time the service begins and ends

Notice how many of those originate in your schedule, not at the point of care. The service type, the client, the assigned caregiver, and the planned window all come from scheduling. If those are wrong or missing when the visit is verified, the record won't match the authorization — and that mismatch is what gets a claim denied. This is the practical reason scheduling and EVV can't be treated as separate silos.

Sandata, HHAeXchange, AuthentiCare: how the aggregator model works

Most states did not build their own EVV system from scratch. Instead they either selected a statewide vendor or opened the market to several, with a designated aggregator that collects EVV data from whatever systems agencies use and forwards it to the state. Which arrangement you're in shapes how your scheduling data needs to move.

Aggregator	Where you'll often see it	What it does
Sandata	States running a single state-mandated vendor	Provides the EVV system directly and aggregates data for the state
HHAeXchange	"Open" or provider-choice states	Aggregates EVV data from many agency systems and normalizes it for the payer
AuthentiCare (Netsmart)	State-selected and MCO programs	EVV capture plus aggregation for participating programs
CareBridge	Managed-care (MCO) programs	Collects and validates EVV data on behalf of health plans

CMS recognizes several implementation models — provider choice, MCO choice, state-mandated vendor, and open models among them — and states mix and match. In most states you'll either use the mandated vendor's own capture tools or send your data to an aggregator through an approved import. The takeaway for scheduling software is the same either way: it needs to export cleanly into whichever aggregator your state or payer uses.

Where scheduling ends and EVV begins

Think of it as a relay. Scheduling software owns the first leg: it tracks the service authorization, checks that the assigned caregiver is qualified and available, and produces a planned visit with a client, a service type, and a time window. At the point of care, the EVV system owns the second leg: the caregiver clocks in and out through the approved method, capturing the actual location and times that prove the visit happened.

The hand-off between those legs is everything. When scheduling exports the planned visit and its authorization to the EVV aggregator, the verified record has a reference to match against — same client, same service, same caregiver, within the authorized amount. When that export is missing or inaccurate, someone reconciles it manually later. An agency scheduling a couple hundred visits a week across a dozen caregivers can lose hours every week to that reconciliation, and every unmatched visit is a claim at risk.

This is also where authorization tracking earns its keep. EVV confirms a visit occurred; it does not confirm the visit was authorized. If a caregiver verifies more hours than the service order allows, EVV will happily record it — and you'll find out at billing. Scheduling that tracks authorizations against planned and delivered time catches that before it becomes a denied claim.

What to look for in EVV-compliant scheduling software

When you evaluate scheduling tools with EVV in mind, look past the marketing and check for a few concrete things:

• Export to your aggregator. Confirm the tool can send visit and authorization data to the specific aggregator your state or payer uses — Sandata, HHAeXchange, AuthentiCare, or CareBridge — not just "EVV" in the abstract.
• Authorization tracking built in. The schedule should know how much service is authorized and warn you before you over-schedule against it.
• Accurate caregiver and service-type data. Because those feed the EVV record, the scheduling side needs to keep them clean and current.
• Honest scope. A tool that claims to replace your state's EVV system should raise an eyebrow. In most states you must use an approved capture method; the realistic, compliant role for scheduling is to integrate with it.
• Security posture. You're handling protected health information, so the platform should be built on HIPAA-eligible infrastructure with encryption in transit and at rest. (Note that "HIPAA-eligible" describes the infrastructure — compliance ultimately depends on how your agency configures and uses it.)

SchedulerPro is built around exactly this division of labor: it handles authorizations, caregiver assignment, and scheduling, and exports the resulting visit data to the major EVV aggregators so your verified records reconcile cleanly. It doesn't try to be your EVV vendor — it makes the one you already use easier to keep in sync.

See SchedulerPro in action

If manual EVV reconciliation is eating your team's week, see how much of it disappears when scheduling and authorizations feed your aggregator automatically.

Request Early Access

See How It Works