Stop, Check, Send: The Case for a Scheduled Pause Before Client Delivery

In many UK professional-services firms, the space between a finished draft and the client's inbox is governed by habit rather than design. A partner reads it on the train. A senior associate forwards it with the words "looks fine to me". A deadline does the rest. The work is usually good. The process around it is usually accidental.

That is not a criticism of the people involved. It is an observation about systems. When review is informal, it is also inconsistent, invisible and difficult to improve. A deliberate pause — short, structured and recorded — changes the economics of delivery without slowing it down.

The real cost of the casual glance

Errors that reach a client are expensive in a way that internal errors are not. They consume goodwill, invite correspondence, and sometimes require a correction that undermines an otherwise sound piece of work. Client confidence is asymmetric: it accumulates slowly and erodes quickly. A single misstated figure, an out-of-date appendix or a tone that reads as dismissive can do more damage than a week of good drafting repairs.

The informal review also hides its own failures. If no one can say who checked a deliverable, or against what standard, then the firm cannot learn from the occasions when something slips. The lesson stays personal rather than becoming procedural.

What a review gate is — and is not

A review gate is not a meeting. It is not a committee, a layer of bureaucracy or a reason to delay. It is a defined checkpoint with three properties: it is triggered by a specific event (a deliverable is about to be sent), it is governed by explicit criteria, and it produces a recorded decision with a named owner.

The distinction matters. Firms often believe they already have a review process because someone senior reads the important things. That is a safety net, not a gate. A gate is repeatable, and it applies whether or not the senior person happens to be available.

A five-point pre-send check

The checklist below is deliberately short enough to complete in ten minutes for routine work, and longer only where the risk justifies it.

Scope. Does the deliverable match what was agreed? Confirm the brief, the agreed outputs and any exclusions. It is common for a document to be excellent and yet answer a slightly different question from the one the client asked. Scope drift is rarely dramatic; it is usually a paragraph that grew.

Evidence. Are the figures traceable, the sources dated and the assumptions labelled? In UK practice, where client decisions often turn on a single number, this is the point at which a second pair of eyes earns its keep. Check calculations against the underlying schedule, not against the summary.

Tone. Is the register appropriate to the relationship and the risk? A formal client may read brevity as distance; a long-standing client may read formality as a change in temperature. Read the opening and closing paragraphs aloud. They are where tone is most exposed.

Risk. What could be misread, and what is missing? Consider confidentiality, regulatory language, third-party information and any statement that could be quoted out of context. Ask plainly: if this appeared in a client board pack without our covering note, would it still stand up?

Sign-off. Who is accountable for this going out? A name, not a team. Record it against the deliverable, along with the date and any conditions attached to the release.

The question of who signs

Named sign-off is the part firms resist most, because it appears to concentrate liability. In practice it concentrates clarity. A single accountable individual can delegate the checking, but not the decision. Thresholds help: routine correspondence may require one reviewer, while advice with financial, legal or regulatory consequences may require two, one of whom is independent of the drafting team.

For smaller firms, a two-person rule is often enough. Where a team is genuinely stretched, the gate should be narrowed rather than abandoned — apply it to client-facing advice and formal reports first, and extend it as capacity allows.

Keeping the pause short

The common objection is speed. A well-designed gate adds very little, because it replaces time already spent on informal checking and rework. The practical disciplines are straightforward: use a single template rather than a bespoke process for each engagement; keep a simple log of what was checked and by whom; and review the log quarterly to see which criteria are catching problems and which are being ticked without thought.

Beware the opposite failure. A gate that expands into a full re-drafting exercise is no longer a gate. Its purpose is to confirm fitness for release, not to achieve perfection. Where a substantive issue is found, the correct outcome is to return the work with a clear note — not to reopen the entire document in the final hour.

What clients notice

Clients rarely see the process. They see its effects: fewer corrections, more consistent quality, and a clear sense of who is responsible. Those effects compound. A firm that can say, credibly, that every deliverable passes a defined check before release is describing a form of reliability that is difficult for competitors to fake.

A place to start

Choose one deliverable type — the monthly report, the formal advice note, the proposal — and run the five-point check for a month. Record the outcome each time. At the end of the month, review what the gate caught. The answer will usually justify extending it, and the record will make the case better than any argument for process ever could.

The pause is not the opposite of pace. It is what makes pace sustainable.