# How to write a project brief (with a one-page example)

> How to write a project brief on one page: ten headings, a filled-in example, how it differs from a statement of work, and a sign-off checklist.

Source: https://plexiidesk.com/blog/how-to-write-a-project-brief
Topic: Work by task (https://plexiidesk.com/blog/c/work-by-task)
Author: The Plexii team
Published: 2026-11-12

A project brief is a one- or two-page document, written before work starts, that says why the project exists, what it will deliver, who it is for, when it is due, how success will be judged and what is out of scope. To write one, answer those six questions in plain sentences, get the people paying for, doing and receiving the work to agree it, and keep it where everyone can see it. This guide gives you the structure, a filled-in example and a review checklist.

[Download Plexii free](https://plexiidesk.com/download) for Mac or Windows if you want the brief to sit on the same desk as the work it describes.

## Why a short brief beats a long one

A brief settles arguments before they start. When someone asks halfway through "was this in scope?", the answer is already written down. The Scottish Government's [Construction Procurement Handbook](https://www.gov.scot/publications/construction-procurement-handbook/pages/2/) puts it well: the brief "is a live document that should be referred to throughout". That only works if it is short enough to reread. One page that people check beats ten pages nobody opens.

## The one-page project brief template

Copy these headings into a document and fill each one in two to five sentences.

1. **Project name and owner.** One name, one person accountable.
2. **Why.** The problem or opportunity, and why now. What happens if we do nothing?
3. **What we will deliver.** The things that will exist at the end that do not exist now. Be concrete: "a 12-page onboarding guide and a 3-minute video", not "better onboarding".
4. **Who it is for.** The audience or users, and who must approve the work.
5. **Out of scope.** What this project will not do. This line prevents more arguments than any other.
6. **Deadline and milestones.** The final date and any fixed dates on the way.
7. **Success measures.** How you will judge it afterwards, in terms you can check.
8. **Budget and resources.** Money, people and tools available, or "to be confirmed by [date]".
9. **Risks and assumptions.** What could stop it, and what you are assuming is true.
10. **Sign-off.** Who agreed the brief, and when.

## A filled-in project brief (fictional)

**Project:** New-starter onboarding guide. **Owner:** Jordan Lee, People team.

**Why.** New starters currently get onboarding information from five different emails in their first week. Managers answer the same questions repeatedly, and new starters have said in exit surveys that the first week felt disorganised.

**What we will deliver.** A single onboarding guide (about 12 pages) covering the first two weeks, a one-page checklist for managers, and a short welcome video.

**Who it is for.** New starters in all teams. Managers use the checklist. Approval: Head of People.

**Out of scope.** Role-specific technical training, payroll set-up instructions (owned by Finance) and changes to the HR system.

**Deadline and milestones.** Draft guide by 5 March, manager review by 12 March, final version live by 26 March for the April intake.

**Success measures.** Every April starter receives the guide before day one; managers confirm they used the checklist; the guide is updated after the first intake's feedback.

**Budget and resources.** Jordan, two days a week; design support for three days; no external spend.

**Risks and assumptions.** Assumes team leads supply their sections by 26 February. Risk: the video slips if filming cannot be scheduled.

**Sign-off.** Agreed by Head of People and two team leads on 14 February.

Notice what the example does not do: it does not explain how every section will be written. That belongs in the plan. The brief says what and why.

## Project brief, creative brief or statement of work?

| Document | Main purpose | Typical length |
|---|---|---|
| Project brief | Agree why, what, who, when and success before work starts | One or two pages |
| Creative brief | Direct a piece of creative work: audience, message, tone, format | One page |
| Statement of work | Define, usually contractually, what a supplier delivers and how it is accepted | Several pages |

If a supplier is doing the work, the brief often becomes the starting point for a [statement of work](https://plexiidesk.com/blog/statement-of-work-template). For design jobs, the [creative brief desk](https://plexiidesk.com/templates/creative-brief) adds rounds of feedback and a change list. Once the brief is agreed, a [work breakdown structure](https://plexiidesk.com/blog/work-breakdown-structure-template) turns the deliverables into tasks.

## How to write the brief in an hour

1. **Talk before you write (20 minutes).** Ask the sponsor three questions: what problem are we solving, what does done look like, and what must this not turn into?
2. **Draft the ten headings (25 minutes).** Write badly and fast. Leave "TBC by Friday" where you do not know yet.
3. **Write the out-of-scope line last,** after you know what is in.
4. **Read it as the most sceptical stakeholder (5 minutes).** Where would they push back?
5. **Send it for sign-off (10 minutes)** with a date: "Please reply with changes by Thursday; after that we will treat this as agreed."

Once the brief is agreed, the first delivery task is usually the [frog to start the next morning](https://plexiidesk.com/blog/eat-the-frog-at-work).

## Review checklist before sign-off

- The deliverables are things you could point to, not activities
- Out of scope has at least two lines
- Every date is a date, not "Q2" or "soon"
- Success measures can be checked afterwards by someone else
- One person owns the project
- Approvers are named
- It fits on one or two pages

## Keep the brief beside the work in Plexii

Plexii is a [desktop workspace where each task gets its own desk](https://plexiidesk.com/product#desk). A project desk can hold the brief as a Page next to the plan, the files, the mail about the project and the people involved, so the brief stays in view rather than in an email from three weeks ago. That is the idea behind [one desk per task](https://plexiidesk.com/blog/one-desk-per-task).

If you start from notes, the Page work widget's **AI draft** can turn kick-off notes into a first brief with your headings. The draft appears for review first, and nothing goes into the page until you click Insert. AI needs Plexii credits or your own Anthropic key; [pricing](https://plexiidesk.com/pricing) explains what is included. When the project ends, [the project handover guide](https://plexiidesk.com/blog/project-handover) shows how to pass the desk on with its brief intact.

More guides for running work by task are in the [work by task hub](https://plexiidesk.com/blog/c/work-by-task). To keep your next brief on the same desk as the work, [download Plexii free](https://plexiidesk.com/download).

## Common questions

**What is a project brief?**
It is a short document, written at the start, that says why a project exists, what it will deliver, who it is for, when it is due, how success will be judged and what is out of scope. The people involved agree it before work begins.

**What should a project brief include?**
At minimum: why, what will be delivered, who it is for, out of scope, deadline, success measures and who signed it off. Budget, risks and assumptions are worth adding for anything larger than a few weeks.

**How long should a project brief be?**
One or two pages. If it is longer, move the detail into the project plan and keep the brief to decisions.

**Who writes the project brief?**
Usually the project owner or manager, with input from the sponsor. The sponsor and key stakeholders approve it.

**What is the difference between a project brief and a project plan?**
The brief agrees what and why. The plan sets out how: tasks, owners, dates and dependencies. Write the brief first; the plan follows from it.

**Should a project brief change during the project?**
It can, but on purpose. If scope, dates or success measures change, update the brief, note the date and who agreed, and tell everyone who signed the original.
