COPRSETR WORKSHEET
RMD mitigation plan control-to-evidence register
FCC Robocall Mitigation Database filing · Step 3 · Build a plan that proves the controls are real- Who prepares it
- Robocall mitigation owner + Fraud operations + Network engineering + Vendor management
- When to prepare it
- Draft only after the call-path and control owners are confirmed
Worked example
This example uses fictional details. Use the same fields with evidence from your work.
- Fictional analytics row
- The fraud lead records the alert for unusual outbound call volume, links the case to its review and disposition, and notes the vendor’s service window.
- Fictional evidence gap
- The plan says every new business customer is checked, but the sample has no result for one reseller. The owner blocks certification until the procedure and evidence trail are corrected.
Gather first
- Current RMD plan
- Customer and upstream-provider procedures
- Analytics configuration
- Sample alerts
- Incident and traceback procedure
- Vendor contracts
How to prepare it
- Break each plan statement into a control row. Capture role, risk, owner, system or procedure, frequency, evidence location, vendor dependency and last test date.
- Trace sample customer onboarding, renewal checks and upstream-provider reviews to dated evidence. For analytics, record signal, threshold, reviewer, disposition and escalation.
- Flag unsupported or aspirational claims. Assign an owner and due date, then revise either the plan or the operating control before officer certification.
Review
Every material statement in the public mitigation plan is supported by a current control owner and evidence.
Handoff
Provide the reviewed register to Legal and the authorized officer before the plan is signed.
Use the issuer’s current instructions and any required forms when you submit.
FCC RMD filer FAQ, DA 26-72 (opens in a new tab)