A brief is a shared document or it is two different projects

Two versions of the same conversation

After a good first meeting both parties leave with a picture of the project, and those pictures are never identical. They aren’t even close, usually, because each person filled the gaps with their own assumptions and neither noticed there were gaps.

The divergence stays invisible while the work is abstract. It becomes visible at delivery, when one side sees the thing they expected and the other sees something else, and by then a great deal has been built on the misunderstanding.

This is the ordinary origin of most client disputes. Not bad faith. Two reasonable people who thought they had agreed.

Writing it down is a test, not a formality

The value of a written brief is not that it can be produced in an argument. It is that the act of writing forces the vagueness to the surface while it is still cheap to resolve.

You discover, in trying to write a sentence about what will be delivered, that you do not actually know how many of something there will be, or who is providing a critical piece, or what the client means by a word both of you have been using comfortably for a week. Every one of those discoveries is worth having early.

Sending it back for confirmation completes the test. A client reading a description of their own project will correct it where it’s wrong, and those corrections are the most valuable feedback in the whole engagement.

What has to be in it

What is being delivered, described concretely enough that both parties could recognise it. What is explicitly not included, which prevents more trouble than any other line. What the client has to supply, and by when, since a great many overruns are caused by waiting rather than by working.

Then the practical terms: timescale, price, payment points, and what happens when something changes. That last item is the one most often omitted and the one that turns a change into an argument rather than a decision.

It does not need to be long or legal in tone. A page in plain language that both sides have actually read beats a formal document nobody opened.

Vocabulary is where the divergence hides

Ordinary words carry different meanings in different trades and different organisations. Finished, draft, simple, standard, urgent, final — each of these has been the subject of a genuine dispute somewhere, because each side used it confidently in its own sense.

Where a word is doing important work in a brief, it is worth defining it in terms of something observable. Not that a draft will be provided, but what a draft consists of and what happens next. Not that the work will be finished, but what the client will have when it’s.

Changes are normal, and they need a route

No project of any length survives contact with reality unchanged, and a brief that forbids change is unrealistic rather than protective. What matters is that changes go through a process instead of accumulating informally in conversation.

The process can be very light. A note recording what changed, what it does to the price and the timescale, and confirmation from the client. Two lines in a message is often enough. The point is that both sides now hold the same updated version, which is the same job the original brief was doing.

Without that, the brief becomes a description of a project that no longer exists, and you’re back to two versions with no way to reconcile them.

When the client will not engage with it

Occasionally a client resists writing anything down, wanting to keep things flexible and informal. That preference deserves attention, because it is one of the more reliable warning signs available.

Sometimes it is genuine informality, and a short summary sent as a message after a call satisfies the need without any paperwork at all. Sometimes it reflects a client who wants the freedom to redefine the work later, and the discomfort of the conversation now is much smaller than the discomfort of the one that follows delivery.

Either way, a written note from you costs nothing and does not require their signature to be useful. A record made at the time by one party is enormously better than no record made by either.

The habit that makes all of this sustainable is small: after any call or meeting where something was decided, send a short message saying what you understood. Three or four lines, sent the same day, ending with an invitation to correct anything. It takes a few minutes, it produces a dated record without any of the formality people resist, and it catches divergence at the point where correcting it costs nothing at all.