The Missing Signature: Identifying Absent Client Decision-Makers Before Approvals Stall

When a client project slows down, the cause is often assumed to be disagreement. In practice, it is frequently non-attendance. The finance director is copied on every update but has never joined a call. The operations manager owns the process but sends a delegate who cannot approve anything. The procurement lead appears at kick-off and then disappears until invoice. These are the absent decision-makers: roles that hold authority but are not present when a decision is required.

The pattern is easy to miss because communication continues. Emails are answered, minutes are circulated, and no one formally complains. Yet the project is accumulating small delays that later surface as rework, escalation, or a signature that takes three weeks to obtain. For UK service teams, the practical task is not to fill every meeting with more people. It is to identify which decisions need which authority, and to confirm that the authority is actually available.

Absence rarely announces itself

A missing decision-maker does not usually send apologies for a whole project. They send a deputy, or they ask to be kept in the loop, or they rely on a colleague to summarise. Each of these is reasonable in isolation. Together they create a gap between the people discussing the work and the people accountable for approving it.

The gap has a cost. A scope question is discussed for two weeks before someone notices that the client's technical lead has a veto. A data protection query is raised late because the client's compliance contact was not in the design review. A final acceptance drags because the budget holder has not seen the acceptance criteria since the proposal. None of these failures looks dramatic at the time. Each one consumes time and goodwill.

The cost sits in the gaps

Three costs recur. The first is decision latency: work waits while a message travels through someone who can only recommend, not approve. The second is hidden risk: a stakeholder with a regulatory, security or operational concern is not present to raise it early. The third is rework: a deliverable is built to an interpretation that the absent authority later rejects.

There is also a quieter cost to the client relationship. When decisions are repeatedly deferred, the service team begins to look slow or evasive, even though the delay sits on the client side. Mapping presence makes that visible without turning the conversation into a blame exercise.

Build a one-page presence map

The map should fit on one side of A4, preferably landscape. It is not a contact list and it is not a full stakeholder analysis. It is a decision-by-decision view of who needs to be present, and whether they are. Use role titles rather than names where possible, so the map survives staff changes.

Keep the gap rating simple: green where the right authority is present and engaged; amber where attendance or authority is unclear; red where a required decision-maker has not been seen at the point of decision. The map is not a performance score for the client. It is a working control for the project.

Five questions that reveal the missing seat

A short set of questions, asked at project start and again at each phase gate, will usually expose the gap:

1. Who signs this off, and who can say no?
2. Who holds the budget, and have they seen the current scope?
3. Who owns the process day to day, and who owns it after handover?
4. Who has a technical, compliance or security veto?
5. Who is not in this conversation but will be affected by the outcome?

If the answer to any of these is vague, the seat is probably empty. A response such as 'we will need to check' is not obstruction; it is useful evidence. Record it against the relevant decision and agree who will confirm the route.

Keep authority in the room without adding meetings

The remedy is rarely a new meeting series. It is a sharper use of the meetings that already exist.

First, make the agenda decision-led. A pre-read should state the decision required, the options, the recommendation and the consequence of delay. Status updates can be circulated in writing.

Second, ask for delegated authority rather than a delegated presence. If a deputy attends, confirm in advance whether they can approve or only note. An observer in the room does not close a decision gap.

Third, align attendance to phase. Kick-off, design sign-off, acceptance and handover need different client roles. Not everyone needs to attend everything, but the accountable role should be present when their decision is on the table.

Fourth, use a short decision slot within an existing governance forum. Fifteen minutes with the right people is more useful than a new hour-long meeting with the wrong ones.

Fifth, escalate absence early and factually. If a required decision-maker has missed two scheduled decision points, raise it with the client project manager and agree a route. Keep the language neutral: the issue is decision availability, not attendance as a courtesy.

Finally, record decisions and absences in the same place. Silence is not sign-off. A minute that says 'no objections raised' is weaker than a minute that names the approver, the decision and the date.

A short routine for client managers

Once a month, take twenty minutes to review the presence map. Confirm the next three decisions due, check that the accountable roles are scheduled or reachable, and update any red or amber gaps. Share the map with the client project manager before the review, not after. At the end of each quarter, look across the portfolio for repeated gaps: the same role missing at the same phase is a pattern worth fixing in the next engagement.

Adsum4 works with UK organisations on practical client management and operations routines. The aim here is modest but useful: not full attendance, but full authority. A missing signature identified early is cheaper than one discovered at the point of invoice.