Every freelancer has been there. The client says "I want a simple website" and three months later you're building a full e-commerce platform with custom CRM integration, for the original price.
The problem isn't bad clients. It's bad briefs.
A project brief is the single most important document in any freelance engagement. It defines what you're building, what you're NOT building, how long it takes, and how much it costs. Without one, every scope conversation for the next two months happens from memory, and the client's memory always favors the client.
This guide covers the 7 sections every brief needs, a worked example that goes from a messy client email to a signed document, the exact sign-off script, and a 15-minute version for when the project is small.
The 7 Sections of a Bulletproof Brief
1. Project Overview
Start with 2-3 sentences that anyone could understand. Not technical jargon. Not marketing fluff. Just: what is this project, and why does it exist?
Bad: "Develop a synergistic digital transformation platform leveraging AI-driven paradigms."
Good: "Build a 5-page marketing website for a dog grooming business in Austin, TX. The site needs online booking and a gallery of past work."
2. Scope of Work (The Most Important Section)
List every deliverable. Be painfully specific. If it's not on this list, it's not in the project.
- Homepage design and development
- About page with team bios
- Services page with pricing grid
- Gallery page with image optimization
- Contact page with form integration
- Mobile responsive design
- Basic SEO setup (meta tags, sitemap)
The test for a good scope line: could a stranger verify it was delivered? "Modern design" fails that test. "Homepage with hero, three service cards, and a booking CTA" passes.
3. Out of Scope (Your Armor)
This is where scope creep dies. Explicitly list what you are NOT doing:
- E-commerce functionality
- Blog setup or content writing
- Logo design or branding
- Ongoing maintenance after launch
- Social media integration beyond link buttons
- Custom animations or video production
Write the exclusions the client is most likely to assume are included. If they mentioned something in early conversations that you're not quoting, it goes here, by name. This single section prevents more unpaid work than everything else in the document combined. If you want to see how expansions sneak in anyway, the patterns are catalogued in these nine scope creep examples.
4. Timeline & Milestones
Break the project into phases with clear deadlines, and make the client's obligations visible:
| Phase | Deliverable | Duration | Client input needed | |-------|------------|----------|---------------------| | Discovery | Wireframes + sitemap | Week 1 | Approval by day 7 | | Design | Visual mockups (2 rounds) | Week 2-3 | Feedback within 48h | | Development | Coded pages + CMS | Week 4-5 | Content delivered by day 28 | | Launch | Testing + go-live | Week 6 | Final approval by day 42 |
That fourth column matters. When the client delivers content two weeks late, the timeline shifts, and the brief already says so.
5. Budget & Payment Terms
Be explicit about money. Vagueness here causes most freelancer-client conflicts.
- Total project cost: $3,500
- 50% upfront deposit: $1,750
- 25% at design approval: $875
- 25% at launch: $875
- Additional revisions beyond 2 rounds: $75/hour
- Invoices due within 14 days
That revision line is not optional. Without a cap, "feedback" becomes an infinite loop, and unlimited revisions is the most expensive sentence in freelancing.
6. Technical Requirements
What tech stack? What hosting? What integrations? Who owns which accounts?
- Platform: WordPress with Elementor
- Hosting: client's existing SiteGround account
- Domain: client already owns doggroomaustin.com
- Analytics: Google Analytics 4
- Forms: Contact Form 7 to client's Gmail
7. Approval & Sign-Off
The last section is one paragraph and two signature lines:
This brief defines the complete scope of the project described above. Work not listed under Scope of Work is not included and can be added through a written change order with its own fee and timeline. Both parties confirm the scope, timeline, and payment terms by signing below.
Name, signature, date, for both sides. An email reply that says "approved, proceed" also works legally in most places, but get one or the other before any work starts.
Worked Example: From Messy Email to Signed Brief
Here's what this looks like in practice. The client's actual email:
Hi! We spoke at the networking thing last month. We finally want to redo our website, the current one is embarrassing honestly. We're a physiotherapy clinic, 2 locations. Want something clean where people can book. My partner also thinks we should have a blog maybe? Budget-wise we're flexible but obviously not looking to spend a fortune. Could you start soon?
Unusable for quoting. Five minutes of extraction produces this brief skeleton:
Overview: Marketing website for a two-location physiotherapy clinic, focused on driving appointment bookings.
Scope: Homepage, two location pages with maps and hours, services page, about page, booking integration (Calendly or the clinic's existing system), mobile responsive, basic on-page SEO.
Out of scope: Blog setup ("maybe" is not a deliverable, priced separately if wanted), content writing, logo refresh, patient portal, ongoing maintenance.
Open questions to resolve before pricing: Which booking system? Who writes the copy? Photography: existing or stock? Deadline driven by anything?
Notice what happened to the blog. It didn't get silently included, and it didn't get ignored. It moved to the exclusions list with a note that it can be quoted separately. That one move is the difference between a brief and a wish list.
The open questions go back to the client before you put a number on anything. If you skip that step, you're pricing guesses. A structured way to do this extraction is the 5-question framework for vague requests.
Getting the Client to Sign (Without Making It Weird)
Freelancers avoid asking for sign-off because it feels bureaucratic. Here's a script that frames it as protection for the client:
Hi [name], attached is the project brief: everything we discussed, pinned down. Two things to check before we start: the Scope of Work list (this is exactly what you're getting) and the Out of Scope list (things we talked about but that aren't in this round, so there are no surprises later). If both look right, reply "approved" or sign page 3, and I'll lock in your start date of [date].
Note the mechanics: the reply costs one word, the start date creates a reason to answer now, and the framing ("no surprises later") is a benefit to them. Most clients approve within a day.
If a client resists signing anything at all, that is information. It's one of the red flags worth taking seriously before you commit your next six weeks.
The 15-Minute Version
Small project, existing client, low stakes? Don't skip the brief, shrink it. The 15-minute version is an email with four headers:
- Doing: 3-6 bullet deliverables
- Not doing: 2-4 bullet exclusions
- Timeline: one line, with the client's obligations
- Price and terms: total, deposit, revision cap
End with "reply 'approved' and I'll get started." That's a brief. It took a fraction of the effort and it will still settle 90% of the disputes that would otherwise cost you a week.
When the Client Pushes Back
"Can't we just get started? We trust you."
I appreciate that, and this document is how I make sure I earn it. It takes one day and saves us both from misunderstandings mid-project. I can't start without it, but I can have it to you by tomorrow.
"This feels very formal for a small project."
The short version is fine for a project this size, I'll send a one-page summary instead. Same content, lighter format.
"Why do you list things you're NOT doing? Feels negative."
That list protects your budget. It means you'll never get an invoice for something you assumed was included. Everything on it can be added later with its own quote if you want it.
Common Mistakes to Avoid
Writing the brief after starting work. The brief comes first. Before any design, code, or creative work begins. A brief written mid-project inherits every assumption already in dispute.
Not getting client sign-off. A brief without a signature is a suggestion. Get it signed or get "approved" in writing.
Being vague about revisions. Define how many rounds of feedback are included and what happens after. Numbers, not vibes.
Skipping the Out of Scope section. If you don't explicitly say what's NOT included, the client will assume everything is included. They're not being malicious. They just have no reason to assume otherwise until you give them one, in writing.
Quoting before the brief is complete. If the client's message left you with more than two or three unanswered scope questions, the project isn't ready to price. Ask first, quote second.
Try the free tool
This article walks through the problem; the free tool turns the answer into a copy-pasteable output in 30 seconds. No account, no signup. Paste your client's message and see exactly which brief sections you can't fill yet.
→ Use the Client Brief Checker
Want this across every project?
Briefance saves every brief, scope check, change order, and revision counter against the client and project. Free plan: 3 briefs/month.