Proof Library Structure
Standardize a reusable Proof Library to power Results pages (case studies, hubs, feature pages), with claims-safe usage rules and schema-ready metadata.
Scope + Principles (Non-Negotiables)
Claims-safe by default
no guarantees (rankings, bookings, revenue) and no medical advice.
Consent-first
publish only proof with documented approval and defined usage rights.
Anonymize by default
named proof requires explicit written approval.
Accessibility
every proof asset must support alt text/captions and non-color-dependent meaning.
Reusability
assets must be linkable to multiple entities (case study, region, segment, growth system).
Asset types (minimum set)
Client logo
(approved brand mark) — optional, named-only.
KPI metric
(numbers + definitions + methodology) — ranges preferred when uncertainty exists.
Screenshot
(analytics/CRM/call tracking/ads dashboards) — redact personal data; include caption + time window.
Testimonial
(text/video) — with attribution level controls (named, role-only, anonymized).
Media
(photos/videos) — only if rights + consent are explicit; avoid patient-identifying content.
Canonical folder model (storage / CMS)
Recommended canonical paths (mirror in cloud storage and CMS media library):
/proof//proof/logos//proof/metrics//proof/screenshots//proof/testimonials//proof/media//proof/redacted-originals/ (restricted access; never public)/proof/archive/ (expired or replaced assets)Naming convention (files + CMS slugs)
Format (use hyphens; avoid spaces):
mds-proof_{type}_{client-or-anon}_{region}_{segment}_{system}_{yyyymm}_{v##}Examples:
mds-proof_metric_anon_canada_multi-specialty_ai-growth-system_202601_v01mds-proof_screenshot_anon_usa_dental_patient-acquisition_202512_v02mds-proof_testimonial_named_europe_hospital_ai-suite_202511_v01Core metadata schema (required fields)
Every asset must store the following fields (CMS + storage manifest):
Asset ID
(immutable) + Asset type
Visibility
Public (named) | Public (anonymized) | Gated (request) | Internal only
Client identity controls
show/hide client name, logo, location, clinician names
Consent status
approved / pending / rejected (with approver + date + notes)
Usage rights
scope (web, ads, sales), territories, expiration date, revocation handling
Time window + methodology notes
(for metrics/screenshots)
Data source
(e.g., GA4, CRM, call tracking) and evidence link (restricted if needed)
Alt text
(EN/AR) + caption (EN/AR) + redaction notes
Tags
region, segment, specialty, growth system, channel (SEO/PPC/WhatsApp/voice), funnel stage
Version
+ supersedes/replaces relationships
Redaction + privacy requirements
Privacy Compliance Required
All published proof assets must comply with these redaction rules:
- Screenshots must be redacted: phone numbers, emails, patient names, IDs, appointment details, chat transcripts with PII.
- Do not publish patient-identifying images. Avoid clinician faces unless consented and legally cleared.
- Prefer aggregated views. If small-sample data risks re-identification, gate or omit.
- Store unredacted originals only in restricted folder; publish only redacted derivatives.
Component mapping (how proof appears on site)
Proof assets should be rendered via consistent UI components:
Proof Card
(default): asset thumbnail + caption + tags + disclosure line.
Metric Strip
1–3 KPIs with definitions + timeframe + 'results vary' disclaimer.
Testimonial Block
quote + attribution level + optional audio/video + consent stamp (internal).
Screenshot Lightbox
opens redacted image with full caption + methodology + source tag.
Proof Pack CTA
gated request module to access private/extended assets.
Implementation Spec (CMS Model + Filters + Search)
Data model (recommended collections)
ProofAsset
(core) — all asset types share a single collection; asset_type controls rendering.
ProofTag
(controlled vocabulary) — regions, segments, growth systems, specialties, channels.
ConsentRecord
— approval artifacts + scope + expiry + revocation.
ProofPackRequest
— gated access workflow (optional).
Filter logic (for Results Hub + Case Studies)
Primary filters
Region • Segment • Growth System.
Secondary filters
Specialty • Channel • Funnel stage • Asset type • Visibility.
Default view
anonymized/public assets only; named assets appear only when consent_status=approved and visibility allows.
Sort order
newest approved first; allow 'Most used' and 'Most relevant' (based on tags + page context).
Gating model (private proof)
- Gated assets are not indexed publicly; only visible after request approval or via sales enablement flows.
- Gating trigger: 'Request Proof Pack' CTA (on Results Hub, case studies, and selected AI Suite pages).
- Approval workflow: auto-email internal team + CRM task creation; response SLA defined by ops.
- If user is not approved, show an anonymized alternative (same tags) where possible.
Analytics Instrumentation (Events + Dimensions)
Required events
proof_filter_change (properties: region, segment, system, asset_type, visibility)proof_asset_view (properties: asset_id, asset_type, context_page, visibility)proof_asset_expand (properties: asset_id, source='lightbox')proof_pack_cta_click (properties: context_page, selected_filters)proof_pack_submit (properties: form_variant, lead_type, consent_ack=true/false)proof_asset_download (gated only; properties: asset_id, approved=true/false)Governance metrics
- Approval lead time (submit → approved)
- Expired assets count and replacement rate
- Top assets by usage and by assisted conversions
- Named vs anonymized publication ratio (should skew anonymized unless explicitly approved)
QA Checklist (Triple Check)
Frequently asked questions
Ready to implement the Proof Library?
Contact our development team to set up your Proof Library structure, CMS collections, and analytics instrumentation.
Summary for LLM / GEO extraction
Structured summary optimized for AI assistants and search engines
Proof Library Structure — MDS Healthcare Results System
SSOT for reusable proof assets (logos, KPIs, screenshots, testimonials, media) with claims-safe rules, consent tracking, and schema-ready metadata. Supports anonymized-by-default publication, gated access workflows, and multi-entity linking (case study, region, segment, system).
Core structure: /proof/ folder taxonomy with redaction protocols, naming convention (mds-proof_{type}_{client}_{region}_{segment}_{system}_{date}_{version}), and required metadata (Asset ID, visibility, consent status, usage rights, time window, data source, alt text, tags, version).
Component mapping: Proof Card, Metric Strip, Testimonial Block, Screenshot Lightbox, Proof Pack CTA (gated request module).
Implementation: ProofAsset collection (CMS), filter logic (region/segment/system), gating workflow, analytics instrumentation (6 core events), QA checklist (metadata, redaction, consent, visibility, schema, events).