The Unwritten Brief: Six Understandings Worth Confirming Before Work Begins

By the time a professional services engagement reaches its first working session, two documents usually exist: the client’s brief and the team’s proposal. A third, less visible document also exists — the set of assumptions each party believes the other has accepted. It is rarely written down. It is often more influential than either formal document.

The risk is not that clients behave unreasonably. It is that ordinary phrases — “keep us posted”, “a couple of rounds”, “just a quick call” — carry different weight on each side. At DGA Ltd, we treat those gaps as a client-guidance issue rather than a legal one. The aim is not to remove all flexibility. It is to make the important expectations visible while they are still inexpensive to correct.

Why silent agreements form

A brief is usually written to win confidence, not to govern delivery. A proposal summarises approach and cost. The kick-off meeting tends to focus on momentum. In the space between those documents, assumptions fill the gaps. Each party supplies the interpretation that seems most natural from its own side of the table.

UK clients are often reluctant to appear demanding; delivery teams are often reluctant to appear inflexible. Politeness encourages both to leave matters unsaid. The result is a working relationship built on two slightly different versions of the same engagement.

Six common assumption traps

1. The response-time gap

The client hears “we will be responsive” and expects same-day replies. The team means within two working days, with urgent matters handled by telephone. Neither statement is dishonest; they are simply different service levels.

Surface it by agreeing a standard response time, a definition of “urgent”, the hours in which it applies, and who covers absence or leave. A simple line in the delivery note — “routine queries within two working days; urgent matters by telephone during agreed hours” — is clearer than an adjective.

2. The revision horizon

“A couple of rounds” is one of the most elastic phrases in professional services. For a client, it can mean “until the document feels right”. For a team, it can mean two consolidated sets of comments. The difference is rarely disputed at the outset; it becomes expensive later.

Define what a round is: one consolidated set of written comments, returned once, rather than a series of individual observations. Explain what counts as a revision and what is a change of direction. State what happens beyond the included rounds — normally a change note, a revised timetable or additional fees. This is not bureaucratic if it is explained as a route to keeping the original promise.

3. The scope edge

Clients often assume that adjacent tasks are included because they are obviously connected. Teams often assume they are excluded because they were not priced. The result is a dispute about a small piece of work that feels large in principle.

A one-page scope should list inclusions, exclusions and client dependencies in plain English. It should also say what is out of scope by default. The point is not to fence off goodwill; it is to ensure that extra work is a conscious choice rather than a quiet expectation.

4. The meeting assumption

The client may expect a weekly in-person session. The team may have planned a fortnightly call. Both can be reasonable, but they produce different costs and different rhythms of decision-making.

Agree the cadence, duration, attendees and notice period. Clarify which meetings are working sessions and which are formal governance. Confirm whether a named decision-maker will be present, and what happens if they are not. A short meeting protocol prevents a longer argument about availability.

5. The approval vacuum

Clients sometimes believe the team can proceed on informal nods. Teams often believe they are waiting for a named approver. Work stalls, and each side believes the other has caused the delay.

Name the approver and, where sensible, a deputy. Define what constitutes approval — an email, a signed form, a minute — and how quickly it will be turned around. If dates depend on client inputs, say so explicitly. A timetable without dependencies is only a hope with dates attached.

6. The handover expectation

At the end, clients may expect editable files, source materials and unrestricted future use. Teams may intend to provide final formats under a defined licence. Both positions can be legitimate, but they should not be discovered at the closing meeting.

Confirm the formats to be supplied, whether working files are included, how intellectual property or licence rights operate, and what support follows handover. If something is excluded, say so early and in ordinary language.

How to surface assumptions without sounding defensive

A useful approach is a first-fortnight confirmation note. It is not a contract and should not read like one. It is a short record of what the team understands the client has asked for, written in neutral language and sent while memories are fresh.

Frame it as a service: “To make sure we are working to the same brief, we have set out our understanding of the main working assumptions.” Invite correction rather than approval. Ask open questions where the answer matters: “What does ‘responsive’ mean in practice for your team?” or “Who will confirm final approval when we reach that stage?”

Keep commercial terms in the commercial documents. Keep working assumptions in a single, easily updated note. Review it at the first fortnight and again before the first substantive deliverable. If a mismatch emerges, do not debate memory. Restate the outcome the client wants, offer the practical options, and adjust the note.

A short audit worth running

Read the brief and proposal with a pen, highlighting every adjective and every vague verb. Then write one sentence for each of the six areas above as you understand it. Send those six sentences to the client and ask them to mark any that are wrong. The exercise takes minutes; the correction can save weeks.

The aim is not to eliminate every ambiguity. That would be neither possible nor desirable. It is to make the important ones visible while they are still cheap to resolve. A client who corrects an assumption in week one is a client cooperating with the engagement. A client who discovers it at handover is a client with a grievance. The difference is rarely a matter of goodwill. It is a matter of when the conversation happens.