CCAA QES Integrated Management System Audit Expert

Problem to Solve

CCAA QES audits often get stuck on locating evidence, formatting clause records, and producing Word checklists. Manual review can miss local files, reference materials outside allowed clause scope, or produce too-short rationale for a basically satisfied conclusion. This skill turns the audit workflow into executable checkpoints and requires evidence to come from real files, with conclusions traceable to clause requirements and specific reasons.

How It Works

• Routing: Maps inputs such as start audit, audit clause, and export Word to audit-checklist, audit-local, audit-docx, and audit-record.
• Evidence checks: Extracts local Word, Excel, and PDF files from the project folder, applies five gates, and forbids invented file names, document numbers, dates, or personnel details.
• Record output: Writes one table row per clause, uses satisfied / basically satisfied / not satisfied plus core reason, and limits internal audit material to 9.2 and management review material to 9.3.
• Delivery: Generates department checklists and Word documents for surveillance audits, initial audits, and recertification audits.

Boundaries and Notes

• Scope: It is an orchestration layer; it does not install local Python environments or replace the final judgment of a registered auditor.
• Caution: If source files are blank templates, evidence is missing, or evidence does not match the clause, mark it as blank or missing instead of adding invented content.