Skip to main content
    CQC Software Requirements: A Practical Checklist for UK Providers
    Compliance

    CQC Software Requirements: A Practical Checklist for UK Providers

    What CQC actually expects from the software that supports regulated care — mapped to the single assessment framework, with a usable checklist.

    Digitalised Solutions Team
    May 29, 2026
    7 min read

    CQC does not certify software, it inspects evidence

    There is no formal "CQC-approved software" list. CQC inspects the service, and the software either makes the evidence easy to produce or it does not. The single assessment framework asks whether services are safe, effective, caring, responsive, and well-led. Every one of those domains depends on what your systems can show on demand.

    A practical checklist

    Use this as a starting frame for any care planning, eMAR, CRM, or rostering platform supporting a CQC-regulated activity.

    Safe

  1. Immutable audit trail on care records, incidents, and medicines.
  2. Role-based access control with least privilege and named accounts (no shared logins).
  3. Medicines administration with refusal, omission, and PRN reasons captured.
  4. Incident, accident, and safeguarding workflows with escalation rules.
  5. Risk assessments versioned, reviewed on a defined cadence, and timestamped.
  6. Effective

  7. Care plans linked to assessed need with measurable outcomes.
  8. Evidence that staff are competent for the tasks they perform (training, supervision, observations).
  9. Outcome data captured consistently enough to report trends, not just events.
  10. Caring

  11. Person-centred fields beyond the regulatory minimum: preferences, communication needs, life history.
  12. Family and advocate communication logged in a way that can be evidenced.
  13. Complaints and compliments captured against the individual and the service.
  14. Responsive

  15. Referral-to-placement and assessment workflows that surface delays.
  16. Capacity, demand, and acuity visible to operations in something close to real time.
  17. Reasonable adjustments and accessible information recorded as structured data.
  18. Well-led

  19. A reporting layer that can produce evidence for a Provider Information Return on demand.
  20. Notifications to CQC tracked against the source incident.
  21. Policy and procedure version control linked to the records that depend on them.
  22. Clear ownership of each system, its configuration, and its data.
  23. Data protection and security baseline

    Sitting underneath all five domains is the security and data protection layer. CQC will not audit your DSPT submission, but a serious failure here is a well-led problem.

  24. UK GDPR and DPA 2018 lawful basis documented per processing activity.
  25. NHS Data Security and Protection Toolkit submission at "standards met" or better.
  26. Cyber Essentials or Cyber Essentials Plus where contracting with NHS.
  27. Processor agreements in place with every software vendor handling personal data.
  28. A documented retention schedule and the ability to enforce it in-system.
  29. Clinical safety where it applies

    If the software supports clinical decision-making, medicines, or care tasks, the deploying organisation should hold a clinical safety case aligned to DCB0160, and the manufacturer should hold one aligned to DCB0129. This is often missed by social care providers who assume the standards only apply to NHS-procured systems. They apply wherever the software is being used as a health IT system.

    Common gaps we see in reviews

  30. Audit trails that exist but are not enforceable because users share logins.
  31. Care plans that are person-centred in narrative but unstructured for reporting.
  32. eMAR data trapped in PDF exports rather than queryable records.
  33. Reporting assembled manually each month, with no replayable definition.
  34. No single owner for data quality across the estate.
  35. Turning the checklist into a plan

    A list of gaps is not a plan. The useful next step is to score each gap by likelihood of inspection exposure, cost to remediate, and dependence on other systems — then sequence the work. Most providers find that two or three structured changes remove the majority of risk.

    If you want an independent read on your current position, our Compliance Automation practice produces a prioritised remediation plan against the single assessment framework. For the broader software estate, the Healthcare Software Solutions hub sets out how compliance fits alongside CRM, integration, and reporting work.

    Healthcare software decisions

    Turn research into a practical review of CRM, CQC evidence, reporting, integrations, and operational risk.