Study guide
5.1 Sampling Plans, Checklists & Working Papers
ASQ Certified Quality Auditor CQA
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
0.1 Current Exam Facts 0.2 Eligibility, Fees & Recertification 0.3 Case Studies & Study Strategy
2 Chapter 1: Types of Quality Audits
1.1 Product, Process, System, Hybrid & Remote Audits 1.2 First-, Second- & Third-Party Context 1.3 CAPA Verification, Risk-Based, Surveillance & For-Cause 1.4 Common Elements with Sustainability, EHS & Financial Audits
3 Chapter 2: Purpose, Scope & Audit Criteria
2.1 Elements of Purpose and Scope 2.2 Benefits of Audits (Effectiveness, Risk, Cyber) 2.3 Criteria: Standards, Contracts, Specs & QMS
4 Chapter 3: Roles, Ethics & Audit Credibility
3.1 Roles: Lead Auditor, Team, Client, Auditee, Observer 3.2 ASQ Code of Ethics, Due Care & Confidentiality 3.3 Legal Consequences of Improper Auditor Actions 3.4 Independence, Objectivity & Qualifications
5 Chapter 4: Audit Planning Fundamentals
4.1 Elements of the Audit Planning Process 4.2 Auditor Selection Criteria 4.3 Pre-Audit Documentation & Gap Assessments 4.4 Logistics: Safety, Escorts, Access & PPE
6 Chapter 5: Auditing Tools, Strategies & the Audit Plan
5.1 Sampling Plans, Checklists & Working Papers 5.2 Forward/Backward Tracing, Discovery & Observation 5.3 Creating and Distributing the Audit Plan
7 Chapter 6: Audit Performance Management
6.1 On-Site Management for the Auditor 6.2 On-Site Management for the Auditee 6.3 Opening Meeting
8 Chapter 7: Evidence Collection & Closing Meetings
7.1 Audit Data Collection and Analysis 7.2 Characteristics of Objective Evidence 7.3 Organizing Evidence by Risk and Significance 7.4 Exit and Closing Meetings
9 Chapter 8: Audit Reporting
8.1 Report Development and Content 8.2 Effective Reports: Summary, Findings & OFIs 8.3 Approvals, Distribution & Audit File Retention
10 Chapter 9: CAPA Follow-Up & Audit Closure
9.1 CAPA Process Elements & Root Cause 9.2 Reviewing and Negotiating CAPA Plans 9.3 Verifying CAPA Effectiveness 9.4 Ineffective CAPA Escalation & Audit Closure
11 Chapter 10: Auditor Characteristics, Resources & Conflict
10.1 Auditor and Lead Auditor Characteristics 10.2 On-Site Audit Resource Management 10.3 Conflict Resolution Techniques
12 Chapter 11: Communication, Interviewing & Team Dynamics
11.1 Communication and Presentation Techniques 11.2 Interviewing Techniques 11.3 Team Building, Facilitation & Development Stages
13 Chapter 12: Audit Program Management Core
12.1 Senior Management Support for the Audit Function 12.2 Staffing and Resource Management 12.3 Auditor Training and Development 12.4 Audit Program Evaluation Metrics
14 Chapter 13: Internal & External Audit Programs
13.1 Internal Audit Program Management 13.2 External / Supplier Audit Program Management 13.3 Standardizing Best Practices from Audit Results
15 Chapter 14: Risk, Management Review & Electronic Systems
14.1 Organizational Risk Management & Continuity 14.2 Management Review Input from the Audit Program 14.3 Electronic Records, Data Integrity & Cybersecurity
16 Chapter 15: Business & Financial Impact of Auditing
15.1 Auditing as a Management Tool 15.2 Interrelationships of Business Processes 15.3 Cost of Quality Principles
17 Chapter 16: Quality Tools & Process Improvement
16.1 Seven Basic Tools, Root Cause & PDCA 16.2 Six Sigma DMAIC for Auditors 16.3 Lean Principles and Tools
18 Chapter 17: Statistics & Process Variation
17.1 Mean, Median & Mode 17.2 Dispersion & Qualitative vs Quantitative Analysis 17.3 Common Cause vs Special Cause Variation 17.4 Process Capability Metrics & Outliers
19 Chapter 18: Sampling, Change Control, V&V & Risk Tools
18.1 Acceptance Sampling & Sampling Types (incl. MSA) 18.2 Consumer Risk, Producer Risk & Confidence 18.3 Change Control, Configuration Management, V&V 18.4 FMEA, HACCP, CTQ & SWOT
5.1 Sampling Plans, Checklists & Working Papers
Key Takeaways Explain This Topic AI
Sampling plans define what will be examined, how much, and why—linking risk and materiality to method (random, stratified, judgmental, block) rather than browsing records ad hoc.
Checklists, log sheets, and forms structure fieldwork; they support consistency and coverage but never replace auditor judgment, interviews, or observation of actual practice.
Working papers are the audit’s evidence trail: they show plan, samples, evidence references, conclusions, and who did what—supporting the report and enabling review or follow-up.
Manual and electronic documentation each need controls for completeness, integrity, version control, confidentiality, and retention; e-tools do not remove the duty to retain objective evidence.
Apply-level CQA items test whether tools match purpose and risk—oversampling low risk, using checklists as scripts, or leaving undocumented samples are common exam traps.
Last updated: August 2026
5.1 Sampling Plans, Checklists & Working Papers (CQA BoK II.A.5 — Apply)
Quick Answer: Auditors apply sampling plans (what to sample, how much, method), checklists/log sheets/forms (structured prompts and records), and working papers (evidence packages that support conclusions). Documentation may be manual or electronic , but every tool must remain risk-based, complete enough for review, and free of unchecked bias. Tools organize work—they do not replace judgment, interviews, or observation.
Domain II (Audit Process) is the largest scored block on the CQA exam (~30%). Planning tools sit at the hinge between planning and performance: if sampling is vague, checklists are used as scripts, or working papers cannot reconstruct how a finding was formed, the audit loses defensibility. At the Apply level, stems ask you to choose or critique tools in realistic scenarios—not merely define them.
Why tools matter before the opening meeting
A solid plan answers why , what , and against what . Tools answer how evidence will be obtained and recorded :
Tool family Primary job Typical failure mode
Sampling plan Select a defensible subset of population (lots, records, transactions, people, times) “We’ll look at some files” with no method, size, or risk link
Checklists / forms / log sheets Structure questions, criteria prompts, and field notes Treating the checklist as the entire audit or as a pass/fail scorecard
Working papers Preserve plan, evidence, analysis, and conclusions for report and review Undated notes, missing sample IDs, conclusions without referenced evidence
Manual vs electronic media Capture, store, protect, and retrieve the above Uncontrolled spreadsheets, shadow files, or lost paper binders
On exam items, if the stem emphasizes coverage without justification , look for a missing or weak sampling plan . If it emphasizes inconsistency across auditors or missed clauses , look for weak checklists/working papers . If it emphasizes integrity or retention , look at documentation media and controls .
Sampling plans: method, size, and rationale
A sampling plan (for audit use—not necessarily a formal acceptance-sampling table from Domain V) states:
Population (e.g., all CAPAs closed in the last 12 months; all incoming lots for product family B; all operators on Line 3).
Objective of the sample (conformity to procedure X; effectiveness of training; timely disposition of NCs).
Method of selection.
Size / intensity (how many, over what period, depth of each item).
Rationale tied to risk, history, materiality, and prior findings .
What will expand the sample (first nonconformity triggers more sampling; contradictory interview answers trigger deeper trace).
Common audit sampling methods
Method How selection works When it fits Caution
Random Each unit has known chance of selection Homogeneous populations; reduce selection bias Needs a usable frame (list of IDs); random ≠ “whatever is handy”
Stratified Population split by risk strata; sample within each Mixed risk (high/medium/low customers, sites, product classes) Strata must be meaningful; don’t under-sample high risk
Judgmental / directed Auditor selects based on risk, changes, complaints, history Risk-based audits; for-cause; follow-up on weak areas Bias risk—document why these items; don’t pretend it is statistical
Block / systematic Every nth record; consecutive periods or lots Detect patterns over time; process stability Can miss seasonal spikes if step size is unlucky
Discovery / exploratory Follow anomalies; expand where risk appears When population is poorly defined or red flags appear Must still document path; not a license for aimless wandering
100% / complete All items in a small critical set Safety-critical releases; tiny populations; regulatory hold points Expensive; reserve for high consequence or small N
CQA distinction: Domain V later covers acceptance sampling (AQL, consumer/producer risk) more formally. For II.A.5 , the exam focus is planning a sample that supports audit conclusions , not calculating OC curves. Still, do not invent statistical claims (“we are 95% confident…”) from a casual judgment sample.
Risk drives intensity
High risk / high impact: larger sample, more strata, more observation of live work, less reliance on “easy” records only.
Stable, low risk, strong history: smaller sample, still with a defined method.
New process, new product, new supplier, prior major NC: increase sample size or shift to judgmental focus on the weak link.
Scenario — CAPA effectiveness sample.
Purpose: verify effectiveness of 12 CAPAs closed after a customer complaint surge. Weak plan: “Review a few CAPAs.” Strong plan: population = 12 CAPAs; method = 100% for majors and high-severity customer issues (n=5), plus random sample of remaining (n=4 of 7); for each, sample implementation evidence (revised SOP, training records) and effectiveness evidence (post-implementation process metrics or recurrence data for 90 days). Expand if any effectiveness claim lacks data.
Scenario — supplier lot records.
Purpose: evaluate incoming inspection control for sterile packaging. Population: 180 lots received in 6 months. Method: stratified —all lots with prior supplier SCAR or near-miss (stratum H), plus random from clean lots (stratum L). Size: all of H (8 lots) + 15 of L. For each lot: COC, inspection record, disposition, and instrument calibration status for gages used. Rationale: prior defects clustered on one material grade.
- Checklists, log sheets, and forms
- Checklists
A checklist is a structured list of criteria-linked prompts—clauses, procedure steps, risk questions—used to guide interviews, document reviews, and observations. Good checklists:
Map to approved criteria (standard, contract, internal procedure)—not personal preference.
Leave room for evidence notes , sample IDs, and “N/A with reason.”
Are customized to purpose and scope (surveillance checklist ≠ full system checklist ≠ for-cause).
Support consistency across team members without freezing inquiry.
Misuse: reading checklist questions verbatim and marking Yes/No without verifying practice; skipping areas because “not on the list”; scoring audits as percentages of checklist ticks.
Log sheets and field forms
- Form type Use What to capture
- Interview log Who, when, role, topics Name/role, date/time, key statements, evidence offered, follow-ups
- Document review log Controlled docs examined Doc ID, rev, date range, conformity notes, gaps
- Observation / tour form Live process watching Location, time, process step, what was observed vs procedure
- Sample register Trace sample selections Population, method, IDs selected, results, expansions
- Finding draft form Build nonconformities early Requirement, evidence, nature of failure, severity draft
- Daily issues / parking lot Scope, access, conflicts Item, owner, resolution needed before exit
Forms reduce lost notes and support working-paper completeness . They do not authorize the auditor to invent requirements.
Customizing vs generic templates
Generic ISO clause checklists are a starting point. Apply-level planning expects tailoring : product-line risks, prior audit history, regulatory focus, multi-site central functions, and remote vs on-site evidence methods. A team that uses last year’s full checklist for a narrow CAPA verification audit is tooling incorrectly relative to purpose.
Working papers: the evidence package
Working papers (audit documentation) are the organized records that show planning decisions, fieldwork, analysis, and the basis for conclusions and the report. They enable:
Lead auditor review of team work before the exit meeting.
Report drafting with cited evidence.
Follow-up audits and CAPA verification.
Defense of conclusions if challenged by auditee or client.
Program evaluation and lessons learned.
Minimum content expectations (practical exam model)
Plan linkage — purpose, scope, criteria, schedule references.
Sampling plan and actual samples examined.
Evidence — what was seen/heard/recorded, with IDs, dates, locations.
Analysis — comparison of evidence to criteria; classification of issues.
Conclusions — conformity, nonconformity, OFI, not auditable (with reason).
Identity trail — who prepared, who reviewed, dates, revisions.
Exam trap: A finding in the report that cannot be traced to working-paper evidence is a documentation failure even if the auditor “remembers” the conversation.
Manual vs electronic documentation
Dimension Manual (paper) Electronic
Strengths Simple in restricted areas; easy markup on floor Searchable; templates; remote collaboration; backup potential
Weaknesses Loss, illegibility, hard multi-site sharing Version chaos, incomplete uploads, access control gaps
Controls needed Unique IDs, binding, custody, scan retention policy Access rights, audit trail if required, backup, naming conventions, offline contingency
Confidentiality Locked storage; controlled copies Encryption, least privilege, secure transfer
Integrity Ink changes initialed; no silent white-out of evidence Controlled edits; preserve original evidence files
Hybrid reality: Many audits use electronic checklists on tablets plus photos or exports from the auditee’s eQMS. The principle is the same: evidence must remain attributable, legible, contemporaneous, original (or controlled copy), and accurate —the ALCOA-style integrity mindset used in regulated environments is a useful quality-auditor discipline even when the audit is not GxP-specific.
Scenario — electronic tool without working papers.
A team completes a cloud checklist with only Yes/No ticks and no sample IDs or evidence notes. The report cites three major nonconformities. The auditee challenges one finding. Without working papers that identify the batch records and the exact requirement text, the team cannot defend the conclusion. Tooling existed; documentation quality failed.
Putting tools together in planning
A coherent toolkit for a three-day process audit might look like:
Risk-ranked process list → drives sample intensity.
Sampling plan per process (records + people + observation windows).
Custom checklist linked to criteria and known weak points.
Sample register + interview logs as daily field tools.
Working-paper index so the lead can review before the closing meeting.
Secure repository (manual binder control or electronic folder with access list).
Exam traps (analyze carefully)
Checklist = audit — False. Checklists guide; evidence and judgment conclude.
Random sampling without a frame — Grabbing folders from a shelf is convenience sampling, not random.
Statistical overclaim — Don’t imply AQL/confidence from a few judgment picks.
Electronic equals controlled — Software alone does not guarantee completeness or retention.
One-size sample — CAPA verification, surveillance, and initial system audits need different intensity and selection logic.
Empty working papers — Conclusions without referenced evidence fail review and exam logic.
For timed practice on planning and evidence tools, use free CQA sets at /practice/cqa and force yourself to name population, method, and what working papers must hold before selecting an answer.
Key Takeaways
Sampling plans state population, method, size, and risk rationale—and when to expand.
Checklists and forms structure fieldwork; they never replace criteria-based judgment or observation of practice.
Working papers reconstruct the audit path from plan to conclusion for report, review, and follow-up.
Manual and electronic media both require integrity, confidentiality, version control, and retention discipline.
Apply-level items punish ad hoc sampling, checklist-only audits, and findings that cannot be traced to documented evidence.