
Accurate FRN data is essential for filing, fee payments, and regulatory communication, and non‑compliance can amplify penalties during FCC investigations, affecting broadcasters’ bottom lines.
The Federal Communications Commission’s latest amendment to the Commission Registration System (CORES) tightens the timeline for updating FCC Registration Numbers (FRNs). Adopted in a robocalling enforcement proceeding, the rule clarifies the previously ambiguous “promptly” standard by setting a ten‑business‑day deadline. While the steep $1,000‑per‑day fine targets illegal robocallers, the FCC signals that any entity with stale FRN data may face modest penalties if the lapse is discovered during another investigation. This shift reflects the agency’s broader push for cleaner, more reliable licensing records.
For broadcasters, the practical impact is immediate. Many stations maintain multiple FRNs across legacy CORES accounts, some tied to former employees or inactive entities. The new deadline forces a systematic review: verify contact names, titles, phone numbers, and email addresses; deactivate unused FRNs; and, where possible, consolidate records to preserve data integrity for ownership reporting. The CORES portal is notoriously slow, especially during peak update periods, so firms should budget extra time and consider contacting the FCC’s CORES help desk for manual assistance. Failure to act can complicate password resets and filing workflows.
From a risk‑management perspective, keeping FRN information current is a low‑cost safeguard against amplified fines. Accurate records ensure that the FCC can reach licensees promptly, reduce the chance of punitive add‑ons in unrelated enforcement actions, and protect against unauthorized access by former staff. As the FCC continues to evaluate other legacy filing requirements—such as the biennial ownership report—broadcasters should treat FRN hygiene as part of a broader compliance program. Proactive data stewardship now will pay dividends when regulatory scrutiny intensifies.
Comments
Want to join the conversation?
Loading comments...