Study guide
6.1 On-Site Management for the Auditor
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
6.1 On-Site Management for the Auditor
Key Takeaways Explain This Topic AI
On-site management for the auditor (II.B.1, Evaluate) means actively controlling time, team resources, plan fit, and communication so the audit still achieves objectives under real-time constraints.
Time management tracks planned versus actual progress by process/area, protects high-risk sample windows, and prevents low-value deep dives from consuming the itinerary.
Resource reallocation (who goes where, SME deployment, remote vs. on-site tasks) is justified when emerging risk, access delays, or evidence quality needs change mid-audit.
Plan reassessment is required when scope, availability, safety, or evidence paths break—not improvisation that silently abandons criteria or objectives.
Status, tentative findings, and observations are communicated promptly to the team and appropriately to the auditee so surprises are minimized before the closing meeting.
Last updated: August 2026
6.1 On-Site Management for the Auditor (CQA BoK II.B.1 — Evaluate)
Quick Answer: Once fieldwork starts, the auditor (especially the lead ) must manage time , reallocate team resources , reassess the plan when conditions change, and communicate status, findings, and observations . Domain II is about 30% of scored CQA items. At the Evaluate level, you decide whether mid-audit adjustments still support objectives, criteria, and evidence quality—or whether they create risk of incomplete, biased, or unmanaged audits.
A solid plan (Chapters 4–5) is necessary but not sufficient. Shifts go offline, servers crash, escorts arrive late, a major nonconformity appears in hour two, and the “easy” warehouse tour becomes a product-trace fire drill. On-site (or live remote) performance management is how professional auditors keep the engagement under control.
Why This Is Evaluate-Level
- Cognitive move What it looks like on the exam
- Remember List lead-auditor duties during fieldwork
- Apply Adjust a half-day schedule when one interview is cancelled
Evaluate (II.B.1) Judge whether reallocation and plan changes preserve objectives, risk focus, and independence
Scenario — evaluate a weak response.
Plan: three auditor-days covering receiving, production, and final release. Day 1 morning: receiving is delayed four hours for a “VIP customer tour.” The lead spends the entire afternoon waiting in the lobby, then rushes production with no sampling depth, and drops final release entirely without documenting a limitation. Evaluation: inadequate management . Waiting is not a strategy; the lead should have reallocated to document review, another process with access, or remote file work; escalated access blockage; and reassessed whether purpose still can be met—or formally limited scope with client/auditee notification.
1. Time Management
Time is the scarcest audit resource. Effective time management means:
Knowing the planned itinerary and risk priorities for each day/shift.
Tracking actual progress against planned process coverage and sample sizes.
Protecting windows that cannot be rescheduled (night shift, sterilization run, end-of-month close, live customer process).
Ending interviews and tours when evidence sufficiency is reached—not when curiosity is satisfied.
Building short buffers for transit, PPE donning, and badge access without turning buffers into unstructured downtime.
- Time-management practice Purpose
- Daily team huddle (10–15 min) Align who covers what; surface blockers
- Midday checkpoint Decide whether afternoon plan still fits
- Parking-lot list Capture issues without derailing current sample
- Time-boxed interviews Prevent single SME monopolizing the day
- Sample completion log See which planned samples remain open
Evaluate rule: Spending extra hours on a low-risk, well-controlled process while skipping a high-risk process with prior majors is poor on-site management—even if the team “felt busy.”
Practical tactics
Front-load high-risk or constrained activities early in the engagement while energy and access are best.
Use parallel paths : one auditor on the floor, another on records; switch when one path stalls.
Convert dead time (waiting for a manager) into working-paper updates , sample selection from electronic lists, or review of previously requested documents.
Do not allow hospitality (long lunches, plant museum tours) to displace evidence work unless the tour itself is planned process observation.
Scenario — good time control.
Audit of a multi-line packaging operation. Line 3 (highest complaint rate) is down for maintenance until 2 p.m. Lead reallocates morning: Auditor A samples Line 1 changeover records; Auditor B reviews complaint CAPAs linked to Line 3; both reconvene for live observation of Line 3 startup. Risk focus preserved; downtime converted to evidence.
2. Reallocating Resources
Resources include auditor-hours, SME specialists, interpreters, tools (video, secure file access), and which team member owns which process thread. Reallocation is justified when:
- Trigger Example reallocation
- Emerging high significance finding Pull second auditor to corroborate evidence and expand sample
- Technical depth exceeded Deploy SME to process; lead stays on system/management interviews
- Access denial in Area A Move team to Area B with access; document limitation on A
- Language barrier Pair interpreter with interviewer; delay complex interviews until support ready
- Remote document cache ready One auditor stays remote-heavy while others observe
Auditor illness / conflict appears Redistribute scope; if independence breaks, remove that person from that process
Reallocation is not dumping all hard work on the junior while the lead disappears, or sending an interested process owner to “help audit” their own area.
Evaluate trap: Moving the only independent SME off a high-risk technical process to cover a ceremonial management interview because “the VP only has 30 minutes now.” Unless the interview is critical path for objectives, protect the high-risk evidence path or reschedule the interview.
Lead auditor role in reallocation
The lead typically:
Maintains the integrated picture of coverage vs. plan.
Approves moves that change process ownership mid-day.
Ensures working papers still show who did what (chain of evidence).
Prevents team members from freelancing outside scope or criteria.
Escalates resource shortfalls that threaten objectives to the client/audit program as needed.
3. Reassessing the Plan
Plans are living documents during fieldwork. Reassessment means consciously comparing current reality to purpose, scope, criteria, schedule, and methods—and deciding to continue, adjust, limit, or (rarely) suspend.
Situation Reassessment options
Critical process unavailable entire audit window Extend dates; switch shifts; formal scope limitation; reschedule module
Major safety incident on site Pause; follow site emergency rules; reassess ability to continue
Evidence reveals purpose was wrong (e.g., process outsourced) Reconfirm purpose/scope with client; adjust criteria and itinerary
Flood of minor clerical issues Keep sample proportional; do not abandon high-risk processes to chase typos
Suspected intentional concealment Escalate per program; increase corroboration; involve client as rules require
Hybrid tech failure Fall back to on-site document review or reschedule remote module
Silent plan abandonment (dropping processes without record) is a performance-management failure and a reporting integrity problem. If coverage will be incomplete, the audit file and eventual report must reflect limitations .
Scenario — evaluate plan change.
Purpose: verify effectiveness of temperature-controlled shipping. On arrival, the auditee states the cold-chain process moved to a 3PL six weeks ago; only paperwork remains on-site. Correct reassessment: update process map and access plan; request 3PL audit rights per quality agreement; if rights/time insufficient, document limitation and inform client that objectives for shipping effectiveness cannot be fully met on-site alone. Incorrect: write “N/A – not observed” with no limitation narrative and claim full purpose achievement.
4. Communicating Status, Findings, and Observations
Communication has two primary audiences during performance: the audit team and the auditee (plus client when required).
Team communication
Daily brief/debrief: progress, open samples, tentative issues, tomorrow’s plan.
Cross-check so two auditors do not unknowingly sample the same lot while missing another risk area.
Harmonize classification language before the closing meeting (major/minor/OFI definitions per program).
Protect confidentiality: hallway talk and shared printers still leak.
Auditee communication
Professional practice minimizes closing-meeting ambush :
- Communicate during fieldwork Why
- Progress against agenda Builds trust; enables escort planning
- Requests for additional records/people Gives auditee time to produce evidence
- Potential nonconformities as they mature Allows clarification and additional objective evidence
- Confirmed factual observations Separates facts from later classification debates
- Plan changes affecting hosts Courtesy and logistics
What not to do:
Promise “you’ll pass” or negotiate findings away without evidence basis.
Announce every incomplete thought as a formal nonconformity before verification.
Hide significant issues until the exit meeting to maximize drama.
Discuss confidential findings with unauthorized personnel.
Findings vs. observations (field language):
Many programs use finding for criteria-linked nonconformity (or positive finding) and observation / opportunity for improvement (OFI) for issues not rising to nonconformity—or for notes still under evaluation. On-site, state facts and criteria references first; apply classification when evidence is sufficient and team consensus exists per program rules.
Scenario — communication done well.
Auditor traces a calibration overdue for a release-critical gauge. Same day, shows the auditee the gauge ID, last cal date, procedure requirement, and product lots released while overdue. Auditee produces a “grace period” memo. Team evaluates memo against criteria (not allowed), confirms nonconformity wording overnight, and presents a no-surprise finding at closing with lots listed. Time, evidence, and communication all managed.
Integrated Daily Cadence (Field Model)
A practical evaluate-ready rhythm for multi-day audits:
Start-of-day team alignment — priorities, assignments, known constraints.
Execute planned samples — interviews, observations, document/record review.
Midday reallocation check — stuck paths, emerging risks, time burn.
Auditee status touchpoint — progress, needs, potential issues maturing.
End-of-day evidence review — working papers complete enough for another auditor to understand; classify tentative issues; update tomorrow’s plan.
Escalate early — access denials, ethics concerns, safety, inability to meet purpose.
Common On-Site Management Failures (Exam Traps)
- Failure Why it fails evaluation
- Rigid adherence to a broken itinerary Misses available evidence; wastes time
- Chaotic constant plan thrash Team loses coverage tracking
- No communication of emerging findings Closing ambush; weaker auditee evidence response
- Reallocating into conflict of interest Ethics/credibility failure
- Dropping scope silently Misleading report; incomplete engagement
- Over-focus on hospitality and soft topics Risk-based objectives unmet
- Lead does all interviews; team idle Poor resource use
- Expanding into consulting redesign Role confusion; independence threat
- Remote and Hybrid Nuances
On-site management principles apply to live remote and hybrid audits:
Time zones and screen-share fatigue require stricter time-boxing.
Reallocate when video cannot show required physical evidence—schedule an on-site module or limitation.
Communicate connectivity failures and reschedule slots promptly.
Status boards (shared secure trackers) help distributed teams see open samples.
Evaluate whether the chosen mode still yields sufficient, appropriate evidence after day-one reality checks.
Key Exam Anchors
II.B.1 Evaluate : time management, resource reallocation, plan reassessment, communication of status/findings/observations.
Protect risk-based coverage ; busyness ≠ effectiveness.
Plan changes must be conscious, documented, and objective-aligned .
Communicate potential issues early with facts and criteria—not drama, not secrecy.
Lead owns integration; team members own assigned threads and escalate blockers fast.