# RMD traceback 24-hour response exercise

FCC Robocall Mitigation Database filing | Worked example with fictional data

Step: Prove the controls and response service before attesting
Owner: Security operations + Fraud operations + NOC + Customer operations + Internal audit
When: Complete before officer signature; repeat at least quarterly and after material changes

## Gather first
- Traceback request procedure
- Call detail record sources
- Carrier contacts
- On-call roster
- Legal approval path
- Secure response channel

## How to prepare it
1. Start a timed exercise at receipt. Record requester validation, request scope, clock owner and the time each internal or supplier handoff begins.
2. Reconcile call records across systems, identify missing fields and conflicts, document escalation and approval, and draft a complete response through the approved channel.
3. Stop the clock only when the response is delivered. Record elapsed time, evidence quality, after-hours coverage, issues, corrective owners and retest date.

## Example

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

## Review
The team can produce and approve a supported traceback response within 24 hours, including on weekends and holidays.

## Handoff
Give the exercise findings to the executive sponsor and track remediation to closure.

Official reference: FCC traceback and mitigation requirements, DA 26-174
https://docs.fcc.gov/public/attachments/DA-26-174A1.pdf

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