7.2 Characteristics of Objective Evidence
Key Takeaways
- Objective evidence is information that can be proven true—typically observed, measured, confirmed, corroborated, and/or documented—not rumor, preference, or unverified assertion.
- CQA BoK II.B.5 is Analyze-level: distinguish objective evidence from subjective opinion and grade how well a source supports a finding or conclusion.
- Strong evidence is relevant to criteria, sufficient in extent, reliable in source, and clear enough that another competent auditor could reach a similar conclusion from the trail.
- Corroboration and confirmation increase confidence; a single weak source may support a lead but usually not a high-severity nonconformity alone.
- Exam traps include equating ‘documented’ with ‘true,’ treating best-practice preferences as criteria, and calling feelings or unaudited hearsay objective.
7.2 Characteristics of Objective Evidence (CQA BoK II.B.5 — Analyze)
Quick Answer: Objective evidence is information that can be verified as true—commonly observed, measured, confirmed, corroborated, and documented. CQA candidates must analyze whether a given source meets these characteristics, how much weight it carries, and whether it is strong enough to support a nonconformity, observation, or clean conclusion against stated criteria.
If II.B.4 is about how auditors collect and analyze data, II.B.5 is about what counts as proof. Case-study items often bury weak “evidence” in a stem (a hallway comment, an auditor’s preference, a single unconfirmed email). Your job is to separate objective evidence from noise.
Definition in Audit Language
Objective evidence is data supporting the existence or verity of something—qualitative or quantitative—obtained through observation, measurement, test, or other suitable means. In practice for CQA:
- It is tied to criteria (standard, procedure, specification, contract, regulation, quality agreement).
- It is reproducible enough that a reviewer can follow the trail in working papers.
- It is free of pure personal preference (“I would have designed it differently”).
- It is more than an unverified claim when used for adverse findings.
| Characteristic | Meaning | Example that qualifies | Example that fails |
|---|---|---|---|
| Observed | Auditor (or authorized remote view) saw the condition/activity | Saw unlabeled drums in quarantine | “I heard warehouse is messy” |
| Measured | Quantified with defined method | Torque wrench readings vs. specification | “Seems tight enough” |
| Confirmed | Verified with the source of truth or authoritative system | ERP shows PO closed; physical count matches | Unchecked verbal “we shipped it” |
| Corroborated | Independent sources agree | Interview + record + observation align | One operator’s claim only |
| Documented | Recorded in a controlled or attributable record | Signed DHR entry, audit-trailed e-record | Sticky note with no attribution |
Not every fact needs all five attributes at maximum strength—but high-severity conclusions demand stronger combinations.
Observed Evidence
Observation produces first-hand evidence of conditions and behaviors at a point in time.
Strengths: hard to argue away when well documented (who/what/when/where, photos if allowed, linked criterion). Limits: staging, temporary cleanup, limited sample of shifts, inability to observe rare events.
Analyze tip: Observation of a nonconforming condition is objective for that moment. Whether it is systemic requires additional samples, records, or history—do not leap from one snapshot to “always” without support.
Measured Evidence
Measurement yields numbers against defined units and methods: dimensional checks, environmental data, cycle times, defect rates, assay results, gauge R&R outputs.
Analyze questions
- Was the correct characteristic measured?
- Was the instrument suitable and in calibration status?
- Was the method the one required by criteria?
- Is statistical interpretation appropriate (single point vs. process capability)?
A measured value is objective as a reading; the conclusion drawn from it still requires analysis against the specification and sampling plan.
Confirmed Evidence
Confirmation means checking a claim against an authoritative source—system of record, original certificate, source document, second independent query, or witnessed demonstration.
| Claim | Weak acceptance | Confirmed approach |
|---|---|---|
| “All suppliers are approved” | Trust the statement | Sample POs → approved supplier list status on order date |
| “CAPA is closed effective” | Status field = Closed | Effectiveness evidence: metrics, verification records, no recurrence |
| “Training complete” | Green matrix cell | Course content vs. job, attendance, competency assessment date |
| “Part meets drawing” | Operator thumbs-up | Inspection record with actuals, method, and acceptance authority |
Confirmation is the antidote to plausible storytelling.
Corroborated Evidence
Corroboration is agreement among independent sources. Independence matters: three people reading the same scripted talking points are not three independent sources.
Typical corroboration sets
- Interview + related quality record + observation of the step
- Complaint file + investigation + related production lot genealogy
- SPC chart + raw data extract + calibration status of the gauge used
- Internal audit finding + management review action + CAPA effectiveness data
When corroboration is mandatory in practice (and on hard exam items): disputed facts, potential fraud/data integrity issues, major/critical product risk, or findings that will drive regulatory or supplier disqualification decisions.
Documented Evidence
Documentation makes evidence reviewable and durable. It includes paper and electronic records, photographs (if permitted), system logs, and the auditor’s own working papers that cite sources.
Critical analysis: “Documented” ≠ “true.” Fabricated, backdated, incomplete, or uncontrolled documents exist. Analyze integrity:
- Attributable (who did it)?
- Contemporaneous (when)?
- Legible and complete?
- Original or controlled copy?
- Consistent with audit trails and physical reality?
Electronic systems add audit-trail, access-control, and backup dimensions—still documentation, still subject to integrity analysis.
Subjective vs. Objective: The CQA Sorting Hat
| Statement type | Classification | Usable as NC basis? |
|---|---|---|
| “The work instruction requires dual verification; record #452 shows one signature only” | Objective (documented + criterion) | Yes, if sample/significance supports |
| “I feel the area is chaotic” | Subjective | No—convert via observation checklist and criteria |
| “Industry best practice is five whys; they used fishbone” | Preference unless criteria require a method | Usually OFI at most |
| “Operator said they sometimes skip torque” | Lead (hearsay until corroborated) | Not alone |
| “Measured torque 3 of 5 fasteners below min on drawing” | Objective (measured + criterion) | Yes |
| “Customer would probably dislike the label font” | Opinion without criterion | No |
Sufficiency, Relevance, and Reliability
Analyze evidence along three classic axes:
| Axis | Question | Failure mode |
|---|---|---|
| Relevance | Does this fact answer the audit objective against criteria? | Interesting but out-of-scope digressions |
| Sufficiency | Is there enough coverage for the risk and conclusion scope? | One record used to bless an entire multi-site process |
| Reliability | How trustworthy is the source and method? | Dependent, staged, or integrity-compromised sources |
Hierarchy of reliability (general guidance, not absolute law)
- Auditor-observed conditions and auditor-performed/measured checks
- Original system records with integrity controls
- Independent third-party certificates/reports (when authentic)
- Contemporaneous internal records
- Recalled interviews
- Hearsay and anonymous tips (leads only until developed)
Building a Defensible Evidence Package
A finding-ready package typically includes:
- Criterion citation (exact requirement).
- What was examined (sample identity, method).
- What was found (facts only—observed/measured/documented).
- How confirmed/corroborated if contested or high risk.
- Why it matters (bridge to significance in II.B.6).
Mini case (analyze the quality of evidence)
Stem facts:
- Procedure requires lot segregation of rejected material.
- Auditor sees two rejected cartons mixed with accepted stock (observed, photographed per rules).
- Inventory system still shows both cartons as “Rejected-Hold” (documented system status).
- Warehouse lead says “temp help must have moved them” (interview lead).
Analysis: Observation + system status provide strong objective evidence of mixed status in physical storage relative to segregation requirements. The interview explains a possible cause but is not required to establish the nonconformity. Further sampling may determine extent (systemic vs. isolated).
Exam Traps for II.B.5
- Calling auditor preference objective evidence.
- Equating existence of a document with conformity of practice.
- Using uncorroborated hearsay as a major finding.
- Ignoring integrity red flags in “perfect” records.
- Demanding laboratory-grade proof for low-risk clerical issues (proportionality).
- Forgetting that positive evidence of conformity also must be objective—not wishful thinking.
Bridge to the Next Sections
Once evidence is objective, the auditor must evaluate significance and risk (II.B.6) and present results with clarity at exit/closing (II.B.7). Weak evidence collapses under challenge in the closing meeting; strong evidence invites concurrence or a clear path to resolve factual disputes.
Which item best meets the characteristics of objective evidence for a potential nonconformity?
An operator claims that every shipment is dual-checked. Which approach best corroborates that claim?
Why is a completed form not automatically strong objective evidence of conformity?
A hallway conversation mentions possible falsification of environmental monitoring data. What is the most appropriate classification of that information at the moment it is heard?