We built the incident log a CQC inspector actually wants to see
ResponzHub started with a simple complaint we kept hearing from care home managers: incident logs were either a folder of paper nobody trusted, or a spreadsheet nobody backdated honestly. We built something built for the job.
Why care homes, specifically
CQC-registered services already run on a system of record — usually Datix or Ulysses. What's missing is the fast, mobile layer in between: the moment an incident happens and the moment it's properly logged.
That gap gets filled with sticky notes, group chats, and end-of-shift memory. None of it survives an inspection well. So we built ResponzHub to sit in that gap: a 60-second mobile log, a timestamped audit trail, and a clean handoff back to the system your governance team already trusts.
We started with care homes because the stakes — safeguarding, falls, medication errors, restraint — are the highest, and the paperwork burden on front-line staff is the heaviest. The same model now also serves dental practices and independent schools with their own regulated incident duties.
What we hold ourselves to
Fast enough to actually get used
If logging an incident takes longer than the incident itself, staff route around it. Every template is built to be completed in under a minute, on the device already in someone’s pocket.
An audit trail that holds up
Entries are timestamped the moment they’re created and can’t be silently edited or backdated. What your inspector sees is what actually happened, in order.
A complement, not a replacement
ResponzHub isn’t trying to replace Datix or Ulysses. It’s the fast front end that feeds your existing system of record with clean, complete data.