What to include in a digital project brief
A clear brief helps your delivery team understand the problem, estimate the scope and agree the next step.
Explain the problem and the people
Describe what happens today and what needs to improve. Name the people who will use the product and the tasks they need to complete. Include a concrete example, such as a customer struggling to request a service or a team re-entering the same order. This gives the project a purpose beyond a list of screens.
List scope and constraints
Set out essential features, existing systems and known limits. Include any deadline and explain what makes it important. Share your budget range if available, so the team can suggest a realistic scope. State which content and assets already exist, who will provide missing material and who can approve decisions.
Describe a successful handover
Ask for the access, documentation and training your team will need. Identify who should own the domain, software accounts and project materials. Describe the support you expect after launch. Acceptance criteria should be observable: a user can complete an enquiry, an administrator can update a page or an approved record reaches the intended system.
Leave room for discovery
A brief does not need to solve every technical question. Flag assumptions and open questions clearly. Share relevant examples and explain what you like about them, such as navigation or content structure. Your delivery team can then explore the uncertain parts with you before turning the brief into a detailed scope and delivery plan.
