Brand Design Brief Checklist: What to Ask the Client

A logo brief that skips positioning, usage and file formats produces revision after revision. Here is what to ask before any concept work starts.

Why a thin brief produces endless revisions

"Something modern and clean, maybe blue" is not a brief. It is a placeholder for a brief, and every round of "not quite that" that follows is the client filling in, one rejected concept at a time, the information a real brief would have collected up front.

Logo work is unusually unforgiving of a thin brief. A homepage built against placeholder copy can absorb the real copy later without much rework — the layout barely changes shape. A concept built without knowing the mark has to work as a single-color embroidery patch, or that a competitor already owns the obvious color, is often not a revision away from correct. It's a restart. The fix isn't a longer conversation about taste; it's a specific set of questions, asked before the first sketch, that catches the constraints taste alone won't surface.

This checklist assumes the shared basics — business goals, target audience at the level of "who buys from you" — are already covered somewhere. If they aren't, run the client onboarding questionnaire for web design first; what follows here goes one layer deeper, into the questions specific to a mark rather than a website. Building an app rather than a site instead? The mobile app project intake checklist covers the store accounts and technical items a logo brief doesn't touch.

The brief, group by group

Seven groups of questions, each with a one-line reason it matters. Not every project needs every row — a solo consultant refreshing a personal logo can skip the trademark question; a national franchise cannot skip it.

Business and positioning

Question	Why it matters
Where does the business sit on price and quality — budget, mid-market, or premium?	A mark that reads premium over a budget price point creates a mismatch the client will feel but can't name.
Does the name need explaining, or does it need to be pronounced correctly on sight?	An invented or foreign-sounding name may need a phonetic hint or a supporting icon a plain wordmark can't give it.
Does this mark need to work as a standalone icon — app icon, social avatar, favicon — separate from the full logo?	A wordmark that only makes sense at full width forces an awkward crop the same week the site launches.
What single association should someone form in the first second of seeing it?	Trustworthy, fast, handmade, cutting-edge — each points to different shapes and colors; this is the one-sentence brief everything else supports.

Audience

Question	Why it matters
Where will people most often encounter this mark first — a phone screen, a storefront, a business card, a highway sign?	A detail that reads clearly on a card can vanish at billboard distance or app-icon size; design for the common encounter, not the flattering one.
Does your industry have a visual convention your audience expects — navy and serif for law, rounded and bright for children's brands?	Knowing it lets you meet it deliberately or break it deliberately, instead of by accident.
Will the same mark travel across very different contexts — a formal invoice and a casual social post?	A logo that only works in one register forces a second version later; better to know that up front.

Personality and values

Question	Why it matters
Pick three words for how the mark should feel.	"Playful," "precise," and "warm" each rule out entire visual directions before anything is drawn — the fastest filter in the whole brief.
Any words, colors, or shapes that would feel wrong for this brand?	A strong negative is often clearer than a positive preference, and clients volunteer it readily once asked.
Name a brand outside your own industry whose personality feels close to what you want.	An outside reference (a bank that wants to feel like a favorite coffee shop) says more than a paragraph of adjectives.

Competitors and references

Question	Why it matters
Who are your two or three direct competitors, and what do you think of their logos?	Shows you the visual field you're either fitting into or deliberately standing out from — designing in ignorance of it risks landing on something a competitor already owns.
Is there a logo you admire, in any industry? What specifically do you like about it?	Push past "I like that one" to the specific element — the weight, the negative space, the color pairing — because the whole logo is rarely what's actually wanted.
Is there a logo, in your industry or not, that you actively dislike? Why?	As useful as the positive reference, and clients are often more articulate about what repels them than what attracts them.

Usage and formats

Question	Why it matters
Where will this mark physically appear — packaging, a vehicle, signage, embroidery, a favicon, a social avatar?	Each context has its own failure mode a screen mockup won't reveal: embroidery loses detail, vehicle wraps need to read at speed, favicons lose everything but the boldest shape.
Does it need a horizontal lockup, a stacked lockup, and an icon-only version?	A scoping question, not a design one — three lockups is a larger job than one, and the client should know that before work starts.
Does it need to work in a single color and in reversed (light-on-dark) form?	A mark that only works in full color fails the moment it needs an invoice, a stamp, or a dark-mode app icon.
What is the smallest size it needs to stay legible at?	Detail that reads beautifully at business-card size can turn into a smudge at favicon size — know the floor before designing toward it.

Constraints and existing assets

Question	Why it matters
Is there anything about the current logo — a shape, a color, an icon — that the business is known for and shouldn't lose?	Years of recognition attached to a particular blue is an asset even when everything else is being replaced; losing it by accident is a real cost.
Has a trademark search been done, or does one need to happen before final designs are shown?	Cheaper to raise before concepts are picked than to fall for a mark that conflicts with an existing registration.
Is there an existing tagline that needs to be incorporated into the lockup, or kept separate?	Changes whether you're designing one component or two that have to work together at every size.

Deliverables and timeline

Question	Why it matters
How many initial directions, and how many revision rounds, are included?	The most common source of scope disputes on logo projects — agree the number before the first concept, not after the third "just one more tweak."
What final file formats are needed — vector source, print-ready PDF, transparent PNG, a favicon?	Each is a different production step; finding out a print-ready CMYK file is needed after delivering only web PNGs means redoing the export.
Who has final sign-off?	Settle this once, at the start — a second decision-maker appearing after approval is the most expensive kind of surprise.
Is there a hard delivery date, and what's driving it?	A rebrand tied to a trade show or funding announcement has a real deadline; one without a driving event has more room to negotiate the revision count above.

Collecting the actual materials

Answers to the questions above are half the brief. The other half is physical material, and it is worth asking for by name rather than a general "send anything relevant":

The existing logo file, in whatever format the client has it — even a low-resolution export from an old business card. Not for reuse; it's the fastest way to see what visual equity exists to keep or deliberately discard.
An existing brand guide, if one exists, as a PDF. Rare below a certain company size, but it answers several constraint questions above without a back-and-forth.
Photos of the mark in its current physical contexts — signage, a vehicle, packaging — as ordinary phone photos. These show real-world failure modes a digital file alone won't.
Screenshots or links for the competitor and reference logos named above. Don't rely on memory of what a competitor's site looks like; pull it up and look again.
A moodboard of likes and dislikes — a shared Pinterest board or a handful of saved screenshots. Ten images with one line each ("like the weight, not the color") reveal more usable taste than a paragraph of adjectives.

Running it: call versus written brief, before versus after kickoff

Split the questions the way you'd split any client request: what benefits from a conversation, and what just needs looking up. Positioning, personality words, and competitor opinions are shorter and vaguer in writing than out loud — "modern, but not corporate" only becomes useful once someone asks "modern like what, specifically?" A written form suits everything else: usage, constraints, deliverables and timeline are factual enough that the client answers them accurately without a call, often more accurately, since they can check a file instead of memory.

Unlike a website project, where placeholder text is a normal way to start before every asset exists, a logo brief mostly resists a partial start. A concept sketched against an incomplete brief usually isn't a revision away from right once the missing piece — a trademark conflict, a required embroidery version — surfaces; it's a restart. Treat the seven groups above as a before-kickoff block, in full, even at the cost of a short delay. The materials above are more forgiving: one more competitor screenshot can arrive a day in without derailing the first round of concepts.

Where BriefGate fits

Turning this checklist into an actual request, instead of a document nobody reads before answering three of nine questions, is a structuring problem more than a design one. BriefGate lets an agent — or you, from the dashboard — declare the seven groups above as typed items: image for the existing logo file, color_list for colors to avoid or preserve, file for a brand guide, structured for grouped answers like usage constraints, all covered in item types. The client gets one branded portal instead of an email with nine questions buried in the body, and if this brief is one piece of a larger website build, it sits alongside the rest of the website project intake checklist in the same request rather than a separate thread.