Project briefing template: ready-made questions and a filled-in example.

What a project brief is

A brief is the set of answers the client gives before the project starts. It says who the company is, what it wants to achieve, for whom, by when and with what budget. Whoever does the work uses those answers to build the scope, the quote and the schedule.

Without a brief, the project starts on assumptions. The designer imagines an audience, the developer imagines a deadline, the client imagines a price. At the first delivery the three imaginations meet, and they rarely match. Half an hour of questions at the start prevents weeks of rework at the end.

How to fill in the brief, block by block

The template groups the questions into blocks. Here's what each one needs to produce and where it usually fails.

Step by step to run the brief

1. Send the questions ahead of time. The client arrives at the conversation having already thought about it, and the meeting is for going deeper.
2. Have a conversation, don't just do a form. The answer "we want a modern website" calls for a "modern how? Show me an example."
3. Ask for numbers. Deadline, budget, current volume, target. Where the client doesn't know, write "TBD" and who will find out.
4. Send it back in writing. Send the completed brief and ask for an "agreed." That record settles a good share of later arguments.
5. Review midway. If the objective changes, update the brief and tell everyone.

Common mistakes when using the brief

• Accepting vague answers. "Young audience" and "clean look" seem like answers, but they guide no decision.
• Talking to only one contact. If the person answering isn't the person deciding, the brief needs a second read by the decision-maker.
• Treating the brief as a contract. It records the client's intent. What will actually be delivered lives in the scope and the approved proposal.
• Keeping it in an email. When the team changes or the project grows, nobody finds the right version.

When the brief isn't enough

The brief says what the client wants, not how the work will be conducted. After it, the project needs a schedule, a definition of who does what, such as the RACI matrix, and a client onboarding to organize access, meetings and first deadlines. And, at the end of each delivery, an acceptance form.

How to use the brief in Tasskee

1. Create a form (a Pro plan feature) with the template's questions and send the public link to the client.
2. Set up the form to create a task for each response. The brief arrives inside the project, with the answers in the description.
3. Add the approvers as watchers and approvers on the tasks (a feature from the Start plan up), so the approval of the brief and of deliveries is on record.
4. Invite the client to the guest portal: they follow the project, comment and approve without taking up a plan seat.
5. Save the final brief as a project document, with version history, to consult whenever a question comes up about what was agreed.

If you're still choosing a tool, see what the free plan includes at free project management.