Getting CQC inspection-ready

For care providers a CQC inspection should not mean a week of panic. The work that makes an inspection calm is not done in the week before it, it is done by keeping a continuous, dated record that is organised the way inspectors actually think, by the five key questions: Safe, Effective, Caring, Responsive and Well-Led.

Be clear about what ships today

Honesty first, because it affects how you plan a rollout. A dedicated Health and Care template pack is on our roadmap and is not available yet. The Construction pack is the one that ships today.

What does work today is the engine underneath: digital forms and registers, recurring scheduled checklists, briefings with signed sign-off, incident reporting and the evidence pack compiler. Those are configurable for a care setting now, and everything described below is built on them. If you would rather wait for a ready-made care pack, that is a reasonable decision and we would rather you made it with the facts.

Organising evidence by key question

The mapping matters more than the tooling. Every audit, supervision record, training certificate and incident belongs under one of the five key questions, and tagging them that way once means a request for evidence becomes a retrieval rather than a reconstruction.

In practice that looks like:

• Safe: environmental and health-and-safety checks, incident and safeguarding reports, fire and water safety records, medication audits.
• Effective: mandatory training records, competency sign-off, care-plan reviews.
• Caring and Responsive: supervision records, complaint handling, resident and family feedback logs.
• Well-Led: audit completion rates, governance meeting records, action tracking.

Registers stop the quiet failures

The failures that hurt at inspection are rarely dramatic. They are a lapsed DBS, a missed refresher, a certificate that expired in a drawer. Held as register items with expiry alerts, those dates surface before they lapse.

Registers also support assignment blocking, so where you choose to enforce it, a task cannot be allocated to someone whose record does not yet cover it. This is a policy you switch on deliberately, per requirement, rather than a blanket rule.

The audit calendar does the chasing

Daily, weekly, monthly and quarterly checks generate themselves on schedule: fire alarm tests, water temperature checks, medication audits, infection control audits and care-plan reviews. Because each is timestamped as it is completed, the result is a continuous record rather than a folder with gaps where somebody was on leave.

Incidents, logged and escalated

Safeguarding and accident reports are captured as structured forms with photo evidence and signatures, then routed to the right manager for approval. The record of who reported, who reviewed and when is written to an append-only audit log.

What OpsCores does not do

• It is not an eMAR and does not handle dose-level medication administration. That stays with your clinical system.
• It does not file notifications to CQC for you. It holds the evidence behind them.
• We hold no SOC 2 certification and publish no uptime SLA, and we will not claim either until they are real. Data is held on servers in Germany, inside the EU, with row-level tenant isolation and an encrypted vault for special-category records such as induction health answers, where every read is audited.

See how the same engine handles care-setting compliance and what a CQC evidence pack contains.