Provision of Supports: service integrity under scrutiny.
Less frequently audited deeply than Module 2, but when corrective actions land here, they tend to be operational and disruptive. The trap is uncontrolled variation.
5 min read
The Provision of Supports domain evaluates whether services are delivered consistently and safely. It is less frequently the source of major findings than Governance, but when it is, the corrective actions tend to be operational and disruptive.
Service agreements and individualised plans.
Auditors examine whether service agreements are clear and current, whether individualised plans are implemented and reviewed, and whether documentation standards are consistent across teams. Inconsistency between sites is one of the most common observations in this module, and it is rarely caused by intention.
The participant-to-enterprise risk loop.
Risk identification within participant planning is particularly important. If participant-level risks are identified but never feed into enterprise risk oversight, the organisation operates with blind spots. The chain that auditors look for runs:
- Participant-level risk identified during planning.
- Risk reflected in the individualised plan and reviewed at planning intervals.
- Significant or systemic patterns escalated to the enterprise risk register.
- Enterprise risk surfaced in governance review.
A break at the third link is the most common. Participant risks are managed locally, but the pattern never reaches leadership.
Variation vs uncontrolled variation.
Supervision and clinical oversight mechanisms must be demonstrable. Inconsistent documentation across practitioners or sites is a common exposure point. Variation may be clinically appropriate (different participants, different supports) but uncontrolled variation indicates system weakness. The distinction the auditor cares about is whether the variation is explainable.
Service integrity is demonstrated through consistency, review discipline, and documented oversight.
Where to start.
Pick three participant files at random. Read each end-to-end. If the documentation style, depth, and discipline differs noticeably between them, you have a consistency finding before you have an audit.