Insights · Brief
What Should a Beverage Branding Brief Include?
Insights · Brief
A beverage branding brief should tell a partner what you are building, what already exists, what is fixed, and what you want the work to resolve. It does not need to be finished, and it should not contain the answers you are paying someone to produce.
A workable brief covers the purpose of the project, the product as it stands today, the opportunity and the occasion, the competitive set, portfolio and format intent, the claims you want against the claims you can substantiate, the constraints you cannot move, the assets that already exist, the scope you think you need, who signs off, and what has to be true when it ships.
Sections you cannot answer stay in the document, marked open. A named gap is worth more than a confident guess.
This article is about the document. It is not about the decisions.
Whether formulation, branding or packaging should move first is a different question, and it has to be settled before a brief means anything. It is answered in what comes first: formulation, branding or packaging, together with the readiness checks that belong before anyone is briefed.
Assume those decisions are underway. What follows is how you turn them into a document someone can price, plan and argue with — and what to write in the sections where the decision has not landed.
The distinction matters commercially. Founders delay contacting anyone because they think a brief is a certificate of readiness. It is not. It is a shared starting position, and its job is to make the state of the project legible, including the unresolved parts.
A beverage branding brief does three things.
It transfers context, so a partner does not spend the first stretch of the project reconstructing what you already know: the stage the liquid is at, the suppliers already committed, the market you are entering first, the arguments the team has already had. It exposes constraints, so nobody designs into a wall. And it defines the question, so the work can be judged against something other than taste.
Everything else in the document is packaging around those three functions. A brief that reads beautifully but hides a committed co-packer has failed, and a messy single page that names every constraint has succeeded. That is the whole test: a brief is judged by what it makes possible for the partner, not by how resolved it looks to the person who wrote it.
A brief is also not an enquiry. An enquiry says where the project stands and opens a conversation, usually in a few lines through a contact form. The brief is the working document that follows — the one that gets priced, planned and argued with.
Confusing these two is the most common reason a beverage branding brief never gets written.
What you need to know is factual. It concerns your own situation and is already true whether or not you write it down: what exists, what is committed, what it would cost to change, who has a veto, which market comes first, what the liquid can currently support. Not knowing these is not a strategy problem. It is homework, solved by asking your own suppliers and your own team.
What you need to have decided is smaller than founders assume. Only the commitments that constrain the work: the ambition, portfolio intent, price posture, first channel, and what you are not willing to do. Nobody outside the business can make those calls for you.
What you should not have decided is the third bucket, and naming it is a relief for most people who reach this article: positioning, proposition wording, name, identity, hierarchy, flavour navigation, pack architecture. Those are outputs. Arrive with them settled and you are buying execution while paying for judgment.
The practical test. If a question can be answered by looking at your own business, it is known and you should go and find out. If it can only be answered by a commitment, it is decided. If it can only be answered by doing the work, leave it open and say so.
This is the template. Each row is a section of the document: what it answers, what a strong version looks like, and what is genuinely acceptable to leave open.
| Section | What it answers | What good looks like | Acceptable to leave open |
|---|---|---|---|
| Purpose | Why this project, why now | The business trigger, plainly: a listing conversation, a funding round, a range that stopped making sense. Not the creative wish | The ambition beyond this launch |
| Product status | What exists today | Where the liquid actually is — concept, bench samples, approved profile, in production — including what is already committed and hard to reverse | Final specification, supplier confirmations, testing results |
| Opportunity and occasion | Who reaches for this, when, instead of what | The occasion as a moment, not a demographic, plus the alternative it displaces. Instinct labelled as instinct where evidence is missing | Whether that occasion is the right one to own. That is work, not input |
| Competitive set | What you are judged against | What a shopper compares this to in the fridge or the aisle, described by behaviour rather than admired for its design | The analysis. Naming the set is enough |
| Portfolio intent | One product, or a range | Whether variants are planned, how the range might grow, whether the identity must carry navigation from launch | Variant names and launch order |
| Format, channel and market | Where it sells and in what | Format shortlist, first channel, first market, and which of those are committed. Constrains more downstream work than any other section | Later formats, channels and markets, stated as ambition rather than requirement |
| Claims | What you want to say versus what you can say | Two lists, kept apart: claims wanted, and claims that can currently be substantiated | Which claims survive. Substantiation and labelling review sit with specialists |
| Fixed constraints | What cannot move | Committed suppliers, filling or dieline limits, certifications promised, legal positions, a stakeholder with a veto | Nothing. The one section where omission causes real damage |
| Existing assets | What is already made | Name, marks, artwork, photography, copy — with your view of what should survive, be questioned, or be retired | The verdict. A partner will disagree with some of it, and should |
| Scope requested | What you think you are buying | The deliverables you believe you need, framed as a proposal so a partner can say the shape is wrong | All of it. This section is a hypothesis, and should be labelled as one |
| Decisions and approvals | Who can say yes | The named approver, anyone with a veto, and how often you can realistically review | The process, where the company is small enough that it is obvious |
| Commercial envelope and timing | What the project has to fit inside | The shape of the investment, and the reason behind the date: a trade show, a listing window, a production slot | The precise figure, if you truly do not have one. The driver still gets written |
| Definition of done | What has to be true at the end | What you need to be able to do and currently cannot: brief a printer, walk into a buyer meeting, launch a range | The measure of success in market |
Two rules make the template work. Answer plainly what you can. Leave the rest in place, marked open, with a line saying whether it is open because you have not decided or because the project is meant to decide it. Deleting a section you cannot answer is what turns a brief into a wish list.
A beverage branding brief is read twice: once for content, once for signal. The signals are read fast, and most of them are structural rather than written:
None of those signals is about writing quality. A plain document written by one person, with the constraints stated in the first half, reads as better prepared than a designed deck that arrives at the same information last.
The questions are predictable, which means a brief can answer them in advance and keep the first conversation for something more useful.
A partner will ask what the drink is chosen instead of; what happens to the identity when the range grows; which claims are substantiated today rather than hoped for; what is already committed with a supplier, a filler or a co-packer; who else approves; and what you would consider a failure. These are not tests. They are what the work cannot proceed without.
A missing answer is not the problem. An unflagged missing answer is, because the partner then has to choose between asking about everything and assuming something — and an assumption made at brief stage reappears later as rework. A brief that says "the first market is not decided yet" removes a question from the list. A brief that simply leaves the first market out adds one, and usually produces a proposal that has quietly assumed an answer.
The same few recur, across categories and company sizes.
The brief that asks for a logo. It names an output and hides the problem. It appears when a founder wants to feel something is moving. But a mark cannot be judged without a proposition to judge it against, so approval collapses into preference — the most expensive way to make brand decisions.
The brief that arrives with the solution instead of the problem. It specifies the answer: the palette, the reference it should feel like, the layout, the tone. It reads as decisive and behaves as a constraint. Sometimes the answer is right, and the brief has bought hands. More often it encodes an untested assumption, and the first honest question — why this and not something else — has no answer in the document.
The brief that hides constraints. The co-packer is chosen. The certification is promised. The name cannot change because it is on the incorporation documents. A stakeholder will veto anything that is not blue. None of these are shameful, and all are cheap to work with when known, expensive to discover late. Hidden constraints do not disappear; they surface once the work has been shaped around their absence.
The brief written by consensus. Everyone contributed and nobody owns it, so it asks for a distinctive brand and a safe one, a premium position and a competitive price. Contradictions are not a drafting error. They are unresolved arguments, and the project will have them anyway — better on the first call than at artwork.
Sidenote. One more deserves a mention: the brief so guarded it cannot be understood. Confidentiality is legitimate and an NDA solves it. But if nobody can restate the problem after reading the document, no useful proposal can be written against it.
Send it anyway. Incomplete is the normal state of a beverage branding brief, and a partner worth hiring is used to it.
What separates a useful incomplete brief from an unusable one is labelling. Mark each unresolved section with the reason:
That labelling turns a thin brief into a working agenda. It also protects you: an unmarked gap gets filled by an assumption, and assumptions surface as rework.
Two practices help. Write the brief before you feel ready and revise it after the first conversation — the fastest route to a good brief is usually a mediocre brief plus one properly structured discussion. And resist writing around the parts you are unsure of. Vagueness is not neutral; it reads as indecision or concealment, and both get priced in.
If most of the document is open, the project does not start with a brief. It starts with an alignment conversation that reviews what exists, keeps what works and identifies what is genuinely missing. That is a legitimate first step, not a failure of preparation.
A branding brief should reference technical workstreams and never absorb them.
The branding brief covers opportunity and positioning direction, consumer and occasion, proposition, storytelling, naming direction, identity, packaging design, portfolio architecture and launch direction.
Separate briefs, for different partners, cover formulation and bench development, sensory and stability testing, regulatory and labelling compliance, trademark searching and registration, manufacturing, co-packing and distribution. Those belong to laboratories, regulatory consultants, IP specialists, co-packers and distribution partners, who carry different liabilities and ask different questions.
The link between them is the constraints section: state what the technical workstreams have already fixed and what they have not yet answered, so the brand work is specified against reality. What a branding brief must never do is ask a design partner for qualified technical or legal judgment. A brief that asks a studio to confirm a claim, clear a name or approve a label is asking the wrong partner — and any partner who agrees is a risk, not a shortcut.
From input to instruction
Questions
Yes, if each one is labelled with what you are responding to. A reference with a reason attached — the confidence of this, the restraint of that — is useful input. A mood board without reasoning transfers taste rather than direction, and taste is hard to work with because it cannot be argued about productively.
Long enough to contain the constraints, short enough that the approver has read it. A dense page that names every fixed constraint beats a long deck that never mentions the committed filler. Length is a poor proxy for readiness.
One, if the same partner handles both — the pack is where positioning becomes visible, and splitting invites two systems that disagree. Two, if different partners are involved, and then the packaging brief inherits the positioning rather than restating it. What the pack has to resolve is covered in what makes beverage packaging retail-ready.
Share the envelope and the reason behind it. Without it, the proposal you receive is a guess at what you can carry, and the fit conversation gets postponed. Withholding it rarely produces a better price; it usually produces a scope that has to be renegotiated.
Yes, and a well-structured brief makes comparison honest because the proposals answer the same question. Say that you are approaching more than one and what you will decide on. A vague brief produces proposals about different problems, and you end up choosing on presentation.
The occasion lens
Who may buy matters. What they are choosing now, where, with whom and instead of what gives the brand something concrete to solve.
Why occasion of consumption matters →