A briefing (or brief) is a document that summarises all the essential information a team needs to execute a project, campaign or specific task. It is the starting point for any professional work in marketing, design, development or consultancy.
A good briefing answers the fundamental questions: what needs to be done, why, for whom, with what resources and by when. It sounds simple, but most briefs circulating in the real world are vague, incomplete or outright contradictory.
And the consequences of a bad briefing are predictable: rework, misunderstandings, missed deadlines, results that do not align with expectations and frustration on both sides. A study by the Association of National Advertisers estimated that companies waste up to 40% of their marketing investment due to deficient briefs.
The good news is that creating an effective briefing does not require creative talent or technical experience. It requires clarity, structure and the discipline to think before acting.
A briefing serves three fundamental functions:
It is the informal contract between the person commissioning the work and the person executing it. If both parties agree on the brief, there is an objective basis for evaluating the result. Without a brief, expectations are subjective and conflicts are inevitable.
Every decision not made in the briefing will be made during execution, often without the necessary context. A good brief reduces uncertainty and enables the executing team to make informed decisions when the unexpected arises.
The brief is not a document you create and forget. It is the constant reference throughout the entire project. When questions, scope changes or directional debates arise, the brief is the anchor point.
There is no single format valid for all contexts, but there are sections that every professional briefing should include.
| Section | What to include | Practical example |
|---|---|---|
| Context | Current situation, background, why the project exists | "Our product landing page conversion rate has dropped from 3.2% to 1.8% over the last 3 months." |
| Objective | What you want to achieve, with specific metrics | "Recover a 3% conversion rate on the product landing page within 8 weeks." |
| Target audience | Who it is aimed at, segments, user profile | "Marketing directors at B2B SaaS companies with teams of 5-20 people." |
| Scope | What the project includes and, just as importantly, what it does NOT include | "Includes: landing page redesign and A/B test. Does not include: changes to the email funnel or onboarding process." |
| Deliverables | What is expected at the end, in what format | "Heuristic analysis report (PDF), wireframes (Figma), testing plan (document)." |
| Available resources | Budget, tools, access, assigned team | "Budget: 5,000 euros. Access: GA4, Hotjar, CMS. Team: 1 designer + 1 developer." |
| Timelines | Key dates, intermediate milestones, final deadline | "Analysis: 15 Aug. Wireframes: 22 Aug. Test live: 1 Sep. Report: 30 Sep." |
| Constraints | Technical, legal, brand or business limitations | "The header cannot be modified (shared component). GDPR: explicit consent required." |
| Success criteria | How you will evaluate whether the project was successful | "Success = conversion rate above 2.8% with 95% statistical significance." |
If you could only complete one section of the briefing, it should be the objective. And not a vague objective like "improve the website" or "increase sales". A useful objective is specific, measurable and has a deadline.
Compare these two objectives:
The second allows you to design a strategy, measure progress and evaluate the result. The first only allows for opinion debates.
Not all briefs are the same. The level of detail and specific sections vary depending on the type of project.
For branding campaigns, graphic design or content production. It includes specific sections such as tone of communication, visual references, key messages and brand style guide.
For advertising campaigns in paid media. It includes budget by channel, target audiences, KPIs per platform, attribution windows and available creatives.
For experimentation and conversion rate improvement projects. This is probably the type of briefing that generates the most value per euro invested, because it defines exactly what will be optimised and how success will be measured.
A CRO brief should include:
| CRO-specific section | Content |
|---|---|
| Pages or flows to optimise | Specific URLs, screenshots of the current state |
| Current data | Current conversion rate, traffic volume, segments |
| Initial hypotheses | What the team believes is failing and why |
| Analytics tools | GA4, heatmaps, session recordings, surveys |
| Technical capacity | What can be changed without development (CMS) vs. what requires dev |
| Test history | Previous experiments, what worked and what did not |
| Significance criteria | Required confidence level (typically 95%) |
To go deeper into what a complete CRO audit should include, it is recommended to start from a structured brief as the basis for the analysis.
For implementation or audit projects of measurement tools. It includes current tech stack, events to track, custom dimensions and metrics, privacy requirements and reporting structure.
Do not sit down to write the brief from scratch. First, talk to the stakeholders involved. Ask questions like:
These preliminary conversations often reveal information that would never appear in a document written in isolation.
Use the SMART framework as a guide: specific, measurable, achievable, relevant and time-bound. If you cannot measure whether the objective has been met, the objective is not useful.
Defining what the project does NOT include is just as important as defining what it does. Explicit exclusions prevent scope creep (uncontrolled expansion of scope), which is the number one cause of projects that fall behind schedule and go over budget.
Do not set arbitrary dates. Consult with the executing team about how much time they need and negotiate a calendar that is ambitious but feasible. Impossible deadlines only produce two outcomes: mediocre deliverables or non-compliance.
The team receiving the brief needs to understand the why behind each decision. If they know why the objective is what it is and not something else, they will make better decisions during execution.
Before starting, make sure all people involved have read the brief, understand it and agree with it. If there are disagreements, it is better to resolve them now than during execution.
Below is a template you can adapt to any digital marketing, CRO or analytics project.
| Field | Content to complete |
|---|---|
| Project name | [Descriptive name] |
| Project lead | [Name and role of the person leading] |
| Brief date | [DD/MM/YYYY] |
| Context | [Current situation, background, problem identified] |
| Primary objective | [Specific, measurable, with deadline] |
| Secondary objectives | [Maximum 2-3, prioritised] |
| Target audience | [Segment, profile, behaviour] |
| Scope (includes) | [Tasks, pages, channels included] |
| Scope (excludes) | [What is explicitly out of scope] |
| Deliverables | [List of expected outputs with format] |
| Budget | [Total amount or range] |
| Tools and access | [Platforms, required access] |
| Timelines | [Intermediate milestones + final deadline] |
| Constraints | [Technical, legal, brand-related] |
| Success criteria | [How success will be measured] |
| Stakeholders | [Who approves, who reviews, who executes] |
"We want something modern that works" is not a briefing. It is a letter to Santa Claus. The more specific you are, the better the result.
A 30-page brief with the company's history since its founding does not help. Include only the information the executing team needs to make decisions.
If you do not define how success is measured, you will never know if the project went well. And discussions about quality become opinion debates.
Scope changes happen. That is normal. What is not normal is not documenting them and not adjusting timelines and budget accordingly. Every change to the brief must be in writing and accepted by both parties.
"We will figure out the budget later" is a recipe for disaster. The team needs to know the budget to size the solution. Optimising a landing page with 2,000 euros is not the same as optimising one with 20,000.
In the world of CRO and digital analytics, the briefing is not an administrative formality. It is the first step of the optimisation process. A well-structured brief defines what will be measured, what hypotheses will be tested and how the result will be evaluated.
Without a brief, an optimisation project becomes a series of random changes with no clear direction. With a brief, it becomes a scientific process with measurable objectives and actionable results.
The time invested in a good briefing is recovered many times over during execution. Fewer reworks, fewer misunderstandings, fewer meetings to "align". More focus, more speed, better results.
Need help defining the briefing for your next optimisation project? At Boost, as a consultancy specialising in conversion, we work with a structured process that always starts with a clear brief and rigorous data analysis. This is how we ensure that every optimisation action is oriented towards measurable results.
What is a digital partner and why does your company need one? Discover its functions, how to choose the best one, the differences with freelancers and...
Learn what CPM means in marketing, how to calculate it, when it makes sense to use it and why optimising conversion matters more than negotiating cost per...
Discover what a conversion funnel is, how it differs from a sales funnel and how to optimise each stage to maximise your results.
