CQC Provider Regulatory Decision Layer / guide

When should a CQC provider check statutory notification requirements?

For an already-operating or registered provider, an incident or post-registration event can raise a statutory-notification question. The first useful step is to organise the facts and identify what still needs human or regulator confirmation. This page is practical information, not legal advice or a CQC determination.

Why these questions are easy to get wrong

A short incident description may omit the fact that changes the route. Similar-looking events can have different notification implications, and a provider may need to distinguish an incident from a service disruption, absence, detention, or change-related question. A structured pre-check helps expose missing facts; it does not replace the provider’s responsibility to confirm the applicable requirement.

Prepare these facts first

• Choose the supported notification question that best describes the event.
• Record whether the event relates to a regulated activity when that distinction matters.
• Gather the relevant yes/no facts about injury, abuse concerns, safety, welfare, police involvement, service disruption, staffing, utilities, or other event-specific conditions.
• For absence, detention, DoLS, Mental Health Act, health-service-body, or statement-of-purpose questions, prepare only the facts relevant to that route.
• Note what is unknown. Do not fill a gap with an assumption merely to obtain a cleaner answer.

Why source linkage matters

A useful result should show the evidence basis behind the rule or route, not just a bare label. The existing CQC decision service links decision-bearing outputs to monitored official-source material and can withhold a conclusion when evidence is stale, changed, conflicting, unavailable, or incomplete.

When manual review is still necessary

• the facts do not clearly fit one supported notification route;
• the event combines several circumstances;
• the evidence or source status is not current or conflicts;
• a deadline, exception, provider-specific fact, or regulator communication needs confirmation;
• the outcome is REVIEW, or the engine preserves an unresolved condition rather than guessing.

What the structured pre-check can do

The existing human workflow accepts the structured notification facts already supported by the deterministic engine. It first gives a bounded readiness explanation: whether the question is sufficiently specified, whether it is in scope, and whether manual review may be needed. A separate checkout-intent step can be used to express interest in an evidence-linked report. No card details are collected and the human-report price is confirmed before payment.

Machine integrations continue to use the existing x402 statutory-notification route. This guide does not change CQC rules, prices, or the human workflow.