HireOrSell logo
All articles

Project brief template

A project brief template with ten fields, a prompt for each and a filled example, so the team and the client agree on goals, scope and success before work begins.

Cover graphic titled Project brief template

A project brief is one page that says what you are building, for whom, by when and how everyone will know it worked. It prevents the most common argument in agency work: two people holding different pictures of the same project. This template gives you ten fields, a prompt for each and a filled example.

When to write it

Write the brief after the proposal is accepted and before the kickoff. Draft it yourself from the proposal and the discovery notes, then send it to the client to confirm. Their correction is the point. The brief is not a contract, but it is the document you point to when a request seems to drift.

Keep it to one page. If it takes two, you are writing the scope document instead.

The ten fields

Copy the headings and answer each prompt in a line or two.

  1. Project name and owner. What is it called, and who on your side is responsible?
  2. Background. What situation led to this project? Two sentences.
  3. Goal. What should be different when this is done? Use one main goal.
  4. Audience. Who will use or see the result?
  5. Deliverables. A list of what you will hand over.
  6. Out of scope. What you are not doing. This line prevents more disputes than any other.
  7. Timeline. Start date, key milestones and the delivery date.
  8. Budget and basis. Price, whether it is fixed or hourly and what is included.
  9. Client responsibilities. What they provide, by when, and who approves.
  10. Success measures. How you and the client will judge the result.

A filled example

Say a fictional veterinary clinic hires you to rebuild its booking page.

  • Project name and owner. Clinic booking page rebuild. Owner: project lead.
  • Background. Clients book by phone, and the front desk is busy in the mornings. The current page lists opening hours and a phone number only.
  • Goal. Let clients request an appointment online, outside opening hours.
  • Audience. Existing pet owners on phones, and new clients finding the clinic by search.
  • Deliverables. A new booking request page, a confirmation email to the client, a notification to the front desk, and a short staff guide.
  • Out of scope. Online payment, a patient records system and changes to the rest of the website.
  • Timeline. Start 3 March. Design approved by 14 March. Build complete by 4 April. Launch 11 April.
  • Budget and basis. Fixed price $4,400. Includes two rounds of revisions.
  • Client responsibilities. Provide opening hours, services list and photos by 7 March. One named approver for each stage. Feedback within five working days.
  • Success measures. Requests can be submitted at any hour. The front desk receives each request by email. Staff confirm they can use the guide without help.

Check the arithmetic in the budget field

Fixed-price projects still need an hours estimate. For the example:

  • Design: 16 hours.
  • Build: 20 hours.
  • Testing and launch: 4 hours.
  • Total: 16 + 20 + 4 = 40 hours.

At $110 an hour, 40 x 110 = $4,400, which matches the fixed price. If the same work ran to 50 hours, the cost at your rate would be 50 x 110 = $5,500, so you would have given away $1,100. Writing the hours behind the price gives you a way to notice that during the project.

Prompts for the harder fields

Goal. If you find yourself writing three goals, ask the client which one wins if they conflict. "Look modern" is not a goal. "Let clients book at night" is.

Out of scope. Think of the three most likely requests that you would not do within this price. Write them down.

Success measures. Choose things you can check. Avoid vague words such as "better" and "improved" unless you say what is compared with what. If you do not have a baseline number, do not invent one. Use a yes or no test instead.

Client responsibilities. Put dates next to each item. A line such as "photos by 7 March" is easier to enforce than "client will supply photos".

Link the brief to daily work

Once the brief is agreed, use it to build the project record. The new project setup checklist lists what to configure at that stage, from budgets to folders.

Hours estimated in the brief should be tracked against actuals. Good time tracking habits on a small team make that comparison possible without extra effort at the end.

Common mistakes

  • A brief that is really a wish list. Everything is in scope, so nothing is.
  • Writing it alone and filing it. If the client has not confirmed, it is only your opinion.
  • No out-of-scope line. The most frequent source of unpaid work.
  • Treating it as fixed. The brief can be updated, but only with a dated note that the client has seen.

Sample wording for the cover note

When you send the brief to the client, keep the note short:

"Here is a one-page summary of what we agreed. Please read the goal, the out-of-scope list and the dates. If anything is wrong or missing, tell me by Friday. Once you confirm, this is the reference we will use for the project."

The deadline matters. A brief that sits unread has no value, and a brief the client confirmed is your best defence against a later change of mind.

Next step

Take the project you are about to start and fill in the ten fields in 20 minutes. Send it to the client with one question: "Is there anything here you would describe differently?"

Free plan available

Ready to run it all in one place?

Projects, clients, time tracking and invoicing in one platform.