FCC Robocall Mitigation Database filing
FCC Robocall Mitigation Database: filing, annual certification and operating controls
A working playbook for U.S. voice and call-path providers. Use it to decide whether each legal entity must file, build a mitigation plan that reflects what your network actually does, submit the filing, and keep the response and renewal process ready for a regulator or carrier partner.
- Issuing authority
- Federal Communications Commission (FCC), Wireline Competition Bureau and Enforcement Bureau
- Timing
- Newly covered providers were required to file by February 26, 2024. Annual recertification is due on or before March 1; the first cycle was 2026. Keep a March 1 internal deadline well ahead of the FCC date. Update changed RMD information within 10 business days. Keep traceback staffing capable of a complete response within 24 hours. FCC announced a $10,000 base forfeiture for false or inaccurate RMD information and $1,000 for failing to update changed information within 10 business days, with continuing violations assessed daily up to statutory limits. As of the FCC’s January 2026 notice, its proposed $100 application fee was not yet effective; verify for the current filing cycle before budgeting.
- Reviewed
- Inside this guide
- 6 steps · 6 templates
Who it applies to
The filing obligation reaches voice service providers, gateway providers and non-gateway intermediate providers. It can include VoIP resellers, MVNOs, and independently qualifying affiliates or subsidiaries. A provider is not outside the rule merely because it leases facilities or cannot implement STIR/SHAKEN itself. Foreign providers that send calls using U.S. NANP numbers into U.S. networks also need an RMD filing for that traffic to be accepted. Determine status for each legal entity and each call-path role with telecom counsel; do not rely on a brand-level answer.
What you’ll produce
A signed, accepted and published FCC filing for every covered entity; a role-specific robocall mitigation plan supported by operating evidence; a complete ownership, contact, FRN and service record; a 24-hour traceback desk; and a controlled annual and change-triggered filing calendar.
The FCC’s February 2026 advisory specifically reminded MVNOs that resellers serving end users must file and describes the KYC processes expected in their plans. A filing must be accepted and published to count as appearing in the database. In DA 25-912, the FCC removed Ananya Traders after it failed to submit a required mitigation plan and cure its filing after notice and a 14-day order. The Commission said providers must stop accepting calls directly from a removed provider within two business days. In September 2025, the FCC also removed 12 voice providers for failing to respond to traceback requests. For perspective, the FCC estimated roughly 9,000 filings in its 2024 rulemaking and estimated about 75 minutes of agency staff review per filing. That is an agency workload estimate, not a provider preparation estimate or a current database count. The FCC’s $100 application fee was still not effective in its January 2026 notice. The September 2026 FCC document at the source link is a proposed rule, not a final rule; do not treat its proposed changes as current requirements unless the Commission adopts them.
Run the project
Go to the roadmapDecisions for leadership
- What applies to each entity, product and activity?
- Have Legal or Regulatory confirm scope and applicable deadlines for each entity, activity and jurisdiction. Assign owners for incident reporting, filings and lifecycle changes where required.
- Who will do the work and who can sign?
- Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
- Which deadlines can we promise?
- Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.
How to spend the first week
- Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
- Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts.
- Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
What to review each week
Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.
Kickoff brief to share with your team
Fill this in with your sponsor and send it to the people who own the work.
FCC Robocall Mitigation Database filing kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Decide which legal entities and call-path roles are in scope · Telecom regulatory counsel + Network architecture + Corporate secretary [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
- Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
- Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
- Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
- Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
How this works in practice
Two questions to check scope
- Which legal entities originate, gateway, carry, process or resell calls in the actual call path, and which of them independently meet a provider definition?
- Could the on-call team produce a complete, accurate traceback response from call records, upstream and downstream data within 24 hours, including weekends and holidays?
Worked scenario
A regional MVNO uses a hosted core, buys numbers from a carrier, and sells voice plans to consumers under two brands. Legal first maps the contracting entity and each affiliate. Network engineering traces which entity originates and routes traffic. Compliance opens one filing record per entity that independently meets a definition, verifies the business FRN and principal details, and confirms whether each entity has a separate filing obligation. The team documents customer onboarding, traffic analytics, upstream-provider review and escalation controls in the plan. Before submission, an officer reviews the certifications against evidence. After acceptance, operations checks that the filing is published, records the RMD number and schedules annual recertification, 10-business-day updates, and a staffed 24-hour traceback rota.
Official milestones
See the deadline calendar- Before providing a covered service
Complete entity-by-entity applicability and filing
Confirm all entities and roles; the filing only counts after FCC acceptance and publication.
Official reference (opens in a new tab) - Within 24 hours of a traceback request
Return a complete, accurate response
Test coverage around the clock and record the exact receipt and response times.
Official reference (opens in a new tab) - Within 10 business days after a relevant information change
Update the RMD and CORES records as applicable
FCC identified a $1,000 base forfeiture for missed RMD updates and a $10,000 base forfeiture for false or inaccurate information, continuing until cured and subject to statutory limits.
Official reference (opens in a new tab) - On or before March 1 each year
Officer recertifies that submitted information is true and correct
FCC’s first annual cycle was 2026. Confirm the current portal instructions, role-specific STIR/SHAKEN statements and any fee notice.
Official reference (opens in a new tab) - At a deficiency notice or FCC order
Calendar the cure response and preserve proof
A prior FCC removal order used a 14-day cure period. The exact response window depends on the notice and applicable current rule, so counsel should calendar the actual deadline immediately.
Official reference (opens in a new tab)
- 01Decide which legal entities and call-path roles are in scope, Telecom regulatory counsel + Network architecture + Corporate secretary, about 5 days
- 02Establish the filing identity and collect accountable-owner facts, Regulatory compliance + Finance/CORES owner + Corporate secretary + Privacy, about 7 days
- 03Build a plan that proves the controls are real, Robocall mitigation owner + Fraud operations + Network engineering + Vendor management, about 10 days
- 04Prove the controls and response service before attesting, Security operations + Fraud operations + NOC + Customer operations + Internal audit, about 14 days
- 05Obtain officer approval and submit through the FCC portal, Filing coordinator + Legal reviewer + Authorized corporate officer, about 3 days
- 06Run the filing as a live operational obligation, RMD owner + Regulatory counsel + Network operations + Executive sponsor, about 30 days
Step by step
Checklist, instructions and 6 templates.
View plan as a table
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Decide which legal entities and call-path roles are in scope | Telecom regulatory counsel + Network architecture + Corporate secretary | First; repeat after acquisitions, product launches, routing changes or new wholesale relationships | Set a start date | RMD entity and call-path applicability memo | Open |
| Establish the filing identity and collect accountable-owner facts | Regulatory compliance + Finance/CORES owner + Corporate secretary + Privacy | Before drafting the filing; allow time to verify every name and principal | Set a start date | RMD verified entity and contact register | Open |
| Build a plan that proves the controls are real | Robocall mitigation owner + Fraud operations + Network engineering + Vendor management | Draft only after the call-path and control owners are confirmed | Set a start date | RMD mitigation plan control-to-evidence register | Open |
| Prove the controls and response service before attesting | Security operations + Fraud operations + NOC + Customer operations + Internal audit | Complete before officer signature; repeat at least quarterly and after material changes | Set a start date | RMD traceback 24-hour response exercise | Open |
| Obtain officer approval and submit through the FCC portal | Filing coordinator + Legal reviewer + Authorized corporate officer | Initial filing before offering covered services; amendments as required | Set a start date | RMD officer certification and portal submission checklist | Open |
| Run the filing as a live operational obligation | RMD owner + Regulatory counsel + Network operations + Executive sponsor | Within 10 business days of changed RMD information; traceback within 24 hours; annual recertification by March 1 | Set a start date | RMD annual recertification and change calendar | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
- 01
Decide which legal entities and call-path roles are in scope
Draw the call path from customer to PSTN and back. For each hop, name the contracting legal entity, service provided, numbering resources, network control, origination/termination functions and upstream/downstream counterparties. Classify voice service, gateway and non-gateway intermediate roles under the current definitions. Test resellers and MVNO operations explicitly. Assess each affiliate and subsidiary separately. Write down borderline cases, assumptions and evidence, then obtain counsel approval. A service brand or parent filing does not automatically cover a distinct entity that meets the definition.
What to produce
RMD entity and call-path applicability memoDecision memo
Gather first
- Entity chart
- Voice products and number resources
- Call routing diagrams
- Carrier and reseller contracts
- Current FCC definitions
How to prepare it
- List every legal entity, product, brand and call-path role. Trace a sample call from customer to PSTN through each carrier and gateway.
- For each entity, record the rule definition tested, facts supporting the conclusion, possible affiliate or subsidiary filing, open legal questions and accountable reviewer.
- Have telecom counsel approve the conclusion and set a review trigger for acquisitions, new services, routing changes and new wholesale counterparties.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional applicability row
- Harbor Loop Mobile resells consumer voice service through a hosted core. The memo marks the reseller entity for review as a voice service provider, identifies the core host separately, and records the evidence needed to confirm whether each independently meets a definition.
- Decision record
- Legal signs the entity-by-entity conclusion and schedules a recheck before launch of international termination.
Check before handing it over
A second reviewer can follow the call path and understand why each entity does or does not have its own filing duty.
Give the approved matrix to the RMD coordinator and service launch gate.
- 02
Establish the filing identity and collect accountable-owner facts
Confirm the entity’s business-type FCC Registration Number in CORES and reconcile its legal and trade names, addresses, other names used, service description, operating roles, FRN, and any OCN. Gather contact information for the responsible robocall mitigation lead, principals, parent, affiliates and subsidiaries, plus U.S. registered-agent details where required. Review any relevant FCC or law-enforcement action or investigation within the lookback period. Restrict principal personal data to the filing team and authorized officers. Get written confirmation from each data owner; do not copy details from a sister company without checking.
What to produce
RMD verified entity and contact registerRestricted register
Gather first
- Legal entity records
- CORES business FRN
- Current and former business names
- Principal and ownership register
- Service and contact owners
How to prepare it
- Create one record per filing entity. Capture legal name, trade names, business FRN, business and mailing addresses, OCN if applicable, role, service description and source owner.
- Reconcile contacts, principals, parents, affiliates and subsidiaries with Corporate. Record when evidence was checked and limit access to personal information to the filing team.
- Route every change to the regulatory filing owner. Preserve the source and approval behind each field so an officer can attest to the filing without relying on memory.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional entity row
- Harbor Loop Mobile records its legal name, business FRN, consumer voice service, regulatory contact and parent. Corporate confirms the principal and registered-agent fields against current records.
- Fictional discrepancy
- CORES uses a former mailing address. The register flags it for correction and prevents the submission checklist from being marked ready until the filing owner resolves it.
Check before handing it over
Every public filing field has a current source, accountable owner, review date and approval trail.
Provide the restricted, reviewed entity packet to Legal and the officer before certification.
- 03
Build a plan that proves the controls are real
Write the plan around the provider’s role and actual traffic. Describe affirmative measures to prevent illegal calls, customer onboarding and renewal checks, identity and use-case review, volume or pattern analytics, alert thresholds, investigation and suspension authority, upstream-provider diligence, escalation paths and records retained. Identify internal and third-party analytics systems, what they detect, who reviews alerts, service coverage and known limits. Explain how the provider knows customers or upstream providers, as applicable. Map each statement to a system configuration, procedure, sample record, vendor commitment or operating report. Do not promise a control that is not implemented. Produce a machine-readable PDF and confirm the current portal format and size constraints.
What to produce
RMD mitigation plan control-to-evidence registerSpreadsheet
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.
Worked example
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.
Check before handing it over
Every material statement in the public mitigation plan is supported by a current control owner and evidence.
Provide the reviewed register to Legal and the authorized officer before the plan is signed.
- 04
Prove the controls and response service before attesting
Run a tabletop using a simulated traceback request. Start the clock at receipt, authenticate the request through the approved process, preserve it, identify the affected calls and upstream/downstream path, retrieve and validate records, resolve conflicting timestamps, approve the response and send it inside 24 hours. Include nights, holidays, supplier unavailability and escalation to counsel. Test customer and upstream review with sample records. Validate STIR/SHAKEN status separately for every role and IP network portion, including exemptions or extensions. Capture evidence, defects, owners and retest results. Maintain controls consistent with the filed plan, rather than treating the filing as a substitute for operations.
What to produce
RMD traceback 24-hour response exerciseExercise record
Gather first
- Traceback request procedure
- Call detail record sources
- Carrier contacts
- On-call roster
- Legal approval path
- Secure response channel
How to prepare it
- Start a timed exercise at receipt. Record requester validation, request scope, clock owner and the time each internal or supplier handoff begins.
- Reconcile call records across systems, identify missing fields and conflicts, document escalation and approval, and draft a complete response through the approved channel.
- Stop the clock only when the response is delivered. Record elapsed time, evidence quality, after-hours coverage, issues, corrective owners and retest date.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional timed result
- A simulated request arrives Friday at 6:20 p.m. The on-call lead starts the clock, the carrier liaison returns a routing record, and counsel approves the response before the 24-hour deadline.
- Fictional finding
- The backup carrier contact is stale. The operations owner updates the rota and schedules a weekend retest.
Check before handing it over
The team can produce and approve a supported traceback response within 24 hours, including on weekends and holidays.
Give the exercise findings to the executive sponsor and track remediation to closure.
- 05
Obtain officer approval and submit through the FCC portal
Have Legal reconcile every certification and disclosure to the approved evidence packet. Check that the filing is complete, truthful, signed by an authorized officer, and in English or accompanied by a certified translation where required. Confirm the plan is a machine-readable PDF. The filer needs a business FRN and current access using FCC multi-factor authentication. Submit through the FCC’s RMD portal, save the submission receipt and submitted version, and monitor for requests, pending status or rejection. Do not tell partners that you are listed until the filing is accepted and published; verify it in the public database and retain a dated screenshot or export.
What to produce
RMD officer certification and portal submission checklistChecklist
Gather first
- Approved entity matrix
- Verified business FRN and CORES record
- Mitigation plan PDF
- Principal and affiliate data
- STIR/SHAKEN evidence
- Current FCC instructions
How to prepare it
- Reconcile every field with a named source owner and mark the evidence date. Confirm the business FRN, names, addresses, contacts, ownership and call-path roles.
- Have Legal validate each statement and confirm that the officer is authorized to sign. Verify the mitigation plan is a machine-readable PDF and the filing is internally consistent.
- Submit through the FCC portal with MFA, save the receipt and version, monitor for follow-up, and confirm the listing is accepted and published before telling counterparties it is live.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional reviewer check
- The legal reviewer finds the brand name on a marketing page but not in the entity record. The filing coordinator confirms the trade name with Corporate before submission.
- Fictional completion evidence
- The coordinator stores the signed submission, portal receipt, published listing URL and verification timestamp in the restricted regulatory file.
Check before handing it over
The officer signs a fact-checked filing and the team can prove the FCC accepted and published it.
Retain the receipt and verified public listing with the entity’s recurring compliance calendar.
- 06
Run the filing as a live operational obligation
Route changes in legal name, address, principal, contact, ownership, role, service, STIR/SHAKEN status, mitigation controls or related FRN data to the filing owner immediately. Update FCC and CORES data within the applicable 10-business-day window. Maintain a 24/7 mailbox and escalation roster for traceback requests; log receipt, scope, data sources, response approvals, transmission and follow-up. Reconcile the published listing monthly against internal entity records and recertify annually by March 1. Check the current FCC fee status and annual filing instructions at each cycle. If the Commission contacts you about a deficiency, preserve the notice and calendared deadlines, engage counsel the same day, answer every issue and document the cure.
What to produce
RMD annual recertification and change calendarCalendar and change log
Gather first
- Current public filing
- CORES record
- Ownership and contact register
- Change management feed
- March 1 recertification date
- Traceback incident log
How to prepare it
- Set an internal recertification deadline before March 1 and assign field owners for names, principals, roles, status, plan controls and STIR/SHAKEN statements.
- Route each triggering business or service change to Regulatory within one business day. Record discovery date, required FCC and CORES action, accountable owner, due date, submission and receipt.
- Keep a 24/7 traceback rota and periodically test it. At each annual review, compare the complete internal record to the published filing and check FCC instructions for fee and form changes.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional annual row
- On February 1, Regulatory sends field attestations to Legal, Network and Corporate. The officer approves the reconciled filing by the internal deadline, ahead of March 1.
- Fictional change row
- A parent company changes its legal name. Corporate opens a change ticket, the RMD owner checks FCC and CORES fields, and the team records the update and receipt within the applicable 10-business-day window.
Check before handing it over
Annual truthfulness and update deadlines have named owners, reliable trigger sources and retained receipts.
Review overdue changes, upcoming certification and traceback readiness in the monthly compliance meeting.
Official sources
- 47 CFR § 64.6305, current rule text (opens in a new tab)
- FCC DA 26-72, filer FAQ and 2026 recertification notice (opens in a new tab)
- FCC Robocall Mitigation Database portal (opens in a new tab)
- FCC RMD filing instructions (opens in a new tab)
- FCC DA 26-174, MVNO enforcement advisory (opens in a new tab)
- FCC DA 25-912, Ananya Traders removal order (opens in a new tab)
- FCC 24-85, 2024 RMD Report and Order (opens in a new tab)
- FCC 26-49, September 2026 proposed rule. Proposals only. (opens in a new tab)