Quality Assurance, Audits, and Compliance Monitoring
This domain tests quality assurance, audits, and compliance monitoring: how you plan checks, collect evidence, classify findings, and verify that corrective action actually works.
Core rules
- Use a written audit plan and checklist tied to the standard, not memory. Sample enough sessions, files, and staff records to support a conclusion.
- Collect objective evidence: logs, rosters, incident reports, training records, CCTV retention checks, and observation notes.
- Write findings against a requirement, with condition, evidence, and risk. Avoid naming individuals when the issue is systemic.
- Require root-cause analysis and a corrective action plan (CAPA) with owner and due date; then verify effectiveness with a follow-up sample.
- Track trends and repeat findings; a closed ticket is not the same as a fixed control.
Worked example
An audit finds 3 of 20 proctor files lack annual refresher sign-off. “Retrain everyone” is weak. The reviewer checks whether the tracking sheet was updated after a form revision, identifies the root cause, assigns a corrected tracker, and later samples 10 files to confirm sign-off. Reasoning: the finding is evidence of a broken monitoring control, not just three careless people.
Traps that cost marks
- Closing a finding without evidence of correction.
- Auditing only what is easy to see.
- Writing vague findings such as “documentation poor.”
- Failing to check whether the same issue appears at other sites.