Domiwise Smarter care. Better outcomes.

For UK home-care agencies

The care is good.
The evidence should say so.

Domiwise records the things an inspector asks about — DBS dates, missed-visit reasons, care-plan changes, who opened which record — as a by-product of running the rota, not as a separate job someone does on a Friday.

Book a demo
The Domiwise dashboard, showing counts for active clients, team members, open tasks, overdue tasks and reviews due, above a list of recent activity.

DBS compliance

Is every DBS in date?

Each carer's DBS carries a status worked out from its expiry date — valid, expiring, expired — so the certificates that need chasing surface on their own. Nobody has to keep a spreadsheet in step with reality.

The team roster, listing carers with role, status and a DBS column showing one expired certificate, one expiring, and three valid.

Missed visits

Why was that visit missed?

A visit cannot be marked missed or cancelled without a reason. The reason and the change itself are both kept, with the time they were recorded — so the answer already exists on the day somebody asks for it.

A visit record marked missed, showing the miss reason 'Client unavailable — hospital appointment' and a status history entry reading planned to missed with the same reason and a timestamp.

Access trail

Who opened that record?

Every action against a client record is written to an audit log — who, what, and when. It is read-only, and an auditor can be given it without being given the run of the system.

The audit log, a table of entries with columns for when, action, entity and actor, including visit transitions and record creations.

Care plans

What does the care plan actually say?

Structured sections — medication, mobility, mental capacity, risks, preferences — rather than one free-text box nobody wants to read. Changes create a new version instead of overwriting what was there before.

A client's care plan, with sections for personal care, medication, mobility, nutrition, communication, mental capacity, risks and safeguarding, preferences, and religious and cultural needs.

Underneath

You are handing over your clients' health records. That deserves specifics.

Separated at the database

Your agency's records are isolated from every other agency's by the database itself, not only by application code that has to remember.

Stays in the UK

Hosted in AWS London. Data is not replicated outside the United Kingdom.

Encrypted, enforced

Encrypted at rest with keys held in your region, and in transit. The database refuses connections that are not encrypted.

Four roles, least privilege

Admin, manager, care worker, auditor. A care worker reaches the people they are assigned to and no further.

Where Domiwise is today

Early, and honest about it.

Everything above is built and running. What it is not yet is in daily use at a live agency — and we would rather tell you that than have you find out in the third meeting.

We are looking for a small number of founding agencies to shape what ships next. That means the awkward parts of your service get designed for while the product is still soft enough to change, instead of being worked around for years.

If that sounds like the right kind of early, it is worth a conversation now rather than later.

Talk to us

Half an hour, with your own service in mind.

Book a demo

or email hello@domiwise.co.uk