How to write brand guidelines that survive a busy week

Fibvo editorial · 24 July 2026 · 4 min read

Your organisation has brand guidelines. The work going out does not look like them. A sales deck leaves with the logo stretched into a corner. An invoice uses a different typeface from the website. Three versions of the same blue appear in one week, none of them the one in the document. Nobody is being difficult. The person building that deck at four in the afternoon had a deadline, no template and a question the guidelines did not answer. They guessed. Guidelines fail at that moment, not at the moment they are written.

Guidelines answer the wrong question

Most guideline documents are organised around the identity: logo, colour, type, photography, tone. That is the order a designer thinks in, not the order anyone else works in. The marketing lead wants to know whether a case study headline takes the heavy weight or the regular one, and whether a partner logo may sit beside yours on a cover. Both answers sit behind pages of principles about breathing space.

Two further failures are mechanical. The document sits as a PDF in a drive folder named by whoever saved it, and states rules nobody can execute in the tool where the work happens. "Maintain generous clear space" means nothing in a slide master. "Clear space equals the height of the wordmark on all four sides" can be set once and left alone.

Write every rule with a worked example

A rule stated in the abstract gets interpreted. A rule shown twice, correct and incorrect, gets copied.

• The wrong way and the right way side by side, with one line saying what changed.
• Real content, not placeholder text. A headline of the length your team actually writes.
• The awkward cases rather than the easy ones. Logo on a photograph. Logo beside a partner logo. A headline running to three lines. A long legal entity name.
• The answer to the question people keep asking. If colleagues keep asking whether the secondary colour works behind body text, answer it in the document with a yes or a no.

Keep the reasoning to one line. Nobody needs the theory behind the type scale; they need to know which of two sizes to pick.

Guidelines are judged not by how well they describe the brand but by how fast someone in a hurry can make the right decision without asking.

Template the formats your team produces every week

Most of what leaves an organisation is not made by a designer. It is assembled by a salesperson, a recruiter or an operations manager in whatever tool is already open. Each of those formats needs a file they can duplicate. Build templates for the ones that recur, not the impressive ones.

• The pitch deck and the shorter follow-up deck, in the software the sales team already uses, with styles built into the master rather than applied by hand.
• The proposal, the quotation and the invoice, including the plain document version.
• Social posts at the sizes each platform crops to, including one with text over a photograph.
• The email signature, as code someone can paste, not as an image.
• The recruitment post and the one-page service sheet that gets printed and handed over.

Store each template where the work starts, not in a brand folder. The deck template belongs in the shared presentation library, the signature on the onboarding checklist beside the laptop and the email account. When the correct file is the easiest file to reach, most of the problem disappears.

Say plainly what is fixed and what is flexible

Most guideline documents imply this split without stating it. Cautious people then freeze and confident people improvise.

• Fixed: logo files and minimum size, clear space, exact colour values, the typefaces and their fallbacks for email and office software, how the legal name is written, and what is never done to the mark.
• Flexible: layout, crop, photograph choice, illustration, headline length, the balance of colour within a piece, and the tone shift a technical audience needs against a retail one.

Then name the grey area and who decides it. Co-branded material, event stands, regional language versions and anything a third party produces on your behalf usually sit here. Naming the few categories that need checking before publishing beats a general instruction to check everything, which people learn to skip.

Give enforcement a name and a route

Guidelines with no owner are a suggestion. Enforcement does not need a committee.

• One owner, named in the document, with a stated response time. If nobody can answer within a working day, the rule loses to the deadline.
• One approval point on the way out: whoever signs the print order, schedules the post or sends the client file.
• A short decision log: every exception granted, with the date and the reason. It becomes the next version of the guidelines.
• A fix-the-template habit. When the same mistake keeps appearing, the template is wrong or missing. Repair the file instead of correcting the person.

Set a review date and keep it. Twice a year, open the files the organisation sent out that month and compare them with the document. The gaps show which rules are unusable, and that is the agenda for the next revision. When we build an identity at Fibvo, the templates and worked examples are part of the delivery. Scope is written down before work starts, and the client owns every file.

---

Written by Fibvo — Bengaluru and Erode, India — working with clients in other time zones. Questions, or think we have it wrong? Tell us.