The Room Is Not the Default: Triage Before You Schedule a Client Meeting

In UK professional services, the meeting request arrives dressed as a courtesy. A client asks whether we can jump on a call, find a slot this week, or talk something through. The instinct to accept is strong, and usually well meant. But the calendar is a delivery resource, not a gesture of goodwill. Before the invitation is sent, it is worth asking what the client actually needs.

The cost hidden in a habitual yes

Every meeting carries preparation, attendance, minutes, follow-up and the quiet cost of divided attention. Those costs are manageable when the meeting has a clear purpose. They become wasteful when the meeting is standing in for an unanswered question, an unsettled scope or a decision the client has not yet made. In those cases, scheduling can make the work feel more active while leaving the underlying issue untouched.

A written response is often faster, clearer and easier to rely on later. A short call can resolve tone or nuance in minutes. A full meeting earns its place when several people must agree, when trade-offs need discussion, or when the relationship itself requires direct conversation. The task is to tell these apart before the diary fills.

Start with the request behind the request

Most client requests fall into three broad categories. The first is an information request: the client needs an answer, a confirmation or a document. The second is a decision request: the client needs to choose between options, approve a position or authorise a next step. The third is a coordination request: several parties need to align, and a conversation is the most efficient way to do it.

Each category suggests a different channel. Information usually belongs in writing. A decision may need a short call if the options are sensitive, but it should still be framed in writing beforehand. Coordination may justify a meeting, provided the right people attend and the decisions sought are stated in advance.

A four-question triage

A simple routine can be applied to each new request before a slot is offered.

First, what output is required? If the client needs a single answer, a confirmation or a document, a written reply is likely to be sufficient. If the client needs consensus across several stakeholders, a meeting may be appropriate. If the client needs reassurance on a sensitive matter, a brief call may be better than a long email.

Second, who must attend? A meeting without the person who can decide is a discussion, not a decision. If the decision-maker cannot attend, the better route may be a written note that sets out the options and asks for a response by a named date.

Third, what is the deadline and what depends on it? Urgency is not the same as complexity. A request that has become urgent because a decision was deferred may be better served by a clear written ask than by a meeting that reopens the subject.

Fourth, what record is needed? Formal approvals, instructions and scope changes should be confirmed in writing. Relationship repair or delicate negotiation may need a conversation first, but the outcome should still be recorded afterwards.

The three routes

A written response works best when the question is clear and the answer can be stated plainly. It should restate the request, give the answer, set out any next action and name the owner. A useful closing line is to invite a specific reply if the note has not covered the point, rather than offering a meeting by default.

A short call works when nuance matters, when tone is at risk, or when a quick exchange will prevent a long chain of emails. It should be deliberately short, with an agenda in the invitation, the decision-maker present and a note circulated afterwards. Fifteen minutes with a clear purpose is often more productive than thirty minutes without one.

A full meeting is justified when several parties must work through trade-offs, when scope is genuinely unresolved, or when governance requires a recorded discussion. Even then, the invitation should state the purpose, the inputs required, the decisions sought and the person responsible for the record. If those details cannot be supplied, the meeting is not ready to be booked.

When the request is really a symptom

Reflexive scheduling often masks an unclear brief. A client asks for a meeting because the scope has not been pinned down, or because a decision has drifted and no one has named it. In these cases, the triage should produce a short written framing before any meeting takes place. Set out the understanding, the options, the decision required and the date by which it is needed.

That note often removes the need for a meeting altogether. Where it does not, it makes the meeting shorter and more useful. It also leaves a cleaner record, which matters when instructions are later reviewed or when a project changes hands.

A routine that protects the week

A ten-minute triage at the start and end of each day is enough for most teams. New requests are held in a short queue and marked as written, call or meeting. Written requests are answered in the next response block. Calls are offered only where they add something a note cannot. Meetings are booked only when the purpose and attendees are clear.

The client experience need not suffer. A reply that says the question can be answered in writing now, with an offer of a short call if the client would prefer to talk it through, gives the client choice while protecting the team’s time. It is direct, helpful and easy to act on.

For DGA Ltd, the principle is straightforward: match the channel to the work. The meeting that did not need to happen is not a missed opportunity. It is a preserved one. Triage is not avoidance. It is the discipline of giving each client request the response it actually requires.