Four Questions, Ten Minutes: The Monthly Supplier Note That Beats the Annual Autopsy

Somewhere in most UK client organisations there's a supplier review that happens once a year, involves a slide deck, and takes place after the thing has already gone wrong. It is conducted politely. Everyone agrees the relationship is broadly positive. Then somebody mentions the invoice, and the room remembers why it's there.

The trouble is timing. An annual review is archaeology. By the time you're sitting in it, the slippage you're discussing happened in the spring, the extra hours were absorbed in July, and the person who could have fixed it has since moved to a different job.

Catch drift while it's still cheap

Drift is nearly free to fix in week two and expensive by week ten. A delivery date that slips by three days in month one is a phone call. The same three days discovered in month four is a re-sequenced programme, a rearranged site visit and a conversation with your own board.

So the review needs to be earlier and smaller. Not a lighter version of the big meeting — a different instrument entirely. Something closer to a postcard.

The postcard principle

One side of A5. If it doesn't fit, it isn't a postcard anymore, it's a report, and reports get drafted by three people and arrive a fortnight late.

The constraint is the whole point. Four prompts, short answers, plain English. The kind of thing a supplier's account lead can write on a Thursday afternoon without asking anyone for a template.

The four prompts

1. What was delivered? Concrete and dated. Not "good progress on the workstream" but "migration script handed over on the 14th; user testing pack issued on the 21st." If a month genuinely had nothing deliverable in it, say so — that's information too.

2. What is slipping? This is the one that earns the format its keep, and the one that needs the most honesty. "Nothing slipping this month" is a perfectly good answer, but it should be earned rather than reflexive. If a date has moved, it goes here with the new date and a one-line reason. Early, small and unglamorous beats late, large and formally escalated every time.

3. What is unclear? Open questions, decisions owed by either side, ambiguities in the statement of work, that thing nobody has ever quite resolved about who owns the reporting feed. This prompt quietly overlaps with a deferred decision list, and that's fine — surfacing the same open question twice from two directions is not a failure.

4. What happens next? The next 30 days, with names and dates. Two or three lines. Enough that both sides know what the following month is supposed to look like before it starts.

How it actually runs

The rhythm that works in practice is unglamorous. Same day each month — the last Thursday is a popular choice, because it lands before the month-end invoice run and after most delivery pressure has passed.

The supplier writes the note. That's deliberate. It puts ownership of the picture with the people doing the work, and it means the write-up reflects what they know rather than what a client has inferred. The client then adds two or three lines at the top: anything they want to flag, anything they're waiting on, anything that's changed on their side.

If everything on the note is green, there is no meeting. If something is amber, there's a ten-minute call, not a workshop. Red gets a phone call that day, which is exactly what you'd want.

Everything goes into one folder. Twelve notes a year, one page each, in date order. That folder is worth more than any slide deck you could build in January.

The month where the answer is awkward

The format survives its own bad months because it's routine. A supplier writing "the integration date has moved by two weeks, here's why, here's the new date" in a small regular note is having a normal professional conversation. The same news delivered as a summoned meeting feels like an incident, and people delay incidents.

Lower the stakes and you get earlier news. Earlier news is cheaper news.

What it does to the annual review

The yearly sit-down doesn't disappear — contracts, rate reviews and renewals still need one. But it stops being an investigation and becomes a summary. You walk in with twelve notes rather than a vague memory of how things felt in Q2. Disagreements are easier to settle because both sides have been writing the same story down all year.

It also helps the supplier. Twelve tidy monthly notes are a decent portfolio when they're pitching for the next phase, and a fairer defence when someone challenges their performance with a feeling rather than a record.

Where it goes wrong

Three familiar failure modes:

• It grows. Someone adds a RAG column, then a KPI table, then a resource histogram. By month four it's a mini-board pack and it stops arriving. Guard the one-page limit.
• It becomes a stick. If the note is used to build a case against the supplier, you'll get marketing copy back within two months and honest answers never again. Frame it as a pulse check and behave accordingly.
• It gets skipped. The months that get skipped are always the busy ones, and the busy ones are exactly when you need the note. If a month is genuinely too frantic, send three lines. Don't send nothing.

Start next month

You don't need a template or a launch email. Put four headings in a message, send it to the supplier's account lead, and ask for a response by Thursday. Then shrink it until it fits on a postcard.

The best time to hear that a delivery date is moving is six weeks before it moves, not six weeks after. A small, boring, monthly note does more for a working relationship than a well-catered review ever will.