·

Steeve Elgui

Brand Guidelines: Core Elements and How to Apply Them

Brand guidelines explained: the core elements, colour, type, imagery and tone rules, plus how to make them usable across digital and print teams.

The web banner uses one blue, the email another, and the shop sign a third. Meanwhile, the product team has given the main button a colour that doesn't appear in any shared file. Everyone has made a reasonable local decision. Together, those decisions no longer look like one identity.

Brand guidelines should function as a change-control system, not a presentation saved after the identity launch. We need fixed tokens, tested combinations and named decision rights, so designers can adapt the work without rebuilding the brand each time.

What Brand Guidelines Are and Who Relies on Them

Brand guidelines define how a brand's visual, written and interactive elements are made and reproduced. Their readers are the people who touch the brand without having designed it: in-house designers, marketing, product and engineering teams, agencies, printers, packaging suppliers, retail partners and freelancers joining halfway through a project.

A brand book explains purpose, positioning and story. A working guideline supplies specifications, approved files, rules and examples. A polished account of the identity is no substitute for a usable export, and that difference decides which documents get followed.

Showfolk's summary of a 2025 study of UK packaged-goods brands reports that 125 brands used their visual elements consistently at an average level of 65%. More than a third sat outside the intended standard, a practical reason to document application rather than intention.

Start with coverage: List the channels in use, then mark those with written rules.

Teams managing several identities can organize client brands with FoPost to keep assets and usage rules together. Each uncovered channel then defines the next deliverable: a lean reference, a full guideline or a component library. Whatever shape it takes, the document earns its keep by naming what stays fixed, which pairings are pre-tested and who signs off a change.

That is what lets a channel flex without the brand losing recognition.

Core Elements at a Glance and Where They Apply

The core elements fall into identity, colour, typography, imagery, language, graphic devices, layout, interaction, production and accessibility. Treat the following reference as a coverage checklist, not a list of chapters that must all be equally long.

Core guideline elements, what they define and where they apply

Element

What It Defines

Typical Specification

Applies To

Logo and identity

Approved marks and their variants

Master files, minimum size, clear space

Digital and print

Colour

Named palette and colour roles

HEX, RGB, CMYK, Pantone and approved pairings

Digital and print

Typography

Typefaces and type scale

Sizes, weights, line height and fallbacks

Digital and print

Imagery

Photography and illustration rules

Art direction, crop ratios and alt text

Digital, print and packaging

Tone of voice

Written character and vocabulary

Attributes, example lines and banned terms

Digital, print and customer messages

Graphic devices

Icons, patterns and shapes

Stroke weight, grid and usage limits

Digital and print

Layout grid

Spacing and structure

Columns, margins and baseline

Digital and print

Digital components

Buttons, forms, cards and states

Tokens, states and contrast

Websites, apps and email

Print specifications

File and finish rules

Bleed, safe area, dieline and spot colours

Print and packaging

Accessibility rules

Contrast, focus and alt text

WCAG 2.2 Level AA checks

All channels, using channel-appropriate tests

Each row corresponds to the detailed rules below. Colour and typography cross physical and digital outputs; dielines belong to packaging, while interactive states belong to interfaces. Email also needs fallback fonts and usable backgrounds when images don't load.

For a brand running on fewer than three channels, start with identity, colour, typography and tone, then extend the document as channels go live. Don't publish an untested row. A real output should demonstrate that its specifications work.

Logo, Clear Space and Misuse Rules

A logo page should remove production guesswork. Designers need the actual artwork, not instructions to extract a mark from an old PDF.

A designer works on brand identity development featuring a Northfield logo design, technical specs, and usage guidelines.
  1. Supply master artwork. Include SVG, EPS and PDF files, plus raster exports at documented sizes. Name primary, reversed, monochrome and mark-only variants consistently.

  2. Define measurable clear space. Choose a reference unit from the artwork, such as a letter height. Show that unit and the exclusion boundary in a labelled diagram.

  3. Test minimum sizes separately. Record screen widths in pixels and print widths in millimetres. Inspect the smallest intended reproduction, including fine counters and gaps.

  4. Approve backgrounds. Show each variant on permitted colours. Photographic placement needs an approved overlay or solid panel, not an improvised contrast fix.

  5. Pair each misuse with its correction. Make the difference visible rather than relying on a prohibition alone.

Incorrect treatment

Correct treatment

Stretched artwork

Original aspect ratio

Unapproved recolouring

Approved colour variant

Added shadow or outline

Unmodified master

Rotated mark

Approved orientation

Rearranged lockup

Supplied lockup

Busy image behind the mark

Approved panel or overlay

Animated logos need approved start and end frames and motion behaviour. App icons need their own safe-area treatment; co-branding needs an explicit relative-size rule.

New variants belong in the master library, not inside a slide deck where the next designer can't find them.

Colour Tokens for Screen and Print

A campaign designer lightens the primary blue for one landing page. Two weeks later that blue is the only signal on an error state. The colour had a value and no decision rights, so recognition slipped.

Roles come before swatches. Name primary, secondary, accent, neutral and feedback colours, then lock each role to channel values and a permitted use. A token is a change-control record: the value can be updated in one place, while the role and the tested pairings stay fixed.

The UK Space Agency's branding guidelines distinguish screen-only RGB colours and require background and font combinations to meet AAA accessibility standards, with contrast checking recommended. That is one organisation's bar, not a reason to call every attractive palette accessible.

A diagram illustrating a color system design hierarchy including primary, secondary, accent, neutral, and feedback colors.

Colour token specification by role

The figures below are one worked example of published tokens, not a universal palette. Screen and print columns are specified separately. They are not conversions of each other. Swap in colours your brand has approved and proofed.

Role

Screen Value

Print Value

Permitted Use

Brand primary

#0B3A4A, rgb(11, 58, 74)

C100 M45 Y30 K20, Pantone 302 C

Logo, headers and key brand moments

Text neutral

#1A1A1A, rgb(26, 26, 26)

C0 M0 Y0 K90

Body text on light surfaces, with a tested ratio

Surface

#F4F1EC, rgb(244, 241, 236)

C3 M4 Y8 K0

Page and card backgrounds

Action

#0E6B5C, rgb(14, 107, 92); dark mode #3DDCB5

C85 M20 Y50 K5

Primary buttons and links only

Success

#1F7A3A, rgb(31, 122, 58)

C80 M10 Y90 K0

Confirmation states, always with an icon or text

Warning

#C47B00, rgb(196, 123, 0)

C0 M40 Y100 K10

Cautions, never the only cue

Error

#B42318, rgb(180, 35, 24)

C0 M90 Y85 K20

Form errors, always with a text label

Add secondary, accent and information tokens only when a component needs them. Semantic names such as colour-action-primary keep the purpose when a value changes. A decorative accent must not be reassigned as a warning or an action without a new pairing test.

A print value is a separate production decision. An automatic RGB-to-CMYK conversion is not approval. Review coated and uncoated samples, and record the approved stock next to the colour reference.

A colour isn't ready for the library until it has a role, channel values and a tested pairing.

Name who may change a token and who may only apply it. Brand owners amend values and pairings. Campaign, product and partner teams use the named role. Document dark-mode tokens as their own set, not as an inverted primary. Product swatches for skincare, cosmetics or clothing should be labelled as product colours outside the identity palette, with product names attached. Record approved logo-on-colour combinations and measured text/background pairings beside the tokens.

Typography Scale and Font Fallbacks

Check licensing before setting type. Confirm permitted web embedding, desktop installation, app bundling, email use and print production, including any restrictions on sharing font files.

Name the headline face and running-text face explicitly. Email requires tested system fallbacks: a sans-serif stack can use Arial and Helvetica before the generic sans-serif family; a serif stack can use Georgia before the generic serif family.

Type scale reference for web and print

The following print sizes are illustrative starting specifications, not universal readability minimums.

Style

Print Size

Weight and Use

Display

Set against the format and proof at final size

Bold, campaign headlines

Heading 1

Larger than section headings, proofed in layout

Semibold, page titles

Heading 2

Between page title and body, proofed in layout

Semibold, section titles

Body

9–11pt, subject to readability testing

Regular, running text

Caption

7–8pt, subject to readability testing

Regular, image captions and notes

Button label

Not a print style; specify interface dimensions

Medium, interactive labels

Alongside this table, record web size, line height, weight and breakpoint behaviour for every style. A useful working target for screen paragraphs is about 45–75 characters per line, checked with actual copy rather than placeholder text.

Packaging legal text needs a separate, verified specification. Variable fonts need fixed-instance fallbacks where unsupported; other scripts need suitable companion faces, and prices or data may need tabular numerals.

Imagery and Art Direction Rules

Art direction needs observable instructions: light direction, softness, colour grade, subject distance, background tone, retouching limits and crop behaviour. Mood words alone won't tell a photographer where to put a light.

A hand points to a selected portrait photo on a storyboard with various photography test prints.

Build a reference set with approved examples and a rejected example carrying a specific reason. For beauty photography, that might distinguish preserved skin texture from smoothing that changes the product result.

  • Photography: Specify background colour, shadow quality, retouching boundaries and permitted crops.

  • Illustration and renders: Fix stroke behaviour, lighting angle and palette limits.

  • Image records: Store whether the asset was shot, licensed or generated, together with rights and provenance.

The University of Exeter DIGIT Lab survey reported by Dezeen found that 81% of designers believed AI dulled creativity. Generated alternatives still need human judgement, material knowledge and critique; visual polish isn't evidence that an image is appropriate.

Alt text should explain the image's purpose in context. Decorative images should be marked accordingly, while user-generated and influencer images need a distinct rights-and-approval route.

Before release, check art-direction fit, contextual text alternatives and recorded provenance. Progress in generation tools doesn't remove those decisions.

Layout Grid, Icons and Graphic Devices

Define the grid by breakpoint, with columns, gutters, outer margins and a baseline unit. Show actual content in each diagram so the reader can see what happens when a heading wraps or an image changes shape.

A rigid grid can make a responsive interface brittle. Specify which relationships stay constant and which dimensions adapt, then identify the templates and crops built on those relationships.

Device

Specification to record

Acceptance check

Icons

Grid, keyline, stroke and corner treatment

Clear at smallest intended size

Patterns

Scale, density and permitted placement

Doesn't interfere with text

Shapes

Geometry, cropping and layering

Matches approved compositions

Print layouts

Margins, baseline and flatplan

Works across facing pages

Give each device a usage limit. That might prohibit patterns behind body text or restrict a surface to a single pattern family.

Status icons need an accompanying label. Print requires a point-based baseline and a document-level flatplan, not merely separate attractive pages.

New devices enter the library only after review against the existing geometry, usage limits and contrast expectations. Record their first approved application so later teams can inspect the original context rather than copying a detached screenshot.

Tone of Voice Written as Rules

Clarity takes priority over personality. A line that sounds distinctive but makes an instruction harder to understand needs rewriting.

Attributes become useful when they set boundaries. The example lines below demonstrate writing style; product claims still require substantiation before use.

Tone attributes with boundaries and example lines

Attribute

We Are

We Are Not

Example Line

Precise

Specific about ingredients, sizes and timings

Vague or superlative

Fragrance-free, tested on sensitive skin.

Warm

Direct and human

Chummy or jokey

Your order is on its way.

Calm

Short sentences and no false urgency

Countdown pressure

Ready when you are.

Plain

Everyday words with the product name used exactly

Jargon and internal terms

Enter your postcode to check delivery.

Record approved product names, preferred button verbs, banned phrases and a rule for sentence length. Favour active voice, but don't force it where a passive construction is clearer.

Errors should explain what happened and the next action. Confirmations should say what is now true, rather than merely celebrating completion.

Read-aloud check: If a sentence needs explanation in the review meeting, the customer probably needs a clearer sentence.

Test example lines across product pages, emails and interface messages with designers, writers and support staff. Email subjects should match the register of the destination page.

Legal and safety wording follows approved terms, not a stylistic rewrite. Record clarity decisions so the next writer doesn't reopen the same debate.

Digital Components, States and Accessibility Contrast

A button isn't specified by its default appearance. Buttons, links, fields, cards, navigation, modals, banners, charts and product swatches need applicable default, hover, focus, active, disabled, error and loading states.

A checklist for digital design components including buttons, modals, links, forms, and ensuring WCAG accessible color contrast.

The ONS accessible text-formatting guidance gives 3:1 as a basic AA contrast value, but that mustn't become a blanket normal-text rule. A production specification should distinguish normal text, large text and meaningful non-text controls.

Minimum contrast for WCAG 2.2 Level AA

Content

Minimum Ratio

Test Note

Normal text

4.5:1

Body and small text, measured against the actual background

Large text

3:1

At least 18pt regular or 14pt bold

UI components and graphical objects

3:1

Borders, icons and states needed to understand a control

Icons that carry status

3:1

Must match the text label beside them

Text over images

4.5:1 for normal text; 3:1 for large text

Measure the worst point behind the text, or use a solid panel

Test behaviour as well as appearance

Focus must remain visible, and keyboard navigation should follow a logical reading and task order. Pair feedback colours with labels and appropriate icons, then test components with assistive technology rather than assuming a Figma annotation proves accessibility.

Measure photography overlays, gradients and dark-mode backgrounds in their rendered context. Disabled controls can have contrast exemptions, but deliberately faint content still deserves a usability review.

Map approved tokens to both Figma components and front-end code. A working design system connects those values with behaviour, ownership and tested implementations.

Motion needs named durations and easing curves, plus a reduced-motion alternative when content moves. Loading information must remain understandable when animation is removed.

The handover deliverable is a state sheet with recorded checks, not a collection of ideal screenshots. Include contrast results, keyboard behaviour, screen-reader observations and unresolved issues alongside each component.

Print and Packaging File Specifications

A print spec sheet is the last control point before ink, substrate and finishing costs get locked. Treat it like change control: fixed tokens such as colour values, dielines and regulatory zones stay stable, while layout, image crop and finish can flex within tested limits and named approval rights.

Print file specifications by format

Use these as typical working ranges to confirm against the supplier's press, finishing and template requirements.

Format

Bleed

Safe Area

Colour and Output

Business card

3mm

3mm inside trim

CMYK, PDF/X-1a

A4 brochure

3mm

5mm inside trim

CMYK, PDF/X-4 or PDF/X-1a

Carton packaging

3mm, dieline on its own layer

5mm inside fold lines

CMYK with spot Pantone, dieline and varnish as separate layers

Sticker

2mm

2mm inside die line

CMYK, kiss-cut die line on its own layer

Large-format poster

10 to 20mm

25 to 50mm inside trim

PDF/X-4, vector artwork where possible, raster images sized for viewing distance

Packaging files need clearly separated foil, varnish, spot-colour and dieline information. Protect barcode quiet zones, keep legal copy inside the required type size, and verify recycling marks against the market where the pack ships.

For beauty branding, assess finishes and colour on the actual substrate. A coated swatch is not approval for an uncoated carton.

Run two checks before release: a viewing-distance pass for large-format type and a flatplan review for editorial pagination. Attach a format sheet recording dimensions, colour mode, fonts, proof type, tolerance limits and the named person allowed to sign off changes.

Deciding What Stays Fixed and What Can Flex

Consistency doesn't mean identical compositions. It means designers understand which decisions preserve recognition and which can respond to a different task.

The GOV.UK brand guidelines' June 2025 update added guidance for extending the identity into contexts including the GOV.UK App and GOV.UK Wallet, with flexibility according to audience, content and context.

A diagram illustrating the distinction between fixed brand elements and flexible design elements in brand guidelines.

Fixed or flexible rules by change type

Element or Change

Fixed or Flexible

Approver

Logo geometry

Fixed

Brand lead

Primary colour values

Fixed

Brand lead and accessibility check

Core typeface

Fixed

Brand lead and licence check

Legal and regulated wording

Fixed

Legal reviewer

Campaign accent colour

Flexible within the palette

Campaign owner

Photography subject and crop

Flexible within art direction

Art director

Tone register for a new audience

Flexible within attributes

Content lead

New channel, such as an app screen

Flexible patterns, fixed tokens

Design lead

Accessibility minimums remain fixed. Secondary colour, illustration and composition can flex within documented limits.

Approved template reuse shouldn't require fresh sign-off. Otherwise the approval process penalises the very behaviour the guidelines encourage.

Log justified exceptions with their owner, reason, scope and review condition. A new logo variant needs brand-lead approval; new type also needs licensing review.

Before a new touchpoint proceeds, classify the proposed changes and route only the decisions requiring approval. That preserves room for craft without leaving ownership vague.

How the Elements Depend on One Another

A local change can leave the surrounding system incorrect. Replacing a typeface in Figma doesn't update the email fallback, packaging line breaks or exported document templates.

Use dependencies as the checking route before approving a change.

Dependencies between guideline elements

If You Change

Also Check

Why It Matters

Primary colour

Contrast pairings, print proofs and logo-on-colour use

Screen legibility and physical reproduction may change

Typeface

Type scale, email fallbacks and line length

Letter widths and metrics differ between faces

Logo proportions

Clear space, minimum sizes and favicon

Existing sizes stop fitting the new mark

Grid or columns

Image crop ratios and layout templates

Crops and templates need rechecking

Button labels

Tone rules and focus order

Changed actions may alter comprehension and require keyboard-flow review

Feedback colours

Icons and error text

Status must remain understandable without colour

A colour revision can also affect photographic grading and every component state using that token. A wording change doesn't change focus order, but a revised task or added control can.

For luxury branding, this scrutiny matters in restrained compositions: small spacing or reproduction differences can alter the intended finish.

Shared components require instance-level checks. Inspect the templates that consume a changed token, including awkward content and narrow layouts.

Record the affected items, rerun their checks and attach the result to the changelog. Approval should describe what was tested, not merely who liked the revision.

Hand Guidelines to Teams Without Losing Control

Order chapters by use: identity, colour, typography, components, templates and tone. Give each chapter an owner, version, date and changelog, with a concise rule, correct and incorrect examples, and downloadable assets.

Wecomeet built an internal design system for Depop with its brand team, bringing sixteen chapters of brand, product and partner guidelines into one searchable place. Searchability matters when someone needs a value during production.

  • Package the working files: Master logos, token exports, licensed font resources, components and templates.

  • Run a working handover: Include developers and internal teams, using actual production tasks.

  • Set maintenance responsibility: Schedule quarterly reviews and additional checks after new channels launch.

Wecomeet's Production & Implementation phase delivers digital and print assets, websites, e-commerce or product interfaces, brand guidelines and toolkits, and handover to development or internal teams.

Distribution needs maintenance too. NanoPIM's guidance on keeping marketplace images up to date is relevant when approved assets also live in product catalogues.

Retire obsolete examples, assign chapter owners and put the first review in the calendar before handover.

Wecomeet connects brand identity, UX/UI and production through guidelines, reusable components and practical handover toolkits. Visit Wecomeet to discuss a system that gives the team clear specifications, tested applications and named routes for change.