Resolve a conflict by preserving both records, comparing the exact requirement and its context, and obtaining a documented decision from the role authorised to determine which record controls. Neither record should be silently overwritten.
ASQ says a supplier quote request can include specifications and other requirements, such as testing. NIST identifies production records, batch records, material traceability records and in-line testing as relevant to manufacturing traceability. Neither cited statement establishes a universal order of precedence, however, so the project’s governing records and decision process still need to be confirmed.
Identify what actually conflicts
“Source record” and “specification record” should be treated as working labels rather than fixed document types. A supplier quote request may itself contain a specification, while production and traceability records may hold evidence about what was made or tested.
For each disputed item, record:
- The exact requirement or statement in dispute.
- The document, record or communication containing it.
- The production, batch, material-traceability or testing entry being compared with it.
- The product, material, batch or production scope covered by each record.
- Any revision, date, attachment or change information available.
- Whether the issue is a wording difference, a version difference, a missing record, a broken traceability link or an apparent mismatch with test information.
A difference is not automatically proof of nonconformity. It may reflect unclear scope, inconsistent revisions, missing context or an error in transcription. Those possibilities must be checked rather than assumed.
Compare the records without merging them
| Comparison point | What to check |
|---|---|
| Requirement | Exact wording, included scope and referenced attachments |
| Provenance | Where the requirement originated and what document carried it |
| Current status | Whether the record was superseded, changed or remains applicable |
| Traceability | Whether the relevant production, batch and material records connect |
| Testing | Whether testing was required, performed and recorded in the applicable context |
| Evidence quality | Whether the record demonstrates the requirement or merely refers to it |
| Authority | Which applicable project record identifies the controlling requirement |
Keep the original entries identifiable throughout the comparison. Combining fields into a new summary can make a later review difficult if the summary does not preserve which record supplied each statement.
Testing also needs careful treatment. A testing requirement does not by itself show that testing occurred, and the presence of in-line testing information does not by itself establish conformity. The applicable method, result and acceptance condition must be identified from the project’s own records.
Resolve the discrepancy through a documented decision
A practical conflict record should contain:
- The disputed requirement from each record.
- Copies or links to the relevant supporting records.
- A plain statement of the mismatch.
- The question requiring a decision.
- The role authorised to answer it.
- The decision and its stated basis.
- Every record affected by the decision.
- Any correction, replacement or further clarification required.
- The status of the conflict until the documentation is complete.
The authorised role should be asked which record controls, under what stated basis, and what must happen to the other affected records. Where the answer changes a requirement or record, the change should remain visible rather than erasing the earlier version.
If no one can identify the controlling record or the appropriate decision role, the conflict should remain marked as unresolved. Choosing one record merely because it is more recent, more complete or stored in a preferred system would create an appearance of resolution without establishing authority.
What the reader must still confirm
The cited statements do not specify:
- Which record takes precedence.
- Who is authorised to resolve a conflict.
- Which revision or change process applies.
- Which test methods or acceptance conditions govern.
- Whether tolerances, sampling rules or exceptions apply.
- Which records must be corrected after a decision.
- How long affected records must be retained.
- What deadline applies to clarification or correction.
Those points cannot be inferred from the two cited statements. The reader should check all applicable project, purchasing, technical, quality and change-control records, then confirm unresolved matters with the accountable role. If those records conflict with one another, the conflict should be documented and escalated rather than resolved by assumption.
A defensible resolution does more than make two files appear consistent. It preserves the original evidence, identifies the mismatch, records who decided the issue and shows which records were affected.