Prompt Notebook

Project brief · Project management · Templates

How to write a project brief, with a filled-in example

By T. Krause

A project brief is one page that says why a project exists, what is in and out of scope, who owns which part and when it is done. Here are the sections it needs, how to write one in five steps, a complete example for an invented climbing centre and a free template.

A project brief is a short document, usually one page, that says why a project exists, what it should achieve, what is in and out of scope, who owns each part and when it is done. You write it before the work starts and send it to everyone involved, including whoever has to approve the time or the money.

To write one, start with the goal in a single sentence, with a number if you can. Then describe the problem that makes the project worth doing, list two to four goals, draw the line between what's in scope and what's out, name an owner for each part, set the milestones with dates and write down the questions nobody can answer yet. Share it for comments, settle the open points and get a yes from the person paying for it.

Below, each section gets a short explanation, then comes a complete brief for an invented project at an invented climbing centre. If you'd rather start from a page with the headings already in place, use our free project brief template.

What a project brief is, and when to write one

A brief is written for the person who has to say yes. It tells them whether the project is worth doing and what exactly they are agreeing to. Keep it short on purpose. A manager or a client should be able to read it in five minutes and either approve it or say what's missing.

Write one when more than two people will work on the project, when you hire an agency or a freelancer, or when someone outside the team has to sign off on time or money. A task one person can finish in a week doesn't need a brief. A line in the task tracker will do.

Project brief, project charter, PRD and creative brief

These four documents get mixed up because they all come before the work. A project brief proposes the project and gets it approved. In the PRINCE2 method, the project brief is the document the project manager writes while starting up a project, and the project board reads it to decide whether to authorise the initiation stage. A project charter, the term the PMBOK Guide uses, formally authorises the project and gives the project manager authority to use the organisation's resources, so it is often the signed version of what the brief proposed. A PRD comes later and only for a product feature. It turns the goal into requirements that design and engineering can build from, and our guide on how to write a PRD covers it. A creative brief is what agencies and design teams work from when they produce creative work such as ads, copy, visual design and websites. In a small team, one page can serve as both brief and charter, as long as someone with the budget signs it.

What goes in a project brief

These are the sections in our project brief template, in the order it uses them. Other templates name some of them differently, but the content is much the same.

  1. The goal line. One sentence at the very top that says what changes when the project is done, with a number if there is one. Readers who stop here should still know what the project is for.
  2. Problem. What goes wrong today, for whom, and how you know. Use something you counted or watched, such as support tickets or a queue you timed. If you can only describe the problem by describing your solution, keep looking.
  3. Goals. Two to four outcomes, each one something you can check when the project ends. "Saturday waits under five minutes" is a goal. "Build an online form" is a task. If the project costs money, put the spending limit here too, because staying within it is something the sponsor will check.
  4. Scope. Two lists, In and Out. The Out list does more work than the In list. Every item on it is a request you've answered before anyone makes it.
  5. Owners. A name for each part of the work, and the person who approves the project. "Marketing" is not an owner. "Ravi" is.
  6. Milestones. Three to six dated points, from approval to launch, plus the date you'll check the goals. Dates are what make a brief a plan instead of a wish.
  7. Open questions. What you don't know yet, each with a proposed answer if you have one, a name and a date to settle it.

Leave out what the reader won't use. A brief doesn't need a background essay or a list of every task. Those belong in the project plan or the task tracker once the brief is approved.

How to write a project brief in five steps

1. Write the goal line last, then move it to the top

Draft the problem and goals first. Once they're settled, compress them into one sentence and put it at the top. Writing it first tends to produce a slogan. Writing it last gives you a summary of what you actually agreed.

2. Put numbers on the problem

Before you write a goal, count something. How long people wait, say, or how many hours a week go on the work you want to remove. One number you measured beats three you estimated, and it gives the goals something to improve on.

3. Write the Out list with the people who'll ask

Ask the two or three people most likely to want more from the project what they expect it to include. Anything you're not doing goes on the Out list, with "later" or "next year" where that's true. A short conversation now saves a long argument in week four.

4. Date every milestone and name every owner

Go through the milestones with the people who own them and check that each date is one they agree to. A milestone without an owner slips without anyone noticing, and an owner who never agreed to the date will tell you so in the first status meeting.

5. Share it, close the questions, get the yes

Send the brief with comment access and a date by which you need replies. Answer each comment in the text and move settled questions into the section they belong to. Then ask the sponsor for an explicit yes. Once the work starts, the brief is the page people check when they wonder whether something is in scope, so keep it current.

A filled-in example: online waivers for a climbing centre

The company, the people, the dates and the figures below are invented. Greyfield Climbing runs one indoor climbing centre with 14 staff. Hannah Brooks owns it and approves the money. Owen Price is the operations manager and leads the project. Sam Okoye runs the front desk. Lucia Ferreira is a freelance developer who has quoted for the build. Owen wrote the brief on Monday 2 November 2026, using the same headings as our template.

Brief: online waivers

Goal: First-time visitors sign their waiver online before they arrive, so their Saturday wait drops from 18 minutes to under 5.

Problem

Every first-time visitor fills in a two-page paper waiver at the front desk before they can climb. On the four Saturdays in September 2026, Sam timed first-time visitors from joining the queue to getting their wristband. The average was 18 minutes, and most of it went on the form. Some visitors left before reaching the desk. On Mondays, Sam's team types the forms into the booking system, which takes about three hours a week.

Goals

  • First-time visitors sign the waiver online, from the link in their booking confirmation email or a QR code at the entrance
  • Signed waivers are saved to the visitor's record in the booking system, so nobody retypes them
  • The Saturday wait for first-time visitors is under 5 minutes, measured on the four Saturdays in February 2027
  • Total spend stays within £6,000: £4,800 for Lucia's build at 40 hours and £120 an hour, £600 for two tablets with stands, £600 for the lawyer's review of the waiver wording

Scope

In

  • An online waiver form, with a link in every booking confirmation email
  • A QR code poster at the entrance for visitors who didn't book ahead
  • Two tablets at the front desk for walk-ins without a phone
  • Searching for a signed waiver by name at check-in
  • A review of the current waiver wording by the centre's lawyer

Out

  • School and group bookings, which keep their single group form
  • Memberships and payments, which stay as they are
  • Translations of the form, planned for next year

Owners

  • Approval and budget: Hannah Brooks
  • Project lead: Owen Price
  • Build: Lucia Ferreira
  • Testing and front-desk training: Sam Okoye
  • Waiver wording: Hannah Brooks, with the lawyer

Milestones

  1. Brief approved: Friday 6 November 2026
  2. Waiver wording back from the lawyer: Friday 20 November 2026
  3. Form built and tested by the front desk: Friday 11 December 2026
  4. Live for all bookings: Monday 4 January 2027
  5. Wait times checked on the four Saturdays in February: 6, 13, 20 and 27 February 2027

Open questions

  • Do under-18s need a parent or guardian to sign online? Proposal: yes, the form asks for a parent's name and signature for anyone under 18. The lawyer confirms by 20 November.
  • What happens to the paper waivers already on file? Proposal: they stay valid, and only visitors without a waiver on file get the online form. Owen decides by 6 November, so the answer is in the approved brief.

Why this example works

The goal line repeats the number from the problem, 18 minutes, and the target from the goals, so a reader who stops after one sentence knows what Hannah is paying for. The budget adds up from its three parts, which lets Hannah question each one instead of the total. Lucia's 40 hours sit in the three weeks between the lawyer's wording on 20 November and testing on 11 December, which gives Owen a way to spot a slip early. The first Saturday measured is 6 February, so the front desk has had four Saturdays in January to get used to the tablets before anyone times the queue. And the Out list answers the question the school-group organiser will ask before they ask it.

Common mistakes

  • No Out list. Scope then grows one reasonable request at a time, and the dates stop making sense by the second month.
  • Goals that are tasks. "Launch the new form" tells you when to stop working, not whether the project worked. Add the measure the form is meant to move.
  • A team instead of a name. If "design" owns a milestone, nobody owns it.
  • Questions without a date. An open question with no deadline stays open until it blocks the work.
  • Writing it after the work starts. A brief written to describe what's already happening can't help anyone decide whether it should.

Writing a project brief in Prompt Notebook

Prompt Notebook is ours, so read this part with that in mind. The project brief template opens as a page with the goal in a callout at the top, then headings for Problem, Goals, Scope with In and Out, Owners, Milestones and Open questions. Open questions sit in toggles, with the answer inside. The sample is a brief for a customer portal at an invented company, so you can see a finished one before you replace it.

Share the page with comment access and resolve each comment thread once the answer is in the text. Once the work starts, mention the brief with @ from the task tracker or the roadmap, and its Linked from list shows every page that refers to it. Page history takes a snapshot every 10 minutes while the page is being edited, so you can see what changed since the sponsor approved it. If a brief turns into a feature with real requirements, our PRD template is the next page to write.

Frequently asked questions

How long should a project brief be?

One page for most projects, two at most. The sponsor should be able to read it in five minutes. If it runs longer, check whether you've written the project plan or the requirements into it, and move those to their own pages.

Who writes a project brief?

The person who will lead the project, or whoever wants it to happen. In a small team that is often the founder or an operations manager. The person who controls the budget approves it.

What is the difference between a project brief and a project charter?

A brief proposes the project and gets it agreed. A charter formally authorises it and gives the project manager authority to use people and money. A small team can write one page and treat the signed brief as the charter.

Should a project brief include a budget?

Yes, if the project costs money or needs people's time beyond their normal work. Give the total and the parts it's made of, so the sponsor can see where the money goes and question a line instead of the whole figure.

Try it on your own notes

Prompt Notebook is free, with unlimited pages. Type one sentence and the AI drafts the first version.

Cookies and storage

Prompt Notebook needs one cookie to keep you signed in. Accepting turns on Google Analytics and Google's reCAPTCHA spam check on the contact form, and declining keeps the form working. Nothing optional runs until you choose.

Read the privacy notice