What California FMS providers need to know about EVV

Electronic Visit Verification (EVV) sits at the intersection of federal mandate and California-specific implementation, which is why it's also the area where FMS providers most often discover something they thought they were doing right wasn't quite enough.

What EVV actually requires

EVV captures six data points each time a worker delivers a covered service:

• The type of service performed
• The individual receiving the service
• The date of the service
• The location of the service delivery
• The individual providing the service
• The time the service begins and ends

The 21st Century Cures Act sets the federal baseline. California's Department of Developmental Services (DDS) implements EVV for the Self-Determination Program with specific guidance on which service codes require EVV, what counts as a valid location capture, and how exception cases must be documented.

The exception report is where audits start

Most EVV audits don't start with "show me your clock-ins." They start with "show me your exception report." Every time a worker can't capture clean EVV — bad GPS, dead phone, missed clock-in — that exception needs a documented reason and an admin acknowledgment. A clean log of clock-ins isn't enough on its own; you need to prove your handling of the cases that didn't go clean.

Common pitfalls

• Manual entries without documented reason. If a worker fills in a shift after the fact, FMS workflows need to capture why — forgot to clock in, phone battery died, no signal — not just accept the entry blindly.
• Admin overrides without justification. When an admin approves an EVV exception, the system needs to capture the override reason. Audit logs that don't include the why aren't useful audit logs.
• EVV for the wrong service codes. Not every California SDP service code requires EVV. Running EVV checks against codes that don't need them creates false exceptions and trains workers to ignore the system.

How FMSLio handles EVV

FMSLio captures the six data points at clock-in, validates them against the service code's EVV requirement, and generates exception reports per worker, per participant, and per date range. Manual entries collect a reason category and free-text justification before they can submit. Admin overrides are audit-logged with the approver's identity, the override reason, and a timestamp. Audit-ready by design.