Write the requirement in business language
Start with the people and the problem: businesses with dated or slow websites need to refresh visual identity without losing important URLs because visitors leave pages that look broken or outdated on phones. A useful project brief should describe the current process before describing technical features.
Section 1: users, roles and real scenarios
List each user group, what information they create, what they can edit, what requires approval and what they can view. Add a typical busy-day scenario and an error-correction scenario.
Section 2: required steps and screens
- Page audit
- Content mapping
- New design system
- Redirect planning
- Speed and accessibility test
Section 3: outputs and acceptance samples
- Responsive new pages
- Redirect map
- Meta migration
- Launch checklist
Section 4: business rules and exceptions
- Seo preservation
- Backup
- Site ownership
Section 5: technology and delivery
Specify devices, hosting responsibilities, integrations where actually needed, data migration, branding, responsive behavior and any language or print constraints. Do not prescribe a technology solely because another company uses it.
Section 6: testing and sign-off
Each requirement should have a test input, an expected result and the name of an approving stakeholder. Track conversion improvement after launch to judge whether the project achieved its intended purpose.
Template request
When asking for a quote, attach sample records or reference materials and request a phased scope with inclusions, exclusions and change management in writing.
Continue exploring
Browse the complete guide library, our software services, website development or creative services.