Bespoke governance software for care homes

A care home for elderly residents has to be able to show its work. Not eventually, and not “give us a fortnight to dig it out” — on the day, in the room, while an inspector is asking.

The Care Quality Commission judges a home on whether it is safe, effective, caring, responsive to people’s needs and well-led. Every one of those is a question about evidence. Is the medication audit up to date? When was the last fire drill, and who attended? Has this resident’s weight been recorded, and did anyone act on the fact that it’s been falling for three months? Was the local authority notified within the statutory window?

The volume was the problem

Our client could answer all of that. What they couldn’t do was answer it quickly, or be confident the answer was the same in every one of their homes.

• Several hundred distinct forms, almost all of them Word documents or Excel workbooks, covering everything from infection control audits to kitchen temperature logs.
• Statutory notifications to local authorities and regulatory bodies, each with its own deadline and its own consequences for missing it.
• Resident-level records — medications, weights, nutrition, falls, behaviour, care plan reviews — that need to be both a live working document and a permanent, tamper-evident history.
• Version drift. When the master audit form gets updated, thirty homes are still using four different older copies, and nobody knows which.

And then the group problem

Manage one home and it’s a hard job done with the wrong tools. Manage twelve and it becomes something else entirely. A senior team is accountable for governance across the whole group, and had no way to see it — no way to ask “which of our homes is behind on audits this month?” without ringing round and waiting for someone to check a folder.

The honest summary of the brief was this: they wanted a single system that held the lot, adapted to how each individual home works, and gave the board a live view across all of it. They’d looked. That software didn’t exist.

You cannot design a system for care governance from the outside. So before any of the real build started we catalogued every form the group used, and sat with home managers while they did the work — because the form tells you what gets recorded, and only the manager tells you why, when, and what happens if it’s late.

Two things came out of that which shaped the entire architecture.

Nothing is hard-coded

No two homes are the same. Nursing care, general residential care and dementia care have genuinely different requirements, different risk profiles and different paperwork. Even two homes doing the same thing do it slightly differently, and both are right.

Hard-code the forms and every one of those differences becomes a change request sitting in our queue. So we didn’t. Every form, audit, field, validation rule and output in Guardian Care is declared in a JSON template, and the templates drive everything — how a form renders, what it will accept, how it scores, and what comes out the other end as a report.

The practical effect: a new audit type is a template, not a release. Tailoring a form to how one particular home runs is configuration, done in minutes, with no developer involved and no risk to the other forty-nine.

A database shaped like the data

The records are documents, and no two shapes match — a medication round and a kitchen temperature log have almost nothing in common. So the store is a NoSQL document database with live indexing: it takes documents of any shape, and because the indexes are maintained as data lands, retrieval is instant. That matters more than it sounds. “Instant” is the entire product promise when someone’s stood in front of an inspector.

A React front end built for a busy shift, not an analyst

The interface is React, and the design brief for it was blunt: it has to be usable by a carer on a shared tablet, mid-shift, who has not been trained on it and has better things to do. Big targets, obvious next steps, no dead ends, no way to lose half-finished work.

On top of that sits the group structure — home, region, group — with role-based permissions so people see exactly their own patch, roll-ups so directors see across all of it, and a full audit trail underneath, because in a regulated setting “who changed this, and when” is not a nice-to-have.

There is a great deal of complexity in this application. Almost none of it is visible to the person using it, which was the point.

Every audit, record, notification and care document the group holds now lives in one system, in the right format, retrievable in seconds. That alone justified the build. But storing things properly turned out to be the least interesting thing it does.

It makes patterns visible

A folder can only ever tell you about one thing at a time. Data tells you about all of it at once. Because everything is captured in a structured way, Guardian Care can show a home things that were always true but never legible:

that falls are clustering in one corridor at one time of day; that weights are drifting downward across a particular floor; that one audit area has been scraping a pass for four months running and is about to become a real problem. Those are the findings that stop an incident happening rather than documenting one after the fact.

And it scales to the group

The senior team opens one screen and sees governance across every home they’re responsible for — what’s complete, what’s overdue, where the soft spots are. Preparing for an inspection stopped being an exercise in ringing round and became an exercise in reading a dashboard.

How it’s landed

It’s fast, it holds up under a thousand-odd daily users, and the feedback from the people who actually use it has been good — which for internal software is a much higher bar than it sounds.

The response we’re most pleased with came from the regulator’s side. Inspectors who have seen the system in use have been positive about it, and specifically about how resident-centred it is: the resident is the thing the records are organised around, not the form.

Why we’re showing you this one

Because it’s the clearest example of what we mean by bespoke. This wasn’t a template with a logo dropped in. It’s a genuinely complex platform, built around how one industry actually works, in a space where the off-the-shelf option didn’t exist — and it’s now the system of record for a thousand people’s working day.

If you’ve got a problem in that shape, it’s the conversation we most enjoy having.