A vendor check-in call takes ten minutes. Writing down what was actually said, in a form that’s useful three weeks later, is the part that usually gets skipped — which is exactly why so many “we followed up” claims turn out to be hard to substantiate when a delivery slips anyway.
What to record every time
A follow-up worth keeping on record includes:
Date
When the contact happened — not approximately, the actual date.
Contact method
Call, email, site visit, video meeting. This matters because different methods carry different weight — a verbal commitment on a call is worth less than the same commitment confirmed in writing afterward.
What the supplier said
As close to their actual words as practical, not a paraphrased summary that loses the specifics. If they said “probably early next month,” record that — not “vendor confirmed early delivery.”
New commitment
Did the vendor give a specific, dated commitment, or a vague estimate? These are different things and should be recorded differently. “We’ll ship by the 15th” is a commitment. “Should be soon” is not.
Evidence
Did the vendor provide anything to support the commitment — a photo of completed work, a shipping booking reference, an updated production schedule? Evidence-backed commitments carry more weight than verbal reassurance alone.
Risk or delay reason
If a delay was mentioned, what reason was given? Recording the stated reason matters even if you’re skeptical of it — a pattern of different reasons across multiple calls is itself useful information.
Next action
What happens as a result of this call — nothing, a follow-up email confirming the commitment, an internal escalation, a request for documentation.
Owner
Who’s responsible for the next action. A follow-up without an assigned owner tends not to happen.
Next follow-up date
When contact will happen again. Leaving this open-ended is how follow-ups drift from weekly to “whenever someone remembers.”
Questions worth asking during the call itself
The quality of the record depends on the quality of the conversation that produced it. A few questions tend to surface more than a general “how’s it going”:
- “What specifically is left before this is ready?” — a vague “almost done” answer often means something different from what you’d assume.
- “What would need to happen for this date to slip further?” — this surfaces risk the vendor might not volunteer unprompted.
- “Can you send me something in writing confirming that?” — asked every time a new commitment is given, not just when you’re suspicious.
- “Has anything changed since we last spoke that I should know about?” — an open invitation that sometimes surfaces a sub-order delay or documentation issue the vendor hadn’t thought to mention.
None of these are confrontational. They’re just specific enough that a vague answer becomes noticeably vague, rather than blending into a reassuring-sounding but empty response.
A bad follow-up record
Called vendor. They said it’s coming soon. Will check again later.
This tells a reader nothing usable. No date, no specific commitment, no next action, no owner. Three weeks from now, this entry is worthless for figuring out what actually happened or what was promised.
A good follow-up record
- Date: 14 March, 10:40am
- Method: Phone call with account manager
- Supplier said: “Manufacturing is complete, final inspection scheduled for 18 March. Should ship 20 March.”
- New commitment: Ship date 20 March (previously forecast 25 March — improved)
- Evidence: None provided verbally; requested written confirmation
- Risk/delay reason: N/A — this call reflects improved status
- Next action: Request written confirmation of 20 March ship date and inspection report once complete
- Owner: J. Rahman
- Next follow-up: 19 March (day after scheduled inspection)
This version is specific enough that someone who wasn’t on the call can understand exactly what was said, what’s expected next, and who’s responsible for making sure it happens.
Reading patterns across multiple follow-ups
A single follow-up record is useful on its own, but the real signal often shows up when you compare several in sequence. A vendor who cited “waiting on a sub-supplier” as the delay reason in March, then “logistics booking issue” in April, then “quality hold” in May isn’t necessarily lying about any individual reason — but a shifting set of explanations, each plausible on its own, is a different risk profile than one consistent, ongoing issue being tracked to resolution. Reviewing a PO’s full follow-up history periodically, not just the most recent entry, is how that pattern becomes visible instead of getting lost between separate conversations.
A note on commitments and disputes
If a vendor’s verbal commitments become relevant to a contractual dispute, what actually holds weight depends on your specific contract terms and applicable law — this is a matter for your own legal counsel to assess, not something a follow-up log can settle on its own. What a good follow-up record does provide is a clear, dated account of what was actually said and when, which is useful input if that conversation becomes necessary — not a substitute for it.
Why this matters more than it seems
Follow-up records rarely get reviewed in the moment they’re written. Their value shows up later — when a delivery slips and someone needs to reconstruct what was promised, when, and by whom. A habit of writing specific, dated, evidence-aware follow-up notes is the difference between having that answer in thirty seconds and spending an afternoon searching old emails hoping to find it.
The PO Delivery Tracker‘s Stage 6 (Vendor Readiness / Expediting) keeps every follow-up entry attached directly to the PO it concerns. Pro adds a Cross-PO Action Register, so open commitments and owners are visible across your whole portfolio, not just one PO at a time.