# Claims Library

> A claims library is the database form of a claims matrix — approved claims stored as reusable, versioned objects linked to their evidence, with usage tracked across deliverables.

> A **claims library** is a [claims matrix](/glossary/claims-matrix/) grown up: approved claims stored as first-class, versioned objects — each linked to its substantiating evidence — rather than rows in a spreadsheet. The distinguishing capabilities are **reuse** (a claim is inserted into deliverables by reference, not retyped), **usage tracking** (the library knows every deck and document where each claim appears), and **lineage** (revisions are appended, never overwritten, preserving the audit trail).

Those three capabilities unlock the behaviors spreadsheets can't provide: when a claim is revised, every deliverable using it can be updated or flagged; when a claim is retired, its surviving appearances become findings automatically; when deliverable text drifts from the approved wording, the divergence is detectable by comparison rather than by a reviewer's memory.

Systems of record (e.g., Veeva Vault PromoMats) include claims-library modules at the organization level. Writer-side tools implement the same concept at the desk where claims are born — in [Claims](/), for instance, the library is the source of truth that deep-links each claim to its page/column/paragraph evidence and propagates revisions across Word and PowerPoint deliverables.

---
Source: https://medcom.claims/glossary/claims-library/ · Updated 2026-07-13 · © Mantir, Inc.