How to Write a Website Specification Brief: Steps and Structure

Introduction

A website specification brief is an essential document that precisely defines the needs, objectives and constraints of a project to create or rebuild a website.

It acts as a roadmap for everyone involved, making sure that every stage of the project stays aligned with your initial expectations.

Whether you're planning to create a professional showcase website, an e-commerce site, or even a blog, a well-structured specification brief helps you avoid misunderstandings and surprises throughout the development process.

This article will show you why writing a website specification brief matters, and how to structure this key document.

Why write a website specification brief?

1. A properly framed project

Writing a website specification brief is an essential step to make sure your project is properly framed from the very start.

This document clarifies the objectives of the website, the expectations of everyone involved, and the technical constraints, which makes the project far easier to plan and track.

A well-framed project is essential to avoid drift, whether in terms of budget, features or deadlines.

2. Clarifying objectives and expectations

A specification brief spells out the specific objectives of the project, whether that's increasing traffic, generating leads, or selling online.

By defining these objectives clearly, you can better focus the development team's efforts and make sure the finished site meets expectations.

This also includes clarifying expectations around the site's design and usability, as well as specific features such as a members' area or an internal search engine.

3. Greater client satisfaction and better use of resources

By formalising the needs and expectations in a specification brief, you increase the chances of fully satisfying the client or the end users.

What's more, this document helps you make the best use of your resources by avoiding superfluous or poorly designed features, and by focusing on what genuinely adds value.

4. Choosing the right provider

Writing a detailed specification brief is also crucial when choosing the provider who will take on the project.

A well-written document lets you request accurate quotes and compare offers objectively. It ensures that the provider you choose fully understands the project's needs and is able to deliver them.

5. Legal value in the event of a dispute

Finally, a specification brief can carry legal weight should a dispute arise between the client and the provider.

It serves as a contractual reference for checking that the deliverables genuinely match the specifications agreed at the outset.

In the event of disagreement, it can be used to demonstrate any shortcomings or divergences from the commitments that were made.

💡

Pro tip
Need help putting together your specification brief? Get in touch with Abstract27 and we'll support you at every stage of the build.

The structure of a website specification brief

The structure of a website specification brief is crucial to ensuring clear, effective communication between everyone involved in the project.

A well-structured document lets you define the project's boundaries and set out a precise framework for each stage of the build.

Here's our go-to template for a well-made specification brief:

1. Context and project overview

• Company overview

It's essential to start with an overview of the company, including its history, its products or services, and its position in the market.

This section helps the provider understand the wider context in which the project to create or rebuild a website sits.

For example, a company looking to launch an e-commerce site will have different needs from one looking to modernise an existing showcase site.

• The web project's role in the wider strategy

The web project needs to be placed within the company's wider strategy. Will the website mainly serve to generate sales, attract leads, or strengthen brand image?

By understanding these factors, the provider can better align the technical and design choices with your strategic objectives.

• Current situation

In the case of a website rebuild, it's important to describe the current state of the existing site. This includes current performance, the technologies in place, and the points to improve.

If the project involves creating a brand-new website, this section should instead highlight the challenges the company wants to overcome, such as a lack of online visibility or the absence of a digital sales channel.

2. Objectives of the website

• Defining the objectives

The objectives of the website need to be clearly defined. These can vary widely: an e-commerce site to increase online sales, a blog to share content and improve search rankings, or an institutional site to inform and engage stakeholders.

Each objective should come with measurable criteria for evaluating the project's success.

• Quantitative and qualitative objectives

Objectives should be both quantitative and qualitative. For example, a quantitative objective might be to increase organic traffic by 30% within a year.

A qualitative objective, on the other hand, might be to improve the user experience through optimised site usability and relevant content.

It's crucial to define these objectives up front to guide decisions throughout the project.

3. Audience and market

• Describing the target audience

Understanding your target audience is a key element in creating a website.

The specification brief should include a detailed description of your personas: who are the end users? What are their expectations, their needs, and their online behaviour?

A solid understanding of the audience lets you tailor the design, the content, and the features of the site to maximise its effectiveness.

• Market and competitor analysis

A market and competitor analysis is also necessary to position the site as effectively as possible.

The specification brief should provide an overview of direct and indirect competitors, as well as market trends.

This helps you identify opportunities and threats, and adjust the project accordingly to stand out in a competitive environment.

4. Project scope

• Defining the functional scope

The functional scope describes the full set of features and services the site will need to offer.

This includes aspects such as multilingual management and the integration of specific features like payment systems, members' areas, or analytics tools.

This section of the specification brief needs to be detailed enough to avoid the misunderstandings and oversights that could delay the project or push up costs.

• Functional and technical description

A clear, detailed functional and technical description is essential for translating the project's needs and objectives into concrete specifications.

This section of the website specification brief lets you define the site's architecture, the content to include, the design choices, and the technical aspects that will need to be taken into account.

5. Site architecture and structure

• Diagrams and page organisation

The site's architecture, also known as its site structure, is the way the site's pages are organised and linked together.

This section of the specification brief should include diagrams or plans showing the organisation of the main pages, sub-pages and navigation elements.

A well-thought-out site structure makes navigation easier for users and improves the accessibility of the content.

• Content to include (text, images, videos, downloads)

The specification brief should specify the types of content that will be included on the site: text, images, videos, downloadable documents, and so on.

It's important to specify the formats, maximum sizes, and quality requirements for each type of content.

For example, high-resolution images may be needed for an e-commerce site, whereas a blog might call for explanatory videos.

6. Design and usability

• Brand guidelines, design, and usability requirements

The site's design and usability are key elements in delivering an optimal user experience.

The brand guidelines need to be defined precisely in the specification brief: choice of colours, typography, image style, and other visual elements that reflect the brand's identity.

In terms of usability, it's crucial to specify the requirements around intuitive navigation, page load times, and accessibility for all types of users.

• Mock-ups and inspiration examples

Mock-ups are visual representations of the site's design. They let you validate the design and usability choices before development begins.

The specification brief can include inspiration examples drawn from other sites, along with preliminary mock-ups to give a clear idea of the desired final look.

7. Specific features

• Members' areas, search engine, newsletter, etc.

This section should detail the specific features the site needs to offer. This includes, for example, creating members' areas.

It could also involve integrating an internal search engine. Newsletter management is another feature to consider.

Finally, think about including the option to leave comments on a blog. Each feature should be described in terms of user needs and the technical solutions being considered.

• Technical aspects (hosting, search optimisation, browser compatibility)

The site's technical aspects need to be addressed in depth. This includes, among other things, the choice of hosting, maintenance, and search optimisation (SEO) strategies.

Finally, it's crucial to check compatibility across different browsers and devices. These elements are essential to ensuring the site's performance and longevity.

8. Budget and timeline

This section of the specification brief lets you define the financial resources needed and set out a precise schedule for how the project will unfold.

• Budget envelope

The budget for the site needs to be clearly set out from the start. This budget envelope should cover the costs of development, maintenance, marketing, and possibly user training.

A sensible allocation of the budget ensures that all phases of the project are properly funded, avoiding interruptions or compromises on quality.

For example, it's important to set aside a budget for search optimisation (SEO) to ensure the site has good visibility once it launches.

• Project timeline

The project timeline needs to be clearly defined, with precise deadlines for each phase, from designing the wireframes through to final testing and launch.

Every intermediate step, such as developing the features, creating the mock-ups for the site, and running compatibility tests, should have a deadline to make sure the project moves along smoothly and according to plan.

The different types of website specification brief

A specification brief can take several forms depending on the specific needs of the project.

It's important to understand the distinctions between these types so you can choose the one that best fits your situation.

1. Functional specification brief

The functional specification brief mainly describes the functional needs of the project.

This covers the objectives of the site, the expected features, the budget, and the people involved in the project.

This type of specification brief is particularly useful for framing the project as a whole, ensuring that all the necessary features are well defined and aligned with the objectives of the website.

2. Technical specification brief

The technical specification brief focuses on the technical aspects of the project.

It details the technologies used for the site, the compatibility requirements, the choices around hosting and site maintenance, as well as the security measures to put in place.

This document is essential for development teams, as it provides them with all the technical specifications they need to deliver the project.

3. Design specification brief

The design specification brief relates specifically to the visual aspects of the site.

It defines the site's brand guidelines, the UX/UI design, the mock-ups, and the visual elements that need to be integrated.

This type of specification brief is crucial for projects where visual identity plays a central role, such as brand sites or sites aimed at a creative audience.

Mistakes to avoid when writing your specification brief

Writing a website specification brief is a crucial step, but it can easily become a source of mistakes.

Here are a few common pitfalls to avoid to ensure your project's success.

1. Poor budget allocation

One of the most frequent mistakes is poor budget allocation. This can show up as a lack of resources allocated to essential aspects such as search optimisation (SEO), maintenance, or content creation.

Neglecting these elements can jeopardise the site's success over the long term. It's therefore crucial to plan a balanced budget envelope that covers all the project's needs, from design through to the post-launch phase.

2. Choosing the provider

Choosing a provider to build the site is a critical decision. A common mistake is to select a provider based on price alone, without assessing their technical skills or their understanding of the objectives of the website.

It's important to carefully check the provider's references, read client reviews, and make sure they have the experience needed to deliver a project similar to yours.

3. Over-specification or under-specification

Another pitfall is over-specifying or under-specifying in the specification brief.

Over-specification can lead to excessive rigidity, making the project difficult to adapt as needs evolve.

Conversely, a lack of specifications can lead to misunderstandings and deviations from the initial expectations.

It's therefore essential to strike the right balance by providing clear specifications that are still flexible enough to allow for adjustments along the way.

4. Risks linked to poorly estimated deadlines

Misjudging the project deadlines is a mistake that can have significant consequences, including delays to the site's launch and rising costs.

To avoid this, you need to plan a realistic schedule that takes possible setbacks into account. It's also important to build in safety margins for the project's critical stages, such as testing and corrections.

Conclusion

Writing a website specification brief is a fundamental step in ensuring your project's success.

A well-designed document not only helps you frame the project, but also ensures clear communication between everyone involved, makes the best use of resources, and reduces the risk of misunderstandings or disputes.

To help you get started, we invite you to follow our website specification brief template.