Project Brief Template + How to Write One
By Danial Pourgolab · 18 min read · July 2026

A blank page is where good projects go to stall. You know roughly what the client wants, you sit down to write it up, and you spend the first twenty minutes deciding what a project brief even needs to contain. A template removes that friction: the same labelled sections, every time, so the only work left is filling them in. Below is one you can copy right now, plus a plain-language guide to what belongs in each field and why.
This post is the template itself. If you want the reasoning behind each choice, how to phrase questions and how to get clients to actually answer, that is a separate guide, linked at the end. Here, the goal is to hand you a working document. Copy the block, drop it into a doc, and you have a brief structure that covers the things projects actually trip over.
The project brief template
Copy everything in the block below. Each section has a one-line prompt in brackets telling you what to put there. Delete the prompt as you fill it in. Thirteen sections looks like a lot, but most fields are a sentence or two; a real project brief for a small site fits on two pages.
PROJECT BRIEF Project name: Prepared by / date: 1. SUMMARY [One short paragraph: what this project is, for whom, and why now.] 2. GOAL & SUCCESS METRICS [The single outcome this project must achieve, and how you will know it worked.] 3. TARGET AUDIENCE [Who actually uses the result. Be specific: "returning customers on mobile", not "everyone".] 4. SCOPE In scope: [What this project includes.] Out of scope: [What it explicitly does NOT include, so later requests become change orders.] 5. DELIVERABLES [The concrete things you will hand over, e.g. 5-page marketing site, booking flow, style guide.] 6. KEY FEATURES & USER FLOW [The main things a user does, in order. One line per step or feature.] 7. DESIGN & BRAND DIRECTION [Look and feel, brand assets, references they like/dislike, any hard constraints.] 8. TECHNICAL NOTES & INTEGRATIONS [Platform, hosting, existing systems, third-party tools this must connect to.] 9. CONTENT & ASSETS [Copy, images, data, translations, and for each: who owns it and when it is due.] 10. TIMELINE & MILESTONES [Launch date or key dates, plus any fixed deadline behind them (event, campaign, etc.).] 11. BUDGET [Range or fixed figure, and what it does / does not cover.] 12. STAKEHOLDERS & SIGN-OFF [Day-to-day contact, anyone else who reviews, and the one person who gives final approval.] 13. OPEN QUESTIONS [Everything not yet decided. An honest list here prevents surprises later.]
That is the whole thing. The rest of this post explains the sections that get skipped or filled in badly, because a template only helps if the answers you put in it are the right kind of answer.
If the job is brand, campaign or design work rather than a build, start from the creative brief template instead: its nine sections are about audience, message and creative direction, not features and integrations.
What each field is really asking for
Most of the thirteen sections are self-explanatory. Five of them are where briefs quietly go wrong, usually because the field gets a vague answer, or gets left blank because nobody wanted to have the conversation it forces. These are the ones worth getting right.
If the structure feels familiar, that is because it mirrors how formal requirements specifications are organised. ISO/IEC/IEEE 29148, the international requirements-engineering standard, defines the same kind of labelled specification template. This is the industrial version, minus the ceremony.
- 1Goal & success metrics: not a feature list. The goal is the outcome, not the thing you are building. "A new website" is not a goal; "cut the booking calls reception handles by letting patients book online" is. Add how you will know it worked, even roughly, because a goal you cannot observe is a wish. This one field quietly decides every trade-off later. When two options compete, the one that serves the stated goal wins.
- 2Scope: the "out" list matters more than the "in" list. Everyone fills in what is included. The section that saves projects is "out of scope": the things a reasonable client might assume are part of the job but are not. Writing "no multilingual content, no payment processing, no patient portal" now means a later request for them is a change order and a conversation, not a silent assumption and an argument. Scope creep almost always starts in the gap this line closes.
- 3Content & assets: attach an owner and a date to each. Copy, photos, product data, translations: someone has to produce all of it, and it is usually a client employee who already has a full-time job. "We'll send copy later" is the phrase that strands more finished builds than any technical problem. Do not just list the assets. Put a name and a due date next to each one, and treat a missing owner as a live project risk.
- 4Stakeholders & sign-off: name the person who approves. Your contact is rarely the whole story. There is usually a second opinion-haver and, separately, a person who approves the final invoice and may not have seen anything yet. The most expensive feedback in agency work is a director reviewing the project for the first time in the last week. Name that person here, now, while it is cheap.
- 5Open questions: an honest list, not an empty one. A brief with no open questions is not finished; it is pretending. Every project has things that are not yet decided, and writing them down turns them from future surprises into a visible to-do list with owners. An empty open-questions section usually means the unknowns are still there, just undocumented, waiting to surface at the worst moment.
The template is a skeleton: the value is in the filling
It is worth being honest about what a template can and cannot do. The template gives every project the same labelled slots, which is genuinely useful: nothing gets forgotten, and everyone knows where to look for the scope or the sign-off. But an empty template is not a brief. Its value is entirely in the quality of what you put in each slot.
A template is a skeleton, the value is in the filling
This is why "just send the client the template" rarely works. Hand a busy client a thirteen-section blank form and you get back a logo, two sentences under "goal", and "TBD" under everything that required a decision. The structure was right; the answers were thin. Getting good answers is a different problem from having a good template, and it is the one that actually determines whether the brief is worth anything, which is why the client requirements template covers how to send one so it comes back complete.
How to actually get the fields filled
A blank form and a real answer are not the same thing. The reliable way to fill a template is not to email it over and wait. It is to interview, one question at a time, so each answer sets up the next. "Who uses this?" leads to "what do they do first?" leads to "what stops them today?". A form asks everything at once and gets shallow replies; a conversation follows the thin answers until they are real.
Business analysts have a name for this: elicitation, actively drawing requirements out rather than waiting to receive them, and interviews are its highest-yield technique for exactly this reason.
✕ Template emailed as a blank form
Client opens a 13-section doc, fills "goal: modern website", skips scope and sign-off because they're unsure, marks half the fields "TBD", and sends it back three days late. You still don't know what done looks like.✓ Template filled through an interview
Client answers one question at a time. "Modern how?" surfaces they mean faster and mobile-first. "Who signs off?" surfaces a director nobody mentioned. Every field ends up with a real answer because each one was drawn out, not demanded.The full method for turning answers into a finished document is covered further down this page, and the exact questions to ask are laid out in the web design questionnaire. Use this template as the destination; use those two as the way to fill it. If you are weighing software for the job, compare the AI client intake tools for agencies and freelancers.
How to structure your brief like a conversation, not a form
A filled template is the goal, but handing someone the blank one is rarely how you get there. The briefs that come back complete are collected more like an interview than a form: one question at a time, each built on the last answer.
This is the same instinct behind a discovery phase, the step the UK Government Digital Service runs before building any service: understand the problem thoroughly before committing to a solution. A good brief is a small, fast discovery.
Why a conversation beats a form
Here's a sequence that fills the template above without it feeling like paperwork:
- 1Start with the why. "What's the main reason you're starting this project right now?" This opens the conversation and gives context for everything that follows.
- 2Clarify the what. Based on their answer, ask what they expect the finished product to do or look like. Keep it concrete.
- 3Uncover the audience. "Who is the main person this is built for?" Let them describe the user in their own words.
- 4Surface constraints early. "Is there anything that's already decided: a platform, a style guide, a deadline?" Getting this early prevents surprises.
- 5Pin down success. "How will you know in 6 months that this project was a success?" Most clients have never been asked this before.
- 6Handle logistics last. Budget, timeline, and stakeholder questions are easier once the client feels understood. Asking them first feels transactional.
If you want the exact questions to put inside that sequence, beyond the obvious ones about goals and audience, we collected the seven questions to ask clients before starting a project, each with what goes wrong when it gets skipped.
What it costs to skip the brief entirely
Scope creep almost always traces back to requirements that were never clearly defined. When both sides hold different assumptions about what is included, those assumptions collide mid-project and someone absorbs the cost. We dug into how that unfolds in how to prevent scope creep before the project starts, and broke down what it actually costs an agency, with real numbers. The total is almost always larger than the rework alone suggests.
Filling this template properly, before the project starts, is the single most effective thing an agency can do about that. It is not a bureaucratic hurdle. It is insurance for both sides.
The template, filled in
Here is the skeleton above with real answers in it, for a familiar example: a three-location dental practice that wants online booking. Notice how each field carries a decision, not a placeholder:
Project brief
Northgate Dental: New website + booking
Three-location dental practice · New site with online appointment booking
- Goal
- Cut the volume of booking phone calls reception handles by letting patients book online, and look modern enough to compete with the two practices that opened nearby. Success = 40% of bookings self-served within three months.
- Scope
- In: marketing site, online booking integration, three location pages. Out (for now): patient portal, payment processing, multilingual content, logged so a later request becomes a change order, not an argument.
- Content owners
- Treatment copy: written by Dr. Owen, due week two.
- Team photos: practice to shoot, or stock as fallback. Decision needed by Friday.
- Sign-off
- Day-to-day contact is Priya (practice manager). Final approval is Dr. Owen, who has not seen the proposal yet. Review booked for Thursday before any design work starts.
- Open questions
- Which booking system stays: existing Dentally account, or migrate? Analytics login for the current site still outstanding.
That one uses a few fields of the template. The three below use a six-part version of it, and each covers a different kind of project.
Project brief examples: three filled-out briefs
Three more briefs, for three projects an agency or freelancer could plausibly take on this year: a small bakery website, a booking platform for a physio clinic, and an internal stock-tracking tool for a trades business. Names and a few details are invented, but the structure, the level of detail and the open questions are what a usable brief looks like. Copy the shape, swap in your own project, and use the note after each one to see the thinking behind it.
All three follow the same six parts: the goal (an outcome, not a deliverable), the target users, scope split into in and out, technical notes, a timeline, and open questions. The difference between a brief that protects you and one that does nothing is how specific those fields get:
✕ Vague field
Goal: "Build a modern, professional website that represents the brand well and is easy to use."✓ Specific field
Goal: "Replace the Instagram-DM ordering for celebration cakes with a web form, so staff stop missing orders during the morning service rush."The first sentence could describe any project ever commissioned. The second one you could measure in a month. Hold that standard against every example below.
Example 1: A bakery website
A two-location artisan bakery in Bristol. They are not trying to become an e-commerce store. They are trying to stop a specific, daily annoyance: custom cake enquiries arriving as Instagram DMs that get lost while the counter is busy.
Project brief
Hearth & Crumb: Bakery website
Artisan bakery, two Bristol locations · WordPress redesign + custom-cake enquiry form
- Goal
- Stop losing custom celebration-cake enquiries in Instagram DMs. Give customers one place to see the cake range and submit a structured order request a week or more ahead, so staff aren't fielding orders mid-service.
- Target users
- Local customers aged roughly 25 to 55, mostly on their phones, ordering a birthday or wedding cake one to three weeks out. Secondary: a handful of café owners who buy wholesale and just need the trade contact and minimums.
- In scope
- Five pages: home, cake range, custom-order enquiry form, about, find us (both locations with hours).
- Enquiry form that emails the shop and includes date needed, servings, flavour, and an allergen note.
- Instagram feed embed on the home page so the site never looks stale.
- Client can edit page copy and the cake range themselves.
- Out of scope (this phase)
- Online payment, delivery, customer accounts/logins, and the daily bread-and-pastry menu (changes too often to maintain). These can be a phase two if the form proves the demand.
- Technical notes
- Current site is WordPress and they want to stay on it so they keep editing access. Brand fonts and colours already exist (supplied as a one-page guide). Must render cleanly on the ageing counter iPad. No payment data stored.
- Timeline
- Five weeks. Soft launch must land before the Mother's Day order rush, which starts in week five. Milestone: design sign-off by end of week two.
- Open questions
- Who supplies the cake photography: existing shots, or a half-day shoot we arrange?
- One shared cake range for both locations, or does each shop have its own specials?
- Does the enquiry form need a deposit step, or is that handled in the follow-up call?
Example 2: A booking platform
A four-practitioner physiotherapy clinic that takes bookings entirely by phone. Reception is drowning, no-shows are costing real money, and patients increasingly expect to book at 9pm without ringing anyone. This is a bigger, riskier project than the bakery, and the brief reflects that by being honest about constraints.
Project brief
Northside Physio: Online booking platform
Physiotherapy clinic, four practitioners · Patient self-booking integrated with their practice software
- Goal
- Move from phone-only booking to patient self-booking, to free up reception time and cut no-shows. Target: at least 40% of appointments booked online within three months, no-show rate down from ~18% to under 10%.
- Target users
- Patients aged 30 to 70, often in pain and short on patience, mostly on mobile. They need to find the right service and practitioner without knowing clinical jargon. Secondary users: two reception staff who manage the diary and need an admin view they trust.
- In scope
- Practitioner profiles and a service catalogue with durations and prices.
- Real-time availability pulled from the practice management system.
- Booking with a card-held deposit, plus a self-service reschedule/cancel link.
- Automated SMS reminders 24 hours before the appointment.
- Out of scope (this phase)
- Clinical notes / full patient records, insurance billing, a native mobile app, and multi-clinic support. The clinic runs one site; we are not building for a chain that does not exist yet.
- Technical notes
- Must integrate with Cliniko (their existing practice management system) via its API; availability and bookings live there, not in a new database we own. SMS goes through their current Twilio account. Health-adjacent data means GDPR applies: explicit consent copy, minimal data captured, EU data region. Needs to respect practitioner holidays already entered in Cliniko.
- Timeline
- Ten weeks, phased. Phase one (weeks 1 to 7): booking and availability live. Phase two (weeks 8 to 10): deposits and SMS reminders. Anchored to the clinic's quiet August so reception can adjust before the September surge.
- Open questions
- Does Cliniko's API expose true real-time availability, or do we poll on an interval and risk double-bookings?
- Deposit amount and refund window, a clinical policy decision the owner needs to set.
- How far ahead can patients book: a rolling six weeks, or the full diary?
Example 3: A small internal tool
Not every brief is for a client-facing product. This one is an internal tool for a twelve-van electrical contractor whose van stock lives in a shared spreadsheet that is permanently out of date. The interesting constraint here is the environment: electricians, gloves on, poor signal, no patience for software.
Project brief
Cleary Electrical: Van stock tracker
12-van electrical contractor · Mobile-first internal tool to replace a shared stock spreadsheet
- Goal
- Replace the always-wrong shared spreadsheet with a stock list the office can actually trust, so they stop over-ordering parts that are already sitting in a van. Concretely: the office should be able to see what is on every van before placing the weekly order.
- Target users
- Twelve electricians who will use it for ten seconds at a time, on a phone, often with one glove off and frequently on sites with poor signal. One office manager who does the reordering and lives in Microsoft 365. The electricians' patience is the real constraint, not their tech skill.
- In scope
- Mobile-first stock list per van, with a one-tap decrement when a part is used.
- Low-stock flag per item so it is obvious what needs reordering.
- Office dashboard showing all twelve vans at a glance.
- Weekly reorder export to Excel.
- Out of scope (this phase)
- Direct supplier ordering, accounting/job-costing integration, dedicated barcode scanner hardware, and per-electrician logins. A single shared login per van is fine to start.
- Technical notes
- Must work offline and sync when signal returns, since site basements have none. Phone camera for any scanning, not bought hardware. Office is on Microsoft 365, so export to Excel rather than a bespoke report. Keep the per-van interface to as few taps as possible.
- Timeline
- Six weeks to a working MVP, then a two-week pilot with three vans before rolling out to all twelve. The pilot is non-negotiable: if the electricians won't use it, nothing else matters.
- Open questions
- Barcode/QR scanning, or a plain searchable list? Scanning is slower with gloves on.
- How do we handle a part moved from one van to another without it going missing in the count?
- Who owns the master parts list, and how often does it change?
What the examples have in common
A bakery site, a booking platform, and a stock tracker have almost nothing in common as products. As briefs, they are nearly identical. Strip the topics away and the same four habits show up every time:
- 1The goal is an outcome, never a deliverable. None of them say "build an X". They say what changes when it exists: orders stop getting lost, no-shows drop, the office trusts the stock count. That single sentence is what every later request gets measured against.
- 2The out-of-scope list is as deliberate as the in-scope list. Each brief names what it is not doing. That is where most scope creep gets stopped, because a request for something on the "out" list is visibly a change, not an assumption.
- 3Constraints are surfaced, not discovered. The Cliniko API, the ageing counter iPad, the no-signal basements. The awkward technical realities are in the brief, not waiting to ambush the build halfway through.
- 4Open questions are written down and owned. Every brief ends by admitting what is still undecided. Naming an open question is not weakness; it is the difference between resolving it on purpose and tripping over it later.
Three ways this template gets misused
- 1Filling it in alone, then asking the client to "confirm". A brief you wrote from memory and sent for a thumbs-up is your assumptions with a signature on them. The client skims, says "looks good", and the gaps surface in week four. The template should capture what the client actually said, drawn out by real questions, not what you guessed and they rubber-stamped.
- 2Deleting the sections that feel awkward. "Out of scope", "budget", and "who signs off" are the fields people quietly drop because they force an uncomfortable conversation. Those are exactly the fields that pay for the whole template. If one genuinely does not apply, write "not applicable" so it is clear you considered it. Do not remove it.
- 3Treating it as a form to survive, not a decision log. The point is not to reach the bottom of the doc; it is to have made every decision the doc asks for. A field full of "TBD" is not a filled field. Better to have five sections with real answers and eight honestly marked open than thirteen that all say nothing.
Filling the template without the chase
However you fill it, the principle holds: the template is only as good as the answers in it, and good answers come from a conversation, not a blank form. This is the part ReqBrief automates. Instead of emailing this template and waiting, you send the client a link and an AI interviews them one question at a time (goals, audience, scope, stakeholders, content, constraints) following up on the thin answers, and hands you back a structured brief with these exact sections already filled in. The client finishes it in one sitting on their own schedule, and unlike a static form it adapts each question to the last answer. It is built for freelancers and small agencies scoping client work.
Copy the template, use it by hand, and it will already make your projects start cleaner. Fill it through a real interview instead of a blank form and it gets better still. Either way, the blank page (and the twenty minutes deciding what a brief needs) is a problem you only have to solve once.
Skip the blank form. ReqBrief interviews your client one question at a time and hands you this exact brief: goals, scope, stakeholders, content owners, and open questions already filled in.
Try ReqBrief free →Frequently asked questions
What is a project brief?
A project brief is a short, shared document that defines what a project is, who it's for, and what success looks like before any work starts. For a digital project it typically captures the business goal behind the work, the target audience, existing constraints, success criteria, timeline and budget range, and who the decision-makers are. Its job is to get both sides agreeing on the same picture so the project doesn't drift later.
How do you get a client to fill out a project brief?
The most reliable way is to stop treating it as a static form the client completes alone. Send a short, warm intro that explains what you'll ask and why it helps them, set a realistic time expectation ("about 10–15 minutes"), and ask one question at a time so each one feels like a natural follow-up rather than homework. Give context and examples with every question so the client can answer something specific instead of facing a blank box. Clients who understand the purpose, and aren't overwhelmed by a wall of fields, complete briefs far more thoroughly.
What should a project brief template include?
A complete project brief template has thirteen sections: a one-paragraph summary, the goal and how success is measured, the target audience, scope (both what is in and what is explicitly out), the deliverables, the key features and user flow, design and brand direction, technical notes and integrations, content and assets with an owner and due date each, the timeline and milestones, the budget, the stakeholders and who signs off, and a list of open questions. The two sections most templates omit and most projects need are "out of scope" and "who gives final sign-off". Leaving them blank is where scope disputes and last-minute rework come from.
Is a project brief the same as a scope of work?
No, though they overlap. A project brief is the shared understanding of what you are building and why: goals, audience, scope, constraints, and open questions, written so everyone starts aligned. A scope of work (or statement of work) is the contractual document that turns that understanding into specific deliverables, terms, and payment. The brief usually comes first and feeds the SOW; you can write a brief without a formal SOW, but you should not write a good SOW without the brief's answers.
How long should a project brief be?
As long as it needs to be to remove ambiguity, and no longer, typically one to three pages for a small-to-mid project. A brief is not padded by length; it is made useful by decisions. A two-page brief where every section contains a real answer beats a ten-page one full of "TBD". If a section genuinely does not apply, write "not applicable" rather than deleting it, so the reader knows it was considered, not forgotten.
What does a project brief look like?
A project brief is a short document, usually one to two pages, not an essay. It states the business goal in plain language, names the people who will actually use the thing, lists what is in scope and what is explicitly out, notes the technical constraints that are already locked in, gives a timeline with a few milestones, and ends with the open questions still to be answered. The bakery, booking platform, and internal tool examples on this page each follow exactly that shape.
How is a project brief template different from a project brief example?
A template is the blank, reusable structure: the labelled sections you fill in for each new project. An example is one filled-out brief, showing what good answers look like in context. Use the template as your starting document every time; use examples to calibrate how much detail each field needs. Many people want both: the empty skeleton to work from, and a completed one to copy the tone and depth from. This page has both: the template near the top and four filled-out examples further down.