The Clockwork Update: Deciding Whether a Standing Consultancy Meeting Still Earns Its Place

Most consultancy engagements acquire a meeting. It starts as a kick-off, settles into a weekly slot, and within two months has become a fixture of the calendar: dial-in details pasted into a recurring invitation, a pack circulated the evening before, and a small cast of people who attend because they always have. Nobody decided this arrangement should be permanent. It simply accrued.

That is not a scandal. Regular contact keeps a project honest and gives a client early sight of trouble. But a recurring update is a cost, paid in the most expensive currency a UK business holds: senior attention. The question worth asking in 2026 is not whether the meeting is well run or whether the adviser is personable. It is whether the meeting changes anything. A short audit, conducted at a natural break in the work or once a quarter on longer programmes, will answer that.

Start with the question the meeting exists to answer

Every standing update should have one sentence behind it. Something like: this meeting exists so that the operations director can approve or reject the next phase of work before Friday. If the sentence cannot be said aloud without hesitation, the meeting is probably a reassurance ritual wearing a project's clothing.

A quick diagnostic: read the agendas from the last six sittings. If every item reads "update on X" or "progress against Y", no decision was ever being requested. That is useful information. It does not necessarily mean the meeting is worthless, but it does mean the client is paying for information that could usually arrive in writing.

The four-part audit

Agenda: where is the decision?

An agenda that produces decisions looks different from one that produces narration. It will contain at least one item phrased as a choice — approve, defer, fund, stop, escalate — with the relevant papers attached beforehand. Where an agenda contains only topics, the meeting will fill the time it is given, and those present will leave informed but not enabled.

Ask the adviser, politely and in advance, to mark each item as for decision, for noting or for discussion. If the answer is that everything is for discussion, the meeting is a seminar.

Attendees: necessity against habit

List everyone who dialled in during the last quarter and count how often each contributed. This is not a popularity exercise. It is a check on whether the right people are in the room. A finance director who has attended eight consecutive calls without speaking is not disengaged; the agenda has simply never needed her. A procurement lead who joined once and settled a dispute in four minutes was worth ten of the others.

Apply the substitution test: if this person were replaced by a colleague of similar seniority, would the outcome of the meeting change? Where the answer is no for several attendees, the invitation list is too long.

Outputs: a note, a call, or nothing

Every update should leave a trace. Preferably a short note recording what was decided, who owns the next action, and when it falls due. Not a transcript, not a set of slides, but a decision record that a person who was absent could read in three minutes and act upon.

If the meeting consistently produces no written output, test the alternative. Ask the adviser to replace next month's session with a two-page note circulated on the Monday. If nothing is lost, the meeting was doing the note's job at ten times the cost.

Decision rights: who can actually say yes

The most common failure in recurring updates is not poor chairing. It is a room full of people who cannot commit the organisation to anything. When the person with authority is absent, the meeting produces recommendations that then travel to a second, undocumented conversation where the real decision is made. The client ends up paying twice for the same decision.

Before the next sitting, confirm in writing who holds the mandate for each standing item. If that person cannot attend, the item should be deferred rather than rehearsed.

Three legitimate outcomes

Convert to a written note

Where the meeting mostly transfers information, a written update circulated on a fixed day is faster, cheaper and searchable. It also creates a record. Keep a short call in reserve for exceptions, convened when the note raises a question that genuinely needs conversation.

Reduce to a short call

Where decisions are needed but the pack is large, separate the two. Let the paper do the reading and hold a twenty-minute call with three or four people to decide. This works particularly well for multi-site projects, where travel and diary friction otherwise crowd out substance.

Retire it, deliberately

Cancelling a recurring meeting is not an insult to the adviser. It is stewardship of the client's own time. If the work is on track and the next genuine decision point is six weeks away, say so and book the next meeting for that date instead.

A worked example

A Midlands manufacturer ran a twelve-week improvement programme with a Tuesday 8.30am call, nine attendees and a forty-minute average. An audit of the previous eight weeks found one decision, taken in week two and revisited three times. The finance director had attended every call and spoken in none. The programme lead had been dialling in from a car park.

The client replaced the weekly call with a Monday written note and a fortnightly twenty-minute decision call limited to four people. The adviser retained a standing offer to convene an exception call within twenty-four hours. Nothing was missed, two decisions surfaced that had previously been buried in narration, and roughly eleven senior hours a month were returned to the business.

Guard against over-correction

Some recurring updates should not be touched. Where safety, regulated reporting or cash flow is involved, latency is expensive and the meeting may be the control. The point of the audit is not to cut meetings for their own sake. It is to check that each one is earning its slot.

A useful test: what would happen if the next sitting were cancelled at short notice? If the honest answer is "nothing much", that is not a reason for embarrassment. It is a reason to redesign the rhythm.

The discipline in one page

Once a quarter, record four answers in the project file: what the meeting decided, who genuinely needed to be present, what written record exists, and what would break if it were cancelled. Keep the answers short. Revisit them at the next review.

A recurring update is a tool, not an institution. Auditing it is not a sign of distrust in the adviser. It is the client taking responsibility for the one resource no consultancy can supply on their behalf.