Automated data quality checks run on every assessment report when a Verifier submits the assessment to the facility. This article explains SLCP's automated data quality checks and the difference between Blocking and Advisory Checks.
- How does it work?
- What kind of checks are we running?
- What happens when a Blocking or Advisory Check is triggered?
- What mistakes are the Blocking Checks actually looking for?
How does it work?
When a Verifier submits a report, several checks run automatically in the background on the SLCP Gateway. While SLCP have always had automated data quality checks, we are now introducing Blocking Checks which not only help identify inconsistencies, errors, or missing data before a report is finalized, but also ensure the mistakes are fixed before a report is resubmitted.
If no issues are identified when the automated data quality checks run, the report is successfully completed and the facility can access the report for review.
If issues are identified, the report bounces back to the Verifier. A notification email is sent to the Verifier and the Verifier Body (VB). The Verifier must then review the notifications and make all necessary edits in order to resubmit the report.
What kind of checks are we running?
There are two types of automated data quality checks – Blocking and Advisory Checks.
Blocking Checks: critical mistakes that prevent the report from being submitted. All mistakes must be corrected in order for the report to be completed. Blocking Checks will be implemented on 2 June 2026.
Advisory Checks: potential mistakes that the Verifier should review to ensure the report does not contain mistakes. Advisory checks do not block a report, and it can still be submitted without any changes made by the Verifier. Advisory Checks will be introduced in late 2026.
What happens when a Blocking or Advisory Check is triggered?
If the mistakes identified by the automated data quality checks are not corrected, SLCP may issue Corrective Action Requests (CARs), regardless of whether the trigger is a Blocking or Advisory Check. Repeated triggers of Blocking or Advisory Checks is also an indication of poor quality management systems, which can result in a Management Systems CAR.
As a result, failure to correct Blocking or Advisory Checks may impact VB quality scores.
What mistakes are the Blocking Checks actually looking for?
Blocking Checks are triggered for mistakes that must be fixed before a Verifier submits a response. They include:
- Questions that have not been answered in full
- Inconsistent answers or contradictions (for example, answering 0 workers are under 18 while also identifying the youngest worker as between the age of 12-17)
- Not correctly flagging when a facility did not answer the question
- Legal non-compliance fields completed incorrectly, without an entry in the Legal Reference field
- Formatting or conditional mistakes: Using non-ISO dates, non-numeric data, skipping mandatory sub-questions, or exceeding the free text character limits.
- Entering a corrected response that is the same as the facility response
- Not including explanations for when data is updated during the Verification
- Not including details of a joint assessment
For more information, see the technical bulletin for VBs on this topic