Preparing for an FCC Audit: A Documentation Checklist
- Certificate issuance and renewal records, SPC token documentation, and RMD filing history are the core of what an audit would ask for.
- Records showing when signing was actually deployed — not just when a certificate was issued — matter just as much.
- None of this needs to be elaborate — a simple, consistently updated log is enough.
- The worst time to start building this documentation is after an audit request has already arrived.
- Keep a single running log of certificate issuance/renewal dates, SPC token history, RMD filing updates, and when signing actually went live on each OCN.
Compliance isn't just about having done the right things — it's about being able to show you did them if asked. A small amount of ongoing documentation makes that straightforward; starting from scratch after a request arrives does not.
What Gets Asked For
A compliance review typically wants to see: proof of an active, valid certificate for each OCN; SPC token documentation showing it's tied to your correct legal entity; your current and historical Robocall Mitigation Database filings; and evidence that signing is actually deployed on your network, not just that a certificate exists.
The Gap Between Issuance and Deployment
It's worth specifically documenting when signing actually went live on your infrastructure, separate from when the certificate was issued. These dates aren't always the same, and being able to show both closes a gap that's easy to otherwise leave ambiguous.
Keep It Simple
None of this requires sophisticated record-keeping. A single shared document listing certificates (with issuance and expiration dates), SPC token history, RMD filing dates, and signing deployment dates is enough. The goal is being able to answer questions quickly and accurately, not producing an elaborate compliance binder.
Start Now, Not Later
The providers who struggle most with a compliance review are the ones trying to reconstruct a timeline after the fact — digging through old emails to remember when a certificate was renewed or when an RMD filing was last updated. A few minutes spent logging these events as they happen avoids that scramble entirely.
Conclusion
Good documentation doesn't need to be complicated — it needs to be consistent. A simple running log, kept up to date as things happen, is the difference between a straightforward compliance review and a stressful one.
This article is provided for general informational purposes only and does not constitute legal or compliance advice. Consult a qualified attorney or compliance professional about your organization’s specific obligations under FCC rules and the STIR/SHAKEN framework.
Need a STIR/SHAKEN certificate?
Telonium is an approved STI-CA — request your first certificate today.