Toolbox

Component Inventory Audit

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

What it is

Purpose and scope.

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

When to use

Signals this is the right tool.

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

How to use

Minimum steps to get value quickly.

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

When NOT to use this

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

Grab the files and ship.

Keep the loop tight.