Brand guidelines for agencies, freelancers, and vendors should function as an operating system, not just a polished PDF. The document needs to explain what the brand looks like, sounds like, and does in the situations outside partners handle every day. For the broader context, explore our design services.
That means documenting core rules, showing realistic applications, providing usable assets, and defining how decisions are approved. The right level of detail depends on the work: a video production partner needs different guidance from a packaging supplier or a freelance social designer.
This guide outlines what to document, how to separate universal rules from project-specific instructions, and how to make guidelines practical across PDF, Figma, web, and asset-library formats. For the broader strategic role of a brand system, see the brand guidelines overview.
What agencies and vendors need from brand guidelines
External partners typically need answers to five questions:
- What is fixed? Core elements such as the logo, primary colors, type hierarchy, and essential voice rules.
- What is flexible? Areas where a partner may make design or editorial decisions within clear boundaries.
- What is the correct asset? Approved logos, fonts, templates, imagery, icons, and production files.
- How should the system be applied? Examples for the channels, formats, and audiences the partner supports.
- Who approves exceptions? A named owner, review process, and escalation path.
Without these answers, a brand book can be visually impressive but operationally weak. Partners fill gaps with assumptions, teams create conflicting interpretations, and internal reviewers spend time correcting preventable issues.
Document the brand system in layers
A useful guideline set usually has three layers. Keeping them separate makes the system easier to maintain and easier for a vendor to navigate.
1. Foundation
The foundation explains the brand’s central principles and non-negotiable visual and verbal assets. Include:
- Brand purpose, positioning, audience, and personality
- Logo family and approved variations
- Color palette with digital and print specifications
- Typography hierarchy and licensing requirements
- Core imagery, illustration, icon, and motion principles
- Voice, tone, terminology, and editorial conventions
2. Application
Application guidance shows how the foundation works in actual deliverables. Examples should reflect the work agencies and vendors are likely to produce, such as presentations, social graphics, email campaigns, websites, event materials, packaging, signage, sales documents, and paid media.
For each major application, explain what changes and what remains consistent. A social template may allow more variation in composition, while a legal notice, product label, or investor presentation may require stricter spacing, hierarchy, and accessibility controls.
3. Operations
The operations layer helps partners work with the system over time. Document:
- Where approved assets are stored
- File naming and version conventions
- Which file formats to use for common tasks
- How requests and reviews are submitted
- Who owns final approval
- How exceptions are recorded
- When the guidelines and asset library are reviewed
This operational layer is often what separates a reference document from a usable brand system.
What to document for each core brand element
Logo usage
Logo guidance should help a partner select and place the correct mark without asking for a custom answer each time. Include primary and secondary versions, minimum size, clear space, approved backgrounds, color treatments, and file formats.
Show common failure cases visually: stretching, rotating, recoloring, adding effects, placing the mark on low-contrast imagery, or combining it with unapproved symbols. If the logo has different lockups for digital, print, or narrow spaces, explain when each one applies. A separate guide on logo usage guidelines can support this section.
Color
List color values for the environments partners actually use: HEX and RGB for digital work, CMYK for print, and named spot colors when production requires them. Identify primary, secondary, accent, neutral, and functional colors.
Do not stop at swatches. Explain hierarchy, proportions, approved combinations, background use, and accessibility expectations. Include examples of text and background pairings that meet the organization’s contrast requirements, especially for websites, presentations, and digital advertising.
Typography
Specify the type families, weights, styles, hierarchy, alignment, and spacing principles. State which fonts are licensed, where they can be downloaded, and what substitutes are permitted when a partner cannot access the primary typeface.
Include practical examples for headlines, body copy, captions, labels, tables, and calls to action. If the organization uses different type systems for product interfaces, marketing, or editorial content, explain the relationship between them rather than presenting one rule set that does not fit every context.
Imagery, illustration, icons, and motion
Define the qualities the visual system should consistently communicate. For photography, cover subject matter, framing, lighting, color treatment, cropping, representation, and prohibited uses. For illustration and icons, document stroke, shape, scale, perspective, and level of detail.
For motion, include pacing, transitions, logo animation, sound considerations, and accessibility requirements such as captions or reduced-motion alternatives. A few annotated examples are usually more useful than a long list of adjectives.
Voice and editorial style
Voice guidance should translate brand personality into decisions a writer, strategist, or production partner can make. Include audience assumptions, preferred terminology, sentence style, point of view, capitalization, punctuation, and examples of language to use or avoid.
Distinguish voice from tone. Voice is the consistent character of the brand; tone changes with context. A product error message, executive announcement, sales email, and social post may share the same voice while using different levels of urgency or formality.
Make the guidelines specific to partner workflows
Not every partner needs the entire brand book in the same format. Create a dependable core system, then provide role-based tools.
| Partner | Most useful guidance | Helpful deliverables |
|---|---|---|
| Creative agency | Strategic rationale, visual principles, campaign flexibility, approval boundaries | Brand book, editable source files, campaign examples, review workflow |
| Freelance designer | Asset selection, layout rules, templates, file preparation | Quick-start guide, Figma library, templates, export specifications |
| Copywriter or content team | Voice, terminology, accessibility, editorial standards | Voice guide, terminology list, examples by channel |
| Print or packaging vendor | Color management, dimensions, substrates, production tolerances | Production specifications, artwork files, preflight checklist |
| Web or product team | Components, responsive behavior, accessibility, digital tokens | Design library, component documentation, code or token references |
This structure avoids two common problems: forcing every vendor to read irrelevant material, or creating disconnected mini-guides that contradict the central system.
Include application examples, not only rules
Rules describe intent; examples demonstrate judgment. Include good and bad examples for the highest-risk or highest-volume applications.
Useful examples may include a campaign layout, presentation cover, email header, social post, website section, event sign, product label, or sales one-pager. Annotate the examples briefly so a partner can see why the composition, image, color balance, or wording is approved.
Show responsive and production realities where relevant. A logo that works on a desktop website may need a different lockup in a mobile header. A color that looks accurate on screen may require a print conversion. A headline that works in a presentation may be too long for a paid social format.
Choose the right format: PDF, Figma, web, and asset library
Format is an operational decision, not merely a presentation preference.
- PDF: Useful for a stable reference, onboarding, procurement, and offline review. It can become outdated quickly if it is the only source of truth.
- Figma or another collaborative design file: Useful for components, templates, examples, and shared design work. Access permissions and library ownership need to be managed.
- Web-based documentation: Useful for searchable, frequently updated guidance and links to related resources. It requires clear navigation and change control.
- Asset library: Useful for distributing approved files, fonts, templates, and production assets. It should include ownership, metadata, and version status.
A practical system often combines these formats: a concise PDF for orientation, a searchable digital guide for current rules, and an organized asset library for execution. Make the relationship between them explicit so partners know which source controls when information conflicts.
Define governance and exception handling
Guidelines should not attempt to predict every possible use. They should explain how unusual situations are handled.
Assign an owner for the system and identify reviewers for visual, editorial, legal, accessibility, or production questions. Define what partners can approve independently and what requires escalation. A short request template can ask for the proposed use, audience, channel, deadline, relevant assets, and reason an exception is needed.
Record approved exceptions rather than relying on informal messages. If the same exception appears repeatedly, update the core guidance or create a reusable pattern. This keeps the system flexible without allowing one-off decisions to become undocumented precedent.
Build a vendor-ready handoff checklist
Before sending guidelines to an outside partner, confirm the following:
- The partner has received the current version and knows the effective date.
- Approved logos, fonts, templates, images, icons, and source files are accessible.
- File formats and export requirements match the intended channels.
- Color specifications distinguish digital, print, and production use.
- Accessibility requirements are stated with practical examples.
- Voice guidance includes terminology and channel-specific examples.
- Examples cover the partner’s actual deliverables.
- Reviewers, approvers, deadlines, and escalation paths are named.
- Confidential, licensed, or restricted assets are clearly marked.
- Old files and superseded guidance are archived or removed from active use.
Ask the partner to complete a small test assignment or explain how they would apply the system. This reveals ambiguous rules before a major campaign, launch, or production run.
Common mistakes to avoid
Writing for insiders
Internal shorthand and unexplained strategic language can confuse an outside partner. Define terms, show examples, and assume the reader understands design production but not the organization’s internal history.
Documenting only the ideal case
Partners work with limited space, incomplete assets, unusual formats, tight deadlines, and mixed media. Include guidance for constrained conditions instead of showing only perfect compositions.
Separating rules from files
A rule is difficult to apply when the required asset is buried in a separate drive or stored under an unclear name. Link each major rule to the relevant current asset or library location.
Letting the PDF become the source of truth
Static documents are valuable, but they should identify their version and point to current digital resources. Otherwise, vendors may continue using an outdated logo, typeface, or template.
Over-prescribing creative work
Detailed rules can protect consistency, but excessive restrictions can make every application look identical. State the objective and boundaries, then leave room for professional judgment where the context allows it.
A practical minimum viable guideline set
If the organization is starting from scratch, prioritize the information that prevents the most expensive or frequent errors:
- Brand purpose, audience, personality, and positioning.
- Approved logo files, clear space, minimum size, and misuse examples.
- Color specifications and accessibility guidance.
- Typography, licensing, fallback fonts, and hierarchy.
- Imagery and illustration principles with representative examples.
- Voice, terminology, and channel-specific writing examples.
- Templates or application examples for the partner’s actual work.
- Asset-library location, file naming, versioning, and approval ownership.
- Exception and update procedures.
Expand the system as new channels and partners reveal recurring questions. This is usually more effective than trying to document every possible use before the guidelines have been tested.
Putting the system into practice
Good brand guidelines make correct decisions easier for people who were not in the room when the brand was created. They combine principles with examples, current assets, production details, and a clear path for questions.
For a broader view of how guidelines connect to identity strategy, review the distinction between brand identity and its individual applications. You can also explore related implementation guidance for distributed teams and growing companies. When the organization is ready to define or strengthen the complete system, the brand guidelines service page provides the appropriate next step.
