Organised by Question
What people look up, not what a designer wants to explain.
Most brand guidelines are eighty pages, beautifully produced, and consulted twice. Brand guidelines services should produce something different: a document organised around the questions people actually have when they are making something, with the assets attached where they are needed.
Guidelines fail when they describe the identity instead of answering questions about using it.
What people look up, not what a designer wants to explain.
Files where the rule is, not in a separate archive nobody can find.
Including what not to do, which is the part people check.
Social avatars, email signatures, a logo on a photograph.
Length is not thoroughness.
Brand guidelines are judged on one thing: whether somebody who has never spoken to the designer can produce correct work from them alone. Every check below is a test of that, because a document that only works when its author is in the room has not solved the problem it was commissioned to solve.
The cold-start test is the only check that reliably predicts whether a guidelines document survives contact with a real organisation. Everything else can pass while the document still fails, because the author knows what they meant.
Four things, and none requires a page about brand values.
Discuss Your Guidelines →For this background, at this size, in this format.
The exact value, for screen or print.
Which face, at what size, and what if it is unavailable.
The edge case they are about to attempt.
The rules that are needed, with the files attached.
The identity itself is covered by brand identity. The identity being documented is brand identity; the digital component layer that enforces it is design systems. The identity being documented is brand identity; the digital component layer that enforces it is design systems.
Find out what people get wrong, then write the document that prevents it.
What is currently being done wrong, and why.
What people need to look up.
Organised by question rather than by element.
Assets where the rule is.
Give it to someone and watch them find something.
A guidelines document should be exactly as long as the number of people who will apply it without supervision. Writing a hundred-page system for a three-person company wastes money; writing an eight-page summary for a franchise network guarantees drift. These are the situations that change the answer.
The moment brand execution stops passing through one person is the moment guidelines start paying for themselves. Before that hire, consistency is maintained by memory. After it, consistency is maintained by documentation or not at all — and the cost of correcting work is higher than the cost of specifying it.
Every agency will otherwise interpret the brand slightly differently, and the differences compound. This is the case where misuse examples earn their place, because the mistakes are made by people acting in good faith who simply were not told. Written rules cost less than the review cycles they replace.
The hardest case, because the people applying the brand do not report to the business that owns it. The document has to anticipate local adaptation and say explicitly what may be changed and what may not — a system that forbids everything gets ignored, and a system that permits everything stops being a brand.
Where disclaimers, mandatory statements and approval workflows are part of every asset, guidelines have to carry them or every piece of work becomes a compliance negotiation. This affects layout as much as wording, since space for required text has to be designed in rather than found later.
The window where guidelines matter most and get written least. A new identity without written rules reverts toward the old one within a year, because the old one is what everyone still has muscle memory for. Guidelines commissioned at the same time as the identity cost less than reconstructing the reasoning later.
Guidelines are reference documents, and reference documents are used by search rather than by reading.
Nobody reads it, which is fine — reference documents are not meant to be read. The problem is that length makes finding things harder, and finding things is the entire purpose.
Someone about to put the logo on a dark photograph has one question. If the answer takes four minutes to locate, they will guess instead.
A shorter document organised by question gets used. A long one organised by element gets opened once, admired, and never referenced again.
Because misuse examples are what people actually check. Someone about to stretch a logo or recolour it looks for permission, and a clear prohibition is faster to interpret than an inferred rule.
It also makes the rules concrete. "Maintain the proportions" is abstract; a picture of a stretched logo with a line through it is not.
The examples should come from real misuse where possible — the things your organisation has actually done wrong, which are the things it will do again.
A style guide documents appearance: the logo, the palette, the typefaces, the spacing. It answers what the brand looks like. It is necessary and it is not sufficient, because appearance is the output of decisions rather than the decisions themselves.
A brand system documents the reasoning as well: why the palette is weighted the way it is, what the secondary colours are for, which typeface carries which job, and what to do when a situation arises that the document did not anticipate. That last part is what separates a system from a catalogue. No document can enumerate every case, so a good one teaches the logic well enough that a competent person can extend it correctly.
The practical difference shows up the first time somebody needs an asset nobody planned for. With a style guide they either guess or wait for approval. With a system they can reason from stated principles and produce something defensible. For an organisation of any size, that difference is most of the document’s value.
Guidelines fail for reasons that have almost nothing to do with their content. The most common is findability: the document exists as a PDF attached to an email from eighteen months ago, and the people who need it do not know it exists. A document that is not where the work happens will not be consulted.
The second is length. A hundred-page document sends the message that using the brand correctly is a research project, so people skim the first ten pages and improvise the rest. The fix is structure rather than compression — the rules somebody needs weekly at the front, the rules somebody needs annually further back, and a genuine index.
The third is the absence of an exception route. Every real organisation eventually faces a case the rules do not cover. If the document does not say who decides, the requester either stalls or proceeds without asking, and proceeding without asking is how brands drift. Naming the decision-maker costs one line and prevents most of the drift.
The fourth is that the document was never tested. Handing it to someone outside the project and asking them to build an asset exposes ambiguity that its author cannot see, because the author is reading their own intention into their own words.
Guidelines should carry the rules that apply everywhere: the mark, its clear space and minimum sizes, the palette with accessible pairings, the type system with fallbacks, photography and illustration direction, and the misuse cases. These are stable, and they are what people need when producing anything at all.
What does not belong is anything that changes faster than the document can be reissued. Campaign layouts, seasonal palettes and channel-specific templates date quickly, and putting them in the core document means the whole document reads as stale within a year. Those live alongside it as templates that reference the rules rather than restating them.
Verbal identity is the common boundary question. Tone rules and vocabulary can live in the same document or in separate brand voice guidance, and either works — provided one of them exists. What does not work is a visual document with a paragraph about tone bolted on the end, which is too thin to apply and too prominent to ignore.







Brand guidelines services produce the reference document for using a brand — logo usage, colour, typography, imagery and applications — organised around the questions people have when making something.
Short enough that finding an answer takes seconds. Length is not thoroughness — a long document organised by element gets admired once and never referenced.
Which logo file for this background, the exact colour value, which typeface at what size, and whether a specific thing they are about to do is allowed.
Yes — they are the section people check. Someone about to stretch or recolour a logo is looking for permission, and a clear prohibition is faster than an inferred rule.
It needs its own section, because avatars and feed content behave differently from print — see social media branding.
As long as the number of people applying them unsupervised, and no longer. A small team executing its own work may need twelve to twenty pages covering the mark, colour, type and a handful of misuse cases. A multi-location network needs considerably more, because it has to anticipate situations nobody will be present to advise on. Length driven by thoroughness is useful; length driven by wanting the document to feel substantial is what causes it to go unread.
They need to cover the rules that apply to both — the mark, palette, type and accessible contrast pairings — and they need to state where screen requirements differ, which they frequently do. Minimum sizes are not the same, and colours that pass in print may fail contrast on screen. What they should not attempt is to specify the website itself. Component behaviour, states and responsive rules belong in a design system, which is a different artefact maintained on a different cycle.
You do, along with the source files, and that should be stated in writing rather than assumed. The more useful question is who maintains them. A document with no named owner is out of date within a year, because brands accumulate legitimate exceptions and nobody has the authority to fold them back in. Naming a maintainer at handover is the single cheapest thing that keeps the document alive.
On events rather than on a calendar. A new sub-brand, a new primary channel, a significant addition to the product line, or an accumulation of approved exceptions are all reasons to revise. Scheduled annual reviews tend to produce cosmetic changes that create version confusion without improving anything. If nothing has changed, the document does not need a new edition.
Yes, and over-restriction fails in a specific way: people stop consulting the document rather than complying with it. A system that forbids everything not explicitly permitted cannot survive a real marketing calendar, so the team quietly works around it and the brand drifts anyway. The more durable approach is to be strict about the small number of things that genuinely carry recognition — the mark, the primary colour, the typeface — and deliberately permissive elsewhere.
Still deciding if brand guidelines services is right for you?
Talk to UsSomeone needs to put the logo on a dark photograph for a presentation due in twenty minutes. They open the brand guidelines to check which version to use.
The document is eighty pages. Logo usage begins on page nine and continues, through clear space, minimum sizes and co-branding, to page twenty-three. The answer about photographic backgrounds is in there somewhere.
They scroll for a minute, then use whichever file is already on their desktop. The rule existed, it was correct, and it was harder to find than to ignore.
Send us your current guidelines. We will tell you what someone can find in them and what they will guess at.
