Everyone worries about using the wrong color. Almost nobody worries about the wrong font, until a client points out that the website, the email templates, and last month’s pitch deck use three typefaces that were never meant to appear together.
Typography drift is subtler than color drift. An off blue shows up in a side-by-side comparison. A slightly wrong font weight, or a fallback font standing in for one that didn’t install, looks a little off. It’s hard to name, easy to ignore, and more common than most teams think.
Font licensing is a separate problem, and a well-documented one. It comes down to whether you’re allowed to use a font everywhere you’re using it. Foundries like Monotype and Extensis have written a lot about that risk, and it deserves attention. This post covers the part that gets far less of it. Leaving licensing aside, is your typography consistent from one asset to the next, and how would you check?
Where typography breaks down
Fallback fonts slip in. When a font isn’t installed on someone’s machine, or isn’t embedded properly in an exported file, most software swaps in a fallback without saying anything. The document looks fine to the person who made it, and they won’t notice the substitution unless they look for it.
Every document reinvents the hierarchy. Most brand guides name a font family but stop short of a full hierarchy with exact sizes and weights for headlines, subheads, and body text in each format. So each new document makes its own call, and a dozen separate calls rarely agree.
Licensing gets ignored, even though the risk is well documented. Fonts aren’t automatically free to use everywhere. A license that covers your website might exclude billboards, and one that covers internal documents might exclude paid ads. Foundries publish good guidance on this. Most marketing teams never read it, because it sits in the font-licensing world rather than the brand-guidelines world. The font is installed and looks right, so people use it until a licensing audit or legal notice arrives.
Nobody owns it. A color has a hex code, which makes it feel like someone owns it. Typography rules are often a single line in the brand guide (“we use [Font Name]”) with no owner and no enforcement.
Treat fonts as a spec.
A typography system people can follow needs more detail than most brand guides give it:
- The exact font files, stored centrally, so nobody depends on whatever happens to be on their machine.
- A defined fallback stack for every context where the primary font won’t work, such as web-safe alternatives for email, so substitutions are planned.
- A full hierarchy with sizes and weights for H1, H2, body, and captions in each format (web, print, social, presentation).
- License terms for each font and use case. Record what’s covered (web, print, embedded in video, paid ad campaigns) and what isn’t. If you’re unsure, ask whoever issued the license before the font turns up in a paid campaign.
Running a typography audit
- Pull a sample of recent assets across every format and channel, the same way you would for a color or tone audit.
- Check the font that rendered. The file may say one thing while the output shows another, and fallback substitutions often only appear when you inspect the output.
- Check hierarchy. See whether headlines are the same relative size and weight from document to document, and whether body text sits at the approved size.
- Compare licensing to usage. Match where each font is licensed to appear against where it does appear. Most teams skip this step entirely, even though it carries the biggest financial and legal risk.
- Go after the root cause. A recurring fallback problem usually means the team isn’t distributing font files properly. A recurring hierarchy issue usually means the typography section of the brand guide needs more detail.
Why fonts need their own audit
Typography rarely gets its own review. At best it gets a glance during a more extensive design check. Licensing risk at least has a body of guidance from the font industry. Consistency drift has no comparable guidance, and in most teams’ processes, it has no home at all. That’s the gap. Nobody routinely checks whether the right font, at the right weight and size, appears correctly on every asset. When anyone looks at fonts, it’s usually a one-off legal review.
A small team with one or two fonts can probably get by with a quick yearly look. An agency managing several client brands, with content going out across print, web, and social at once, is better off automating typography checks alongside color and tone so nothing depends on someone happening to notice.
BrandMind checks typography alongside color and tone in every compliance scan. See how it works or start free.
