How to Reconcile Inspection Findings With the Purchase-Order Revision

At final inspection, a finding is meaningful only when it is compared with the requirement that actually applies to the inspected purchase-order line and lot. Using the newest drawing, an obsolete specification, or an unapproved email attachment can produce an incorrect release or rejection decision—even when the physical inspection itself was performed correctly.

The task is therefore not simply to decide whether a product “passes.” You must connect each result to the correct purchase-order revision, approved specification, effective date or lot, and any authorized deviation. You must also preserve the original observation and determine whether correcting a revision mismatch changes defect classification, sampling counts, or the final lot decision.

The practical control is a revision reconciliation register. It creates a traceable path from the inspected lot and original report to the controlling requirement, approval evidence, reconciled result, sampling impact, and authorized disposition.

Establish the controlling revision at final inspection

Freeze the inspection reference set

Before evaluating findings, assemble a controlled inspection packet containing:

• Purchase-order number, line, and revision.
• Item, model, or part identifier.
• Lot, batch, or shipment identifier.
• Quantity presented for inspection.
• Approved specifications and drawings referenced by the order.
• Applicable bill of materials, workmanship standard, packaging instruction, labeling requirement, or approved sample.
• Revision identifiers and approval dates.
• Recorded approval evidence for authorized changes, concessions, or deviations.
• Final-inspection report identifier and revision.
• Inspection date.
• Sampling-plan information used for the inspection.

Record the contents of this packet. Do not rely on filenames, the order of email messages, folder timestamps, or verbal confirmation to establish document control. A filename containing “final,” for example, does not demonstrate that the document was approved or incorporated into the order.

Preserve the packet used for the original inspection decision if documents change later. New information may justify a controlled reevaluation, but it should not silently replace the evidence behind the initial decision.

Determine which revision applies

For every document cited by the purchase order or inspection report, verify seven points:

1. Identity: Does the document identifier match the purchase-order reference?
2. Revision: Is the revision explicitly stated?
3. Approval: Is there recorded evidence that an authorized party approved it?
4. Effective point: Did it become effective before production, before shipment, on a stated date, or beginning with a specified lot?
5. Applicability: Does it cover this order, line, item, production location, and inspected lot?
6. Supersession: Did another revision replace it, and was that revision incorporated into the purchase order?
7. Exceptions: Does an approved deviation alter only a specific characteristic while leaving the base specification in force?

Do not assume that the latest available file is the applicable file. A newer revision may apply only to future production, another factory, or a later purchase order. Likewise, a revision issued after inspection is not automatically retroactive. Its approval must explicitly cover the inspected lot before it can govern the reconciliation.

If applicability cannot be demonstrated, record the requirement-version link as unresolved. Suspend the affected release or rejection decision and route the issue to the authorized decision owner.

Keep sampling and specification control separate

When the agreed inspection approach requires lot-by-lot inspection by attributes, use the applicable version of ISO 2859-1. Record the plan inputs and outputs used for the inspected lot, including:

• Lot definition.
• Inspection level or other plan-selection basis.
• Contractually specified AQL.
• Sample size.
• Acceptance and rejection numbers.
• Observed nonconforming items or nonconformities, as applicable.

Obtain numerical sampling tables from an authorized copy of the standard. The ISO webpage identifies the standard but does not provide the operational tables.

A sampling plan is a method for reaching a lot decision. It is not the source of product dimensions, workmanship requirements, defect definitions, labeling instructions, or approval authority. Those requirements must come from the controlling purchase-order documents and approved changes.

Reconcile each finding with its governing requirement

Follow a requirement-to-finding sequence

Process each final-inspection finding individually:

1. Identify the characteristic that was inspected.
2. Locate the exact requirement governing that characteristic.
3. Record the document identifier, revision, and precise locator, such as a clause, page, drawing zone, or sample attribute.
4. Confirm that the requirement version applies to the inspected purchase-order line and lot.
5. Preserve the measured or observed result exactly as recorded.
6. Compare that observation with the applicable requirement.
7. Classify the reconciled result as:
   • Meets the applicable requirement.
   • Does not meet the applicable requirement.
   • Not assessable because the requirement or revision is unclear.
   • Requires reevaluation because the wrong version was used.
8. Link any approved deviation or concession separately rather than overwriting the base requirement.
9. Determine whether the corrected classification changes a sampling count or lot decision.
10. Record the reviewer, review date, and evidence used.

The observation and the evaluation are different records. For example, a measured dimension should remain unchanged even if a later review determines that the inspector compared it with the wrong drawing revision. Retain the measurement, preserve the original evaluation, and add the reconciled evaluation through a controlled amendment.

Revision reconciliation register

The following register is an operational template. Its fields and workflow states are not prescribed by ISO 2859-1, ISO 19011, or CPSC guidance.

Register field	What to enter	Completion rule
Reconciliation ID	Unique record identifier	Use one controlled identifier per reconciliation record
Purchase order and line	Order number and affected line	Must match the inspected item
Purchase-order revision	Revision in the inspection packet	Do not substitute the latest available revision
Item identifier	Item, model, or part number	Match the order and inspection report
Inspected lot	Lot, batch, shipment, and presented quantity	Define the population covered by the decision
Inspection report	Report identifier, revision, and inspection date	Link to the unchanged original report
Sampling-plan reference	Applicable ISO 2859-1 edition or contractual reference, plus plan inputs	Complete only when attribute sampling applies
Requirement document	Specification, drawing, approved sample, labeling instruction, or other requirement	Record the document type and identifier
Requirement revision	Revision used for reconciliation	Enter “unresolved” if it cannot be established
Requirement locator	Clause, page, drawing zone, characteristic, or other locator	Another reviewer must be able to find the requirement
Approval evidence	Approval-record identifier and date	Verbal approval alone is insufficient for closure
Effective applicability	Applicable order, line, item, lot, location, or date	Confirm that the scope includes the inspected lot
Finding reference	Finding number and inspected characteristic	Maintain the link to the original observation
Observed result	Measured or observed inspection result	Copy accurately without reinterpretation
Initial comparison version	Revision originally used by the inspector, if known	Identify any possible version mismatch
Reconciled result	Meets, does not meet, not assessable, or requires reevaluation	Apply internal workflow labels consistently
Sampling impact	Effect on counts or the lot decision	Recalculate only under the applicable agreed plan
Deviation or change link	Authorized deviation, concession, or change record	Record its scope and approval without altering history
Decision	Release, hold, reject, reinspect, or escalate	Follow documented organizational authority
Decision owner	Authorized role or recorded approver	Do not attribute unsupported approval
Closure evidence	Corrected report, reinspection record, approval, or other closing document	Evidence must be independently traceable
Closure date and reviewer	Date and responsible reviewer	Preserve the audit trail

Reconciliation checklist

• The purchase-order line and revision are identified.
• The inspected lot and presented quantity are unambiguous.
• Every finding links to a specific requirement and revision.
• Recorded approval evidence exists for the version applied.
• The revision’s effective scope includes the inspected lot.
• Deviations are linked without replacing the original requirement.
• Findings evaluated against the wrong revision have been reevaluated.
• Effects on sampling counts and the lot decision have been reviewed.
• The final disposition and authorized decision owner are recorded.
• Original inspection evidence remains unchanged and accessible.

Control the decision and close the record

Apply an evidence-based review

Structure the review so that another competent reviewer can reconstruct the decision from objective records. This is consistent with the evidence-based auditing approach described in ISO 19011.

The closed record should show:

• What was inspected.
• Which purchase-order line and lot were involved.
• Which requirement governed each characteristic.
• Which revision was approved.
• What evidence established its applicability.
• Whether a deviation changed the requirement for a limited scope.
• How the finding affected sampling counts and the final lot result.
• Who authorized the disposition.

Separate factual inspection evidence from interpretation, approval, and disposition. If a correction is necessary, make it through a traceable amendment or revised report. Do not delete a finding merely because reconciliation changes its classification.

Resolve common revision conflicts

Conflict	Required response
Inspection used an obsolete requirement	Reevaluate the finding against the applicable approved revision and assess the sampling impact
Latest document is not incorporated into the order	Continue with the demonstrably applicable version or escalate for documented clarification
Revision changed after production	Determine whether approval explicitly covers the inspected lot; do not assume retroactive effect
Approved deviation changes one characteristic	Apply it only within its documented scope and retain the base requirement
Inspection report omits the specification revision	Obtain objective linkage evidence or classify the connection as unresolved
Two approved documents conflict	Hold the affected decision and obtain a documented precedence determination from authorized parties
Finding was removed after a revision change	Retain the original finding and document the revised evaluation separately
Sampling classification changes after reconciliation	Recalculate the lot result under the agreed sampling plan and preserve both decision records

Support product-safety control

The CPSC manufacturing best-practices guidance provides product-safety context for documented controls, production oversight, and corrective action. Revision conflicts that could affect safety or regulatory compliance should be escalated rather than closed through an unsupported interpretation.

Purchase-order approval and sampling acceptance do not replace applicable product-safety obligations. A lot that satisfies a contractual sampling rule may still require action under applicable laws, regulations, testing requirements, or reporting duties.

Final next move

Complete the revision reconciliation register for every open final-inspection finding. Route unresolved applicability, missing approval evidence, and conflicting requirements to the authorized decision owner.

Release the lot only after the applicable requirement version, reconciled finding classification, sampling impact, and authorized disposition are traceable in the closed register. If any of those links remains unresolved, maintain the hold or escalation status under the organization’s documented authority process.

Scope and limits

• This article addresses document-version reconciliation at final inspection.
• It does not establish product-specific specifications, defect classifications, AQL values, inspection levels, acceptance criteria, or approval authority.
• ISO 2859-1 provides sampling procedures; it does not determine whether a specific product characteristic is acceptable.
• ISO 19011 provides auditing guidance; it does not prescribe this register or make product-conformity decisions.
• CPSC guidance does not replace applicable statutes, regulations, testing requirements, reporting duties, or product-specific legal advice.
• The revision reconciliation register is a practical control artifact, not a form mandated by the cited sources.
• Contractual requirements, applicable law, and documented organizational authority govern final release or rejection.

Image credit

Illustrative image of a collaborative document-review process; it is not evidence of a specific inspection. Photo by Học Viện Chăm Sóc Sắc Đẹp Á Âu on Unsplash, used under the Unsplash License.

Sources

• ISO 2859-1 — Sampling procedures for inspection by attributes
• ISO 19011 — Guidelines for auditing management systems
• U.S. Consumer Product Safety Commission — Manufacturing Best Practices