Brand Kit Templates: What a Usable Kit Contains and How to Keep It Current
The minimum files, colour specifications, and font license checks a brand kit template needs so it remains usable when handed to a non-designer.
Brand Kit Template Contents Maintenance: The Minimum That Actually Works
A brand kit template is not a folder full of logos. That folder is the reason print jobs fail, colours shift, and third parties produce materials that look like a different company. The usable kit is a set of production specifications, each one solving a failure mode that recurs in screen, print, or third-party implementation. Brand kit template contents maintenance means keeping those specifications current against the tools and standards that break when they are stale.
Graphic design is engineering with aesthetic consequences. The six files that follow cover every production context where a brand kit fails. SVG for screen. EPS for print. A spot colour reference. WOFF2 for web type. A PDF colour swatch sheet for soft-proofing. A one-page usage spec that states clear space in logo-relative units, not millimetres, so it works at any size. Everything else is decoration until those six are correct and current.
Minimum Viable Brand Kit Files: The Six That Cover Every Failure Mode
Screen failure: a logo saved as a PNG that looks soft on a retina display. Print failure: an RGB colour that shifts 15 percent toward magenta when converted to CMYK at the RIP. Third-party failure: a developer who receives a logo as a JPEG and cannot isolate it from its background. The six-file minimum eliminates all three.
SVG Logo Delivery Format
The SVG file is the correct delivery format for logos on the web. It is XML-based, resolution-independent, and supports embedded styling. A brand kit that contains only raster logos is a source-file failure. The SVG must include the viewBox attribute, no inline raster elements, and the font should be converted to paths unless the kit also supplies the WOFF2 file.
EPS Vector Master
The EPS vector master is the archival file. It preserves layers, spot colours, and editability for a print designer. Save it with spot colour references, not process builds, and embed the ICC profile for the intended output condition: PSO Coated v3 (FOGRA51) for European coated offset, GRACoL2013_CRPC6 for US sheetfed coated.
Spot Colour Reference
A spot colour swatch in the EPS is not optional. Process colour builds of a spot colour vary by output device, paper, and press. The physical fan deck is the only durable reference; the software library changed in 2022 when Adobe removed preloaded books. Include the spot colour number and the closest hex and CMYK values, but label them as approximations.
WOFF2 Web Font Performance Budget
The WOFF2 file is the web font format specified by the W3C in 2018. Include only the weights and styles the brand uses. A variable font with a full 100-to-900 weight axis is dead weight if the brand uses only Regular and Bold. Subset the font to the glyphs the content needs. A font with 400 glyphs covers Latin Extended; 200 glyphs may fail on common diacritics.
PDF Colour Swatch Sheet
A single-page PDF that shows every brand colour as a solid swatch, with its hex, RGB, CMYK, and spot colour values printed beside it. Print it under ISO 3664 D50 viewing conditions to verify the match. The file itself should be PDF/X-4, with the output intent profile embedded. This sheet is what the output provider uses to approve colour before the job runs.
One-Page Usage Spec
State clear space in logo-relative units: the height of the logo itself is the unit, so the rule scales. Safe area inside trim is 3 to 5 millimetres, specific to the output device. Bleed is 3 millimetres per the Ghent Workgroup standard. Typeface rights are stated explicitly: if the font is under the SIL Open Font License, the derivative font file clause applies if the font has been modified, and the license text must be included in the kit.
Brand Kit Version Control Process: How to Keep the Kit Current
A brand kit that is not versioned is obsolete on delivery. The brand kit version control process has three rules. One: every file name includes a date stamp in ISO 8601 format, YYYY-MM-DD. Two: the kit contains a changelog that records what changed, why, and who approved it. Three: the kit is stored in a single location that the team treats as the brand asset single source of truth. No duplicates in shared drives. No email attachments with final_v3 in the name.
The most common breakdown in version control is the font update. A brand switches from a static OpenType family to a variable font. The kit still contains the old TTF files. The new variable font has a weight axis from 100 to 900, but the rendering engine on the live site supports only the default position because the font-variation-settings declaration is missing. The kit must include a note about axis syntax and browser support. The durable principle: a font embedding permission is encoded in the OS/2 table of the OpenType file. The fsType bit determines whether the font may be embedded. That mechanism has been stable for two decades. Check the bit before distributing the font.
Brand Asset Single Source of Truth: Where It Lives and Who Updates It
The brand asset single source of truth is one location. Not a folder on a designer's desktop. Not a shared drive with duplicates. Not a Figma file that has been forked six times. It is a single repository, version-controlled, with a named owner. The owner is responsible for the brand kit template contents maintenance: updating colour values when an output provider changes its ICC profile, replacing font files when the foundry releases a revision, and checking that the SVG logo still validates against the W3C schema.
Who should own it? The person who is the only design-literate person in the room at a non-design organisation. That person needs external authority to cite when advocating for process. The WCAG 2.2 standard is one such authority: it specifies contrast ratios of 4.5:1 for normal text and 3:1 for large text and UI components. The kit must document which colour combinations pass and which fail. A palette that fails the 3:1 minimum on graphical objects is a liability, not an asset.
Brand Kit SVG Logo Specification: What the Vector File Must Contain
The SVG logo specification is a production requirement, not a design preference. The SVG file must be self-contained: no external stylesheets, no linked images, no fonts that are not converted to paths. The viewBox must match the logo's actual bounding box, with no extra white space. Validate the file against the W3C SVG schema before it enters the kit.
Raster-Only Logo: The Most Common Production Failure
A logo saved as a 72 PPI PNG that is upsampled to 300 PPI in the layout application still contains only 72 PPI of optical information. The metadata reports 300 PPI, but the effective resolution at final size is below 150 PPI. The result is a soft, pixelated logo on a business card. The only fix is to start with the SVG vector master and export from it.
Logo Lockup Variations and Naming
Include four logo lockup variations: full colour, reversed (white on dark), monochrome (single colour), and icon-only. Each lockup is a separate SVG file. The naming convention uses hyphens: brandname-logo-fullcolor.svg, brandname-logo-reversed.svg. The kit also includes the EPS master for print, saved with spot colours and the correct ICC profile for the output condition.
| Asset | Failed Kit | Complete Kit |
|---|---|---|
| Logo file | Raster PNG, 72 PPI | SVG plus EPS vector master with spot colour references |
| Colour specification | RGB only, no values given | Hex, RGB, CMYK, spot colour, HSL per swatch; ICC profile embedded in EPS and PDF |
| Font file | TTF without embedding check | WOFF2 subset to used weights, with fsType bit verified and OFL license text if applicable |
| Colour swatch sheet | Not included | PDF/X-4 with output intent profile, printed under D50 viewing conditions for approval |
| Usage spec | No clear space or safe area defined | Clear space in logo-relative units, safe area 3-5 mm, bleed 3 mm per Ghent Workgroup |
| Version control | No date stamp or changelog | ISO 8601 date stamp, changelog with reason and approver, single source of truth |
Brand Kit That Looks Complete but Fails: Raster Logo and RGB-Only Colour
A brand kit arrives. It contains a PNG logo, a JPEG version of the same logo, an RGB colour palette in a PDF, and a Google Fonts link. It looks complete to someone who has never sent a file to a commercial output provider. It fails in three ways.
First, the raster logo. The designer exports it from Canva at 72 PPI. The developer uses it on the website at 144 PPI for retina displays. The logo looks soft. The print designer places it in an InDesign layout at 300 PPI. The effective resolution at final size is below 150 PPI because the file was upsampled. The printed business cards show a blurry logo.
Second, the RGB-only colour palette. The brand colour is a bright blue that looks clean on screen. The output provider converts it to CMYK at export using a generic sRGB-to-CMYK conversion. The result is muddy and desaturated, shifted 15 percent toward magenta. The output provider blames the file; the designer blames the output provider. The problem is the absence of a CMYK specification with a named ICC profile. PSO Coated v3 (FOGRA51) for European coated offset. GRACoL2013_CRPC6 for US sheetfed coated. The kit has neither.
Third, the font. The kit links to Google Fonts, which distributes fonts under the SIL Open Font License version 1.1. The license allows embedding in a website. It does not automatically allow embedding in a SaaS tool that generates PDFs. That requires a server license the designer did not read. A brand kit that includes an OFL font as a design file must also include the license text, and the derivative font file clause applies if the font has been modified.
Corrected Kit: Vector Assets and Per-Medium Colour Specifications
The corrected kit contains the SVG logo with four lockup variations, each validated against the W3C schema. The EPS vector master includes spot colour references and the correct ICC profile. The colour specification provides hex, RGB, CMYK, HSL, and spot colour values for each colour, with a note that the screen values are sRGB IEC 61966-2-1 and the print values are ISO Coated v2 or GRACoL 2013. The font is supplied as a WOFF2 file subset to the weights and glyphs the brand uses, with the OFL license text included and the fsType bit verified for embedding. The PDF colour swatch sheet is saved as PDF/X-4 with the output intent profile embedded. The one-page usage spec states clear space in logo-relative units, safe area at 3-5 mm, bleed at 3 mm per Ghent Workgroup, and a warning about total ink coverage: keep TAC below 300 percent on coated stock and lower on uncoated.
SIL Open Font License: The Copyleft Condition You Cannot Ignore
The SIL Open Font License version 1.1, published in 2007, is the most common open license for brand fonts. It permits use, embedding, and modification, but it includes a copyleft condition: if you modify the font file and distribute it, you must distribute the modified font under the same license. A brand kit that includes an OFL font as a design file must also include the license text. If a designer has modified the font, the derivative font file clause applies. Rename the font file to distinguish it from the original.
The practical consequence: a brand kit that contains a modified OFL font without the license text is distributing a non-compliant file. The brand can be held liable if a third party uses the modified font and the original foundry pursues enforcement. Include the license text in the kit. Document any modifications in the changelog.
What to Do Next: Audit Your Kit Against These Six Files
Open your brand kit. Count the files. If you do not have an SVG logo, an EPS vector master, a spot colour reference, a WOFF2 web font, a PDF colour swatch sheet, and a one-page usage spec, your kit is incomplete. A raster logo where the SVG should be is a production failure waiting to happen. Replace every raster logo in your kit with the SVG vector master. Validate it against the W3C schema. Update the colour specification with per-medium values and ICC profiles. Then set a calendar reminder for three months from now to check that nothing has changed.
Common Questions
How often should I update the brand kit?
Update it when any production specification changes: an output provider switches ICC profiles, a font foundry releases a revision, or a platform updates its image dimensions. Check the kit quarterly against the live production files. A kit that has not been touched in 12 months is almost certainly stale.
What do I do if the output provider rejects my PDF/X-4 file?
Run the file through Acrobat's preflight with the PDF/X-4 profile. The most common breakdown is unflattened transparency or RGB images inside the file. The export preset name does not guarantee compliance; the preflight check does. Fix the violations in the source application and re-export.
Can I use a template from Canva as my brand kit?
Not for print. Canva uses an RGB-only colour model and does not support PDF/X-4 export, spot colours, or bleed beyond its own limits. The template is a starting point for screen use only. For print, rebuild the assets from the vector master in InDesign or Illustrator.
What is the single most important file in the kit?
The EPS vector master. It is the only file from which every other format can be derived. If the EPS is lost, the kit is broken. Store it in the single source of truth, version-controlled, with a backup. Every other file in the kit is a derivative of this one.