How to Write a Project Brief: Template and Examples
A project brief turns scattered handover material into a short shared starting point. It helps people understand the purpose of the work, what success looks like, who is involved and which major results are expected, without forcing them to read every sales or planning document.
What a brief should do
Create the brief early, ideally before the internal kick-off, so discussion can focus on decisions rather than basic orientation. Keep it to about one page where practical. That constraint forces useful selection: include what helps people act, and leave detailed tracking to the project manager and supporting plans.
A brief is most useful when it creates a common picture of the work. It can clarify roles, surface grey areas, reduce confusion and give everyone a reason to feel part of the same effort. Reviewing it together also helps the group test scope and goals before detailed commitments harden.
Fields to include
Use this field map as a drafting checklist:
- Project summary: a brief elevator-style explanation of the work, why it is happening now and the value expected.
- Goals or success criteria: three to five outcomes, linked to wider business objectives where possible.
- Client or organisation background: two or three sentences plus a few quick facts about funding, audience, market or operating context.
- Project team: names, roles, photos where helpful and the share of time each person has allocated.
- Stakeholders: names, titles and project responsibilities, with the decision-maker and main client contact clearly identified.
- Deliverables and timing: five to ten major milestones, shown visually if that makes dates easier to grasp.
- Scope boundaries: major items outside the current work, plus any significant breaks in delivery.
- Notes: risks and mitigations, possible later phases, market changes, dependencies and other points that could affect decisions.
The exact sections can change with project size and complexity. The test is whether a new team member can read the page and understand the assignment without hunting through unrelated material.
How to write one, step by step
- Summarise the project and its purpose
Start with a concise pitch. Say what is being done, why now and what value the organisation should receive. For a website redesign, that might mean moving from an outdated content platform to a current secure version, applying refreshed branding and adding digitised user material.
- State what success requires
List the main goals in plain language. In the redesign illustration, the goals are: give visitors a searchable way to browse a collection of more than 100 gantt chart templates; move the site from Drupal 7 to Drupal 9 so content admins can work with current technology; apply the new branding throughout the site; and raise conversions across template downloads, newsletter signups and training course registration.
- Add only useful client context
A short background is enough. The illustration describes an organisation built around a large collection of project charts, supported by training, template sales and visits. It notes that 75% of users only engage with the museum online, and that the museum has only existed for 5 years, so the team structure and decision-making process are still in flux.
- Introduce the people
Separate the delivery team from client stakeholders. For the team, show role and allocation. For stakeholders, show title and responsibility, and make decision-making clear. Photos can help people connect names with faces, but missing stakeholder photos should not delay the brief.
- Show deliverables and dates
Use a small set of high-level milestones rather than a complete task schedule. A visual timeline can make sequence and timing easier to scan. Mark out-of-scope work separately so it is visible rather than buried in prose.
- Capture remaining notes
Use this final area for risks, unresolved role questions, readiness issues and possible future phases. In the illustration, notes flag that many stakeholders want involvement, roles still need to be communicated, branding is not yet ready and completion is estimated at one month.
Before sharing, check that every field answers a practical question: Why are we doing this? What must change? Who decides? What will be delivered? When should it happen? What is excluded? What could get in the way?
Assembled sample brief: all elements together
The six steps above compose one complete sample brief. Assembled together, it reads as a single worked example for a sample web design project:
Project summary: The museum's website is on an outdated Drupal platform. The project moves it to a modern, secure version of Drupal, implements updated branding including a new logo, colors, fonts, and iconography, and includes user-sourced templates that have been digitized.
Goals: Build a searchable online home for a library of more than 100 gantt chart templates. Migrate the site from Drupal 7 to Drupal 9 so content admins can use current technology. Roll the new branding out across the site. Lift conversions across template downloads, newsletter signups and training course registration.
Organisation background: The museum holds a large collection of gantt charts created by project managers from around the world. It is funded by engagement through user training, template sales, and in-person visits. 75% of users only engage with the museum online. The museum has only existed for 5 years, so the team structure and decision-making process are still in flux.
Team and stakeholders: Core team members are listed by name, role, and percent allocation, with photos where available. Key stakeholders are listed by name, title, and project role, with the decision-maker and main client contact identified.
Deliverables and timeline: Five to ten major milestones are shown on a visual timeline, with out-of-scope items called out separately so they are not overlooked.
Notes: Many stakeholders want to be involved, so clear roles need to be determined and communicated to all users. New branding is available but not ready yet. Completion is estimated in 1 month.
Use this assembled version as a check: if your draft cannot be read in this order, in one pass, it is probably carrying too much detail or missing a field.
Brief, creative brief and charter: the distinction
A creative brief narrows in on audience, differentiation, strategy, messaging and design for creative work. A project brief sits above that detail and covers the entire engagement. If creative output is central, the project brief can point readers toward the separate creative direction rather than trying to contain it.
A project charter is different again. It is longer, more formal and designed to record fuller detail and support client approval. It may become the reference point when scope is disputed. The brief should stay consistent with the charter while remaining shorter and easier to use for orientation.
Make the template work for you
A reusable template saves formatting time and gives projects a consistent structure. Choose a layout that everyone can access and edit comfortably, add the organisation's branding and adapt the fields to the work at hand. Landscape and portrait versions can suit different meeting or printing needs.
Treat the first version as a starting point. After a few projects, review which sections people actually use, remove low-value fields and add anything repeatedly missing. Also gather material from sales discussions, proposals, requests for proposals, customer relationship records and the client directly, so useful information from earlier documents is not lost when new working documents replace them.
Finally, do the thinking rather than merely completing boxes. The value comes from judging what the team needs to start confidently: the client's situation, the purpose of the project and the information that will prevent avoidable confusion.
| Document | Main job | Typical depth |
|---|---|---|
| Project brief | Align team and stakeholders on purpose, goals, people and major outcomes | Short and high-level |
| Creative brief | Direct audience, strategy, messaging and design choices | Focused on the creative portion |
| Project charter | Record fuller detail and support client approval | Longer and more formal |
Use the project brief for orientation, the creative brief for creative direction and the charter for fuller formal approval and scope reference.
Frequently asked questions
What is a project brief?
It is a short, readable overview of the essential who, what, when, where and why for a project. A fuller plan explains how delivery will happen; the brief gives team members and stakeholders the shared context they need before detailed planning.
How does a project brief differ from a creative brief?
A creative brief concentrates on strategy, audience, messaging and design direction for the creative portion of work. A project brief covers the whole engagement, including purpose, goals, people, deliverables and timing. Larger creative projects often need both, with the project brief providing the broad frame and the creative brief adding specialist direction.
How does a project brief differ from a project charter?
A charter is usually longer and more formal, records fuller project detail and is used to obtain client approval. It can act as a reference for scope discussions. A brief is a shorter, less formal summary aligned with that detail, intended to inform people rather than serve as a contract.
Who is responsible for writing a project brief?
The project manager is accountable for making sure the brief is complete and understood. Sales or account colleagues may draft an initial version during handover, but the project manager should check it, fill gaps and confirm that the team and stakeholders understand it.