Fewer Calls, Better Answers: The Written Update That Does the Meeting's Work

Most recurring status meetings are not really meetings. They are a delivery mechanism for information that nobody wrote down, convened at a fixed hour because the alternative — someone producing a clear written account — has never been agreed. The dial-in exists to answer questions that could have been answered on Tuesday afternoon by a document read in five minutes.

That is not a criticism of clients. It is an observation about incentives. A meeting is visible; a note is not. Attendance can be recorded; comprehension cannot. And so the calendar fills, the same ground is covered, and the actual work of resolving issues waits until the call has ended.

There is a better arrangement, and it costs about forty minutes a week.

The Principle: Answer First, Convene Second

The note is not a summary of what happened. It is an anticipation of what will be asked. The distinction matters. A summary looks backwards and satisfies the writer's sense of completeness. An anticipatory note looks forwards and satisfies the reader's need to decide something.

Write it as though the client has fourteen minutes between two other commitments and will read it on a phone. If that reader finishes the page and has no remaining questions, the call becomes optional. If they finish with two specific questions, the call becomes short and useful. Either outcome is an improvement on a thirty-minute recital.

A Structure That Fits on One Page

Five blocks, in this order, no preamble.

Position against milestones. Not a percentage. A plain statement: which milestones are met, which are in flight, which have moved, and by how long. If a date has shifted, say so in the first line rather than the fourth paragraph. Clients forgive slippage far more readily than they forgive discovering it themselves.

Decisions required. Each decision gets a question, an owner, and a date by which it is needed. "Awaiting input" is not a decision request; it is a shrug with a deadline attached. Write: "Do we extend the pilot to the Leeds site in Q1, or hold until the March review? Needed by 21 November to preserve the February start."

Risks, each with a named owner. Four at most. A risk without an owner is a worry, and worries do not belong in a client document. State what would trigger the risk, what it would cost, and who is watching it — client side or ours.

Assumptions under test. This is the block most often omitted and most often missed. Every project runs on beliefs that have not yet been confirmed: that the data will be clean, that the third-party integration will behave, that the sign-off route is as described. Naming them early converts future surprises into shared contingencies.

Next actions. Who, what, by when. Keep it to six lines. If it needs more, the project has a prioritisation problem, not a communication problem.

One page. If it spills, the excess belongs in an appendix nobody will read, or in a conversation.

What Changes in Practice

On a recent engagement with a regional housing provider, the fortnightly governance call had run for eleven months. It was well attended, courteous, and largely devoted to restating the position. We replaced the pre-call pack with a single page in the structure above, issued every Thursday by noon.

Within three cycles, attendance had fallen by half — not through disengagement, but because three of the eight attendees had no decisions to make and no risks to own. The call itself shortened from sixty minutes to twenty-five and shifted almost entirely to the decisions block. Two risks were resolved in writing before the meeting, by the simple expedient of naming an owner who had not previously realised the item was theirs.

The client's programme manager described the effect plainly: the meetings had stopped being about the project and started being about the choices.

The Tone Question

Formal does not mean stiff, and brief does not mean curt. A written note carries more weight than speech, and a badly judged sentence can read as deflection long after the call would have been forgotten. Two disciplines help.

First, avoid the passive where responsibility is at stake. "The dependency was not confirmed" invites a hunt for culprits. "We did not confirm the dependency before the design freeze; we are confirming it now, with a decision needed by 4 December" closes the matter and moves on.

Second, do not soften bad news into ambiguity. UK client organisations — particularly in the public and regulated sectors — are accustomed to reading governance paperwork closely. Vagueness is not read as tact; it is read as a gap, and gaps get escalated.

When the Call Is Still Right

The note does not abolish meetings. It reclassifies them. Routine reporting disappears; genuine deliberation remains. Difficult conversations, contractual stress, relationship repair, and anything where tone of voice is doing half the work should still happen live. A written note is a poor vehicle for an apology and a worse one for a negotiation.

There is also a governance reality to respect. Some clients are obliged to convene boards at fixed intervals regardless of content, and no document will change a standing order. In those cases the note does not replace the meeting; it shortens it, and gives the chair something to structure the agenda around.

A Modest Discipline

The barrier is rarely skill. It is habit. Writing the note takes forty minutes; attending and preparing for a status call takes perhaps three hours across the attendees, and produces no artefact anyone can return to. The arithmetic is not close.

The practical step is to propose it as a trial rather than a reform. Six weeks, one page, issued on a fixed day. Keep the meeting in the calendar but let it lapse if nobody needs it. Most clients will notice the difference by week three, and the ones who do not were never reading the pack anyway.

The aim is not fewer meetings for their own sake. It is that when people do gather, they are resolving rather than reporting. A page written well on Thursday can make that happen on Monday.