In short
A brand guideline is used when it answers the specific questions people have while working — what colour is this, how much space goes here, what do we call this thing — and when it lives where the work happens. Document the reasoning behind decisions, not only the rules, because reasoning transfers to situations the document did not anticipate.
Why most go unread
They are written as a definitive artefact rather than a working reference. Fifty pages, delivered as a PDF, exhaustive on the logo and silent on the situations that actually arise.
The result is predictable: someone needs a hex code, cannot find the file, uses the one from the last deck, and the brand drifts.
A guideline is used when it is findable, searchable, and answers the question being asked at that moment. That usually means a web page or a shared workspace, not a PDF in an email from eighteen months ago.
What people actually need
Colour values, in every format they might need — hex, RGB, and print equivalents if print is relevant. With rules about which colours are for what, not merely a palette.
Typefaces, with the licence, where to obtain them, and the fallbacks. Include what to do when the brand face is unavailable, because it will be — in an email client, in a customer's template, on someone's laptop.
Logo files, in the formats needed, with the clear space rule and the minimum size. And the versions: horizontal, stacked, mark only, single colour.
Spacing and layout principles, which are what makes materials look consistent even when the elements vary.
Voice, with examples rather than adjectives. "Confident but not arrogant" tells nobody anything; a before-and-after pair of sentences does.
Photography and imagery direction, including what to avoid.
Document reasoning, not only rules
The difference between a guideline that holds up and one that gets ignored.
A rule covers the situation it anticipated. Reasoning covers the ones it did not.
"Use the accent colour only for interactive elements" is a rule. Adding because it teaches people that this colour means something is clickable, and using it decoratively breaks that means someone facing an unanticipated case can reason to the right answer instead of guessing.
This matters most for the people who were not in the room when the brand was made, which after a year is most people.
Show wrong as well as right
Examples of misuse are more instructive than examples of correct use, because they name the mistakes people actually make.
The logo stretched. The accent colour used as a background. Text over a busy image. The typeface substituted. Two competing calls to action.
Each one is a mistake someone will make. Showing it, with a brief note on why it fails, prevents it far more effectively than a correct example alone.
What belongs in code instead of a document
The most useful shift: for anything digital, the guideline should be implemented, not described.
Colours, spacing, type scale, component styles — these belong in design tokens and a component library, where they are used by default rather than looked up and applied manually.
A developer should not need to read a document to get the right blue. They should use the token, and the token should be right. A designer should not measure spacing; the scale should be in the file.
When that exists, the written guideline shrinks to what code cannot express: voice, photography, the reasoning, and the situations requiring judgement. That is a much shorter and more useful document.
Keeping it current
A guideline that is out of date is worse than none, because it produces confident mistakes.
Version it and date it, so people can tell whether they are looking at the current one.
Give it an owner. Unowned documents rot.
Review it when the brand is used somewhere new — a new product surface, a new market, a new format. Those are the moments the gaps appear.
Record decisions as they are made. Most brand drift happens through small choices nobody wrote down, then contradicted six months later.
Sizing it to the organisation
A two-person studio does not need what a multinational needs, and building the large version for a small team produces something nobody maintains.
Small team: a single page with colours, type, logo files, spacing, and a few voice examples. Genuinely enough.
Growing team: add component documentation, misuse examples, and the reasoning behind the main decisions.
Large organisation or agency partners: add governance — who approves exceptions, how to request assets, what is fixed and what is flexible.
The question that sizes it correctly: who will use this, and what will they be trying to do? Write for those situations and stop.
If you are handing a brand to a team that will apply it without you, book a call — what to document is usually a shorter list than people expect.
Common questions
What should a brand guideline include?
Colour values in every format needed with rules about what each is for, typefaces with licences and fallbacks, logo files with clear space and minimum size, spacing and layout principles, voice with example sentences rather than adjectives, and imagery direction including what to avoid.
Why do brand guidelines go unread?
Because they are written as a definitive artefact rather than a working reference — usually a long PDF that is exhaustive about the logo and silent on the situations people actually face. A guideline gets used when it is findable and searchable at the moment the question arises.
Should brand guidelines explain the reasoning behind rules?
Yes. A rule only covers the situation it anticipated; reasoning covers the ones it did not. Saying the accent colour is for interactive elements because that teaches people what is clickable lets someone facing an unanticipated case reason to the right answer rather than guess.
What belongs in code rather than in a brand document?
Anything digital and mechanical — colours, spacing, type scale, component styles — which belong in design tokens and a component library where they apply by default. That shrinks the written guideline to what code cannot express: voice, photography, reasoning, and situations needing judgement.
How long should a brand guideline be?
As long as the situations it needs to cover. A two-person studio needs one page with colours, type, logo files, spacing and a few voice examples. Larger organisations need component documentation, misuse examples and governance. Building the large version for a small team produces something nobody maintains.
