The Unanswered Thread: Making Client Inaction Contractually Legible

A mandate can be delayed by a dispute, a missing signature or a change of sponsor. It can also be delayed by nothing at all. An approval request is issued, copied to the right people and logged in the portal. Then the thread goes quiet. Weeks later, the project plan shows a gap that nobody owns and the client asks why the firm did not proceed. The contractual question is simple but uncomfortable: did the client decide, or did the firm simply wait?

For UK advisory firms, the answer should not depend on recollection. Silence is a common feature of complex client relationships, particularly where decision rights are diffuse and internal approvals sit outside the room. The drafting response is not to convert every unanswered email into consent. It is to identify where silence is intended to have contractual effect, make that effect visible, and preserve a record that both sides can rely on.

Silence is an event, not an absence

Most engagement letters describe what happens when a client gives an instruction. Fewer describe what happens when the client gives none. That gap matters because advisory work is often sequenced around client-dependent decisions: sign-off of a scope change, acceptance of a deliverable, release of information, approval of a draft report or authorisation to contact a third party.

A well-drafted mandate treats non-response as a defined event with a defined consequence. That may be a deemed approval after a stated period, an obligation to escalate, a right to suspend work, or an express statement that silence has no effect at all. Each is commercially defensible. What is less defensible is ambiguity, because ambiguity invites the firm to infer consent when convenient and the client to deny it when challenged.

Map the decisions before drafting the clause

The starting point is not the clause library. It is the mandate map. Firms should identify the decisions that genuinely affect time, cost or liability, and distinguish them from routine communications. A client's failure to comment on a weekly progress note should not trigger the same machinery as a failure to approve a revised scope or a regulatory submission.

A useful discipline is to classify decision points into three groups. First, decisions where the firm needs positive approval and silence must not be treated as consent. Second, decisions where a deemed-approval mechanism is commercially appropriate because the client has been given adequate information and a fair opportunity to object. Third, decisions where the firm retains discretion and the client's silence is irrelevant. Drafting becomes clearer once the parties agree which category applies to each milestone.

The engagement letter should also name the authorised respondent. A notice sent to a copied mailbox is not the same as a notice sent to the individual with authority to approve. Where decision rights sit with a committee, the firm should know the route and the expected turnaround, and should avoid drafting a response period that the client's own governance cannot meet.

Deemed approval and its limits

Negative-option clauses, often expressed as deemed approval or deemed acceptance, can be effective in commercial contracts. They are not a substitute for clear notice. A clause that simply states that silence constitutes approval may be read narrowly, particularly where the consequence is significant or the client has not been alerted to the mechanism.

Drafters should therefore specify the trigger, the information to be provided, the response window, the method of objection and the consequence of failing to object. The clause should state whether the deemed approval covers the whole deliverable or only the specific matter put forward. It should also address whether a deemed approval can override a client's internal compliance requirements, regulatory approvals or express restrictions in the engagement letter. In most cases it should not.

There are limits beyond drafting. A deemed approval cannot manufacture a decision that the client had no contractual power to make, and it should not be used to bypass a mandatory approval process. Firms should also consider whether the mechanism is fair and transparent in context, particularly where the client is a regulated entity or a public body subject to its own governance. The clause is a commercial tool, not a means of ambushing the counterparty.

Time-impact notices and escalation ladders

Silence often becomes a scheduling problem before it becomes a legal one. Where the mandate includes time-impact notices, the firm should link them to the response mechanics. A notice that identifies a delay event should state what decision is required, by when, and what happens if no decision is received. The firm can then rely on the notice as evidence that the client was put on notice of the consequence.

An escalation ladder is equally useful. A first notice may be a routine reminder. A second may identify the contractual consequence and the date on which work will be suspended. A third may trigger a formal decision meeting or a written instruction from the client's sponsor. The ladder should be proportionate and should be set out in the engagement letter rather than invented after the delay has occurred. It should also identify who at the firm is responsible for escalation, so that silence is not left to the original engagement team to manage indefinitely.

The evidence trail

If silence is to be relied on, the firm must be able to show what was sent, to whom, when and by what method. That means retaining the notice, the delivery record, the portal log and any reminder. It also means keeping the underlying information that the client was asked to approve, because a deemed approval is only as useful as the material it relates to.

Firms should avoid relying on an oral warning that a deadline is approaching. A short written notice is more useful than a detailed recollection. Where the client responds informally, the firm should confirm the position in writing and identify whether the response is an approval, an objection or a request for more time. The record should be capable of withstanding scrutiny from a client, an insurer or a dispute resolver, not merely satisfying the firm's own project tracker.

Preserving the relationship

The commercial risk of a silence clause is not usually legal invalidity. It is resentment. A client that feels trapped by a technical default may comply while withdrawing cooperation elsewhere. The remedy is transparency. Firms should explain the mechanism at the outset, use it sparingly and pair it with a human escalation route. A telephone call to the sponsor before a deemed approval takes effect is often more valuable than a perfectly drafted clause.

For Poulten & Graf's commercial clients, the practical lesson is that silence should be designed into the mandate rather than discovered in the file. A clear decision map, a visible notice process and a proportionate escalation ladder do not make the relationship adversarial. They make it predictable. In advisory work, predictability is part of the service.