“Chased again” describes an activity, but it does not explain what a supplier owes you, what their last reply meant or what you should do tomorrow. A supplier follow-up tracker becomes useful when it turns each outstanding item into a clear next action, with the business impact and decision owner alongside it.
This guide is for everyday coordination such as delivery confirmations, document requests, quotations and agreed project inputs. It is not a guide to contractual disputes or purchasing law. The aim is to make routine follow-through easier to share and review, while keeping commitments and spending decisions with the people authorised to make them.
Start with one row per outstanding request
Use the request as the unit of work. One supplier might owe you a delivery date, a revised quotation and a product specification. Combining all three under the supplier name makes it hard to tell what is finished. Separate rows are appropriate when the requests have different owners, deadlines or consequences.
Give each row a short reference and a description that another person could understand without reading the whole email chain. “Order 42: confirm delivery window for display stands” is more useful than “delivery”. Link or refer to the original correspondence in your agreed records, then summarise the current position in the tracker.
Include the fields that change what you do next
Start with a compact set of fields. A useful test is whether a column helps someone understand the request, take the next action or make a decision. Add other information only when it solves a recurring coordination problem. A spreadsheet or shared list can be sufficient if access and ownership are clear.
Distinguish your internal required-by date from the supplier’s confirmed commitment. If the business needs an item on Thursday but the supplier has not agreed that date, the tracker should show that gap. Treating a preferred date as a promise can leave everyone planning around an assumption.
| Field | What to record |
|---|---|
| Request and reference | The precise answer or item needed and the source message |
| Owner and supplier contact | Who follows through and who can answer |
| Required by / confirmed by | Your business need alongside any supplier commitment |
| Last meaningful response | A dated summary of what the supplier actually said |
| Next action and date | A specific action with a named owner |
| Impact and decision owner | What is affected and who can authorise a change |
Replace vague statuses with a visible next move
A status should tell a colleague what kind of attention is needed. Try “request sent”, “awaiting supplier”, “internal decision”, “date confirmed” and “complete”. Keep the wording simple enough that people apply it consistently. Do not use “complete” merely because someone replied; close the row when the required outcome has been checked.
Pair every live status with a next action and date. For “awaiting supplier”, the action might be “ask for the dispatch reference on Tuesday”. For “internal decision”, it could be “owner to choose whether to accept the revised delivery window”. A row that cannot name a next action may need clarification before more chasing.
- Weak entry: pending; chased Monday.
- Useful entry: awaiting supplier; request a confirmed delivery window from the account contact on Wednesday.
- Escalated entry: internal decision; owner to confirm whether the revised date is workable before the customer update.
Write a follow-up the recipient can answer
Use the reference, ask the precise outstanding question and explain the practical timing. A long forwarded chain with “any update?” can make the recipient work out what you need. Keep the tone clear and professional, and distinguish a request for information from an instruction that changes an order.
Here is a fictional follow-up: “Regarding order 42, please confirm the delivery window for the display stands. We are planning the room setup and need to know whether delivery is expected before Thursday afternoon. If that is still unconfirmed, please tell us when you expect to be able to confirm it.” The supplier can answer the question or identify the next point of certainty.
After a call, record the useful substance rather than a verdict such as “all sorted”. Note the commitment, any conditions and the person who gave the information. Where appropriate, send a written summary for confirmation through the agreed channel.
Escalate because of the impact, with a decision to make
Agree escalation rules with the owner before a difficult item arises. A missing document might simply need another enquiry; an unconfirmed item needed for tomorrow’s client visit may need a decision today. Base the escalation on the affected work and remaining options, rather than on an arbitrary number of unanswered messages.
A useful escalation says what is missing, which commitment is affected, what has been tried and which decision is needed. If alternatives are available, present only options that have actually been checked. Do not book replacements, accept changed costs or promise a customer a new date unless that authority has been agreed.
Review the next actions, then close the loop
Filter the tracker by actions due and decisions outstanding. Review older rows too: an item without a recent update can be forgotten even when its date has been moved forward. If a request is no longer needed, close it with a reason rather than quietly deleting the row.
When the answer or delivery arrives, check it against the original need and update the person whose work depended on it. A confirmed delivery date may close the date enquiry while leaving receipt of the goods as a separate task. This distinction keeps the tracker honest and gives the next person a reliable place to continue.
Put it to work.
- Track a specific outstanding request rather than a supplier name alone.
- Record your required date separately from a supplier’s confirmed commitment.
- Give every open row a next action, review date and route to an authorised decision.
Could a little support make a difference?
Tell Anna about the task or process you would like help with. A clear starting point is enough for a first conversation.
Discuss your support
