# RMD annual recertification and change calendar

FCC Robocall Mitigation Database filing | Worked example with fictional data

Step: Run the filing as a live operational obligation
Owner: RMD owner + Regulatory counsel + Network operations + Executive sponsor
When: Within 10 business days of changed RMD information; traceback within 24 hours; annual recertification by March 1

## 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
1. Set an internal recertification deadline before March 1 and assign field owners for names, principals, roles, status, plan controls and STIR/SHAKEN statements.
2. 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.
3. 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.

## Example

### 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.

## Review
Annual truthfulness and update deadlines have named owners, reliable trigger sources and retained receipts.

## Handoff
Review overdue changes, upcoming certification and traceback readiness in the monthly compliance meeting.

Official reference: FCC annual recertification and change update notice, DA 26-72
https://docs.fcc.gov/public/attachments/DA-26-72A1.pdf

Use the current rules and any prescribed forms for your engagement.
