How to brief a software project.
A useful brief explains the problem and desired outcome. It does not need to prescribe the technology.
Download the PDF guide ↓1. Describe the current process
Who does what, which systems or documents are involved, how frequently it happens and where delays or errors occur.
2. Define the outcome
Explain what should become faster, safer, easier or more measurable—and how you will recognise success.
3. Identify users and access
List staff, customers, suppliers or partners who may use the software and what each group should be allowed to see or change.
4. Note essential connections
Record existing finance, CRM, ERP, e-commerce, email or specialist systems that may need to exchange information.
5. Separate must-haves from later ideas
A focused first release reduces risk and gets useful software into people's hands earlier.
6. Share constraints honestly
Budget range, deadlines, compliance, data sensitivity and internal availability all shape the best delivery plan.
Use the online project planner →