Brand guidelines are a documented set of rules governing how a brand's visual and verbal identity is applied across every touchpoint — covering logo usage, colour specifications, typography, imagery direction, tone of voice, and application rules. Research from Lucidpress found that consistent brand presentation across all platforms can increase revenue by up to 23%.
Version 1.0 — Published April 2026
Most brand guidelines are dead on arrival
Here's what typically happens. An agency delivers a 40-page PDF. It specifies logo clear space, lists Pantone codes, and includes a few "do's and don'ts" pages. Everyone nods. The PDF goes into a shared drive. Six months later, your new freelancer uses the wrong shade of blue because they never found the document. Your social media posts use four different fonts because nobody checked.
The document was technically complete. It was practically useless.
Good brand guidelines aren't a reference document. They're an operating system. The difference matters — and it starts with what you put in them.
The non-negotiable sections
Every brand guidelines document needs these. Skip any of them and you're shipping an incomplete manual.
Logo usage rules. Your primary logo, secondary marks, monochrome variants, and favicon versions. Minimum sizes. Clear space requirements — defined in a measurable unit, not "roughly this much." Backgrounds it works on. Backgrounds it doesn't. A "don't" gallery showing common misuses: stretching, recolouring, placing on clashing backgrounds, adding drop shadows. Be specific. Designers will test every boundary you leave undefined.
Colour system. Primary and secondary palettes with exact specifications: HEX for digital, RGB for screen, CMYK for print, Pantone for physical production. Accessibility matters here — document contrast ratios for text-on-background combinations. The Web Content Accessibility Guidelines (WCAG) require a minimum contrast ratio of 4.5:1 for standard text. If your brand blue fails that test against white, your guidelines need to say so.
Typography. Primary and secondary typefaces. Where each is used — headings, body text, captions, UI elements. Fallback fonts for environments where your primary typeface isn't available. Size scales, line heights, and letter-spacing values. "Use Helvetica for headings" is a suggestion. "Helvetica Neue Bold, 32px, line-height 1.2, letter-spacing -0.02em" is a guideline.
Imagery and photography direction. Not stock photo links — a description of your visual language. Are your images documentary or staged? Warm or cool? A few photographic examples with annotations explaining what makes them on-brand beats a vague "authentic and modern" description every time.
Tone of voice. How your brand sounds in writing. This should include voice attributes (e.g., "direct but not blunt, warm but not casual"), examples of how each attribute plays out in real copy, and before-and-after rewrites. The best voice guides also specify how tone shifts across contexts — a support email shouldn't read like a landing page headline.
What separates good from great
The sections above are table stakes. To build a system that actually works under pressure — across teams, freelancers, platforms, and time — you need more. A Marq (formerly Lucidpress) study found that 60% of organisations say brand consistency is a challenge, with teams frequently deviating from guidelines due to access or clarity issues.
| Element | Basic guidelines | Production-grade system |
|---|---|---|
| Colours | HEX codes in a PDF | HEX + RGB + CMYK + Pantone + contrast ratios + CSS tokens |
| Typography | "Use Inter for headings" | Full scale: sizes, weights, line-heights, fallbacks, tokens |
| Voice | Not included | Attributes + examples + do/don't + context shifts |
| Spacing | Not included | 4px base scale with named tokens |
| Components | Not included | Button, card, form patterns documented |
| Format | Static PDF | Living docs (Notion/Zeroheight/website) |
| Design tokens | Not included | Code-ready CSS custom properties |
Design tokens. These are the code-ready values that translate your visual identity into something developers can actually implement. Colour variables, spacing scales, border radii, shadow values, typography tokens — all named, documented, and structured for CSS or design tool consumption. Without tokens, every developer interprets the brand guide slightly differently. With them, your brand renders consistently whether it's built in React, Figma, or Webflow. This is one of the outputs from The Brand Protocol's System stage — and it's the layer most traditional brand guidelines completely miss.
Layout and spacing systems. A grid isn't enough. Document your spacing scale (4px, 8px, 16px, 24px, 32px, etc.), your content width constraints, your approach to whitespace. These rules prevent the slow visual entropy that makes brands look inconsistent even when they're using the right colours and fonts.
Component patterns. How do buttons look? What about cards, forms, callout boxes? If your brand appears in a product interface, these patterns need documenting. If it appears only in marketing materials, specify your approach to layout modules.
Motion and interaction principles. Animation is part of brand expression now. Document your approach: easing curves, duration ranges, when to animate and when to stay static.
The format problem
PDF brand guides are the default. They're also the worst format for guidelines that need to be used daily.
PDFs can't be searched easily. They can't be updated without regenerating the whole file. They can't link to live assets. Living guidelines — hosted on platforms like Notion, Zeroheight, or as a dedicated section of your own website — stay current because they're part of the workflow.
The brand identity system that actually gets used is the one that meets people where they already work.
Common mistakes to avoid
Documenting aspirational guidelines instead of actual ones. If your brand photography direction says "cinematic, editorial, high-production" but your budget means you're using iPhone photos, the guidelines should address how to shoot well on a phone — not pretend you have a studio.
Being too vague. "Our tone is friendly and professional" describes 90% of all brands. It's not a guideline — it's a horoscope. Specify what friendly means in practice. Give examples. Show what you reject, not just what you aspire to.
Being too rigid. Guidelines that specify every possible scenario become encyclopaedias. Nobody reads them. Focus on principles with enough examples to build pattern recognition, then trust your team to apply those principles to new situations.
Forgetting the "why." Every rule should carry a reason. "Don't place the logo on busy backgrounds" is a rule. "Don't place the logo on busy backgrounds — the mark loses legibility below 60% contrast" is a guideline people actually follow, because they understand the principle behind it.
What brand guidelines should look like in 2026
The old model: a designer hands you a PDF, you put it in a folder, it goes stale. The new model: a brand system with living documentation, design tokens your developer can import, templates your team can actually edit, and voice guidelines specific enough to brief a freelance writer in five minutes.
The Brand Protocol produces this in its System stage. Strategy feeds identity. Identity feeds the system. The system feeds everything your brand touches — and it arrives as something you can deploy, not just read.