What a Website Brief Should Include

A good website brief includes seven elements: the project goal, the target audience, the tone and design direction, the list of pages, the content responsibilities, the deadline, and the budget. Cover all seven and a studio can scope, quote, and start work inside 24 hours. Leave any of them out and the project will stall somewhere between the first call and launch.

This is not bureaucracy for its own sake. A brief is the device that protects you from scope creep and protects the studio from building the wrong thing. It is the moment at which a vague idea becomes a specific project. Without it, both sides are building from assumptions rather than agreement — and assumptions are where timelines slip and budgets go.

What a Brief Is For

The purpose of a brief is not to tell us what to build. It is to create shared truth before work begins.

A good brief answers the question that sits behind every design decision: what is this site trying to do, for whom, and by when? When that question is answered in writing and agreed upon before the first design choice, every decision that follows has a reference point. When it is not, every decision becomes a negotiation.

Scope creep — the phenomenon where a project quietly expands beyond what was agreed — almost always traces back to a brief that was missing something. A client who expected five pages when the studio quoted for three is not being difficult. There was just no document that said "three pages". A studio that builds a contact form when the client expected a booking calendar with deposit handling has not made a mistake. It built what the brief described. The brief was wrong.

A brief does not remove all ambiguity — projects evolve, and good studios handle that gracefully. But it sets a baseline. Changes to that baseline are visible, priceable, and agreed upon — not discovered on launch day.

What You Need to Know Before Writing One

You cannot write a useful brief without first knowing a few things about your own project. These are not things the studio can discover for you. They require decisions on your side first.

Your domain. What is the website for? A consultancy, a shop, a booking platform, a portfolio, a product launch? Each of these is a fundamentally different type of site with different structural requirements. Knowing which one you are building — or being honest that you are still deciding — matters before the brief is written.

Your audience. Who is the site for? Not in a marketing abstract sense, but specifically. Are they returning customers who know your brand? New visitors who need to be convinced? Professionals assessing your credentials? Each of these audiences arrives at the site with different questions and needs different things from the design. A site for existing customers prioritises account management and trust. A site for cold visitors prioritises persuasion and clarity.

One primary goal. What is the single most important thing the site needs to do? Take an enquiry. Sell a product. Demonstrate expertise. Get a booking. Most sites have one primary job, even if they do several things. Naming it forces useful clarity and prevents the site from trying to do too many things at once.

Your existing assets. Do you have a logo? Brand guidelines? Approved copy? Photography? If the answer is "sort of" or "we're working on it", that needs to be in the brief. A studio building a site cannot design around brand assets that do not yet exist. Knowing what is ready — and what still needs to be produced — is essential to building a realistic timeline. See how long it takes to build a website for how asset readiness affects the schedule.

The 7 Things Every Brief Should Include

Once you know the above, a brief can be written. These are the seven elements we look for — and the ones most likely to be missing when a project runs into trouble.

1. The Goal

State the primary objective in one clear sentence. "The site should generate enquiries from hospitality businesses looking to rebrand." "The site should sell wine online to customers across Spain." "The site should present our studio's work to potential clients in London and Barcelona."

Vague goals ("we want a professional website that represents the brand") are understandable but unhelpful for scoping. A studio cannot build to a vague goal. Translating it into something specific is the first useful thing a brief does.

2. The Audience

Name the people the site is for. Age range if relevant. Industry if relevant. What they already know about you when they arrive. What questions they are likely to have. The more specific this is, the better the design can serve them — and the easier it is to make decisions about copy, hierarchy, and tone. The brief should also note if there are secondary audiences who matter less but still need to be served.

3. Tone

How should the site sound and feel? Formal or conversational? Technical or accessible? Warm and personal or precise and efficient? Tone shapes every word on the site and has significant influence on visual decisions like typeface and spacing. If you have existing brand guidelines with a tone of voice section, include them or reference them. If you do not, a few well-chosen comparators — sites you admire or businesses whose tone you want to match — are a useful starting point.

4. Pages

List the pages you need. Not aspirationally — practically. What does the site actually require to achieve the goal? A typical brief for a professional services business might read: Home, About, Services, Work (case studies), Contact. A brief for an e-commerce business might read: Home, Shop (category), Product (template), Cart, Checkout, About, Contact.

Listing the pages has two purposes: it shows whether the scope matches the budget tier you have in mind, and it surfaces disagreements about scope before they become expensive. If the studio quotes for six pages and the client expects twelve, a page list in the brief makes that visible immediately.

5. Content

Who is writing the copy? Who is providing the images? Are there existing assets ready to use, or does everything need to be produced during the project?

This is one of the most common gaps in briefs we receive. A studio can design and build a page, but it cannot write your case studies or photograph your product range. If content production is not in the brief — including who is responsible for it and when it will be ready — it becomes a dependency that delays the project. Content bottlenecks account for a large proportion of delayed launches.

If you need help with copy or photography, say so in the brief. That opens a conversation about whether the studio can help, or whether a copywriter or photographer should be added to the project. It is a much easier conversation before work starts than after.

6. Deadline

When does the site need to be live? Work backwards from that date: if the launch is in eight weeks, and the studio needs two weeks for design and two weeks for development, that leaves four weeks for discovery, revisions, content delivery, and QA. If the content is not ready in week three, the launch date moves. A brief with a deadline makes these dependencies visible and keeps everyone accountable.

If the deadline is flexible, say so — and say what is driving it. An event, a product launch, a funding announcement. Knowing the context helps the studio understand which parts of the schedule are genuinely fixed and which have room.

7. Budget

State the budget, or at minimum the tier you are working within. We understand that this is uncomfortable for many clients — there is a reasonable fear of anchoring the price too high. But a studio that does not know the budget cannot tell you whether the project is feasible. It can only quote what it would charge for a project in isolation, and that quote may be significantly more or less than you were expecting.

Naming a budget is not a negotiating disadvantage. It is the thing that allows a studio to tell you honestly whether it can deliver what you need within that number — and if not, what would need to change. Without a budget in the brief, you risk spending three weeks scoping a project that does not fit the number you had in mind.

What Happens When Something Is Missing

Illustrating this is more useful than describing it abstractly. Consider a business that approaches a studio for a new website. The brief covers the goal, the audience, and the tone — it is thoughtful and clear on those points. But the pages section says "five or six pages, to be discussed", the content section is blank, and the deadline section says "as soon as possible".

By week three, the client has sent over three of the six pages of copy. The remaining pages are "almost ready". By week five, the design is done but the studio cannot finish the build without the content. The "as soon as possible" deadline now has an implicit date attached — the client mentioned offhand that they want to launch before a trade show in week seven.

That trade show date was not in the brief. It could have been. If it had been, the studio would have flagged in week one that the content needed to arrive by week four to hit the date. Instead, it arrives in week six. The launch is pushed. The client is frustrated. The studio has spent time designing placeholder pages it now has to redo. None of this is anyone's fault. The brief just did not cover the things that would have prevented it.

How to Submit Your Brief and What to Expect Next

Once you have a brief written — even a rough one — bring it to an initial call. A written brief, even if incomplete, is more useful than no brief. It shows the studio where you are in your thinking and makes the conversation more productive.

At Atlas, we work through the brief on the call: clarifying anything that needs clarification, flagging gaps, and using it to confirm the scope and tier. A brief that covers the seven points above typically allows us to quote within 24 hours. A brief that is missing significant sections leads to a longer scoping process.

After the brief is agreed, we write a project scope document that expands on it — specific page count, content responsibilities, milestone dates, and payment terms. The brief is the starting point; the scope document is the contract. Both need to exist before work begins.

If you are not sure how to start, the simplest version of a brief is a one-page document that answers these questions in plain language. You do not need a template. You need answers. The more specific those answers are, the faster we can move from conversation to build.

---

Have a brief forming? Talk to us — we'll tell you what's missing before work starts.