BDC Coverage Restoration Filing Tutorial
Why It Matters
Timely, compliant restoration filings ensure providers can reclaim removed coverage on the national map, influencing funding, competition, and consumer access.
Key Takeaways
- •Providers must upload restoration data before next filing window opens.
- •Use reason codes and infrastructure files matching each technology type.
- •Final data checks flag errors; hard stops prevent certification.
- •FCC adjudicates each response, updating verified, pending, and failed counts.
- •Decertify option allows corrections before FCC final decision.
Summary
The video walks broadband providers through the BDC coverage restoration filing workflow, explaining how to respond to restoration requests generated after challenges, verifications, or audits. It emphasizes the strict deadline: providers must complete and certify their response data before the opening of the next biannual filing window, or the request becomes moot. Key steps include selecting a reason code, uploading a restoration‑code response file, and providing technology‑specific infrastructure files. Final data checks automatically flag inconsistencies; any hard‑stop errors must be resolved before certification can proceed. The interface tracks counts of locations submitted, pending, verified, or failed, and each response is adjudicated separately by the FCC. The tutorial demonstrates the process with both fixed‑line and mobile (hexagon) examples, highlighting how to export pending IDs, populate the response file, and attach supporting documentation. It also shows how to decertify a submission if the FCC has not yet rendered a decision, allowing providers to amend data before final adjudication. For providers, mastering this workflow is essential to restore broadband coverage on the National Broadband Map, maintain compliance, and avoid losing restoration opportunities. Accurate, timely filings directly affect map accuracy, funding eligibility, and regulatory reporting.
Comments
Want to join the conversation?
Loading comments...