create-a-customer-proof-library

name	create-a-customer-proof-library
category	start
description	Govern reusable customer claims, quotes, stories, and evidence with clear permissions. Use when teams need searchable proof without losing source context, approval scope, confidentiality, expiry, or revocation.

create-a-customer-proof-library

Make proof reusable without turning one approval into permission for every future claim and channel.

Procedure

1. Define users, approved purposes, proof types, sensitive boundaries, systems, and accountable owner.
2. Inventory case studies, quotes, references, metrics, logos, recordings, reviews, and supporting source material.
3. For each item, record customer, claim, context, source, date, metric definition, evidence, approver, and confidence.
4. Record permission scope by wording, identity, logo, channel, geography, audience, edits, paid use, and expiration.
5. Separate raw confidential evidence from approved reusable excerpts.
6. Create taxonomy for audience, industry, use case, outcome, product, geography, date, and claim status.
7. Add review states for draft, verified, approved, restricted, expired, revoked, disputed, and archived.
8. Test search and retrieval using real requests, including a case that should not be returned.
9. Define reuse review, attribution, version, correction, renewal, withdrawal, and deletion workflows.
10. Audit a sample of published uses against the library and correct scope drift.

Guardrails

• Do not treat public customer identity as blanket endorsement permission.
• Never detach a metric from its definition, period, cohort, and limitations.
• Limit access to raw recordings, contacts, contracts, and confidential source files.
• Honor withdrawal and correct stale claims across downstream uses.

Done

• A proof library records source, claim, context, evidence, permission, status, and expiry
• Restricted and revoked items are excluded from ordinary retrieval tests
• Published-use sampling verifies scope and wording
• Ownership, renewal, correction, and deletion workflows are active