Toolbox

Component Inventory Audit

Template for mapping what exists, what is missing and what drifts.

What it is

A spreadsheet template for auditing your component library against actual product usage.

When to use

Before roadmap planning or when leadership asks what the system covers.

How to use

Export all components: grep for export patterns, list unique component names with file paths
Cross-reference with design system: mark each In System / Partial / Missing / Duplicate
Score usage: count instances per component (High=10+, Medium=3-9, Low=1-2 surfaces)
Score drift: for components In System, count deviations from system (custom props, style overrides)
Prioritize: P1 = High usage + High drift, P2 = High usage OR high drift, P3 = Low both
Assign owners and next actions: Maintain, Extend, Create, Audit, Deprecate per component

Before you start

Prerequisites and when to skip this.

Prerequisites

You have a design system to audit against (even a partial one)
Codebase is searchable (not compiled/minified source)
Time allocated to act on findings (audit without action is waste)

When NOT to use this

No design system exists yet (you're auditing against nothing)
Already know the problem (skip audit, fix the known issues)
Team won't prioritize fixes (audit becomes shelfware)

Consider instead

Need quick visibility: Audit 3 highest-traffic pages, not entire codebase
Stakeholder wants audit but no fix budget: Fix one visible drift issue to demonstrate value first

Downloads

Component Audit Pack (ZIP)Component Audit template (accessible HTML)Component Audit filled example (accessible HTML)

Design Debt AuditAdoption Dashboard

The share link includes source tracking so LinkedIn traffic stays measurable in analytics.

Share on LinkedIn

Toolbox

Component Inventory Audit

Template for mapping what exists, what is missing and what drifts.

What it is

A spreadsheet template for auditing your component library against actual product usage.

When to use

Before roadmap planning or when leadership asks what the system covers.

How to use

Export all components: grep for export patterns, list unique component names with file paths
Cross-reference with design system: mark each In System / Partial / Missing / Duplicate
Score usage: count instances per component (High=10+, Medium=3-9, Low=1-2 surfaces)
Score drift: for components In System, count deviations from system (custom props, style overrides)
Prioritize: P1 = High usage + High drift, P2 = High usage OR high drift, P3 = Low both
Assign owners and next actions: Maintain, Extend, Create, Audit, Deprecate per component

Before you start

Prerequisites and when to skip this.

Prerequisites

You have a design system to audit against (even a partial one)
Codebase is searchable (not compiled/minified source)
Time allocated to act on findings (audit without action is waste)

When NOT to use this

No design system exists yet (you're auditing against nothing)
Already know the problem (skip audit, fix the known issues)
Team won't prioritize fixes (audit becomes shelfware)

Consider instead

Need quick visibility: Audit 3 highest-traffic pages, not entire codebase
Stakeholder wants audit but no fix budget: Fix one visible drift issue to demonstrate value first

Downloads

Component Audit Pack (ZIP)Component Audit template (accessible HTML)Component Audit filled example (accessible HTML)

Design Debt AuditAdoption Dashboard

The share link includes source tracking so LinkedIn traffic stays measurable in analytics.

Share on LinkedIn

Component Inventory Audit

What it is

When to use

How to use

Before you start

Downloads

Related

Component Inventory Audit

What it is

When to use

How to use

Before you start

Downloads

Related

What it is

When to use

How to use

Before you start

Downloads

Related

Share this resource

What it is

When to use

How to use

Before you start

Downloads

Related

Share this resource