Brand Guideline

A small company doesn't need the rules written down. One or two people make everything, and anything unclear gets settled by asking the person at the next desk. Past roughly twenty people, with business cards, pitch decks, ad creative, job postings and event banners all going out at once, that arrangement stops working.

Pagedeck hit this. Ravi pulled the logo off an old blog post and stretched it sideways to fit a banner. Sofia picked a blue from memory for a proposal. The booth graphics that went to an outside agency came back in a third typeface. Four things left the company in one week and looked like they came from four companies.

The cost isn't that it looks careless. Recognition builds by seeing the same thing several times, and when each sighting is slightly different, four exposures register as one. The ad budget spends four times and the memory stores once.

Noa was stuck on the other side of the same problem. "Where's the logo file?" and "is this the right blue?" arrived a few times a day, and because one person held the answers, nothing could be made while that person was out. A brand guideline solves both at once. The answers are written down in advance so nobody has to ask, and because there is exactly one written answer, what comes out matches.

Six things, broadly. One principle runs through all of them: write values, not judgments. "Leave enough space around the logo" is a preference. "Leave half the logo's height clear on every side" is a rule.

1. Logo — how the logo gets placed. Minimum size, clear space around it, which background colors it may sit on, and which alterations are off limits. Show the banned cases as pictures rather than sentences: the stretched logo, the logo with a drop shadow, the logo dropped straight onto a busy photo.
2. Color — primary and secondary colors written as values, with separate screen and print numbers, plus how much of each to use. A primary color meant for accents will read as a completely different brand when it covers a whole background.
3. Type — the typefaces for headings and body text, the size and weight steps, and the fallback face for machines that don't have the real one installed. Skip that last item and a proposal opened on a client's computer renders in a default font.
4. Images and icons — photo mood, icon stroke weight. Individually invisible, obvious the moment two styles sit side by side.
5. Voice — the attitude set in tone and manner, turned into rules about actual sentences. Whether an error message reads "the request failed" or "try that again in a moment" is decided here. So is how the company name and the tagline are spaced and how far either may be shortened.
6. Worked examples — one finished version of each thing the company makes often: a business card, a deck cover, an ad, a job posting. A single finished page is read faster than ten lines of rules.

The boundaries are worth writing down too. Button and input specs inside the product belong to the design system, and named color and spacing values shared with engineers are design tokens. The guideline covers what leaves the building.

It's written by the brand designer and the brand marketer, and read by everyone who makes something that goes outside the company.

The part that trips up writers: neither of them invents the rules. What the company is like and what it promises has already been settled in the brand identity, and the guideline is that character transcribed into visible numbers and examples. Start the guideline with the identity still blank and the colors and typefaces get chosen, but nobody can say why those ones.

At Pagedeck the readers fall into three groups: employees building proposals and job postings, outside agencies building banners and booths, and the designer who joins later and inherits the rules.

The document alone doesn't get used. Logo files, font files and deck templates belong in the same place as the rules. If the color codes are written down but the files aren't there, Ravi goes back to the old blog post.

A quarterly pass through the document is a reasonable default, but it grows for a different reason: someone asks about a case the document doesn't cover. Write that answer in while answering it and the same question never comes twice.

"The blue in this proposal looks off to me — is that the value from the guideline?"

The written document is the reference, and memory isn't.

"I sent the agency the guideline for the booth, so they just need to respect the logo clear space."

A document replaces the explanation that used to be given from scratch each time.

"We don't have a guideline yet, so for now I'll just send you the logo file."

Without rules, there's no way to promise what will come back.

When Pagedeck handed its year-end booth to an outside agency, what Noa sent was not an explanatory email but a folder: the guideline, logo files for each background, the color table, and the font files. The first round of concepts came back with exactly one thing wrong, the clear space around the logo. Noa replied with a page number.

The previous event took five rounds for the same job. A concept would arrive, the color would be wrong, the correct value would be sent over, and then the typeface would be off.

The most common misreading is that a good guideline builds the brand. A thick document feels like the work got organized. But the document is a container for decisions already made, and recognition accumulates from what customers actually saw. A hundred-page guideline with nothing shipped out behind it leaves the number of people who know the company unchanged six months later.

Treating more rules as better rules has the same shape. Covering every case looks like a way to make sure nothing goes wrong, but rules that are hard to follow don't get followed, and a few months later nobody opens the file at all. A thin document that answers the ten situations that come up constantly does more.