TL;DR
Most of what happens in a vendor review meeting is a slide deck of things you already knew. The hour earns its hour only when both sides arrive with numbers neither has seen, and when somebody is willing to say what is not working. Five measures and one question do most of the work. Everything else is theatre.
- A review built on the supplier’s own deck tells you what they want you to know.
- Bring your own five numbers, measured your way, and compare them to theirs.
- The useful question is what went wrong that we did not report.
- Exceptions are the signal. Averages hide the cases that cost you time.
- Agree two actions with owners and dates, or the meeting was a status call.
- If nothing changes for two quarters, stop holding it and switch to email.
Why most vendor review meetings waste an hour
The standard shape is that the supplier presents. They bring a deck, the deck shows volumes delivered and tickets closed, everything trends in a pleasant direction, and the meeting ends.
Nothing in that is dishonest. It is also useless, because a supplier reporting on its own performance will reliably pick the measures that flatter it. So would you.
Best tools for HR Operations
The second failure is that only one side prepared. Your team arrives having read the agenda in the lift, so the only numbers in the room are the supplier’s, and the conversation can only go where those numbers lead.
The structural fix
Both sides bring data. Yours is measured your way and does not need to agree with theirs. Where the two disagree, that gap is the most interesting thing in the meeting, because it usually means you are counting different events.
One real example of that shape: a supplier counts a delivery as complete when the courier marks it delivered. You count it as complete when the person can work. Those differ by however long it takes somebody to get the machine out of reception.
Neither measure is wrong. Discovering that they differ is worth more than either number alone.
The five numbers worth bringing
Keep it to five. A review with fifteen metrics is a report, and reports get skimmed.
| Measure | How to count it | What it exposes |
|---|---|---|
| Time to usable | Order placed to person working | The gap between delivered and ready |
| Failed first attempts | Deliveries needing a second try | Address quality and courier choice |
| Retrieval success | Devices requested back that arrived | The weakest part of most contracts |
| Reopened tickets | Closed then reopened within 14 days | Whether fixes actually fixed |
| Invoice variance | Quoted against invoiced, per month | Scope creep and unexpected charges |
Retrieval success is the one to insist on. Delivery is the part suppliers optimise because it is visible and it is what wins the deal. Getting devices back is harder, less visible and far more often where the money leaks.
Where retrieval feeds disposal, ask for the sanitization standard in the same breath. NIST Special Publication 800-88 on media sanitization is the usual reference, and a supplier reporting retrieval without being able to name it has only told you half the story.
Count exceptions, not averages
An average delivery time of four days sounds fine and tells you almost nothing. What costs you is the handful that took three weeks, because each of those consumed somebody’s attention and probably a new starter’s first week.
So report the count above a threshold rather than the mean. Five deliveries over fourteen days is a sentence anybody can act on. A mean of 4.2 days is not.
The question that changes the meeting
Disclosure: RemoAsset, named below, is owned by the same people who publish HROpsLab. It is described with its limitations stated, on the same terms as every other supplier. This site takes no vendor money and sells no placements.
Ask it near the start, not at the end: what went wrong this quarter that we did not report to you?
It works because suppliers see failures you never hear about. A courier that lost a device and replaced it quietly. A warehouse that shipped the wrong specification and caught it before dispatch. A repair that took three attempts.
None of that reaches you, because it was resolved. And all of it tells you where the process is fragile.
Why suppliers usually answer
Because the alternative is worse for them. A supplier that says nothing went wrong, in a quarter where you know something did, has told you it will not raise problems early. That is a far more expensive trait than the original problem.
The good ones answer in detail, because a near miss they fixed is evidence of competence rather than an admission of failure. If you get a long honest answer, say so, and the next quarter’s answer will be longer still.
A note on who is in the room. Your account manager will have one version of this. The operations person who actually runs your shipments will have another, and theirs is more useful. Ask for them by name.
Leave with two actions, not twelve
A vendor review meeting that produces a list of twelve improvements produces none of them.
Pick two. One for you, one for them. Each with a named owner and a date. Write them in the meeting, not afterwards, and read them back before anybody leaves.
Then open the next review with those two items. If both were done, the meeting has a track record and people start taking it seriously. If neither was done twice running, you have learned something important about whether this relationship responds to conversation.
The cadence question
Quarterly suits most equipment relationships. Monthly is too often for a service where a full cycle takes weeks, and it degrades into a status call. Annual is too rare to catch anything while it is still fixable.
Where the supplier covers several countries, consider rotating the focus rather than trying to cover everywhere each time. One market in depth beats five in summary.
Suppliers that run the whole chain rather than one segment tend to have more to discuss here, because delivery, retrieval, storage and disposal all sit in one conversation. That is the practical case for running the lifecycle through one supplier. The honest counterpoint is that a single supplier also means a single account manager presenting on every part of it, so your own five numbers matter more rather than less.
The decision table
| Situation | Scale | Setup | Primary pain | Recommended starting point |
|---|---|---|---|---|
| No review happening | Under 50 | One supplier, informal | No visibility | One hour a quarter, your five numbers |
| Review is a slide deck | 50 to 200 | Supplier presents | Nothing changes | Bring your own data and the one question |
| Several regional suppliers | Distributed | Different vendor per market | Not comparable | Same five measures everywhere, rotate focus |
| Actions never completed | Any | Review exists | No follow through | Two actions only, opened at the next review |
| Two quarters, no change | Any | Mature relationship | Meeting is theatre | Stop meeting, move to exception email |
When to stop holding it
Not every supplier relationship needs a recurring meeting, and keeping one alive out of habit costs more than it looks.
Three signs it has run its course.
Nothing has changed for two reviews. Not nothing improved. Nothing changed, in either direction. That means the relationship is stable and the meeting is reporting on stability.
The actions are always yours. If every agreed item lands on your side, the supplier has stopped treating this as a two-way review and you are running their improvement programme for them.
Attendance has drifted. When the operations person stops coming and you are left with an account manager, the meeting has become a relationship call. Those have value, and they do not need an hour each quarter.
What to replace it with
An exception report. Agree the thresholds that matter, have the supplier email when one is breached, and keep an annual review for the contract itself.
That is less effort for both sides and it catches the same problems, because problems announce themselves through exceptions rather than through quarterly averages. Structured collaboration frameworks such as ISO 44001 on collaborative business relationship management make the same point at greater length.
For what to put in the contract so these measures exist at all, see our guide to equipment SLAs and what to demand.
See how one supplier covering the full chain changes the conversation at laptop lifecycle management, or read our guide to equipment SLAs.
Frequently asked questions
What should a vendor review meeting cover?
Five measures you counted yourself: time from order to somebody actually working, deliveries that needed a second attempt, the share of requested devices that came back, tickets reopened within a fortnight, and the gap between quoted and invoiced. Then one question, asked early: what went wrong this quarter that we did not report to you. Everything beyond that is usually a status update.
How often should we review an equipment supplier?
Quarterly suits most equipment relationships. Monthly is too frequent for a service where a full cycle takes weeks, so it decays into a status call, and annual is too rare to catch anything while it can still be fixed. If the supplier covers several countries, rotate the focus and look at one market properly rather than five in summary.
Why bring our own numbers if the supplier reports?
Because a supplier reporting on itself will pick measures that flatter it, which is normal rather than dishonest. The valuable moment is when your number and theirs disagree, since that usually means you are counting different events. A common example: they count a delivery complete when the courier marks it delivered, you count it when the person can work. The gap between those is the finding.
Which single measure matters most?
Retrieval success, meaning the share of devices you asked for back that actually arrived. Delivery is what suppliers optimise because it is visible and it wins the deal. Getting equipment back is harder, far less visible, and where most of the money quietly leaks. A supplier reluctant to report it is telling you something before the number does.
Should we track averages or exceptions?
Exceptions. An average delivery time of four days sounds acceptable and hides the handful that took three weeks, and those are what consumed somebody’s attention and probably a new starter’s first week. Report the count above a threshold instead. Five deliveries over fourteen days is a sentence somebody can act on, while a mean of 4.2 days is not.
How many actions should come out of a review?
Two, one on each side, each with a named owner and a date, written during the meeting and read back before anybody leaves. A review producing twelve improvements produces none of them. Open the next review with those two items, because that builds a track record and people begin to take the meeting seriously.
When should we stop holding the vendor review meeting?
When nothing has changed in either direction for two reviews, when every agreed action lands on your side, or when the operations person stops attending and you are left with an account manager. Replace it with an exception report against agreed thresholds plus an annual contract review. That catches the same problems for less effort, because problems announce themselves through exceptions.
