A production timing change is a single event but it creates several simultaneous choices: do you accept the new date, request mitigation, split shipments, or look for alternatives? The right choice depends on a clear, auditable record. This article gives a compact working method for recording the reason, product impact, new date, and recovery question and then turning that record into the next sourcing decision.

Make the change record immediately and consistently

Start a single change log entry as soon as the supplier notifies you. Each entry should be one line in a shared spreadsheet or your sourcing system so status checks and decisions remain visible. Time stamp the entry and name the person who received the update.

Include four mandatory fields first: supplier reason, product impact, supplier new date, and recovery question. Add supporting fields such as SKU, PO number, original date, quantities affected, and any supplier evidence like factory photos, QC reports, or shipping booking references. Keeping this format consistent speeds later comparison and escalation.

• Mandatory fields: timestamp, notifier, reason, impacted SKUs and quantities, new date, recovery question
• Supporting fields: PO number, batch number, evidence links, negotiated concessions, next follow up date

Phrase and test the recovery question

The recovery question is the operational test you ask the supplier to force a concrete plan. Write it as a single, specific request such as Can you recover X days by adding a second shift, or can you ship a partial batch by X date? Replace vague phrases with measurable actions and deadlines.

After you submit the recovery question, ask the supplier to confirm actions, responsible person, and delivery evidence. If their reply is another vague promise, follow up with narrower alternatives. A clear recovery answer is often the difference between an actionable mitigation and a future dispute.

• Examples: Can you complete final assembly two days earlier by shifting to a night shift? Can you ship 30 percent of the order by date X?
• Require: specific action, who will do it, expected date, and proof to deliver (photo, production log, booking)

Document product impact precisely

Do not record only aggregate impact. Specify which SKUs, colorways, sizes, or components are delayed and how the delay affects downstream operations like packaging, inspection, or value added services. Note whether the delay affects finished goods, subcomponents, or raw material arrivals.

Quantify the impact: units delayed per SKU, percent of the PO, revenue at risk, and any knock-on timing such as missed retail windows. This level of detail lets procurement, sales, and operations compare mitigation options and calculate true cost of delay.

• Capture: SKU, units impacted, percent of PO, critical components affected, downstream processes blocked
• Add a short impact note for each stakeholder: sales launch, promotional dates, and inventory safety stock

Verify evidence and judge reliability

Treat supplier claims as hypotheses to verify. Ask for dated production photos, booking confirmations, packing lists, or material receipts. For repeated suppliers, compare this event to past behavior in your change log to judge whether the new date is credible.

If evidence is thin, escalate follow up frequency and consider independent verification such as third party inspection or a factory call. The goal is not to punish the supplier but to create a reliable basis for your next sourcing decision.

• Request specific evidence tied to the recovery plan: shift rosters, purchase orders for substitute components, or QC checklists
• Use past performance metrics in your log: on time history, frequency of date changes, and response time to recovery questions

Translate the record into clear options and timelines

From the record build a short options matrix. Typical options are accept the new date, request a partial shipment with penalties or cost sharing, escalate for priority, or initiate alternative sourcing. For each option list expected dates, costs, and operational consequences such as additional freight or rework.

Assign decision owners and deadlines. For example an option to air freight partial stock requires procurement to approve extra cost within two business days and logistics to secure capacity by a fixed date. Use the change log entry as the single source of truth so decisions remain traceable to the original supplier claim.

• Options matrix columns: option, actions required, responsible person, financial impact, deadline
• Make a recommended option and a fallback so stakeholders can sign off quickly

Follow up, escalate, and close the loop

Set a follow up cadence based on risk. For low impact delays a single confirmation the week before revised ship date may suffice. For high impact delays set daily or alternate day check ins until the recovery question is answered with verifiable evidence. Record each follow up in the same change log entry so the record shows progression.

If the supplier fails to meet commitments, escalate using the documented chain: procurement lead, supplier account manager, and then senior commercial contact. If escalation does not work, the recorded options matrix supports rapid decisions about partial acceptance, rerouting components, or engaging alternate suppliers. Close the loop by updating the log entry with the final decision, agreed concessions, and any revised SOPs to reduce recurrence.

• Follow up schedule: low risk weekly, moderate risk twice weekly, high risk daily
• Escalation path: procurement lead to commercial manager to senior supplier contact; attach log entry to each escalation message

Open a change log entry now and capture the four mandatory fields for the current delay.