The Supplier Decision Log: Closing Open Issues After China Sourcing Meetings

A productive supplier conversation is not complete when everyone leaves the call with a general sense of agreement. It is complete when each decision, action, open issue, and proposal has been classified, assigned, acknowledged, and connected to the documents that control purchasing, production, inspection, or shipment.

The practical objective is to establish a post-conversation control loop. Buyers should distinguish what was merely discussed from what was explicitly agreed, identify who owns the next step, define the evidence required for closure, and record what happens if a commitment cannot be met. This discipline applies to individual suppliers according to their actual conduct and operating processes; it does not depend on assumptions about nationality or conversational style.

The primary artifact is a one-page supplier decision log linked to specifications, approvals, purchase orders, schedules, and exception records. Use it after a sourcing conversation but before sampling, purchasing, production, or shipment proceeds on an assumption.

Image credit

Useful supplier records make decisions, ownership, revisions, and unresolved issues visible.

Photo by Tianhao Zhang on Unsplash. Licensed under the Unsplash License.

Set the output and rhythm before the conversation starts

Define what the meeting must produce

Open with the operational question the conversation needs to resolve. A meeting about sample approval requires a different decision from a call about late materials or a shipment hold. State the relevant stage—quotation, sample approval, purchase-order confirmation, pre-production review, inspection, shipment, or corrective action—and identify what must be decided before the next stage may begin.

Name the source documents that constrain the discussion. These may include:

• Current specification or drawing revision
• Approved sample and sample ID
• Quotation
• Purchase order
• Packaging instructions
• Inspection criteria
• Delivery plan
• Contract or quality agreement

Every topic should lead to one of four outputs:

1. Decision: A choice has been explicitly approved and can be recorded.
2. Action: Work must be completed by a named owner and deadline.
3. Open issue: Evidence, confirmation, or approval is still required.
4. Proposal: An option has been raised but is not authorized.

This distinction prevents a supplier from treating buyer interest as approval, and it prevents a buyer from treating a supplier’s tentative estimate as a firm commitment.

Use a repeatable meeting rhythm

A consistent rhythm makes the process easier for both parties:

• Before the meeting: Circulate the issue list, requested decisions, relevant revisions, and evidence needed.
• At the opening: Confirm participants, decision authority, agenda, and available time.
• During each topic: State the issue, examine the evidence, identify the decision or missing input, and assign an owner.
• Before closing: Read back decisions, actions, deadlines, and unresolved points.
• After the meeting: Send a written recap within a defined period, preferably the same business day.
• At the next checkpoint: Review overdue actions and exceptions before adding new topics.

A regular control loop is more reliable than trying to reconstruct commitments from scattered emails, chat messages, and meeting memories.

Identify who can decide and who can relay information

Record the buyer-side approvers for commercial, technical, quality, and schedule changes. Ask the supplier to name the responsible person for each deliverable rather than assuming every attendee can authorize a change.

If a response depends on engineering, management, a subcontractor, or a material supplier, mark it as conditional. For example, “delivery by 30 July, pending fabric availability confirmation by 12 July” is not the same as an unconditional delivery commitment. Escalation should begin when the named owner cannot resolve the issue by the agreed deadline—not simply because several people attended the meeting.

Convert the conversation into an owned decision record

Apply the conversation-to-record checklist

Use this checklist before closing the record:

Check	Question to answer	What to capture
Topic	What exact product, order, batch, sample, or shipment is affected?	SKU, PO, project, lot, or sample ID
Source	Which document or physical reference governs the issue?	File name, revision, date, or approved sample ID
Status	Was this discussed, proposed, decided, or left open?	One explicit status label
Decision	What was approved or rejected?	Precise outcome without conversational background
Change	Does it alter price, specification, quality, quantity, tooling, packaging, or timing?	Changed field, previous value, and new value
Owner	Who must take the next action?	Named person and organization
Deadline	When is the action or response due?	Date, time, and time zone where material
Evidence	What will demonstrate completion?	Quote, drawing, photograph, report, sample, certificate, or booking
Dependency	What must happen before work proceeds?	Approval, payment, material arrival, test, or customer input
Exception	What happens if the commitment cannot be met?	Notification trigger and escalation route
Acknowledgment	Has the other party confirmed the record?	Confirmation date or requested corrections
System update	Which controlling document must change?	PO, specification, schedule, inspection plan, or addendum

Keep one row per decision or action

Do not combine several commitments into a narrative paragraph. Give each item a stable identifier, such as D-014 for a decision, A-027 for an action, or E-006 for an exception. Preserve earlier entries instead of silently overwriting them, and link superseded records to their replacements.

Use one consistent status set:

• Proposed
• Awaiting evidence
• Awaiting buyer approval
• Agreed
• In progress
• Completed
• Blocked
• Superseded
• Rejected

A simple one-page log might look like this:

ID	Reference	Status	Decision or action	Owner	Deadline	Evidence	Exception trigger	Acknowledgment	Document update
D-014	PO 1842	Agreed	Use 48 units per master carton	Supplier packaging engineer	18 June, 15:00 CST	Revision C packaging drawing	Notify buyer if carton test fails	Confirmed 17 June	Packaging specification
A-027	Resin batch R62	Awaiting evidence	Send material certificate	Supplier quality manager	20 June	Batch-linked certificate	Place batch on hold if unavailable	Pending	Incoming inspection file
E-006	Shipment 1842-2	Blocked	Confirm recovery date after material delay	Supplier planner	19 June, 12:00 CST	Revised production and booking plan	Escalate if delay exceeds five days	Pending	Delivery schedule

Require evidence that matches the commitment

Evidence should fit the nature of the commitment:

• Verify dimensional changes with a revised drawing.
• Verify material decisions with a labeled sample or material certificate.
• Use photographs only when they show the required detail, batch identity, and date.
• Verify measurable requirements with test or inspection results.
• Verify shipment milestones with a confirmed booking or logistics document.

A general assurance such as “no problem” is not evidence that a technical requirement has been met or a shipment milestone secured. Close an item only when the defined deliverable has been received and, where necessary, approved.

Resolve conflicts between chat, recaps, and controlling documents

The decision log is an index and audit trail, not automatically a substitute for the purchase order, specification, or signed agreement. State which document governs if records conflict, and update the controlling document whenever an authorized conversation changes price, scope, quality, packaging, or timing.

Do not rely on silence as acceptance of a recap. Request explicit confirmation or corrections. If a mismatch could affect safety, compliance, fit, quality, cost, or delivery, pause the affected work until the discrepancy is resolved. Record who approved the revision and when it became effective.

Write recaps that are neutral, specific, and easy to correct

Use a fixed recap structure

A practical recap should contain:

1. Meeting date, channel, and participants
2. Products, orders, batches, or documents covered
3. Decisions made
4. Actions, owners, and deadlines
5. Open issues and evidence required
6. Approved changes and commercial effects
7. Exceptions or risks raised
8. Documents requiring revision
9. A request for acknowledgment or factual corrections

Send the recap promptly while the details remain current. Ask the supplier to confirm individual items rather than approve a long narrative that may contain several different commitments.

Use neutral recap language

Situation	Neutral recap language
Recording a decision	“The agreed packaging configuration for PO 1842 is 12 units per inner carton and 48 units per master carton.”
Recording a proposal	“The supplier proposed changing the fabric weight from 220 gsm to 210 gsm. This is not approved, and production should remain on hold for this point.”
Confirming ownership	“Li Wei will send revised drawing C by 15:00 China Standard Time on 18 June.”
Requesting evidence	“Please attach the material certificate for the resin batch before we close item A-027.”
Clarifying an open issue	“The delivery date remains open pending confirmation of material availability.”
Correcting a mismatch	“Our notes differ on the carton dimensions. We recorded 52 × 34 × 28 cm; your message shows 52 × 36 × 28 cm. Please confirm the correct dimensions before carton printing.”
Recording buyer feedback	“The sample result at measurement point B was 14.8 mm against the required 15.0 ± 0.1 mm.”
Handling schedule risk	“You advised that the original completion date may not be achievable. Please provide the cause, affected quantity, containment action, and earliest supportable date.”
Requesting acknowledgment	“Please reply ‘confirmed’ or list corrections to items D-014 through A-019 by 12:00 China Standard Time tomorrow.”
Preventing accidental authorization	“Discussion of this option does not authorize a material, tooling, price, or production change.”
Superseding an instruction	“Decision D-011 is superseded by D-016. Revision B should no longer be used for production.”
Closing an item	“Item A-027 is closed based on the attached certificate dated 20 June and buyer quality approval received on 21 June.”

Keep the language operational, not personal

Describe the requirement, observation, evidence, scope, and requested response. Avoid assigning motives when the available evidence shows only a mismatch, omission, or delay.

Instead of writing, “You ignored our instructions,” identify the instruction and observed result: “Packaging specification revision C requires two labels per carton; inspection photographs show one label on 34 cartons. Please segregate the affected quantity and provide the rework plan by 14:00 CST.”

Similarly, replace “This is unacceptable” with the failed criterion, affected quantity, containment request, and response deadline. Invite corrections to factual records without reopening decisions that were already formally approved. For critical technical, legal, or compliance terms, use qualified translation rather than relying solely on informal chat translation.

Build trust through delivery history and useful feedback

Track repeated delivery, not conversational confidence

Trust becomes operational when commitments are repeatedly completed and supported by evidence. Maintain a simple history containing:

• Commitment made
• Due date
• Actual completion date
• Evidence received
• Quality of the deliverable
• Advance warning provided when delayed
• Corrective action completed

Evaluate reliability across several cycles rather than treating one smooth meeting or one mistake as conclusive. Accurate early warnings are more useful than unsupported reassurance because they allow the buyer to contain risk. The resulting record can support decisions about trial-order size, lead-time assumptions, inspection intensity, or escalation.

Give feedback that can produce corrective action

Link feedback to a specification, approved sample, drawing, or other documented requirement. State the observed result and affected scope, then separate immediate containment from root-cause analysis.

For example, first request segregation of the affected batch and a shipment hold. Then request the cause analysis, permanent correction, responsible owner, and verification evidence. Confirm whether the corrective action applies only to the current batch or to future production as well.

Apply the same transparency to buyer-caused changes, late approvals, or unclear instructions. A credible record should show where buyer actions affected cost or schedule instead of assigning every disruption to the supplier.

Handle exceptions visibly

An exception should be disclosed and controlled before it becomes an undocumented deviation. Encourage early reporting by responding predictably: contain the risk first, assess the evidence, and then decide whether recovery, concession, rework, or rejection is appropriate.

Step	Record required	Decision enabled
Notify	What changed, when it was identified, and which order or batch is affected	Whether work should pause
Contain	Segregation, rework hold, material stop, or shipment hold	How to limit exposure
Assess	Quantity, quality, cost, compliance, and schedule impact	Whether the exception is tolerable
Propose	Recovery options with evidence and realistic dates	Which response to approve
Authorize	Named approver and conditions	Whether the supplier may proceed
Verify	Inspection, test, sample, document, or delivery evidence	Whether the action worked
Close	Final disposition and preventive follow-up	Whether normal controls can resume

Constructive supplier relationships and formal controls are complementary. Direct discussion can help surface problems early, but rapport should not replace specifications, approvals, inspections, contractual remedies, or quality controls. Timely disclosure should receive a consistent response, while repeated failures should trigger proportionate controls and escalation.

Final next move: Pilot a one-page decision log

Choose one upcoming supplier meeting connected to a sample, purchase order, production checkpoint, inspection, or shipment decision. Create the log in advance with columns for:

• Item ID
• Product or order reference
• Status
• Decision or action
• Owner
• Deadline
• Required evidence
• Exception trigger
• Acknowledgment
• Controlling document update

Send the first recap on the same business day and ask the supplier to confirm or correct each item. At the next checkpoint, review overdue actions and exceptions before adding new topics. Close items only when the required evidence is attached and the controlling documents have been updated.

After two or three cycles, assess whether the log has reduced repeated questions, undocumented changes, missed deadlines, and disputes about what was agreed. Keep the format if it improves those outcomes; revise it if it creates records without producing clearer decisions.

Scope and limits

This article is an editorial decision framework based on secondary sources. It does not verify any specific supplier, factory, product, quotation, legal requirement, compliance status, travel condition, or commercial outcome. Buyers should independently confirm the facts and evidence relevant to their own order before making a decision.

Sources

• ISO 9001:2015 — Quality management systems requirements
• OECD Due Diligence Guidance for Responsible Business Conduct