Product
One system for the whole round
Records, rosters, the carer app and the office day board share one database, one audit spine and one permission model. Families and money come in phase two. Medication records come last, with a safety case.
Modules and phases
Built in the order that keeps people safe
Designed offline-first
The day pack for each carer is built before the round. Every write on the phone is an event with its own id, queued and sent in order; the server accepts each once and rejects individually with a reason a person can read. Nothing merges silently.
An audit spine, not an audit feature
Every write records who, in which role at the time, when, and what changed. The timeline, check-ins, medication administrations and the audit log are append-only: nobody, including an administrator, can update or delete them.
Your data, exportable
Your data stays in the UK/EEA, you are the data controller, and everything is exportable in open formats at any time.
Shape
How Kindround is shaped
| Area | Typical suite | Kindround |
|---|---|---|
| Pricing shape | Modules priced separately, add-ons per user | One platform. Terms agreed in writing at commercial grade. No module maze. |
| Onboarding | Weeks of configuration by the vendor | Discovery week with the registered manager, then a pilot group first |
| Offline working | Often partial | Designed offline-first: the day pack loads before the round, events queue and sync |
| Records | Editable history | Append-only timeline, check-ins and audit. Corrections are new entries, never edits |
| Your data | Export on request | You are the controller. Open-format export at any time, UK and EEA residency |
| Medication records | Included from day one | Deliberately last, with a clinical safety case and a parallel paper run |
| Claims | Badges on the homepage | A roadmap that says held, in progress, planned or not claimed |
See Kindround on a real round, on your own visit types and funders.