ClientCentric

Features · EVV

Verification without theater.

Electronic visit verification exists to prove a visit happened — not to surveil staff or to paint red marks on services that never required it. ClientCentric draws both lines exactly where they belong.

How EVV works in ClientCentric: staff clock in and out from their own view; location is captured at those two moments only — never tracked between them. Anything irregular becomes a visit exception with its evidence attached: late clock-in, missing clock-out, a location outside the expected area, low location accuracy. Exceptions queue for human judgement. Services that do not require EVV display not applicable — never a failed-looking “no.” Compliance math counts only the visits that required verification.

Exceptions are the product working, not failing

Real operations produce irregular visits: a ride ran late, a phone died, GPS drifted in a rural driveway. A system that hides those is lying; one that punishes them indiscriminately teaches staff to game it. ClientCentric queues each exception with what actually happened and hands it to a reviewer — resolved with judgement, on the record.

  • Location at clock-in and clock-out only — captured, shown, and never streamed
  • A forgotten clock-out auto-closes after a configured wait, as an exception — never as invented data
  • Per-service verification requirements: remote and community services configured honestly
  • Compliance percentage computed over EVV-required visits only
  • Aggregator integration status stated truthfully — configured is not connected until verified for your deployment
ClientCentric EVV page: exception cards with evidence and review actions, integration status banner, and compliance computed over required visits only

Every count opens its list. The exception number equals the reviewable cards behind it — a figure that cannot be clicked is decoration, and these all can.

Clock a visit in the staff demoBook a walkthroughNo signup. Fictional data. Everything resets on refresh.

Keep reading

Written and maintained by the ClientCentric team from the working product. Last reviewed .