...

Design System Audit: When and Why You Need One

A design system audit is a structured review of the foundations, components, code, documentation and governance behind your digital products. You need one when your interfaces have started to drift: five shades of the same blue, three versions of the same button, developers rebuilding components that already exist, or a design system that nobody seems to use.

A good audit replaces opinions with evidence and ends with a prioritised roadmap. Below: the warning signs, what an audit covers, a design system checklist you can use yourself, and what a professional audit costs.

In short: A design system audit reviews how consistently your products use shared colours, typography, components and patterns, in both design files and code. It identifies duplicates, accessibility gaps and missing documentation, then prioritises fixes. You need one when the interface becomes inconsistent, delivery slows down, a redesign is planned or an existing system is not being adopted.

 

 

What is a design system audit?

 

A design system audit examines five layers of your product interface:

  • Design files: the Figma (or Sketch) libraries, styles, variables and components your designers use
  • Code: the component library, CSS and tokens your developers actually ship
  • Live product: what users really see across pages, apps and platforms
  • Documentation: the guidance that explains when and how to use each element
  • Governance: who owns the system, how changes are proposed and released

Each layer can be healthy on its own and still disagree with the others. The most common finding is drift: the Figma library says one thing, the code another, and the live product a third.

A design system audit is not the same as a UX audit. A UX audit asks whether users can complete their tasks; a design system audit asks whether the building blocks are consistent, reusable and maintained. The two often run together, because inconsistent components are a frequent cause of usability problems.

 

 

When do you need a design system audit?

 

These eight signs usually mean an audit is overdue:

  1. Visible inconsistency. The same action looks different on different screens.
  2. Duplicate components. Developers find it quicker to build a new modal than to find the existing one.
  3. Slow delivery. Simple features take weeks because every screen is designed from scratch.
  4. Design–code drift. Handover files no longer match what is in production.
  5. Accessibility complaints or legal exposure. Contrast, focus states or keyboard navigation fail in places. The European Accessibility Act has applied to many digital products and services since June 2025.
  6. A rebrand or website redesign is planned. Auditing first tells you what to keep and what to replace. Our guide on when to redesign your website lists the wider signs.
  7. Several products need to converge, after a merger, an acquisition or years of separate teams. Our guide to scaling a design system across multiple products covers what comes next.
  8. An existing system is not being adopted. Teams detach components or keep local copies.

If you have no design system yet, an audit still helps: it becomes the inventory you build from. Our article on when your company needs a design system helps you decide whether to go further.

 

 

Why is a design system audit worth doing?

 

Two Capital Foncier web pages designed by Morpheon, sharing the same navigation bar, typography and colour system
Capital Foncier: shared navigation, type and colours across page templates

An audit is a decision tool. Its value comes from five outcomes:

  • A shared fact base. Designers, developers and product owners stop arguing from impressions and look at the same inventory.
  • Clear priorities. Not every inconsistency matters. An audit ranks issues by user impact, frequency and effort.
  • Avoided costs. Every duplicated component is designed, built, tested and maintained more than once. Consolidating them reduces that work for every future release.
  • Reduced accessibility risk. Fixing a colour token or a focus style once in the system fixes it everywhere.
  • A realistic roadmap. The audit tells you whether you need a light clean-up, a rebuild of the component library or a full system. Our guide on how to build a design system picks up from there.

 

 

What does a design system audit cover?

 

Foundations and design tokens

Colours, typography, spacing, radius, elevation, grid, iconography and motion. The auditor counts how many unique values exist in design and code, checks whether they are stored as tokens or hard-coded, and compares them with the brand rules. If your brand guidelines define three blues and the code contains fourteen, that is the first fix. For Figma, see our Figma design system best practices.

Components and patterns

An inventory of every button, input, card, table, modal and navigation pattern, grouped by function. For each: how many variants exist, which ones are justified, and which are accidents. Patterns such as forms, empty states, errors and onboarding are reviewed the same way. Our comparison of a design system vs UI kit vs component library explains the vocabulary.

Code and implementation

How components are built in your web and mobile applications: is there a shared component library, is it versioned, do products use it or copy it, and do coded components match the design files? Technical debt in CSS and front-end frameworks shows up here.

Accessibility

Contrast ratios (WCAG asks for at least 4.5:1 for body text), focus states, keyboard navigation, touch target sizes, form labels and error messages, checked against WCAG 2.2 AA.

Documentation and governance

Is there documentation, is it current, and can a new developer use it without help? Who owns the system, how are new components proposed, and how are changes communicated?

Adoption and usage

What share of screens use system components, how often components are detached or overridden in Figma, and which teams work outside the system. Interviews with designers and developers explain the numbers.

 

 

Design system checklist: a template for your own audit

 

Use this design system audit template to run a first review. Score each line 0 (missing), 1 (partial) or 2 (in place), and note the evidence.

AreaQuestionScore (0–2)Evidence
TokensAre colours, type, spacing and radius defined as named tokens?
TokensAre the same tokens used in design files and code?
TokensDo token values match the brand guidelines?
ComponentsIs there one source of truth for each core component?
ComponentsAre all states documented (default, hover, focus, disabled, error, loading)?
ComponentsIs the number of variants justified and limited?
CodeIs there a versioned, shared component library?
CodeDo coded components match the design files?
AccessibilityDo colour pairs meet WCAG 2.2 AA contrast?
AccessibilityAre focus states visible and keyboard navigation complete?
DocumentationDoes each component have usage guidance and examples?
DocumentationIs the documentation updated with each release?
GovernanceIs there a named owner of the system?
GovernanceIs there a process to propose, review and release changes?
AdoptionDo all product teams use the system components?
AdoptionAre detached or overridden components tracked?

Out of 32 points: above 24, your system needs maintenance rather than repair; 12 to 24, plan a targeted clean-up; below 12, treat it as a rebuild or a first build.

 

 

How does a design system audit work, step by step?

 

  1. Scope. Agree which products, platforms and teams are included, and what decision the audit should support.
  2. Collect. Gather Figma libraries, repositories, documentation and screenshots of key journeys.
  3. Inventory. Catalogue foundations and components across design, code and the live product.
  4. Assess. Score each area against the checklist, test accessibility and interview designers and developers.
  5. Prioritise. Rank issues by user impact, frequency and effort to fix.
  6. Recommend. Deliver a report and a roadmap: quick wins, structural fixes and the target system.

 

 

How much does a design system audit cost?

 

Design system audit pricing depends on the number of products, platforms and components, and on whether code is reviewed as well as design. Indicative market ranges in Europe:

Audit scopeWhat it includesIndicative design system audit service cost
Light reviewOne product, design files only, checklist and recommendations€3,000–€5,000
Standard auditOne or two products, design and code, accessibility review, roadmap€5,000–€9,000
Multi-product auditSeveral products or brands, interviews, governance review, detailed roadmap€9,000–€12,000+

These are market ranges, not Morpheon quotes. What raises the price: more products and platforms, native mobile apps alongside web, a code review across several repositories, and detailed accessibility testing. If the audit leads to a build, our breakdown of design system cost shows what to budget next.

 

 

Should you audit your design system yourself or hire an agency?

 

A senior designer and a front-end developer can run a useful first pass with the checklist above. The limits are time, and objectivity: teams tend to overlook the inconsistencies they created.

An external audit makes sense when several teams or products are involved, when the result must convince leadership to fund a rebuild, or when no one in-house has built a system before. Our guide on how to choose a design system agency lists the questions to ask.

At Morpheon, our designers and developers audit design files and code together, so recommendations are realistic to implement. On the ESA Solar Eclipse Trilogy platform, branding, UX/UI and development were handled by one team, which is the kind of alignment an audit should aim to restore.

 

 

Frequently asked questions

 

How long does a design system audit take?

A light review of one product can take one to two weeks. A standard audit covering design, code and accessibility usually takes two to four weeks, and a multi-product audit longer, mainly because of interviews and the number of components to inventory.

What do you receive at the end of a design system audit?

Typically a component and token inventory, scores by area, an accessibility summary, a list of issues ranked by impact and effort, and a roadmap with quick wins and structural changes. The best reports also estimate the effort for each recommendation.

How often should you audit a design system?

A light check once a year keeps a healthy system on track, with a fuller audit before a redesign, a rebrand or a merger of products. Ongoing practices that reduce the need for audits are covered in our guide to design system maintenance.

Can you audit a product that has no design system yet?

Yes. The audit then works as an interface inventory: it catalogues the colours, type styles and components already in use, shows the duplicates, and becomes the starting point for defining tokens and a core component library.

Is a design system audit the same as a UX audit?

No. A UX audit evaluates whether users can complete their tasks easily; a design system audit evaluates whether the building blocks are consistent, reusable, accessible and maintained. They overlap, and many organisations run them together.

Who should be involved in a design system audit?

At minimum, a designer and a front-end developer, plus the product owner who will act on the results. Interviews with every team that uses the system, and a sponsor who can approve the roadmap, make the findings far more likely to be implemented.

 

 

Not sure where your design system stands?

 

We review your interfaces, Figma libraries and code, then give you a prioritised roadmap your team can act on.

Request a design system audit

Contact us

GDPR Agreement

We store and process your personal data only to respond to your request. You can withdraw your consent at any time. For more details, please consult our privacy policy.

Non-Disclosure Agreement (NDA)

Seraphinite AcceleratorOptimized by Seraphinite Accelerator
Turns on site high speed to be attractive for people and search engines.