A project brief.
Everyone starts aligned.

A project brief is a short document that explains what a project is for and what it involves, so everyone starts with the same understanding. It’s lighter than a statement of work: it aligns people on goals and constraints before the detailed scope and contract.

Details

• Client / company: [Name]
• Completed by: [Name, role]
• Date: [Date]

Background

• What’s the context for this project? [Answer]
• What problem or opportunity does it address? [Answer]

Objectives

• What must the project achieve? [Answer]
• How will we measure success? [Answer]

Scope

• What’s included? [Answer]
• What’s explicitly not included? [Answer]

Stakeholders

• Who is the sponsor? [Answer]
• Who is the day-to-day contact? [Answer]
• Who else must be consulted or kept informed? [Answer]

Timeline and budget

• What are the key dates? [Answer]
• What’s the budget range? [Answer]

Risks and dependencies

• What could delay or derail the project? [Answer]
• What do we depend on from others? [Answer]

1. Write the background and problem in a few sentences.
2. Agree two or three objectives and how you’ll measure them.
3. List what’s in and out of scope.
4. Name the sponsor, contact and other stakeholders.
5. Add key dates, budget and the main risks.
6. Share it for comment, then use it to write the proposal or SOW.

Microsoft Word

1. Download the Word (.docx) file and open it. If Word opens it in Protected View, select Enable Editing.
2. Use Find (Ctrl+F or Cmd+F) and search for “[” to jump between the placeholders you need to replace.
3. Save a clean copy as a Word template (File → Save As → Word Template) so every new document starts from it.

Google Docs

1. Upload the .docx file to Google Drive.
2. Right-click it and choose Open with → Google Docs, then File → Save as Google Docs to keep an editable copy.
3. Use File → Make a copy for each new client so your master stays clean.

PDF

Fill it in Word or Google Docs, then export it: File → Save As → PDF in Word, or File → Download → PDF document in Google Docs.

Sample answers from a fictional client.

Sample answers

• Problem? Order fulfilment times have doubled in a year; we don’t know why.
• Success? A prioritised plan the board approves by the end of Q3.
• Not included? Implementing changes or buying new systems.
• Sponsor? The COO. Day-to-day contact: the operations manager.
• Risks? Peak season in October limits staff time for interviews.

• Keep it to two pages; the detail belongs in the scope of work.
• Name people, not departments.
• Write risks down early: they’re easier to discuss before anyone is committed.

Angelwood turns questions like these into an onboarding plan: requests with instructions, owners and dates that clients answer in their portal, reviewed by your team before kickoff.

Browse all briefs templates or the full template library.