The Evidence Tracker and Policy Data Bank: how a compliance platform actually works

Strip a CQC compliance platform down to its essentials and two ideas do almost all of the work: a matrix that links every requirement to its evidence, and a library of policies that can be reused across services rather than written from scratch each time. Everything else is built on top of these two.

The Evidence Tracker

Think of it as the gap-analysis spreadsheet’s structure, made real. One axis is every requirement under the five key questions: Safe, Effective, Caring, Responsive, Well-led. The other is the evidence that’s meant to prove each one, whatever form that takes, a policy, a certificate, a training record, a log.

Each cell carries a status. Commonly Red, Amber or Green, though the underlying idea is finer than a traffic light: is there real, current, in-date evidence (proven), is it inferred from something adjacent like a reference spreadsheet, or is it simply claimed, with nothing behind it. Anything short of proven gets a gap description and a proposed action, the same way a consultant’s report would flag it.

The part that makes this more than a checklist is that clicking a cell should show you the actual document behind it, not just a status someone typed in. If the evidence isn’t real and current, the cell can’t honestly be green.

The Policy Data Bank

A policy written once, generically, against a requirement, is only half useful. A safeguarding policy for an 18-bed residential care home isn’t the same document as one for a domiciliary care agency sending staff into people’s own homes, even though they’re answering the same underlying requirement.

The Policy Data Bank is that library, authored once per requirement and then tailored by provider type and by service, so a care home, a GP practice and a dental practice each draw the version that actually applies to them, rather than a manager starting from a blank page every time a new service is set up.

Updated centrally, it also solves the quieter problem: when guidance changes, everyone using that policy should get the update, not just whoever happens to notice.

Why neither works alone

A tracker with nothing real linked behind its cells is a checklist, useful for spotting gaps once, useless for proving anything at inspection. A policy library with no tracker checking it against reality is a folder nobody ever revisits until something goes wrong.

Put together, they answer the only question that actually matters when an inspector asks about a requirement: where’s the proof, and is it current. Everything a compliance platform does above this, dashboards, gap scans, inspection-ready exports, is a different view onto the same underlying matrix.