How to prepare a website brief: a template to copy

A good brief explains what the website should let people do, who it is for and what needs to be ready at publication. You do not need to know how to code. Use this guide’s template to turn scattered ideas into a description that makes it possible to design, quote for and approve the work.

By Lyntev. Updated on .
About 4 minutes to read.

From review to publicationA process with approval criteria at every stage.

Translation published on . Original Portuguese guide; source revision .

By the end, you can:

  • Define the visitor’s main action
  • Organise content and functionality
  • Prepare approval criteria

Start with the action you want to make easier

“I want a modern website” describes a preference, but does not yet explain the website’s job. Complete the sentence: “When the right person arrives on the website, they should be able to…”. Requesting a technical visit, choosing a service, booking a conversation or buying a product are actions that guide the pages, copy and buttons.

Choose a main action and identify useful alternatives. Also describe the visitor: what they already know, what they need to confirm and what prevents them from proceeding. Questions received by phone or email are better raw material than a long list of adjectives.

Turn features into specific situations

For each feature, state the input, result and who follows up the request. “Have a form” can mean sending a simple email, collecting attachments, assigning a responsible person or creating a record in a system. That difference affects development and data handling.

Organise needs into three groups: essential at publication, desirable if the budget allows and a future phase. Do not hide an essential need among the extras to obtain a lower proposal: it will reappear when you start using the website.

Turn features into specific situations
Vague requestDescription that makes the work possible
I want enquiriesThe visitor chooses the service and provides their location and contact details; the team receives the request at the specified email address.
I want a galleryProjects have a photograph, description and category; define who adds new projects.
I want appointmentsDefine duration, professionals, availability, confirmation and the option to reschedule.
I want several languagesState the languages, translated pages, person responsible for the copy and how it will be updated.

Organise the materials and identify gaps

Gather the logo, contact details that will be public, service descriptions and photographs you have permission to use. Identify which files are final. If content is missing, write “to prepare” and assign an owner; this makes the dependency visible before setting a date.

Provide visual references and explain what you like in each one: space, typography, motion or the way services are presented. A reference helps you discuss direction; it is not an instruction to copy another company’s identity or copy. In the Lyntev catalogue, you can try your branding on the template itself.

The brief to copy and complete

Answer in short sentences. You can use “to decide” when you do not yet know the answer. The aim is to distinguish decisions made, missing work and choices that need guidance. Do not include passwords or customer data in this document.

Worksheet for your project

Business name and activity:
Person responsible for decisions:
Audience and locations we serve:
Main objective of the website:
Main action and secondary actions:
Questions the visitor needs answered:
Pages or sections needed:
Features: input, result and owner:
Essential at publication:
Possible future phase:
Logo, colours and annotated references:
Copy and photographs available:
Missing materials, owner and expected date:
Existing domain and who manages it:
Tools the website needs to connect to:
Planned budget and recurring costs to consider:
Preferred date and reason for it:
Who collects and approves feedback:
How we will confirm the website is ready:
Who updates and monitors the website afterwards:

Illustrative example: a maintenance company

Imagine a fictitious company that receives enquiries by phone but needs to explain its services better. The objective would be to let visitors identify the type of maintenance and request contact. The website would have a business introduction, services, authorised examples of work and contact options. Automatic appointment booking would be left for a later phase.

The form would ask for service, location and contact details, with an optional message. The person responsible for sales would receive the enquiry and confirm availability. The team would supply its own photographs; the person responsible for the project would approve the copy. This example sets the boundaries of the first project without inventing results, customers or an existing integration.

Define how you will approve the website

Agree observable criteria: correct contact details, planned pages, receipt of a submitted form, working mobile navigation, approved photographs and links to the right destinations. If there are payments, appointments or integrations, describe the journeys that need testing and the limits of the delivery.

Choose one person to collect the team’s feedback. Instead of scattered messages, send a list with the page, element, requested change and reason. Separate corrections from new requests. At Lyntev, bring this brief to your quote request; if you choose a template-based website, the help guide explains how to prepare the order’s materials.

Sources and criteria

Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.

Wellinton Oliveira

Written by

CEO of Lyntev

Technology with context, original analysis and sources you can consult.