Free creative brief generator for a stronger first draft.

Fallowfield Ferments brews kombucha in a converted dairy unit and sells four flavours through delis and farm shops. The labels date from the founder's spreadsheet era and look homemade beside the drinks they sit next to. The inputs are an objective of getting listed in shops that currently decline on presentation, an audience of deli buyers, a deliverable of four labels plus a shelf talker, and constraints of an existing bottle, six weeks and one freelance designer.

The brief that comes out reads roughly like this. Objective: remove presentation as a reason for a buyer to decline the range, judged by buyers agreeing to a tasting rather than by internal preference. Audience: deli buyers who give about one shelf to soft drinks and choose on how a product will sit beside what they already carry; secondary, the shopper who holds the bottle for four seconds. Single message: a proper ferment made in small batches, not a flavoured soft drink. Deliverables: four label artworks front and back, one A6 shelf talker, print ready to the existing printer's template. Mandatories: current 330ml bottle and crown cap, the printer's bleed and safe area, ingredient panel, allergen line, best before block and recycling mark at legible size. Tone: plain and confident, not folksy, not wellness. Constraints: four colour flexo, no foil, no spot varnish, unit cost cannot rise. Approval: the founder signs off concepts, production checks the panel, two revision rounds are in budget. Timeline: concepts at two weeks, chosen route at three, print ready files at six.

It holds up because each line closes an argument that would otherwise turn up at round two. Fixing the bottle and cap rules out the concept that reshapes the pack. The flexo line rules out a foil route the designer would otherwise be right to explore. Naming the buyer as the primary audience settles the recurring disagreement about whether a label speaks to a stockist or a shopper, and the single message settles whether the drink is being positioned as a health product.

Each reference in the real document carries a reason rather than only a picture, which lets a designer honour it without copying it. Saying you like a farmhouse beer label for its single strong colour, and not for being a beer label, gives permission to arrive somewhere that looks nothing like it and still meets the brief.

The weaker version, and the one most often sent, runs to three sentences: we need new labels for our four flavours, something fresh and modern that pops on shelf, in line with our brand. Fresh, modern and pops are preferences with no test attached, so no concept can fail them and none can pass. With the flexo constraint missing, the first round may be unprintable. With no approval line, the founder's partner sees round two and reopens the flavour naming. Six weeks later there are three near identical routes, an unresolved argument about what the drink is, and a designer being blamed for a decision the business never made.

Do not write a brief when the decision it depends on has not been made. If the business has not settled who the product is for or what it costs, a brief written now records that confusion in a form that looks authoritative, and the designer resolves it by guessing. Positioning first, brief second.

Skip it while there is no single approver. A document cannot fix a committee that has not agreed. If four people each hold a veto and none will sign, the work gets judged four ways whatever the brief says. The honest move is to spend an hour getting one name against the objective, then write. Circulating a draft brief for comment before that mostly collects more vetoes.

Skip it for work small enough that the brief costs more than the job: one social tile in an existing template, a resize, a colour swap. Ten lines of specification for twenty minutes of production slows the person down and signals you do not trust them. The format, the deadline and where the files live is the whole brief there, and it fits in a message.

And do not use a brief as a contract. Fee, scope, ownership of the artwork, licensing for any fonts or photography, and what happens when the deadline moves belong in the engagement terms. Mixing them in blurs both documents: the designer skims commercial paragraphs looking for the objective, and the objective gets read as a warranty. Keep the brief about the work and let the agreement carry the money.

The convention is short because the brief has to stay readable at round two, when someone opens it to settle a disagreement. Objective, audience, single message and mandatories belong on the first page, in that order. Background, market context and the history of the previous attempt go last, or into an appendix, because they are the parts most likely to be skimmed and least likely to change what gets made.

Write the objective as one sentence with a test in it. If you cannot say how you would know the work succeeded, you have written an aspiration. Keep the mandatories as a plain list rather than prose: formats, sizes, legal lines, colour restrictions, technical delivery. Lists survive being scanned by a person under time pressure, whereas a paragraph containing four constraints reliably loses one of them. Version and date the document, because a brief revised in conversation and never rewritten becomes two briefs, and the one in circulation is usually the wrong one when the argument happens.

A designer reads it for constraints and for room. The first pass hunts for anything that rules out a direction: fixed dimensions, existing assets, a colour that cannot be used, a deadline that makes one approach impossible. The second pass looks for where the judgement has been left to them, because that is what they were engaged for. A brief that specifies everything gets an execution, and a brief that specifies nothing gets a lottery.

The project manager reads a different document: deliverable list, formats, dates, revision rounds. The schedule is built from those, so anything vague there becomes a scope argument later. The approver reads a third one, checking whether their concern appears anywhere. If it does not, they will raise it at the first review instead, which is the expensive moment. Getting each named stakeholder to point at the line that represents their interest before work starts is the cheapest hour in the project.

A creative brief is about the message and the idea: what the audience should think or feel, what the single proposition is, what tone carries it. A design brief goes further into the artefact: formats, sizes, colour systems, typography, file specification, print or platform requirements, accessibility standards where they apply. Campaign work usually needs the first and inherits the second from an existing system. A packaging job, a website or an identity needs the specification spelled out, because there is no system yet to inherit from.

Both differ again from a project brief, which is about resourcing and sequence, and from a scope of work, which is commercial. Small teams often merge all of these into one document, and that works as long as somebody has checked that the objective is still findable in it. Once the merged document passes two pages, the usual fix is to split the specification out as an appendix and keep the thinking on the front page.

Send the brief, then talk it through, in that order. A designer reading it cold will spot the contradictions you cannot see, because you know what you meant. Ask them to say the objective back in their own words. If the version that comes back differs from what you intended, the brief is wrong, and that is the cheapest moment to fix it.

Expect to revise once straight after that conversation, then freeze it. A brief that keeps being edited quietly through the project stops being a shared reference and becomes a record of whoever spoke last. If something genuinely changes, change it openly, date it, and say what it costs in time or rounds, because a mid project change absorbed silently is what turns two revision rounds into five.

When the work comes back, review against the brief rather than against taste. The useful question is whether this meets the objective for that audience under those constraints. Whether you personally like it is a separate question, worth asking second.