CT EVV — GPS verification

GPS visit verification, end to end.

GPS captured at check-in, then every 5 minutes throughout the visit, even when the phone is locked. Movement detection alerts on drift over 500m. Tamper-evident audit trail on every reading. The proof when a billing dispute or state audit lands.

Schedule a demo How GPS verification works

Every 5 min: GPS sync interval during visits
500m: Movement detection alert radius
Tamper-evident: Cryptographic audit chain

What gets captured

Location data on every visit

Initial GPS at check-in plus continuous tracking during the visit, with movement detection and complete audit trail.

Latitude/longitude at check-in
Continuous GPS waypoints every 5 minutes
Background tracking when app is closed
Movement detection alerts (>500m drift)
Tamper-evident logs — edits are detectable

Background-capable

Works when phone is locked

Offline-resilient

Caches locally, syncs on reconnect

Hardware-backed auth

Biometric login per check-in

Privacy-aware

GPS only during active visits

Why this matters

GPS that only fires at check-in is not actually verification.

Many EVV systems capture a single GPS reading at check-in and call it 'verification.' That's enough to satisfy the federal Cures Act on paper, but it doesn't verify what actually happens between check-in and check-out. A worker could check in at the consumer's home, drive somewhere else, and check out four hours later with no record of where they actually were. The location data point exists, but the verification doesn't.

CT EVV captures GPS continuously during active visits — a waypoint every 5 minutes throughout the visit, captured even when the phone is locked, the screen is off, or the worker switches to another app. Movement detection alerts fire if the worker drifts more than 500m from the check-in location, prompting either 'Still with consumer' or 'Check out now.' The result is GPS verification that actually means something: visible staff path, defensible visit duration, and detection of the patterns that look like fraud.

Every GPS reading is part of a tamper-evident audit chain. Cryptographic signing means a captured location can be verified later as authentic. Edits to visit records are themselves logged with attribution and timestamps, so any post-visit modification is detectable. When a billing dispute lands or a state audit asks for evidence, the GPS data isn't just present — it's defensible.

What real GPS verification gives you

Visible staff path — admin web view shows the route from check-in to check-out
Defensible visit duration — not just timestamps but locations throughout
Movement-detection alerts — flag drift in real time, not after the dispute
Tamper-evident logs — edits are themselves logged, integrity verifiable
Privacy-aware design — GPS only during active visits, never at rest

How GPS verification works in CT EVV

The location-tracking capabilities CT EVV delivers.

GPS captured at check-in

When the worker checks in, the app captures latitude/longitude immediately. The address picker in the app helps verify it's at the consumer's location: registered addresses, nearby known facilities within 0.25 miles, or 'Other' with required notes.

Continuous GPS during active visits

Throughout the visit, GPS readings are captured every 5 minutes. The capture continues even when the phone is locked, the screen is off, or the worker switches to another app. Background-capable on both iOS and Android.

Movement detection alerts

If the worker drifts more than 500m from the check-in location, an alert fires: 'Still with consumer' or 'Check out now.' This catches the case where a worker forgot to check out and left the location, before it becomes a problem.

Offline-resilient capture

Spotty cellular signal? GPS readings cache locally and sync as soon as connectivity returns. Active visits never lose data because of signal issues. The worker's experience is the same regardless of connectivity.

Admin map view with staff path

Office team gets a live Google Maps view of every visit: check-in location pin, full staff path during the visit, check-out location, and any movement alerts. Filter to alerts only to focus on visits that need follow-up.

Tamper-evident audit chain

Every GPS reading is part of a cryptographically signed audit chain. Edits to visit records are themselves logged with attribution and timestamps. Forensic review can detect any post-visit modification. Defensible under audit.

What it looks like in practice

A few ways teams use this.

Movement-detection alert in real time

Caregiver checks in at consumer's home for an 8-hour visit. Two hours in, worker leaves to grab lunch and forgets to pause the visit. App detects 850m drift, fires an alert: 'Still with consumer? Check out now.' Worker sees the alert, checks out, returns later and starts a new visit. The would-be timeclock fraud doesn't happen.

Billing dispute three weeks later

Insurance disputes a visit, claiming services weren't provided as documented. Office staff pulls the visit's complete record: check-in GPS at consumer's address, continuous GPS throughout 6 hours showing worker stayed within 50m of check-in, check-out at the same location, signed signature, audit log showing no edits. Dispute closes in agency's favor with defensible evidence.

State audit reviewing a quarter of visits

Audit team requests evidence on 30 visits. Admin view exports each one's complete GPS history with cryptographically verifiable timestamps, plus the full audit trail showing no post-visit edits. The integrity of the data is mathematically demonstrable, not just procedurally claimed. Audit closes without findings on the EVV side.

Frequently asked

Common questions about GPS visit verification.

How often is GPS captured during a visit?

Initial GPS reading at check-in. Then continuous waypoints every 5 minutes throughout the visit. The 5-minute interval is configurable per agency for cases where more frequent or less frequent capture makes sense, but the default is the standard most agencies use.

Does GPS tracking continue when the phone is locked or the app is closed?

Yes. The mobile app uses background location services on both iOS and Android — GPS continues to capture even when the phone is locked, the screen is off, or the worker switches to another app. The active-visit timer also continues running. Workers don't have to keep the app open.

What about privacy when a worker isn't on a visit?

GPS is only captured during active visits. When a worker is not checked in, no location data is collected. The platform respects the worker's privacy off the clock. iOS and Android both surface this clearly to workers when they install the app.

What happens if cellular signal is weak or non-existent?

GPS readings cache locally on the device. As soon as connectivity returns, cached readings sync to the platform with their original timestamps. Active visits don't lose data because of signal issues. The worker's experience during the visit is identical regardless of signal.

Can a worker disable GPS to avoid being tracked?

If a worker disables location services on their phone or denies the app permission, the app surfaces this clearly and check-in cannot proceed. The agency configures whether GPS is required for check-in (the standard for Cures Act compliance). Workers cannot silently bypass tracking; either GPS is on and the visit is verified, or check-in fails and the agency knows.

How is the GPS data secured against tampering?

Every GPS reading is part of a cryptographically signed audit chain. The mathematical structure means a reading cannot be silently altered after capture — any modification breaks the signature chain and is detectable. Edits to visit records are themselves logged as separate events with attribution. Forensic review can verify the integrity of the GPS history.

GPS verification that holds up under scrutiny.

Schedule a demo and we'll walk through how CT EVV's continuous GPS capture, movement detection, and tamper-evident audit trail look in practice.

Schedule a demo Back to CT EVV