ASQ CHA / CFSQA common mistakes
ASQ CHA / CFSQA · Understand the traps and how to avoid them.
Treating 'audit' as synonymous with 'inspection' or 'testing' and selecting answers that describe product measurement activities when the question asks for the defining characteristics of an audit.
Candidates come from quality inspection and QC backgrounds where 'audit' colloquially means checking product, and the ISO 19011 distinction between audit (systematic, independent, documented process for obtaining objective evidence and evaluating it against criteria) and inspection is never rehearsed.
What to do instead
Memorize the ISO 19011 definition verbatim and build a two-column contrast sheet: audit vs. inspection vs. surveillance vs. verification. For every practice question, first ask 'is this evaluating a process/system against criteria by an independent party?' before choosing.
Confusing the audit types (first-party/internal, second-party/supplier, third-party/certification) when the scenario describes who is auditing whom, and selecting the wrong type or the wrong independence conclusion.
Scenarios use role labels (customer, registrar, sister plant) rather than the party names, and candidates map 'customer audit' to third-party because the customer is external to the auditee.
What to do instead
Use the ownership test: who holds the audit? If the auditee's own organization, first-party; if a customer or contracted party with a commercial relationship, second-party; if an independent body issuing certification/accreditation, third-party. Drill 20 short scenarios until the mapping is automatic.
Building an audit program as a list of individual audits without documented objectives, scope, criteria, responsibilities, resources, or a schedule justified by risk, status, and importance of processes.
Candidates memorize clause lists but never construct an actual program plan, so they answer program-design questions with fragments (e.g., 'make a schedule') instead of the full plan-do-check-act program cycle.
What to do instead
Practice drafting a one-page program plan for a fictional company: objectives, scope, criteria, roles, resources, schedule with risk rationale, and performance monitoring. Use ISO 19011 program management guidance as the structural template, and check every answer option against those elements.
Ignoring the distinction between program management and individual audit management, and answering a program-level question with audit-level tactics (or vice versa).
The two levels share vocabulary (scope, criteria, schedule), and exam stems do not always say 'program' explicitly, so candidates default to the level they know best.
What to do instead
Before answering, underline the subject of the stem: does it concern multiple audits over time (program) or one audit event (audit)? Program answers involve resourcing, competence planning, monitoring, and improvement across audits; audit answers involve planning, conducting, reporting, and follow-up of a single audit.
Selecting an auditor for an assignment based on availability or seniority rather than evaluating competence against the specific audit's technical, process, and standard knowledge needs.
In practice, scheduling convenience dominates, and candidates transfer that habit; they also conflate 'qualified' (completed a course) with 'competent' (demonstrated ability to apply knowledge and skills).
What to do instead
Apply the competence equation: knowledge + skills + personal attributes, evaluated against the audit's specific scope. For scenarios, ask which auditor has evidence of competence in that industry/process; prefer the answer that describes evaluating competence and providing training or technical experts to close gaps.
Missing independence and objectivity conflicts (auditing one's own work, auditing a process the auditor manages, or an auditor with a prior consulting relationship) and choosing the technically strongest auditor instead.
Candidates focus on technical fit and forget the impartiality requirement, especially in internal audit scenarios where everyone is a colleague.
What to do instead
Add a mandatory independence screen to every auditor-selection question: can this person audit this process without evaluating their own decisions? If not, the correct answer involves reassignment, a different auditor, or use of an independent technical expert.
Writing or choosing an audit plan that omits audit criteria, sampling approach, or the auditee's process interactions, and treating the checklist as the plan.
Candidates equate the checklist of questions with the audit plan, and they underweight document review and process-turtle/process-interaction analysis during preparation.
What to do instead
Use a fixed plan template: objectives, scope, criteria, dates, sites, auditee contacts, team roles, sampling strategy, audit trail, and logistics. In questions, eliminate any option missing criteria or sampling rationale. Practice mapping process inputs, outputs, and interactions before writing checklist items.
Accepting verbal assurances or undocumented statements as objective evidence, and failing to trace findings to a specific criterion, evidence, and requirement.
Auditors want to be agreeable and time-pressured; candidates also confuse 'evidence exists somewhere' with 'evidence was verified and recorded'.
What to do instead
Apply the three-part finding test: criterion cited, objective evidence recorded (document, record, observation, interview corroborated), and the gap stated. In scenario questions, reject options that rely on hearsay, and prefer options that involve sampling records, observing the process, and corroborating interviews with documentation.
Classifying nonconformities inconsistently, and writing findings that describe a solution or an opinion rather than the observed condition against the requirement.
Candidates blend correction, corrective action, and root cause into the finding statement, and they grade severity by how upset the auditee will be rather than by the organization's defined criteria.
What to do instead
Separate the elements explicitly: finding = requirement + evidence + gap; correction = fix the instance; corrective action = eliminate the cause. Grade against the organization's documented classification scheme (major/minor/observation) and the risk to the management system, not the auditee's reaction.
Treating report issuance as the end of the audit and neglecting corrective action verification, effectiveness review, closure evidence, and feeding results into program improvement.
Candidates memorize report contents thoroughly and treat follow-up as an afterthought, and they confuse 'action taken' with 'action verified effective'.
What to do instead
Memorize the follow-up chain: finding issued, action plan with owner and due date, implementation evidence, verification of effectiveness, closure recorded, and results used to update the audit program and risk assessment. In questions, prefer answers that require verification of effectiveness rather than acceptance of a stated completion date.