Brand Drift Audit: Catching the Off-Brand Files
Objective: Given a mock list of 12 recently-published assets with their hex codes and fonts, apply the lesson's Brand Kit and single-source-of-truth principles to identify which assets drifted off-brand and why.
You've just joined Casper Sleep's marketing team. Nobody set up a Brand Kit before you arrived, and a stakeholder just noticed three shades of blue across last month's assets.
Audit 12 recently-shipped assets against the approved brand hex codes and fonts, flag every drifted file, and trace each drift back to a root cause from the lesson's Common Mistakes list.
Before you start
What you'll need
Free path (everything below is enough to finish)
Free, and every stakeholder can review the same evidence
The process
2 steps
Step 01 of 02
The lesson's Brand Kit setup locks a primary, secondary, and accent hex code so every new design pulls the right colors automatically instead of a designer eyeballing 'close enough' blue.
The approved primary hex is #1B2A4A. Of the 12 assets, 4 use a slightly different blue (#1C2E52, #1A2847, #24365E, and one using pure black #000000 for text that should be the brand navy). Which of these actually count as brand drift versus an acceptable variant?
Procedure
- List each asset's file name and the hex code actually used in it
- Flag any hex code that differs from #1B2A4A by more than a rounding error
- Separate 'wrong hex' drift from 'no Brand Kit was used at all' drift
Asset Hex used Approved Drift? Instagram_post_launch.png #1C2E52 #1B2A4A Minor drift Email_header_v3.png #24365E #1B2A4A Clear drift Pitch_deck_slide12.png #1B2A4A #1B2A4A On-brand
Healthy
Every asset traces back to the exact approved hex because it pulled from a shared Brand Kit, no manual re-entry, no eyeballing.
Unhealthy
4 of 12 assets show a visibly different blue because whoever built them typed a hex code from memory instead of pulling it from Brand Kit.
What this means
Brand drift is invisible file-by-file but obvious the moment 12 assets sit side by side, which is exactly why the lesson calls it invisible until you print a brochure that doesn't match the website.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| More than 2 of 12 assets show hex drift | Re-set the Brand Kit as the mandatory starting template for every new design, not an optional reference | 30 min |
Step 02 of 02
The lesson's Common Mistakes list warns that Canva and Figma brand kits live separately, so a hex code change has to be made in both on the same day or the tools drift apart from each other.
2 of the drifted assets came from Figma, not Canva, and both use a hex code that matches an OLD Canva brand color from before a rebrand. What does that pattern tell you about when the drift actually started?
Procedure
- Mark which tool (Canva or Figma) produced each drifted asset
- Compare file creation dates against the known rebrand date
- Confirm whether the Figma library was ever updated after the rebrand
Asset Source Date Matches old brand? Landing_page_mock.png Figma Post-rebrand Yes, old hex Web_banner_v2.png Figma Post-rebrand Yes, old hex
Healthy
Both tools' brand kits get updated the same day a color changes, verified by checking both libraries against the approved hex list.
Unhealthy
Canva's Brand Kit was updated after the rebrand but Figma's component library never was, so every Figma-sourced asset since then quietly carries the old color.
What this means
The 2 Figma-sourced drifted files aren't random mistakes, they're a single missed update that then repeats itself in every file pulled from that stale library.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| Drifted assets cluster by source tool and date rather than being scattered randomly | Update both tools' brand kits on the same day, then re-check both libraries a week later to confirm the sync held | 30 min |
Final deliverable
A 12-row brand drift audit flagging every off-brand asset, with each drift traced to either 'no Brand Kit used' or 'stale cross-tool library' as the root cause.
See a reference example
Warby Parker Q2 asset audit (excerpt) Asset Drift? Root cause Blog_thumbnail_003.png Yes No Brand Kit used, hex typed from memory Carousel_slide2.png No Pulled correctly from Brand Kit Dev_handoff_banner.fig Yes Figma library not updated after rebrand
Success criteria
You're done when you can:
- Correctly separates 'minor rounding' drift from 'clear drift' using the approved hex as the baseline
- Traces the 2 Figma-sourced drifts to a stale post-rebrand library rather than treating them as isolated mistakes