Policies should describe the service you will actually run.
A registration application describes the proposed service. The policy framework should support that operating model instead of sitting beside it as generic paperwork.
The standard Monad policy route
QCS is the standard policy route for the Monad Build Phase because a new provider needs a maintained policy framework that supports the proposed service from registration day. This is a Monad programme requirement: CQC does not require an applicant to buy QCS.
Before Pheon accepts a provider into Build, the provider must either hold an appropriate active QCS account or agree to obtain one. Customers without QCS are referred through Pheon. Any customer discount is subject to the current QCS referral terms. No fixed discount is promised.
Why policies matter
Policies are where the proposed service’s promises become operating rules: safeguarding, recruitment, training, medicines, complaints, records, quality checks, continuity and risk. If the application says the provider will do one thing but the policy framework cannot support it, the case starts to look like theory rather than a service ready to operate.
What Monad checks
Monad checks that the required QCS documents are present and that the provider completes the local approval information needed for its own service. Pheon does not present QCS as endorsed or required by CQC.