A Project Brief is that essential document, which defines the primary client's requirements for the project.
Typically, any project starts with this document. An executor sends the brief to the customer, who should concretize the project. Based on the data provided, you initiate the project realization run-up or further discussion on the details.
A good brief should contain all the key information about the client’s project and businesses an executor needs to evaluate and proceed with the project development.
You should realize – there’s no universal brief template. Each type of project – design, web development, mobile app development, PR, etc. - requires different briefs. Yet, the general brief structure stays the same in most cases. It’s the niche-specific elements that vary.
When outlining briefs, the amount of required data can vary significantly as well. In certain cases a few very short and general phrases are sufficient (when the brief’s just 1-2 pages long), while in some other cases all the major project points should be set out in detail (then the brief can stretch up to 10-20 pages).
Here’s a quick winning formula for briefs: at the beginning 5-6 most important questions, aimed at getting the crucial information you cannot start without; next – detailed, additional information that may be required during the work phase.
Below is the list of the most common questions you are likely to find in any brief:
- Company profile/ description of the client:
- Project description
- Technical requirements
- Project Budget
- Project Timeline and Deadlines
In this toolkit, we’ve gathered sample project briefs and brief templates from different niches. Inside, you’ll find a design brief template, creative brief, sample mobile, and web development brief.
You can find more essential information about briefs in the video guides below and in the Additional Materials.
