The Unwritten Brief: A Pre-Engagement Test for Professional Firms

Most engagement letters are drafted with care around the parts that are easy to see: the services, the fee, the timetable, the standard terms. The difficulty usually sits elsewhere. It sits in the assumptions nobody articulated, the client dependencies nobody owned, the change triggers nobody defined and the decision rights nobody allocated. These are not legal technicalities. They are commercial facts about how the work will actually be delivered.

When those facts remain unwritten, the consequences are predictable. A matter expands without a corresponding conversation about fee. A client team misses a review date and the firm absorbs the delay. A new stakeholder asks for a different output, and the adviser makes a judgement call about whether to absorb the work or raise it. By the time the invoice arrives, the relationship is carrying an argument that should have been settled before the first meeting.

A scope test is not a substitute for a well-drafted engagement letter. It is a commercial discipline that sits alongside it. The aim is simple: make the unwritten brief visible while the relationship is still easy.

Where scope actually slips

Scope does not usually fail at the headline deliverable. It fails at the boundaries. A client assumes that “support” includes attendance at internal meetings. The firm assumes that the client will provide clean data by an agreed date. Neither assumption is unreasonable. Neither is recorded. The work begins, the assumption is tested, and the first person to notice is often the person preparing the invoice.

The same pattern appears with change. A professional-services engagement rarely changes in one dramatic moment. It changes through a series of small, reasonable requests: an extra workshop, a second jurisdiction, a revised timetable, a new board paper. Each request feels minor in isolation. Together they reshape the commercial basis of the work. Without a shared definition of what constitutes a change, the firm is left to decide retrospectively whether it should have charged for something it has already done.

Decision rights matter for the same reason. If the client’s project lead cannot authorise additional fee, and the firm’s engagement partner is not involved in the day-to-day request, then a small change can sit unresolved for weeks. The work continues. The commercial position drifts.

A one-page test before work begins

The most useful scope test is short enough to be used. A single page, completed jointly with the client, is usually sufficient. It should answer four questions in plain language.

First, what are we assuming? These are the conditions that must hold for the engagement to proceed as priced. Examples might include timely access to a named finance contact, availability of historical data, or a single point of coordination on the client side. The test is not whether the assumption is flattering to either party. The test is whether it is explicit enough that both parties would recognise it if it failed.

Second, what do we need from the client, and by when? Dependencies should be named, dated and owned. “Client to provide information” is not a dependency. “Client finance director to provide completed template by 20 January” is. The difference is not bureaucratic. It is the difference between a plan and a hope.

Third, what triggers a change? The trigger might be a new entity, a new jurisdiction, a material shift in timetable or a request that falls outside the agreed output list. The point is not to make change difficult. The point is to make change visible. A change trigger should lead to a short note, an estimate and a decision, not a dispute at the end of the matter.

Fourth, who decides what? The client should name the person who can approve a change in scope or fee. The firm should name the person who can commit to it. If those two people are not in the room when the request is made, the process should say what happens next. This is not about hierarchy. It is about avoiding the slow accumulation of unresolved commercial questions.

Assumptions are not small print

There is a tendency to treat assumptions as protective language buried near the back of the letter. That is a mistake. An assumption is a working condition. It should be discussed, not merely drafted.

A useful discipline is to ask, for each assumption: what happens if this is not true? If the answer is “we will need to re-plan and re-price”, that belongs in the engagement conversation. If the answer is “it will probably be fine”, it probably belongs in the test as well, because “probably” is where margin goes to die.

The commercial benefit is not only protection. It is clarity. When assumptions are shared, the client can see what the firm needs to deliver the work well. That often improves the quality of the engagement before it has begun.

Dependencies belong in the plan, not the post-mortem

Client dependencies are frequently the least comfortable part of the conversation because they can sound like blame in advance. They need not be. A dependency is simply a fact about sequence. The firm cannot complete a review without the client’s data. The client cannot receive a draft before its own team has commented. Writing that down is not an accusation. It is planning.

The practical step is to attach each dependency to a named owner and a date, and to state the consequence of delay. That consequence might be a revised timetable, a change in fee or a reallocation of resource. The important thing is that it is agreed before the delay occurs, not negotiated after it.

Change triggers protect judgement

Professional firms often absorb small changes because raising them feels disproportionate. That instinct is understandable, but it has a cost. It trains the client to expect absorption. It also asks the adviser to make commercial judgements in the moment, when the easier course is usually to say yes and sort it out later.

A change trigger gives the adviser a neutral reference point. It is not the adviser saying no. It is the engagement saying: this is different from what we agreed. That distinction matters. It protects the adviser’s judgement and the client’s trust at the same time.

The commercial point

A scope test is not a sign of mistrust. It is a sign that both parties intend the work to be delivered on a stable footing. The engagement letter records the bargain. The scope test records the operating assumptions behind it.

For UK professional-services firms, the discipline is especially useful where work is complex, multi-stakeholder and delivered over time. Those are exactly the conditions in which small omissions become large commercial questions. A one-page test will not eliminate every disagreement. It will make the important ones visible earlier, when they are still a conversation rather than a dispute.