How to write a project brief

By the WorkKitly Team · Last updated: November 2026 · 7 min read

Projects rarely fail in the doing. They fail in the gap between what the client said on a call and what they pictured while saying it — a gap nobody discovers until the first draft lands and the reply begins “not quite what I meant.” A project brief closes it: one page, written by you from the discovery call, stating the outcome, the deliverables, the exclusions and the dates, signed off by the client before any quote exists. You write it because you pay for the gap — in revision rounds, in scope arguments, in work done twice. The client had a conversation; you get the consequences. So you hold the pen.

1. What a brief is not

A brief is not a proposal. The proposal template sells: it argues that you are the right hands, at a stated price. The brief defines what the work actually is. Writing the selling document before the defining one is how quotes come to rest on a conversation instead of a scope — and how “the website” in your price turns out to be nine pages in the client's head and five in yours.

A brief is not the contract either. The contract carries the legal weight — payment terms, ownership, endings. The brief carries the picture. It is deliberately lighter: no clauses, nothing a client needs a lawyer to approve. A client will read and correct one honest page today; a fourteen-page agreement gets skimmed, signed and argued about later.

And it is not a quote: no number lives in a brief, only the shape of the price. Keep the whole thing to one page. A brief that needs a table of contents has become a specification, and a specification is real, billable work — scoping a large build in full is a paid phase, not a favour folded into a sales call. For the ordinary project, one page is not a summary of the picture. It is the picture.

2. The anatomy: seven parts, each one a protection

None of the seven parts is long; each is a line you will be glad exists in week three.

The outcome. One sentence, in the client's words — not your tasks. “A site that takes bookings while I'm away” is an outcome. “Build a website with a booking form” is a task list wearing the outcome's clothes. When a disagreement starts later, both sides return to this sentence.

The deliverables. Countable nouns only. “A website” cannot be counted, checked or finished; “a five-page site — Home, Menu, Story, Visit, Contact” can. Every deliverable should be something a stranger could tick off a list. It is the same inclusion discipline as productizing a service: what is inside, named one by one.

What is not included. The section that does the protecting. Two or three exclusions, written while everyone is still friendly: no copy written from scratch, no online ordering, no logo redesign. Scope creep rarely arrives as a demand; it arrives as an assumption — and an assumption dies on contact with a list the client has already agreed to.

What the client owes you. Inputs, with dates: text, images, logins, decisions. The onboarding checklist collects them later; the brief promises them now, with dates, because a timeline is only as real as its inputs. “Photos by Friday” is a commitment. “Photos soon” is a delay with good manners.

The timeline, with the rounds counted. Start, draft dates, finish — counted in working days, not calendar hope. And name the review rounds: “two rounds of revisions” ends arguments that “revisions included” starts forever. A round is a defined thing: one consolidated set of comments, answered once. If your process has a standard shape, your process notes already hold it — the brief simply quotes it.

The success test. How both sides will know it is done: the acceptance line. “The site live on the client's domain, the booking form delivering to their inbox, every page loading on a phone.” Vague projects end in feelings; briefed ones end in a test.

The price shape. Not the number — the shape. A fixed fee for the whole, a range with what moves it, or the start of a retainer. The shape tells the client what kind of commitment this is; the figure waits for the next step.

3. From call to signature

The workflow is four moves, and the first has a deadline. Write the brief the same day as the discovery call — within twenty-four hours, while the call is still what was said, not what you remember. Memory edits itself overnight; by Friday you will sincerely recall agreements that were never made. A brief written on day one is evidence. Written on day four, it is a reconstruction.

Send it back for edits in the document. The client corrects the page, not the memory: changes arrive as changed words you can both see, not as a second call. Most clients fix two or three lines — a page count, a date, a missing exclusion — and each fix is the brief doing its job while corrections are still free.

The sign-off is a line, not a ceremony. A dated reply — “looks right, go ahead” — under the final version is enough for most solo work. It is not the legal instrument — the contract carries that weight, and the brief rides inside it as the scope it refers to. What the reply gives you is proof the client saw the picture and called it theirs.

Only then does the number get built. Price from the signed page with the project price calculator, and let the proposal quote the brief back: same deliverables, same exclusions, now with a figure attached. A client comparing your quote against the page they approved finds nothing to renegotiate. That quiet is what the brief was for.

4. A brief at full size

Here is the whole thing, for a fictional but ordinary job: a bakery website. Its length is the lesson: the complete brief below runs to 183 words.

That is all of it. If your briefs run to three pages, the excess is almost never information — it is anxiety, yours. Cut until a busy client can check the page in two minutes, because a brief nobody reads protects nobody.

5. How briefs go bad

The brief written after the quote. It reads fine and protects nothing: every line was chosen to justify a number already sent, so the gaps the client would have caught stay hidden until delivery. Sequence is the entire trick — brief, signature, price.

The brief the client never saw. Written for your own files, it is a diary, not an agreement. It can organise your work; it cannot settle a single disagreement, because the other party never agreed to be in it.

The brief that grows by chat message. A page agreed in November quietly acquires a page, a feature and a favour across a winter of small messages, each one too small to argue about. The fix is versioning, not vigilance: any change that would alter a deliverable, a date or the price shape is re-issued as brief v2, with the changed lines visible — the same habit that keeps scope creep priced instead of absorbed. File each version where your working documents live; the template library is where the blank waits between jobs.

None of this is bureaucracy. It is one page, written once, at the only moment when agreement is cheap. Every later document in the chain — proposal, contract, invoice — assumes this page exists. Most project pain is the sound of that assumption failing.

Questions

Related: the brief in the chain

The brief sits in the middle of a chain: written from the discovery call, priced with the project price calculator, argued for by the proposal, and started by the onboarding checklist, which collects the inputs it promised. It is the shortest document in the chain — and the only one every other document assumes. And when two honest readings of it collide mid-project, how to handle a scope dispute runs the three-pile resolution that settles it against the brief's own words. The brief is also where the rounds get counted: how to charge for extra revisions builds the menu that prices the rounds beyond the included count.