Proving the Visit Happened: An Audit Trail Home Care Can Assemble in an Afternoon

A funder audit lands and asks about visits delivered nine months ago. The agency knows the care happened. Proving it means opening a schedule that records what was planned, a box of paper notes that record what a caregiver wrote afterwards, and a care plan that has been revised twice since. Three people spend four days assembling an answer, and the answer is still partly an argument rather than a record.

This is the transformation we would run for that agency. It is presented as a concept, built on the same method we use in client engagements, so the before, the after, and the path between them are all visible.

Why is proving it harder than doing it?

Because the systems record intention, not delivery. A scheduling system stores the visit that was planned. If a caregiver arrived twenty minutes late, completed four of five tasks and could not complete the fifth because the client declined, none of that has anywhere to live except a paper note written from memory at the end of a shift.

Home care is a measured sector. The Canadian Institute for Health Information publishes home care indicators at health region and provincial level, including caregiver distress among long-stay clients. There is no published Canadian index of what audit response costs an agency, so this study does not quote one; the CAQH Index 2025 puts annual US staff time on routine provider-to-payer administrative transactions at $83 billion, which sizes the category and nothing more.

The structural point is simpler than any statistic. Evidence assembled after the fact is reconstruction, and reconstruction is expensive and weak. Evidence captured as the work happens is a record, and it is nearly free.

Before and after: the visit record

Drag the handle. The before is a planned visit plus a paper note; the after is the delivered visit as it is captured.

The caregiver’s job does not get heavier. What changes is that a structured check-in replaces an unstructured write-up, and the exception a caregiver used to mention verbally now has a field.

What we built

The concept above is the output of the same engagement steps we run in client work, and several are decisions a competent peer could argue with.

• We capture delivered rather than planned, which sounds obvious and is the entire architecture. Every downstream capability, audit response, funder reporting, quality review, follows from the record describing what happened instead of what was scheduled.
• We refused location tracking between visits, audio recording, and per-caregiver scoring. All three would have improved the evidence and all three would have changed the relationship with a workforce that is already under strain, which would have cost more than it returned. An agency that wants them should hire someone else.
• We surface a missing check-in as missing rather than inferring it from the schedule. Filling that gap automatically would manufacture evidence, which is a worse position than an honest hole.
• We capture slightly more than any one funder currently asks, bounded by what the care plan justifies collecting, so that a changed requirement is usually answerable from what already exists.
• We wire evals from day one against the agency’s own historical audit responses, scored on whether the captured record would have answered the questions actually asked.

How it works

The scheduling system stays the source of truth for what was planned. At the visit, a caregiver checks in, marks planned tasks complete or not, and records any exception in structure rather than in prose. Missing check-ins surface to a supervisor within the week, while the visit is still rememberable, and are resolved with the caregiver rather than silently completed. When an audit arrives, the response assembles from those records, and anything genuinely absent is reported as absent.

Because visit records and client details stay in Canadian infrastructure and processing runs with zero data retention, the design lines up with what PHIPA expects: a privacy impact assessment before deployment, an agreement naming the processor as an agent under section 17, an audit log on every access, and deliberate data minimisation, which is the principle Ontario’s privacy commissioner set out for healthcare AI deployments in January 2026.

Why this pays back

The return is staff days not spent reconstructing the past, plus a reduction in the risk that a defensible service cannot be defended. Break-even for the first slice is about nine full audit-response days removed a year at the agency’s own loaded administrative cost.

The limit worth stating before anyone signs, and it can lose the sale: this improves records from the day it is turned on and does nothing whatsoever for the nine months already behind you. An agency facing an audit right now should not buy this to solve that audit, because it will not. It is worth buying the week after the audit closes, which is exactly when nobody wants to think about it.