EVV Software for Colorado Home and Community-Based Services

Capture at the point of service

A caregiver opens the app, sees their schedule, and clocks in. Location is captured from the device, the service type comes from the client's active authorization, and start and end times are stamped rather than typed. Documentation for the visit happens in the same flow, so there is nothing to reconstruct at the end of a shift.

Where connectivity is unreliable, visits are recorded offline with their original timestamps and location fix and sync automatically once the device reconnects. Where a smartphone is not appropriate, a telephony fallback verifies the visit from the member's phone.

Validation before transmission

• Authorization checks: active authorization, available units, matching service code.
• Location checks: GPS fix compared against the expected service location.
• Staff checks: assigned caregiver with current, unexpired credentials.
• Completeness checks: required documentation and signatures present.
• Exceptions routed to a correction queue with the reason attached.

Transmission and reconciliation

Clean visits transmit to the state aggregator on a schedule, and every response is stored against the visit. Rejections arrive in a work queue with their reason rather than sitting in a portal. Supervisors see open exception counts on their dashboard, and every transmission is retained for audit.

One verified record, three downstream uses

• Payroll hours generated from verified visits, not from separate timesheets.
• Medicaid 837 claims generated from the same verified visits, so billing matches EVV.
• Family portal visibility into completed visits without manual updates.

What EVV replaces in a Colorado agency

Most agencies arrive at EVV with three parallel records of the same shift: a paper or spreadsheet timesheet, a schedule that may or may not reflect what happened, and a separate portal entry made after the fact by an office coordinator. Each of those is a place for hours to disagree, and reconciling them is a recurring, unbillable cost that grows with headcount.

A single verified visit collapses all three. The scheduled shift sets the expectation, the caregiver's clock-in and clock-out create the record, and the service documentation is attached to that same record. Coordinators move from re-keying time into a state portal to working a short exception queue, which is a fundamentally smaller job. Agencies that make this change usually notice it first in the week after a pay period closes, because the reconciliation meeting has nothing left to reconcile.

It also changes what an audit looks like. Instead of assembling evidence from several systems and hoping the timestamps agree, you produce one record per visit with its location fix, its aggregator response, its documentation, and its claim — already linked.

Rollout without a coverage crisis

EVV rollouts fail on the frontline, not in the office. OutcomeGrid implementations typically start with one program or one office, run parallel for a short period so supervisors can compare verified visits against the timesheets they trust, and expand once exception volume settles. Caregivers are trained on the app during a normal shift rather than in a classroom, because the workflow is a single tap at the start and end of a visit.

Exception handling is deliberately the first thing supervisors learn. Early in a rollout, most exceptions are process artifacts — a caregiver who forgot to clock out, a service location whose address in the system does not match where care is actually delivered — and clearing them quickly is what keeps transmission clean once volume ramps up.