A brief is a decision document, not a wish list
A brief that reads as a list of hopes — improve efficiency, grow revenue, modernise systems, sort out the culture — cannot be scoped, cannot be priced and cannot be judged when it ends. It is not a failure of ambition; it is a failure of decision. Somebody has to choose which of those matters most in the next six months.
The purpose of the brief is to let a serious consultancy say whether the work is worth doing, what it will take, and what it will not achieve. That conversation is only possible if the brief states a problem in terms somebody could disagree with.
The best briefs we see are one page. The appendices behind them are long, but the front page is a single decision: this is the outcome, this is where we are, this is what we cannot change, this is who decides.
The five things it must contain
The outcome, expressed as a result and not an activity: not 'review our pricing' but 'increase gross margin by three points without losing our top twenty customers'. There has to be a way to tell, at the end, whether it happened.
The current position, honestly stated. What has been tried, what failed, what the numbers actually look like, and what the internal politics are. A consultancy that discovers the real problem in week four has spent your money finding out what you already knew.
The constraints: budget range, deadline, systems that cannot change, people who will not move, regulatory limits. A brief that pretends there are no constraints produces a plan that cannot be executed.
Decision rights. Who signs off, who can say no, who has to be consulted, and how quickly. This single item determines whether a project takes three months or nine.
The measure of success, agreed in advance. If the board will judge the work by a number, say which number now, while it can still be designed into the work.
What vagueness costs
A vague brief produces one of two outcomes. Either the consultancy defines the scope itself, which means you are buying their interpretation of your problem, or the engagement proceeds on time and materials, and the scope expands politely until the budget is gone.
Both are expensive in different ways. The first produces a competent piece of work aimed at slightly the wrong target. The second produces a long piece of work that never quite arrives.
Vagueness also makes it impossible to hold the engagement to account. If nobody agreed what success looks like, every review meeting becomes a discussion about effort rather than outcome.
Who writes it, and how long it takes
It should be written by the person who owns the outcome — a chief executive, a managing director, a finance director with the board behind them — not delegated to somebody who will not be in the room when the decisions are taken.
Two hours is usually enough for a first draft. The value is in the argument about the draft, because that is where the outcome and the constraints get genuinely agreed. Where the leadership team cannot agree a brief, the engagement should not start: no consultancy can resolve a disagreement that has not been named.
Bring the draft to the first conversation and expect it to be challenged. The right consultancy will tell you which of the five items is missing, and will say so before quoting a fee rather than after.