Skip to main content
The PDF brand book is the wrong shape for a working brand. It decays the moment it ships, it cannot be edited by the people who need to act on it, and it has no way of knowing whether the person reading it is the brand owner or the freelance designer hired last Tuesday. Brand Atlas exists because a brand is a working system, and a working system needs a working surface.

​
The PDF was designed for delivery, not stewardship

A PDF is a delivery format. A studio finishes a brand identity, exports the rules to a PDF, sends it to the founder, and considers the work complete. The format was never asked to do anything after that. It was asked to look impressive on day one. It does. The problem is that a brand does not stop on day one. It is used every day for years by people the studio has never met. The PDF cannot be edited by them. It cannot be searched usefully by them. It cannot tell them which version they are looking at, whether it is current, whether the colour they are about to use has been retired, or whether the logo they are about to place has been replaced. It can only sit in a folder.

​
What the PDF actually causes

The brand starts to drift. Brand drift is the operating problem every brand owner faces six months after launch, and it has consistent symptoms:
  • The logo gets redrawn in PowerPoint by someone who cannot find the source file.
  • The typography stretches across three weights because the team licensed two of them and improvised the third.
  • The colour palette picks up a fourth blue, lifted from a screenshot of a screenshot.
  • Two suppliers print on different stocks because no-one specified which is canonical.
  • The voice loosens, then tightens, then loosens again, depending on who is writing.
  • The social grid stops looking like the brand by month nine.
None of this is the team’s fault. The PDF gave them no way to get it right, and no way to surface the problem when they got it wrong. The brand drifted because the system could not hold.

​
The replacement is not a better PDF

It is tempting to think the answer is a nicer PDF, an interactive PDF, a hyperlinked PDF, a Figma file pretending to be a PDF. None of these solve the problem, because the problem is not the document. The problem is the absence of a system. A brand needs five things the PDF cannot provide:
  1. A single current version. Everyone reads the same source of truth. There is no v3-final-final.
  2. Role-aware access. The brand owner edits. The team member reads. The agency partner reads a subset. The printer reads a subset of that.
  3. A request channel. When the team spots something missing or wrong, they ask. The brand owner answers. The change is recorded.
  4. Structured extensibility. When the brand stretches, the system stretches with it through Horizons.
  5. An accountable history. What changed, when, by whom, and why.
These are not features of a document. They are features of a portal.

​
The case Brand Atlas makes

Brand Atlas is the portal. It contains everything a PDF contained, organised the way a brand book has always been organised, and adds the five things above. It does not replace the studio that built the brand. It replaces the artefact the studio used to deliver. The studio still designs the identity. The atlas is where the identity lives afterwards. That is the case. The rest of these docs are the detail behind it.

​
Next steps

What a brand atlas is

The definition the rest of the docs build on.

Brand drift, the concept

A deeper look at the problem Brand Atlas solves.

Why a portal beats a PDF

The pillar comparison page.