A brand book is the document that holds the rules of a brand: positioning, logo, colour, typefaces, graphics and templates for every medium. Guidelines cover only the visual part of those rules, while a design system is the library of components and values a website and an app are assembled from.
Key takeaways
The three documents solve different problems and live in different places: guidelines answer the question of how to lay things out, a brand book answers what the brand is and how it behaves, and a design system answers what the product is assembled from.
| Document | What is inside | Who it is for | When it is needed | Format |
|---|---|---|---|---|
| Guidelines | Rules for the logo, colour, typefaces and media | Designers, contractors, printers | As soon as more than one person makes the materials | PDF or a page with the files |
| Brand book | Guidelines plus the brand platform: positioning, character, tone of voice | Marketing, sales, franchisees, new employees | When many people and channels carry the brand | PDF, an online document, a dedicated site |
| Design system | Tokens, components, states, a link to the code | Product designers and developers | When there is a site, an app or a client portal in active development | A library in the design tool and a package in the code |
The documents do not replace each other, they stack: brand rules on top, visual rules in the middle, ready components at the bottom. The system of decisions these documents describe is covered in our piece on brand identity.
The contents are assembled for a particular business, but the skeleton repeats. Below are the sections found in almost any working document.
The business dictates the set of sections. A delivery service needs sections on vehicles and courier uniforms — that is how our QADAM project is built. An IT company needs sections on interfaces, decks and documents instead.
The format follows the way the document will be used day to day, not the way it looks in a final presentation. Each option carries its own cost of error.
In practice the formats are combined: a short PDF for external contractors, an online document for the team, a design library and a code package for the product. One rule holds it together: there must be a single source of truth, and everything else is an export of it.
Example In the QADAM project the rules are collected into an interactive brand book of 14 sections: mark, palette, pattern, icons, packaging, merchandise, vehicles, courier uniform. States and colours are described there in advance, so that the build only has to assemble the product.
A design system is not guidelines for a website but a working library an interface is assembled from. At its core are tokens: named values for colour, spacing, radius and type that every component refers to.
The format of those values is being standardised: the Design Tokens Community Group at the W3C released the first stable version of its specification in October 2025 so that tokens travel between design tools and code without being retyped. Design tools implement the same idea through variables and modes: Figma variables store the values, modes switch them for light and dark themes, and libraries publish all of it to the team.
A design system describes how an interface behaves, not only how it looks, so it has a direct effect on whether a person reaches their goal. How that connects to conversion and retention is covered in our piece on website UX/UI design.
The document is needed wherever the identity is applied by someone other than the person who designed it. The more hands and channels there are, the more each spoken explanation costs.
A small company with one website and a couple of channels is usually fine with guidelines and a set of templates: logo, colours, typefaces, a deck, a social post and a letterhead. A full brand book pays off once a franchise, retail, packaging or several product lines appear.
The document is written from the jobs a team does every day rather than for the look of it. The order of the work is usually as follows.
The sections on logo, colour and typefaces come out of a finished system — if there is none yet, the work starts with brand identity design, while the requirements for the mark itself are covered in our piece on the logo.
The document needs one owner: a brand manager, a marketer or a lead designer. They sign off contested layouts, take in proposals for changes and make sure the team has one current version.
The mechanics of updating are worth borrowing from public design systems. The GOV.UK Design System is run by a team at the Government Digital Service: components carry a status, changes are discussed in the open and ship as versions with release notes. A business does not need that scale, but the scheme itself — owner, statuses, versions, history — transfers to a brand book of any size.
An outdated PDF in ten copies is worse than one living document behind a link. How to hand the rules to a team and its contractors so that they are actually used is described in the rollout section of our piece on brand identity.
Length is not a measure of quality. A thick document can sit untouched while a short set of rules with templates saves a team hours every week. The usual reasons a document fails to take hold are these.
Checking it is simple: give the document to someone who was not involved in making it and ask them to build a deck and a social post. Everything they have to ask out loud is a hole in the brand book.
We write rules so that a product can be built from them, not so that the presentation looks good. In the QADAM project the document was built from the media of a delivery service: packaging, merchandise, vehicles, courier uniforms and a pickup point each got a section with ready decisions rather than general principles.
In the KruchuVerchu project the design system took on the role of the document: palette, typography, grids, icons and components hold one character across every screen and medium, and the materials were handed over ready for development.
Design sits in the same team as development here, so the rules are written in a form the code can take directly. If the document is needed mainly for digital media, look at what website development includes: prototype, design and build run as one project.
Let’s discuss your project
Tell us what you need, and we will estimate the timeline and cost and suggest a solution.
The document itself in the agreed format, the source files, the logo in every version, the typefaces with their licences noted, the media templates and access to the storage where all of it lives. Without source files and typefaces the document becomes a picture within six months, and a picture cannot be developed.
Don't count pages — count applied media. A company with a website and a couple of channels is fine with a guideline plus templates for a deck, a post and a letterhead; a franchise or retail chain adds outlets, packaging, vehicles and uniforms. For comparison, the brand book for the delivery service QADAM runs to 14 sections.
It can, for as long as that one designer stays. But the rules live only in their head, so when they leave, the company loses both the style and the ability to produce materials quickly. Even a short guideline with templates removes that dependency.
For a franchise, a brand book is a working tool rather than an image document — every outlet needs the same standard. The partner receives the rules for the outlet's look, signage, uniforms, packaging and advertising, instead of inventing their own. The document also becomes part of what you sell along with the franchise.
By events rather than by calendar: a new website, a new product line, entering a new market or language, a medium that did not exist before. Every change is recorded as a new version with a date, so the team knows which file is current.
A live website is a solid starting point. The palette, typography, components and composition rules are pulled from it, and then whatever the interface doesn't cover — print, packaging, documents — is added on top. A brand book put together this way appears faster than one built from scratch.
