How to Write a Vendor Delay Message

A vendor delay message has two audiences. The supplier needs a clear response, while internal teams need to know what the delay changes.

Confirm The New Fact

State what the vendor told you and when:

Northstar confirmed today that the replacement units will ship on 22 October, nine days later than the contracted dispatch date.

Distinguish a confirmed delay from a risk. If the date is still uncertain, say that explicitly.

Translate The Delay Into Business Impact

Do not forward the supplier email without interpretation. Explain the effect:

At the new date, the units would arrive after the Berlin installation window. The training session can continue, but the live setup would move to the week of 4 November.

Name affected milestones, customers, locations, or costs. Avoid broad statements such as “this impacts everything.”

Show The Recovery Options

For example:

1. Accept the new date and move installation.
2. Pay EUR 420 for split air freight on the first ten units.
3. Use loan equipment for the Berlin session.

Include who is checking each option and when you will confirm it.

Write Separate Messages When Needed

The supplier message may ask for root cause, expedited shipping, or a service credit. The customer message should focus on the customer impact and recovery plan. Do not expose contract disputes that do not help the customer.

A useful rewrite instruction is:

Rewrite this as a concise vendor delay update. State the confirmed delay, old and new dates, affected work, recovery options, owner, and next update. Preserve all figures and contract terms. Keep vendor statements separate from our assessment. Do not invent a cause.

For customer-facing wording, use how to tell a customer about a delay. For internal dependency tracking, use the project risk update.

See Wrivio’s rewrite workflow for turning a supplier thread into a clear update for the people who need to act.