A website project starts long before the first layout is designed or the first line of code is written. It starts with a shared understanding of what the business needs, who the website should serve, and what a successful result would look like.

That understanding belongs in your website brief.

A useful brief gives your agency enough context to ask better questions, recommend an appropriate approach, and prepare a proposal you can evaluate. It also gives your own team a clear reference when priorities compete or opinions differ.

You do not need technical knowledge to write one. You need a practical explanation of your business, your audience, your goals, and your constraints.

This guide explains what to include, how specific to be, and how to turn an initial idea into a brief that supports better decisions throughout the project.

1. Explain your business and why the project matters now

Start with the context someone outside your organisation would need to understand the project.

Describe what your business does, who it serves, and how customers typically find and choose you. Include the products or services that matter most to the website.

Then explain what prompted the project.

Perhaps your business has outgrown its current site. Your positioning may have changed. Your team might struggle to update content, or customers may repeatedly ask questions the website should answer.

“Building a modern website” describes an intention, but it leaves the underlying problem unclear.

A more useful explanation would be:

We provide commercial cleaning services to offices and retail businesses. Most enquiries currently come through referrals. Our website does not clearly explain our service areas, the types of contracts we accept, or how to request an assessment. We need a clearer website that supports prospective customers and reduces repetitive questions.

That paragraph gives a designer, strategist, and developer something concrete to work with.

If you already have a website, include its address and explain what works well enough to preserve. Existing content, familiar navigation, useful resources, and established search traffic should be considered before decisions are made about replacing them.

2. Define the business goals

A website can serve several purposes, but the brief should identify which ones matter most.

Common goals include generating qualified enquiries, supporting purchases, explaining a complicated service, attracting suitable applicants, or helping existing customers find information.

Prioritise these goals. A website trying to give every audience and action equal prominence can become difficult to navigate.

For each goal, explain the problem behind it and how you might judge progress.

  • Improve enquiry quality. Help visitors understand the service and provide relevant project information. A possible measure is the number of enquiries that match your service criteria.

  • Reduce repetitive questions. Help people find accurate answers independently. A possible measure is the frequency of recurring support questions.

  • Support recruitment. Help candidates explore roles and submit a complete application. A possible measure is completed applications for suitable roles.

  • Improve product discovery. Help visitors find and compare relevant products. A possible measure is progression from product listings to product detail pages.

These measures provide direction; they are not guaranteed outcomes. Results also depend on factors such as your offer, traffic sources, pricing, content, and response process.

Where possible, record your current position before work begins. Without a baseline, it becomes harder to assess what has changed.

If reliable data is unavailable, say so. Establishing appropriate measurement can become part of the project scope.

3. Describe your audience through their needs

Broad audience labels provide limited guidance on their own.

“Business owners aged 25–55” does not explain what someone needs to know before contacting you, what might make them hesitate, or which task they need to complete.

Describe your audience in terms of their situation and questions:

  • What brings them to the website?

  • What are they trying to accomplish?

  • How familiar are they with your services?

  • What information do they need before making a decision?

  • What concerns could prevent them from proceeding?

  • Will they commonly visit on a phone, at work, or while travelling?

For a school website, prospective parents might need to understand the academic offering, admissions process, location, and fees. Existing parents may arrive looking for calendars, notices, or resources.

Those audiences share a website, but their immediate needs differ.

Identify your primary audience and any important secondary audiences. If you are uncertain about their needs, make that uncertainty visible so the agency can recommend an appropriate discovery process.

4. Map the most important visitor journeys

Your brief should explain the actions the website needs to support.

A visitor journey connects a person’s starting point to a useful outcome. It helps the project team understand how pages, content, and functionality must work together.

For example:

A prospective customer arrives from a search result, checks whether we serve their area, reviews the relevant service, and submits a request for an assessment.

That journey suggests several requirements: clear service information, visible coverage details, appropriate proof, and an enquiry form that collects the information needed to respond.

Choose a small number of important journeys and describe them in plain language.

Include what should happen after the visitor takes action. If someone submits a form, who receives it? What information should the confirmation contain? Does the submission need to enter another system?

The experience continues beyond the button click.

5. Outline the pages and content

A proposed page list helps establish the size and structure of the project. It does not need to be a final sitemap.

Start with the pages you believe are necessary, then describe the purpose of each.

  • Homepage: Explain the business and direct visitors. Likely content includes the core offer, service summary, relevant proof, and next steps.

  • Service pages: Help visitors assess suitability. Likely content includes scope, process, examples, and common questions.

  • About: Introduce the organisation and its people. Likely content includes background, team, and approach.

  • Projects or case studies: Demonstrate relevant experience. Likely content includes context, work completed, images, and outcomes where documented.

  • Contact: Make starting a conversation straightforward. Likely content includes contact options, an enquiry form, and response expectations.

Identify repeated page types. A site with twenty service pages built from one consistent structure differs from a site requiring twenty individually designed layouts.

Be clear about content ownership, too. For each major content type, record whether it exists, whether it needs revision, and who will prepare and approve it.

Include written copy, photography, team biographies, product information, downloadable documents, testimonials, and videos.

Content readiness affects both the design and the schedule. A layout based on short placeholder text may need substantial adjustment when the actual material arrives.

6. Describe functionality through its purpose

Features are easier to assess when their purpose is clear.

Instead of writing “We need a booking system,” explain the booking process:

Visitors should be able to select a consultation type, choose an available time, receive confirmation, and reschedule through a link. Our team currently manages availability in an existing calendar.

That description allows the agency to investigate whether an existing service, an integration, or custom functionality would fit.

Apply the same approach to forms, search, payments, accounts, applications, product catalogues, and dashboards.

For each important feature, identify:

  • Who will use it.

  • What they need to accomplish.

  • What information it collects or displays.

  • What should happen after completion.

  • Which existing systems it needs to connect to.

  • Who will manage it after launch.

Separate essential launch requirements from later improvements. Explain the reason for each priority.

If a requirement remains uncertain, label it as an open question. “We need help deciding whether online booking belongs in the first release” is useful information.

7. Explain the visual direction with specific references

Reference websites help communicate preferences when you explain what you find useful about them.

For each reference, identify the relevant detail. You might appreciate its typography, service navigation, project presentation, product filtering, or restrained animation.

For example:

We like the clear service hierarchy on this website and the amount of information included in its project pages. Our own site should use similarly confident typography, adapted to our brand and content.

Include any existing brand guidelines, logos, fonts, photography, or other assets the team is expected to use. Explain whether the identity is established or whether brand development belongs in the project.

Where your team has firm constraints, make them explicit. Examples might include preserving an established logo, supporting two languages, or avoiding automatic video playback.

The references should help the agency understand your priorities and develop an appropriate direction for your business.

8. Share the practical requirements

A useful brief covers how the website will operate after launch.

Explain who will update it and what they will need to manage. Your team may require straightforward controls for services, products, vacancies, articles, or project galleries.

List existing systems that could affect delivery, such as hosting, domain management, a customer relationship management platform, email tools, booking software, or payment services.

You should also describe expectations around:

  • Accessibility: Readable content, keyboard access, understandable forms, and any known requirements.

  • Performance: Important pages and interactions that need to work well across your audience’s devices and connections.

  • Search visibility: Existing pages, URLs, and content that require migration planning.

  • Data handling: The information forms will collect, who needs access, and where it should be stored.

  • Measurement: The visitor actions you need to understand after launch.

  • Handover: Training, documentation, administrative access, and ongoing support.

You do not need to prescribe the technical solution. Describe your operational needs and ask the agency to explain its recommendations.

9. Give an honest budget and timeline

A budget range helps the agency recommend a realistic scope.

It allows the team to explain which requirements fit, where trade-offs may be necessary, and whether delivery should be phased.

Clarify what the budget is intended to cover. Design and development may be only part of the total requirement if the project also needs copywriting, photography, branding, migration, or ongoing support.

If you have not established a budget, explain how you will assess proposals and which requirements take priority. Avoid presenting an unconfirmed figure as a fixed commitment.

Treat the timeline with the same clarity.

Include the desired launch date, why it matters, and whether it is fixed or flexible. List dependencies such as brand approval, photography, content preparation, access to existing systems, and stakeholder review.

“Launch before our admissions campaign begins” gives the team more useful context than “as soon as possible.”

A realistic schedule accounts for your organisation’s responsibilities as well as the agency’s work.

10. Identify the people making decisions

A project can slow down when several people provide conflicting feedback or when approval responsibilities remain unclear.

Name the main contact, the people who will contribute information, and the person responsible for final approval.

Explain how feedback will be collected and consolidated. If different departments own different content, identify those responsibilities early.

Include any expected absences or internal review periods that could affect the schedule.

A simple decision process helps the project move forward without leaving important stakeholders out.

11. Agree on what completion means

The brief should give an initial view of what the delivered project needs to include. The proposal and project agreement can then turn those expectations into a more precise scope.

Useful acceptance points describe observable behaviour.

Examples include:

  • Enquiry forms send the agreed information to the correct destination and display confirmation.

  • Important visitor journeys work across the agreed browsers and screen sizes.

  • The team can update the content identified during planning.

  • Existing URLs included in the migration plan are handled as agreed.

  • Required administrative access, documentation, and training are provided.

  • Launch responsibilities and the process for reporting issues are understood.

Replace broad phrases such as “fully optimised” or “easy to use” with specific expectations wherever possible.

This makes review more constructive because everyone can assess the same result.

A website brief template you can adapt

Use the following outline as a starting point. Answer what you know and mark unresolved items clearly.

Business background

What do you do, who do you serve, and why are you undertaking this project now?

Current website

What is the address? What works, what causes problems, and what should be preserved?

Project goals

What are the primary business objectives? How could progress be measured?

Audience and journeys

Who will visit? What do they need to understand or accomplish?

Pages and content

Which pages do you expect to need? What material exists, what needs work, and who owns it?

Functionality

Which features are essential? What should they do, and which systems must they connect to?

Design direction

Which brand assets are available? Which references are useful, and why?

Operational requirements

Who will maintain the site? What accessibility, performance, migration, data, and reporting needs should be considered?

Budget and timing

What range is available? What does it cover? Which dates and dependencies matter?

Stakeholders and approvals

Who supplies information, consolidates feedback, and approves the work?

Delivery and handover

What should be included at launch? What access, training, documentation, and support will your team need?

Open questions

Which decisions require advice or further investigation?

Review the brief before requesting proposals

Before sharing the document, check that it explains the business problem, gives the project clear priorities, and distinguishes confirmed requirements from assumptions.

Make sure your own team broadly agrees with it. An agency cannot resolve an internal disagreement that has not been made visible.

Then use the brief as the starting point for a conversation. A thoughtful agency should ask questions, identify gaps, discuss trade-offs, and explain its proposed approach.

As decisions are made, update the brief or the agreed project scope so the reference remains useful.

The purpose of a website brief is to give everyone enough shared context to make good decisions. When the goals, audience, responsibilities, and constraints are clear, the project has a stronger foundation for design, development, and delivery.

Planning a website project? Share your goals, current challenges, and available materials with Apporal Digital. We can help clarify the requirements and shape an appropriate scope for your business.