COMPLIANCE · Agency PLAYBOOK

The audit file: building the documentation system that saves your business

Updated 2026-10-16 · Sources & methodology noted inline

THE THESIS: every compliance rule in this library ultimately reduces to one operational question — can you produce the paper? The FTC's substantiation doctrine requires evidence before the claim; the review rule makes your knowledge the liability line; the endorsement rules make your disclosure history discoverable. Sellers who survive enforcement, platform audits, and payment-processor reviews share one trait: a maintained, dated, retrievable audit file. This article is the build spec for that file — the system that turns compliance from a performance anxiety into a file drawer.

THE SIX FOLDERS (MINIMUM VIABLE AUDIT FILE): (1) Claims substantiation — for every objective claim in active use, the supporting document (lab report, certification, test data you've read) with dates, filed by claim text so 'what supports this exact sentence' has a one-step answer. (2) Disclosure log — every disclosure you run (verbal scripts, pinned comments, platform toggle usage), dated, so a two-year-old stream's compliance is reconstructable. (3) Product compliance certificates — CPCs, test reports, supplier declarations, per SKU, refreshed on any spec or supplier change. (4) Pricing records — the dated screenshots behind every anchor, the price history behind every 'was', the real inventory figures behind scarcity statements. (5) Consent records — email/SMS opt-ins with timestamps and language versions. (6) Incident log — every claim, dispute, refund anomaly, and platform notice, with resolution. Six folders, one owner, one update rhythm.