Study guide
9.2 Reviewing and Negotiating CAPA Plans
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
9.2 Reviewing and Negotiating CAPA Plans
Key Takeaways Explain This Topic AI
CQA BoK II.D.2 (Evaluate) requires judging CAPA plan acceptability—including actions, responsibilities, and schedule—against finding significance, risk, and the auditee’s CAPA procedure.
Acceptable plans show a clear finding→cause→action chain, realistic milestones, interim containment when risk remains, and defined effectiveness checks.
Negotiation is professional and evidence-based: push for stronger controls or tighter timing when risk warrants; do not trade away criteria or invent root causes for the auditee.
Schedule evaluation balances urgency (customer/regulatory/product risk) with feasibility; aggressive dates without resources are as unacceptable as open-ended delays.
Exam trap: approving any signed plan; or the auditor rewriting the entire CAPA as the auditee’s substitute process owner.
Last updated: August 2026
9.2 Reviewing and Negotiating CAPA Plans (CQA BoK II.D.2 — Evaluate)
Quick Answer: Evaluate CAPA plans for action adequacy , ownership , and schedule realism relative to risk; negotiate changes when the plan is incomplete, misaligned to root cause, or too slow/fast to be credible. Accepting a weak plan guarantees weak verification later. Practice plan-review scenarios at /practice/cqa .
After findings are reported, the auditee (or supplier) typically submits a corrective action plan . BoK II.D.2 tests whether you can evaluate that plan’s acceptability —including timing—and professionally negotiate improvements. This is still Evaluate , not “become the process owner.”
Why Plan Review Matters
Verification (II.D.3) can only confirm what was planned and done. If the plan never addresses root cause, verification may “pass” implementation of a useless action. Plan review is the control gate that protects the audit program’s integrity and the customer’s risk posture.
- Stakeholder need Plan review contribution
- Customer / client Confidence that serious findings will be fixed on time
- Auditee management Clear expectations; fewer late surprises
- Auditor / program Traceable acceptance decisions; defensible escalation later
- Regulators / certifiers Evidence that NCs are managed systematically
- Inputs to Plan Acceptability
Evaluate plans against multiple inputs—not only politeness of the wording:
- Original finding — criteria, evidence, significance/severity, unique ID
- Risk — product safety, compliance, customer impact, process criticality
- Auditee CAPA procedure — required elements, approval levels, time limits
- Contract / scheme rules — customer quality agreements, certification body response times
- Extent of condition — one instance vs systemic pattern
- Prior history — repeat findings, overdue CAPAs, previous ineffective closures
A minor administrative NC and a systemic safety-related NC do not deserve identical plan scrutiny depth—but both need logical completeness.
- CAPA Plan Acceptability Checklist
- A. Scope and linkage
Plan references the correct finding ID(s) and restates the problem accurately.
Root cause (or investigation plan with due date) is stated and plausibly explains the evidence.
Actions map cause → control , not only symptoms.
Related processes/products/sites affected by extent analysis are included or justified as out of scope.
B. Action quality
- Acceptable action traits Unacceptable traits
- Specific and verifiable (“implement barcode match gate in ERP module X”) Vague (“improve awareness”)
- Addresses system, not only one person Pure blame without process change
- Includes interim containment if risk continues Open risk with no protection
- Defines deliverables (doc rev, training, software change, validation) “Will try harder”
- Considers side effects / change control Uncontrolled change risks new failures
- C. Responsibility and resources
Named owners for each action line item.
Evidence that owners have authority and bandwidth (or escalation if not).
Cross-functional support identified when needed (IT, Engineering, HR, Supplier Quality).
Customer approval steps included when the quality agreement requires them.
D. Schedule and milestones
Schedules should be risk-based and resource-realistic .
- Schedule pattern Evaluation
- Immediate containment within hours/days for ongoing product risk Expected for high risk
Investigation complete with interim actions, then systemic fix on a staged timeline Often acceptable if risk controlled
- 18-month due date for a simple document correction with no interim control Usually unacceptable
- All majors due “tomorrow” with no resources Not credible; negotiate realistic plan with interim controls
- Open-ended “ongoing” with no milestones Not acceptable for formal CAPA closure tracking
Break complex CAPAs into milestones : investigation complete → interim controls live → permanent change implemented → training/effectiveness criteria ready → request verification.
E. Effectiveness criteria (designed up front)
Even before full verification, the plan should state how success will be judged (metrics, period, sample, audit method). “We’ll know it when we see it” is not an acceptable effectiveness plan for significant findings.
Negotiation: What It Is and Is Not
Negotiation means professional dialogue to improve plan quality and timing while remaining objective and criteria-based.
- Negotiation is Negotiation is not
- Requesting clearer actions tied to root cause Trading away the finding because the auditee is upset
- Aligning due dates to risk and resources Accepting indefinite delay for major safety issues
- Clarifying evidence needed at verification Writing the entire CAPA for the auditee as default
- Escalating when agreement cannot be reached Public shaming or personal attacks
- Documenting agreed plan changes Silent side deals not reflected in records
- Practical negotiation moves
Mirror the risk: “Because product was released without inspection evidence, we need interim release controls by date X, not only a document rewrite in Q4.”
Ask for the chain: “Help me see how action 3 removes the root cause you stated.”
Offer structure, not ownership: Suggest missing elements (effectiveness metric, extent check) without dictating the technical design solution if the auditee owns the process.
Use procedure and agreement language: Point to the auditee’s CAPA SOP or customer response-time clauses.
Record the outcome: Accepted plan, conditional acceptance with required revisions, or rejection with reasons and escalation path.
Scenario — Negotiate the schedule
Supplier CAPA for a major labeling NC proposes permanent artwork system change in 12 months, with no interim control. Customer risk is high (wrong clinical labels).
Weak auditor response: “OK, see you in a year.”
Strong evaluate + negotiate response: Require immediate containment and interim 100% inspection / barcode check within days; staged permanent system change with interim milestones; effectiveness monitoring of complaint and internal reject codes monthly; escalate if supplier refuses interim protection.
Conditional Acceptance and Rejection
Not every plan is binary pass/fail on first submission.
- Decision When used Follow-through
- Accept Elements complete; schedule risk-appropriate; owners clear Track milestones; plan verification
Conditional accept Core direction sound; minor gaps (metric clarity, missing training audience) Written conditions and resubmittal date
Reject / return No root cause, actions unrelated, schedule ignores risk, ownership missing Document reasons; require resubmittal; escalate if late
Escalate Repeat refusal, political blockage, regulatory exposure Client, certification body rules, senior management per program
Document why you accepted or rejected. Future auditors and management review need the trail.
- Special Contexts
- Internal audits
Plan review may be performed by the lead auditor, audit program manager, or process owner’s management per procedure. Independence matters when the reviewer is too close to the failure.
Supplier (second-party) audits
Customer quality agreements often set response and closure clocks. Negotiation includes commercial leverage—but auditors still need objective evaluation of technical adequacy, not only “supplier promised hard.”
Certification / third-party
Schemes may define nonconformity response timelines and evidence packages. Auditors evaluate against scheme rules plus good CAPA practice.
Multi-site / corporate CAPA
When the root is corporate (shared ERP), site-level plans that only retrain local staff are incomplete. Negotiate elevation to the level that can change the system.
Red Flags During Plan Review
- Red flag Why it matters
- Investigation due after “effectiveness complete” Logic inverted
- Same CAPA text reused for unrelated NCs Not problem-specific
- Due date equals verification date with no implementation window No time to show sustained control
- Owner is on leave / vacant role Schedule not credible
- Actions increase risk elsewhere without change control Side-effect blindness
- Plan disputes the finding facts without new evidence Re-litigation instead of CAPA
- “Awaiting budget” with no interim risk control Risk left open
Worked Example — Accept or Negotiate?
Finding: Temperature-sensitive components stored outside validated range for 11 days (logger data); criteria = validated 2–8°C storage.
Plan submitted:
Cause: “Door left open.”
Action: Email reminder to staff.
Due: 6 months.
Effectiveness: none stated.
Evaluation: Reject/return. Cause likely incomplete (why alarms failed, why door ajar possible, mapping/logger response). Action is low on effectiveness hierarchy. Schedule not aligned to product risk. Missing containment of exposed product disposition history.
Negotiated expectations: Immediate product impact assessment and disposition; alarm challenge testing; door/alarm engineering or procedural interlocks; short-interval monitoring; training with competency check; effectiveness = alarm response metrics + no excursions beyond defined limits for defined period; earlier due dates for interim controls.
Interface with Reporting and Ethics
Plan review must stay consistent with the issued finding. Do not “negotiate” the finding out of existence without evidence that it was factually wrong (that is correction of the audit record, a different process). Confidentiality and professional conduct still apply—supplier negotiations may be commercially sensitive.
Exam Anchors
Evaluate plan adequacy + schedule , not signatures alone.
Negotiate for risk-proportional strength and timing.
Demand linkage finding → cause → action → effectiveness plan.
Use conditional acceptance and documented rejection when needed.
Know when to escalate rather than endlessly re-negotiate a non-viable plan.