How to get a client to actually read the brief

The brief was six pages. Two weeks into the project, the client asks for a feature you explicitly excluded in section two.

“I don’t remember seeing that,” they say.

They didn’t read it. You both know it. Now you’re in a negotiation that didn’t need to happen.

The problem isn’t the brief

Most briefs that don’t get read aren’t bad briefs. They’re PDFs emailed at the end of a discovery call, at 11pm, with a subject line that says “brief attached.” The client opens it once, skims the first page, closes it, and mentally marks it as “handled.”

Two weeks later, they remember the conversation, not the document.

The format makes this worse. If your brief is structured like a legal contract — dense paragraphs, numbered clauses, appendices — it signals to the client that it’s a formality, not something they need to engage with. They sign without reading, because that’s what you do with formal documents.

Make the brief a conversation, not a deliverable

Don’t send the brief. Walk through it.

After writing it, schedule a 20-minute call for the sole purpose of reviewing it together, out loud. Not to present — to check. “Does this reflect what you told me?” Ask about each section. When clients hear their own words played back, they engage. They’ll correct small things. That’s good — it means they’re reading.

This call does something else: it creates a shared memory. Two weeks later, when they ask for something excluded in the brief, the reference point isn’t a PDF they half-read. It’s a conversation they were part of.

One page beats six

If your brief is six pages, it won’t be read. The goal isn’t comprehensiveness — it’s clarity on the three things that matter most: what’s in scope, what’s out, and what success looks like.

The structure that works:

• In scope — specific deliverables, not categories
• Out of scope — explicit exclusions, written as concretely as the inclusions
• Deliverables and milestones — dates, versions, formats
• Revision rounds — how many, how defined

That fits on one page. Everything else goes in a separate reference document that you link to but don’t require them to sign.

The part most freelancers skip is the out-of-scope section. Listing what’s excluded feels defensive. It isn’t — it’s specific. A client who sees “mobile version: out of scope” can’t later claim they assumed it was included. A brief that doesn’t say that leaves room for the assumption.

Required sign-off before work starts

The brief doesn’t exist until the client confirms it in writing.

Not a signature on a PDF — a reply email. “Looks good, let’s proceed” is enough. What you need is a timestamp and their name on record.

This takes one sentence at the end of your brief review call: “I’ll send you a clean copy. Just reply to confirm it looks right and I’ll get started.” Almost everyone replies. The ones who don’t — follow up once. If there’s still no confirmation after that, you don’t start.

Starting without confirmation doesn’t protect you. When a dispute arrives, the question isn’t whether the brief was sent. It’s whether the client had a chance to read and agree to it.

When they still don’t read it

Some clients will confirm without reading. You’ll know when week three brings requests that contradict the brief.

This isn’t a failure of the brief — it’s a scope conversation. The brief is now your evidence. “This was out of scope in the document you confirmed — here’s the email.” You’re not accusing them of bad faith. You’re establishing that there’s new work, and it needs to be scoped and priced.

A change order at that point is one paragraph: what’s added, what it costs, delivery impact. Without a confirmed brief, that conversation is much harder to have cleanly — because the scope you’re deviating from was never anchored.

This is the real reason to get the brief confirmed. Not to avoid doing extra work, but to make the conversation about extra work factual instead of adversarial.

What the brief review reveals

When you walk through a brief together and a client starts adding things, that’s useful information. Either they didn’t understand the scope during discovery, or the scope grew between the call and the write-up.

The brief review is a scope check. Run it before contracts are signed, and discoveries there are easy to absorb — add it to scope, adjust price, move on. Discover them on week four and you’re dealing with scope creep mid-project, which costs more to handle than the work itself.

The brief that gets read isn’t longer or more detailed. It’s shorter, reviewed out loud, confirmed in writing, and treated as a living reference — not a formality you send once and forget.

When work runs over because the brief wasn’t followed, those hours are the hardest to bill. Timescanner reads your calendar and shows exactly how much time went into each client and project — so you can see what unscoped work actually cost, and price the next project accordingly. Works with any iCal-compatible calendar.