What a project brief includes
A project brief is the one-page agreement that lets everyone start the same project. Not the plan (that comes after), not the proposal (that came before): the distilled agreement on what we are doing, for whom, by when, and what done looks like. The settled elements:
| Element | What it settles | The trap it prevents |
|---|---|---|
| Goal | What changes and how success is judged | A finished project nobody can call a success |
| Scope, in and out | What’s included, and explicitly what isn’t | The month-two “I thought that was included” |
| Deliverables | The things that will exist, each dated | Effort mistaken for output |
| Timeline | Start, key milestones, end | A project with no finish line |
| Stakeholders | Who decides, who does, who’s informed | Five people with veto, none with a decision |
| Risks & assumptions | The top three, written down | “We always knew that might happen” |
How long should a project brief be?
One page. That is not a style preference; it is the mechanism. A brief works because everyone actually reads it, agrees to it, and can recall it in a disagreement. At two pages it becomes a document people skim; at five it becomes a document people cite selectively. If the project genuinely cannot be captured on one page, that usually means it is two projects, or that the plan is trying to move into the brief. Push detail down into the plan and keep the brief as the thing everyone signed.
Project brief example
One page, filled in, for a dental practice’s website project:
PROJECT BRIEF · Bexley Dental website rebuild Client: Bexley Dental (sponsor: practice manager) Owner: Studio · Date: 18 Jul GOAL Stop losing bookings to the phone queue: online booking live and taking 30% of appointments within 2 months of launch. SCOPE In: 6-page site, online booking, treatment pages, reviews feed Out: rebrand, patient portal, paid-ads landing pages DELIVERABLES Sitemap & wireframes → 1 Aug Design sign-off → 15 Aug Build with booking integration → 12 Sep Launch + handover doc → 26 Sep STAKEHOLDERS Practice manager → decides · Studio → does Practice owner → informed (weekly summary) BUDGET & CONSTRAINTS £12,400 fixed · booking system must be the practice’s existing provider RISKS & ASSUMPTIONS - Assumes photography exists (none seen yet) - Booking provider’s API access approved by 8 Aug - Content sign-off within 5 working days per round
Free project brief template (plain text, Google Docs, Notion)
Three ways to a signed one-pager. The plain text pastes cleanly into Google Docs or Notion, wherever the project team lives.
The plain-text template
Genuinely one page: goal, scope in/out, dated deliverables, stakeholder roles.
PROJECT BRIEF · [Project name] Client/sponsor: [who it’s for] · Owner: [who runs it] Date: [date] GOAL (1-2 lines) What this project changes, and how we’ll know it worked. SCOPE In: [what this project includes] Out: [what it deliberately does not, written down now, not argued later] DELIVERABLES - [Thing that will exist at the end] → [due date] - … TIMELINE [Start] → [key milestone] → [key milestone] → [end date] STAKEHOLDERS [Name] → [role: decides / does / informed] BUDGET & CONSTRAINTS [Budget if set; the constraint everyone should know about] RISKS & ASSUMPTIONS (top 3) - [What we’re assuming true; what could knock the timeline] One page. If it doesn’t fit, it isn’t briefed yet.
The AI prompt
Prefer to use your own AI? Copy this into Claude or ChatGPT with your kickoff emails or proposal, and it distils the brief.
--- title: Project Brief Generator description: A prompt that distils a one-page project brief (goals, scope, timeline, deliverables) from your kickoff emails, proposals and notes. author: readywhen source: https://readywhen.ai/project-brief-template homepage: https://readywhen.ai license: CC BY 4.0 (free to use and share with attribution to readywhen) version: 1.0 updated: 2026-07-18 keywords: [project brief template, project brief example, one page project brief, project kickoff] --- # Project Brief Generator _By readywhen. Full guide + free template: https://readywhen.ai/project-brief-template_ You are distilling a one-page project brief from source material: kickoff emails, a proposal, call notes, whatever exists. ## Principles - One page, hard limit. A brief that needs scrolling isn’t briefed yet. - The goal states what changes and how success will be judged, in 1-2 lines. - Scope has an explicit OUT list. The out-of-scope line you write today is the argument you don’t have in month two. - Deliverables are things that will exist, each with a date. "Ongoing support" is not a deliverable. - Stakeholders get one of three roles: decides, does, or informed. - Where the source material is silent (budget, a date, a decider), leave a marked gap rather than inventing one. ## Structure Goal · scope (in/out) · deliverables with dates · timeline · stakeholders · budget and constraints · top 3 risks and assumptions. ## What I need from you Paste whatever exists: the kickoff email thread, the proposal, discovery call notes. Tell me who’s sponsoring and who’s running it. I’ll distil the brief and list every gap the sources didn’t answer. --- _Made by readywhen. readywhen distils the brief from the thread and proposal already in your tools, gaps flagged, before the kickoff meeting. https://readywhen.ai/project-brief-template_
Let readywhen do itRecommended
The brief’s raw material is the thread and the proposal you already have. readywhen distils them into the one-pager, flags the questions the sources never answered, and has it ready before kickoff.
Everything the brief needs is already in the thread and the proposal. readywhen distils it in ~45 seconds, so kickoff starts from a signed page instead of a re-telling of fourteen emails.
Watch readywhen draft a project brief from your connected tools
By the time a project needs a brief, the raw material already exists: the enquiry thread where the client said what they actually want, the proposal that fixed the price, the discovery call where the constraints came out. readywhen distils those sources into the one-page brief: the goal in the client’s own words, scope with the OUT list made explicit, deliverables dated from the proposal, and, crucially, a flagged list of the questions the sources never answered, which is exactly the agenda for your kickoff meeting.
Works with your existing tools
Project brief template FAQs
What is the difference between a project brief and a project plan?
The brief is the one-page agreement on what and why: goal, scope, deliverables, timeline, stakeholders. The plan is the how: tasks, dependencies, scheduling. The brief gets signed before work starts; the plan evolves throughout. Skipping the brief and going straight to a plan is how teams execute the wrong project efficiently.
What is the difference between a project brief and a creative brief?
Scope of use. A project brief covers any project (a website, an office move, a product launch). A creative brief is the design-and-marketing variant, heavier on audience, message and tone. The bones (goal, scope, deliverables, timeline) are the same.
How long should a project brief be?
One page. It works because everyone reads it, agrees to it, and can recall it in a disagreement. If it will not fit, it is usually two projects, or plan-level detail is creeping in.
Who writes the project brief?
Whoever owns the project’s delivery, but its contents come from the sponsor and the source material: the enquiry, the proposal, the discovery call. The owner’s job is distillation and getting it signed, not invention.
Is there a project brief template for Google Docs or Word?
Yes. Copy the plain-text template on this page into Google Docs, Word or Notion, or download it as a file. All formats are free.
Can’t I just use ChatGPT or Claude to write my project brief?
Yes. Paste the thread or proposal with the prompt above, and you get a clean one-pager. readywhen is the version already connected to those sources, so the brief turns up distilled before kickoff, with the unanswered questions flagged as your meeting agenda.
More templates for projects and plans
Roadmap
Now/Next/Later milestones with owners, drafted from your real work.
OKR
Objectives and measurable key results, drafted from your own numbers.
SOP
Standard operating procedures, written from how you already do the task.
Stop kicking off without a signed page.
Draft your brief free with readywhen
About the author and editorial standards
About the author. Sançar Şahin is co-founder and CMO of readywhen. readywhen catches everything you say you’ll do and helps you move it forward: drafted, chased or flagged, ready when you are. He builds readywhen in public on LinkedIn.
Editorial standards. No paid placements. The one-page convention and brief elements (goal, scope, deliverables, stakeholders) reflect common project practice rather than a single authority. How this page was made: Sançar built the multi-agent research and drafting system behind it, checks its work at several phases, and approves the final page himself. To flag an error, email hello@readywhen.ai.
Last updated: 19 July 2026.