How to Turn an Unresolved Supplier Answer into a Verifiable Follow-Up Request

Executive introduction

A supplier’s answer can be relevant without resolving the issue. Statements such as “the inspection was completed,” “the product meets the requirement,” or “the change has been implemented” tell you the supplier’s position, but they do not necessarily provide enough information to verify it.

The correct next step is not to reject the answer automatically or accept it as confirmation. Record the answer accurately, keep the issue classified as unresolved pending evidence, and request documented information that is identifiable, retrievable, and reviewable. ISO guidance on documented information supports a structured approach to identifying and controlling information used to operate processes or retained as evidence, although it does not prescribe a universal format for supplier responses (ISO 9001:2015 documented-information guidance).

The objective is to reach one of three defensible investigation outcomes:

• Verified: The reviewed evidence supports the specific point under investigation.
• Not verified: The evidence conflicts with the answer or does not support it.
• Still unresolved: The evidence is missing, incomplete, unclear, outdated, or outside the relevant scope.

Issue-investigation frame

Reader task and intended outcome

When a supplier’s initial response is relevant but inconclusive, your task is to convert it into a testable follow-up request. This involves four actions:

1. Record what the supplier actually stated.
2. Identify the exact point that remains unresolved.
3. Specify the documented information needed to test that point.
4. Review the submission before deciding whether the issue is verified.

Do not strengthen the supplier’s statement while summarizing it. For example, “we checked the material” should not become “the material passed inspection.” Those are different claims.

Communication principle: acknowledge without confirming

Separate receipt of the supplier’s message from acceptance of its content. Suitable wording includes:

• “Thank you for clarifying your position.”
• “We have recorded your answer, but the issue remains open pending review of the supporting information.”
• “To verify this point, please provide the records listed below.”

Avoid language that closes the investigation before evidence has been reviewed:

• “Confirmed.”
• “Understood and accepted.”
• “This resolves the issue.”
• “We trust that the requirement was met.”

The follow-up should not accuse the supplier of dishonesty or question its motives. Focus on the missing verification step:

“The current response does not include the record needed to verify the inspection result.”

This is more precise and constructive than:

“You have not proved that your answer is true.”

Business-culture and communication considerations

Directness and respect can coexist. Use specific language, but avoid cultural stereotypes, sarcasm, idioms, implied blame, and vague urgency.

Make a clear distinction among four separate stages:

1. Acknowledgment: You received the response.
2. Understanding: You understand what the supplier claims.
3. Verification: You reviewed evidence that tests the claim.
4. Approval or closure: Your organization made the applicable decision.

A response can complete the first two stages without completing the last two.

Keep the request focused on the issue rather than the commercial relationship. Give the supplier a structured opportunity to:

• provide the requested information;
• explain why the information is unavailable;
• correct or limit the original answer;
• identify an alternative record supporting the same point; or
• explain any discrepancy between the answer and the records.

Use consistent names for the product, component, process, site, requirement, order, batch, period, and issue reference. If one message says “Model A,” another says “the current unit,” and a third says “the shipment,” the scope may become unclear even when everyone intends to discuss the same subject.

Turn the initial answer into an evidence request

Step 1: Extract the supplier’s exact claim

Record the answer without strengthening, weakening, or reinterpreting it.

Investigation element	What to capture	Drafting prompt
Supplier statement	The exact claim made	“Your response states that…”
Relevant subject	Product, component, process, site, shipment, or period at issue	“Does this statement apply to…?”
Claimed action or condition	What was done, checked, changed, approved, or found	“Please identify the record showing…”
Timing	When the claimed activity occurred	“Please provide the date or applicable period…”
Responsible function	Who created, reviewed, or approved the information	“Please identify the responsible role or function…”
Missing support	What currently prevents verification	“The current response does not include…”

For example, suppose the supplier writes:

“The issue was checked, and the new process is already in use.”

This contains at least two claims: a check occurred, and a process change was implemented. It does not identify what was checked, the criteria or result, the process revision, the effective date, the applicable site, or the affected products. Each missing element may require a separate evidence request.

Step 2: Define what would verify the claim

Do not ask only for “proof” or “supporting documents.” Those phrases leave the supplier to guess what will satisfy the investigation.

Instead, name the information needed to test the claim. Depending on the issue, request:

• document or record title;
• unique identifier, revision, or version;
• creation, completion, or issue date;
• product, process, site, order, batch, lot, model, shipment, or period covered;
• responsible author, reviewer, approver, laboratory, or function;
• recorded result, conclusion, or status relevant to the issue;
• applicable requirement or acceptance criteria;
• relevant pages, attachments, or referenced records;
• approval or authorization status; and
• a readable file or controlled link containing the complete relevant record.

These details help establish whether the information is identifiable, applicable, current, complete, and retrievable. They do not establish that its contents are accurate merely because a document exists. ISO’s documented-information guidance addresses the role and control of documented information, while ISO 19011 provides broader evidence-oriented guidance for management-system auditing.

Step 3: Match the request to the unresolved point

Unresolved point	More verifiable follow-up request
The answer says an action was completed	Request the dated completion record, identifier, scope, and responsible function.
The answer says a check was performed	Request the inspection or check record, criteria used, recorded result, date, and identifier.
The answer says a requirement was met	Request the record showing the applicable requirement, evaluated subject, result, and approval status.
The answer says a change was made	Request the controlled change record, revision information, effective date, approval status, and affected scope.
The answer refers to another document	Request that document and the exact section or page supporting the statement.
An attachment is incomplete	Request the complete and legible record, including identifiers, relevant pages, and referenced attachments.
The answer does not identify its scope	Ask which product, process, site, batch, model, order, shipment, or period the answer covers.
The answer cannot currently be supported	Ask the supplier to state that the record is unavailable, explain the gap, and identify any alternative documented information.

One document may not resolve every part of the issue. If the supplier claims both that a change was approved and that it was implemented, an approved change record may support approval but not implementation. Evidence of the effective date and affected production scope may also be necessary.

Step 4: Make the response reviewable

Ask the supplier to submit the evidence in a form that allows another reviewer to locate and assess the relevant information without relying solely on the supplier’s explanation.

The response should include:

• the evidence as an attachment or accessible controlled link;
• a short explanation connecting each item to the unresolved point;
• the document title, identifier, revision, and date;
• the exact page, section, field, or recorded result to review;
• any limitation in product, site, batch, order, or period coverage;
• any known inconsistency with the initial answer; and
• a clear statement if the requested information does not exist or cannot be retrieved.

A useful connection statement is:

“Record ABC-123, revision 2, page 4, identifies the inspection result for Batch 456 produced at Site X on the stated date.”

A vague connection statement is:

“Please see the attached files.”

Evidence-quality checklist

Before treating the issue as verified, check:

• The evidence addresses the exact question under investigation.
• The covered product, process, site, batch, model, order, shipment, or period is identifiable.
• The record is legible and complete enough to review.
• Its title, identifier, date, revision, or status is visible where applicable.
• The responsible function, reviewer, approver, or issuing body is identifiable where relevant.
• The applicable requirement or acceptance criteria can be identified.
• The result or conclusion is explicit rather than inferred.
• Referenced attachments, pages, and supporting records are included.
• The information does not conflict with other evidence already collected.
• Redactions or omissions do not prevent verification.
• The evidence supports the claim rather than merely repeating it.
• The investigation record identifies who reviewed the evidence and what conclusion was reached.

Follow-up evidence request template

Subject line

Evidence request for unresolved issue: [issue reference] — [product/process/site/period]

Message template

Hello [supplier contact or function],

Thank you for your response regarding [brief issue description].

We understand your response to state that:

[Quote or neutrally summarize the supplier’s exact statement.]

We have recorded this answer. The issue remains open pending verification, because the current response does not include enough documented information to confirm [specific unresolved point].

Please provide the following:

1. Requested evidence: [Name the document, record, or documented information needed.]
2. Relevant scope: [Product, component, process, site, model, batch, lot, order, shipment, or period.]
3. Identification details: [Document title, identifier, revision or version, and date, where applicable.]
4. Verification location: [Relevant page, section, field, result, or attachment.]
5. Responsible function: [Role or function that created, reviewed, approved, or issued the information, where relevant.]
6. Requirement and result: [Applicable requirement or acceptance criteria and the recorded outcome.]

Please also explain briefly how each submitted item supports the statement above.

If the requested information is unavailable, please state that clearly and provide:

• the reason it is unavailable;
• whether the initial answer should be corrected or limited;
• any alternative documented information that may support the point; and
• the scope that can and cannot currently be verified.

Please provide the response by [date and time zone]. If more time is needed, please reply by that date with the expected submission date and the reason for the delay.

Until the supporting information has been reviewed, we will continue to record the issue as:

Unresolved — supplier answer received; verification evidence pending.

Regards,
[Name or function]
[Issue reference]
[Contact details]

Optional supplier response table

Requested item	Supplier response	Document identifier and revision	Relevant page or section	Attachment included?	Scope or limitation
[Item 1]
[Item 2]
[Item 3]

Review language after evidence arrives

Use wording that preserves the distinction between receiving information and verifying the claim:

• Receipt only: “We received the submitted information and will review it against the unresolved point.”
• Clarification needed: “The record was received, but its scope or connection to the issue is not yet clear.”
• Incomplete evidence: “The submission does not include the referenced attachment, applicable criteria, or recorded result.”
• Conflict identified: “The submitted record appears inconsistent with the earlier answer. Please reconcile the two.”
• Verified: “The reviewed information supports the specific point identified in this investigation.”
• Not verified: “The information reviewed does not support the specific claim under investigation.”
• Still unresolved: “The available information is insufficient to reach a verification conclusion.”

Final next move

1. Complete and send the template with one clear response date and time zone.
2. Log the issue as open pending evidence rather than confirmed or closed.
3. Review submitted records against the evidence-quality checklist, not against the supplier’s explanation alone.
4. Record the conclusion as verified, not verified, or still unresolved, together with the evidence and reasoning used.
5. If the deadline passes or the submission remains insufficient, keep the issue unresolved and route it through your organization’s applicable investigation or escalation process.

Scope and limits

• This article addresses communication and evidence requests during supplier issue investigation.
• It does not establish that a supplier’s claim is true, false, compliant, or noncompliant.
• ISO 9001 guidance supports structured treatment of documented information, but it does not prescribe one universal supplier-response format.
• ISO 19011 provides guidance for auditing management systems. Its evidence-oriented discipline may inform an investigation, but a supplier follow-up is not automatically a formal audit.
• U.S. Consumer Product Safety Commission requirements and guidance depend on the product, responsible business role, and applicable legal requirements. Evidence appropriate to one product or issue may not be appropriate to another; relevant businesses should consult the CPSC Business and Manufacturing Guidance.
• The existence of a document does not by itself establish that its contents are accurate, applicable, current, or sufficient.
• Do not request irrelevant, excessive, privileged, confidential beyond necessity, or legally restricted information.
• Do not describe a certification, test, inspection, or record as mandatory unless an applicable requirement makes it mandatory.
• The selected image provides general visual context only. It does not depict a verified supplier meeting, investigation, audit, or evidence review.

Image credit

“People seated at tables under a covered outdoor seating area” by panpan ma. View the image source. Licensed under the Unsplash License.

Sources

• ISO 9001:2015 — Guidance on the requirements for documented information
• ISO 19011 — Guidelines for auditing management systems
• U.S. Consumer Product Safety Commission — Business and Manufacturing Guidance