Start with the job the identity needs to do
A visual identity brief is a working document, not a test of whether you know design terminology. Its purpose is to give a designer enough context to make informed choices and enough room to propose ideas you may not have considered. Before listing colors or logos you like, explain what your business offers, who it serves, and why you are commissioning the work now.
Describe the practical change you want the identity to support. Perhaps your packaging looks unrelated across products, your social posts are hard to recognize, or a new service needs to fit alongside an established name. Keep the goal specific without promising a business outcome: “Create a consistent look for our market stall, labels, and online shop” is more useful than “Make us stand out everywhere.” If you already have a logo or other assets, say what works, what does not, and what must remain.
Describe the audience and the context
Write about the people who need to understand and use your brand, rather than relying only on broad labels such as “everyone” or “young professionals.” What are they trying to choose, compare, buy, or learn? Where are they likely to encounter you first? A neighborhood bakery may need to be legible from across a street, recognizable on a small pastry label, and easy to identify in a crowded photo feed. Those situations give a designer more to work with than a list of demographic traits alone.
Include a short description of your position in the market. Name a few alternatives customers might consider and explain how your offer differs, without insisting that the identity imitate or oppose theirs. You can also describe the impression you want to make in ordinary language: careful but approachable, playful but not childish, or established without looking formal. If two qualities seem to pull in different directions, include both. That tension can lead to a better design conversation.
List the places the identity must work
A logo is only one part of a visual identity. List the items you expect to use soon, such as a website header, social profile image, business card, product label, shop sign, presentation template, or printed flyer. Note any sizes, materials, or production methods you already know. A mark intended for a tiny label may need a simpler version than one used on a large sign; a single-color stamp has different demands from a full-color digital graphic.
Separate essential applications from possible future uses. This helps the designer judge what to prioritize and can prevent a small project from quietly becoming a request for every conceivable asset. Ask which final files, variations, and basic usage guidance are included in the proposed scope. If photography, illustration, packaging layouts, or copywriting are needed, say so explicitly rather than assuming they are part of “the branding.”
Share references without prescribing the answer
Examples can clarify taste, but a folder of images without comments leaves too much open to interpretation. For each reference, explain what you respond to: the restrained color palette, generous spacing, expressive lettering, clear hierarchy, or way a system adapts across formats. Add examples you dislike when you can explain why. “This script is difficult to read at small sizes” is more actionable than “not my style.”
Be clear about fixed requirements, such as a business name, an existing color that must stay, or a partner logo that must appear on materials. Label everything else as a preference or an idea to explore. If you propose a symbol, explain the meaning you hope it conveys rather than demanding that exact symbol. For example, “We want to suggest care and hand-making, but not necessarily with a hand icon” gives the designer a problem to solve.
Make decisions and feedback easier
End the brief with the practical details: your expected budget range, desired schedule, key milestones, and who will approve the work. Identify one person who can consolidate feedback if several people have a say. Tell the designer whether there are upcoming deadlines tied to a launch, print order, or event, and distinguish firm dates from preferences. A schedule is more useful when it includes time for your team to review and respond.
Before sending the brief, check it for contradictions and unanswered questions. A simple example statement might be: “We sell small-batch pantry goods to local shoppers. We need a flexible identity for jar labels, a market banner, and our online shop. It should feel warm and orderly, remain readable on narrow labels, and avoid looking rustic.” That is enough to begin a conversation, not a demand for a predetermined design. Invite the designer to ask questions and challenge assumptions; a good brief gives the project direction while leaving space for craft.
