Web Design · 6 min read
What a useful website brief should contain
The essential decisions and inputs that help a website project begin with clarity instead of assumptions.
Describe the business outcome
A website is not successful merely because it is attractive. The brief should state what the organisation needs visitors to understand or do.
Examples include requesting a quotation, booking a consultation, evaluating services, accessing documents, applying for a programme, or completing a purchase.
Define the audience and their questions
List the primary visitor groups and the questions each group must answer before taking action. This shapes navigation, content order, calls to action, and proof.
- Who is the visitor?
- What problem brought them here?
- What may prevent them from trusting the offer?
- What action should they take next?
Confirm scope and content ownership
The brief should identify required pages, content that already exists, content that must be written, and the person responsible for approvals.
Missing content is one of the most common causes of delayed website projects.
Record functional and operational requirements
Forms, booking, ecommerce, payments, user accounts, integrations, languages, analytics, hosting, maintenance, and legal content should be identified early.
A clear brief does not need to solve every detail. It needs to expose the decisions that affect scope and architecture.
Use the brief as a decision tool
A useful brief gives design and development a shared reference. When new requests appear, they can be evaluated against the original outcome rather than added without considering cost or complexity.