Writing an event visual identity brief
A designer is waiting for direction, and the committee has strong views but nothing written down.
The short answer
A visual identity brief fixes the event's names, languages, approved logos, tone, list of items to be designed and the people who approve. It does not describe fonts and colours first.
Without it, each supplier invents their own version of the event's look, and corrections arrive one item at a time.
What the brief must settle
- The exact event name, short name and tagline, in each language you will use, with correct spelling.
- The organiser, co-organiser and partner names as they should appear, and who confirms them.
- Existing brand assets: logo files, colour and typography rules, and who supplied them.
- Tone: formal association, corporate, youthful, or a mix, with two or three examples you like.
- Applications: the list of items the identity must work on, such as backdrop, signage, lanyards, programme booklet and slides.
Languages and names
Decide which languages appear on which items before design starts, because text length changes layouts. Use only the names your organisation has approved, including any official Chinese or Malay rendering it already uses.
Do not let the designer or a translator invent a translated name for an organisation or venue. Ask the owner.
Approvals and rounds
- Name one approver for the identity and one backup, with authority to say yes.
- State how many rounds of feedback each stage includes, and who consolidates comments.
- Agree how files are named and versioned so the approved version is obvious.
- Record the sign-off date and version before anything goes to print or production.
Trademark and usage questions
If you are unsure whether an event name, logo or phrase can be used, or who owns existing artwork, take it to your legal adviser or the rights owner. A brief should list the question and who is asked, not answer it.
How the brief connects to the rest
The applications list becomes your collateral inventory, and partner order is settled in the co-branding hierarchy. The trilingual signage planner turns the language decisions into a sign plan.
Worked example · Fictional example
A first identity brief for an annual forum
Fictional organisation and figures, for illustration only.
Persatuan Fiktif Profesional Teknologi is holding its annual forum for about 300 members. The secretariat's earlier brief to the designer said 'modern and professional' and nothing more.
The revised brief lists the English and Malay event names, notes that the Chinese name is still to be confirmed by the council, attaches the association's logo files, names the president's office as approver, and lists eleven items to be designed. The designer's first round arrives with the right names and one question about the Chinese title.
Use this yourself
Visual identity brief template
Copy into a document and send to your designer or agency with the logo files attached.
- Event name, short name and tagline, per language (spelling confirmed by):
- Organiser, co-organiser and partner names as they must appear:
- Logo files provided, version and source:
- Existing brand rules (colours, typefaces) or 'none, designer to propose':
- Tone and two or three examples you like and dislike:
- Languages on each item:
- Applications list (see collateral inventory):
- Approver, backup and authority to approve:
- Feedback rounds per stage and who consolidates comments:
- File naming and versioning rule:
- Questions on names, logos or artwork ownership sent to legal or the rights owner (who, date):
- Key dates: first draft, approved identity, print or production start:
Handle it in-house, or bring in help?
Your team can usually handle this when
- Your organisation already has brand rules and a designer who knows them.
- A single approver can answer quickly.
- The event is small and needs few printed items.
Outside planning help earns its fee when
- Several partners, committees or regions each want a say in the look.
- Languages, partner order or name spelling are still disputed.
- Nobody on the team has time to consolidate feedback and keep versions straight.
Want the brief written and agreed with your committee?
A conference project lead can draft the brief with you, collect the confirmed names and logo files, run the approval rounds and keep the version record. Design work and any legal questions on names or artwork remain with your designer and legal adviser.
Questions organisers ask
Should the brief include colours and fonts?
Include them if your organisation already has them. If not, say so and ask the designer to propose options, with the approver choosing.
How many logo files should we send?
Send the master files, in the versions the owner approves, with a note of which to use on light and dark backgrounds. Avoid sending screenshots.
Who owns the artwork the designer makes?
That depends on the agreement with the designer. Put the question to your legal adviser before the work starts.
Can we use the same identity next year?
Often yes, but record what changes, such as the year and venue, and keep a dated master file.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.