Home and community based services software that works where your staff do. In the field.

The note written in the driveway. The visit happened at a kitchen table. The note happens in the car afterward - on a legal pad, or in a phone memo the worker swears they’ll type up tonight. By Friday there are three visits in their head and they’ve started to blur. The note that finally lands in the file was written from memory, days after the encounter it’s supposed to support.

The 2:15 cancellation. The client texts “not today” when your worker is already forty minutes out. The hour dies in a gas station parking lot. Multiply that across a team and a month, and a chunk of your billable time quietly evaporates - and nobody can tell you how much, because cancellations live in text threads, not in any system.

The mileage spreadsheet nobody believes. Reconstructed at month end from memory and a maps app. Finance contests it, workers resent it, and if an auditor ever compares the mileage log to the visit log, you’d rather not be in the room. It’s the most argued-over document in the agency and the least trustworthy.

The field goes dark at 9 a.m. Once the cars leave, a supervisor’s only window into the day is whatever paper shows up later. Which visits actually happened? Is anyone stuck at an address that made them uneasy? If a lone worker doesn’t check back in, who knows which house they were at? Right now the honest answer is: nobody, until it’s written down.

The driveway note → written in the moment, with KORA helping. Staff document on a phone during or right after the visit, and KORA helps get the note finished before the engine starts - signed and time-stamped the second it’s saved. The whole in-home services case management file travels with the worker: face sheet, contacts, service plan, encounter history. And because the note is done, the claim is already forming - billing builds straight from the finished encounter, no re-typing at a desk.

The cancellation → the schedule everyone can see. When a visit falls through, the slot opens on the calendar where the supervisor and the worker both see it - so a make-up visit slides in instead of an hour dying in a parking lot. The cancellation itself is logged with a reason, which means at month end you finally know how much billable time reschedules are eating, per worker and per client.

The mileage spreadsheet → mileage tracking on the visit itself. Miles are captured on the encounter form, at the visit, by the person who drove - not rebuilt from memory on the 30th. Your setup puts the mileage field on your forms with your wording, and totals roll up for reimbursement without a spreadsheet argument.

The dark field → a record that lights up as it happens. Every saved note tells the supervisor a visit occurred - who, where, when, how long - while the worker is still in the driveway, not next week. Safety protocols for lone workers run as automatic follow-ups: the check-in that doesn’t happen becomes a flag, and an incident written on a porch routes to a supervisor’s signature automatically.

7:40 a.m. - A worker checks the day on her phone: four visits across two counties, one moved to Friday overnight. Her supervisor’s board shows every worker’s route the same way - nobody prints a schedule.

9:20 a.m. - First visit, a kitchen table. Skills work gets documented in the moment; the note is signed in the driveway before she pulls out, mileage on the same form. Done means done.

12:50 p.m. - A cancellation text. The open slot shows on the calendar, a make-up visit for a nearby client slides in, and the missed encounter is logged with its reason instead of vanishing into a text thread.

3:05 p.m. - Something at a home visit doesn’t feel right. The worker writes the incident on the porch, on the format the state expects; it routes to her supervisor before she’s back on the highway, and the wraparound team sees it ahead of the family team meeting.

End of month - The encounters staff already wrote become the claims. The mileage they already logged becomes the reimbursement. The supervisor reads the field’s month without collecting a single sheet of paper.

Home and community-based programs live under Medicaid waiver rules and state licensing: an encounter note behind every billed unit, services matching the service plan, visit details - worker, client, time in and out, place of service - that hold up to verification, training and background checks current, incident timelines met. Kordera captures all of it as a side effect of the visit itself, with every entry signed and time-stamped in the field and an integrity-checked audit log underneath.

When your state pulls a sample of claims, each one traces to a real note written the day of the visit - not a quarter’s worth of paper reconstructed the week before the review. That’s the difference between an audit and a bad month.