FCC Broadband Map Challenge: Filing One That Sticks

Ten business days, at the provider's standard installation charge. That is the whole of the claim sitting behind a green dot on the National Broadband Map, and the challenge form never puts that sentence in front of you while you are filling it in.

Which is why filings die at screening. The portal is genuinely usable — the link sits under the address in the Location Summary panel once the Fixed Broadband tab is selected at broadbandmap.fcc.gov. The hard part is that a challenge is a narrow assertion about a company's federal filing, and the box where you type is just a box.

What a green dot actually asserts

The FCC's own help text defines it plainly: service counts as available at a location if the provider has, or previously had, a connection in service there, or could initiate service through a routine installation within 10 business days of a request, with no extraordinary charges or delays attributable to extending the provider's network (How to Submit an Availability Challenge, last updated 15 May 2025, read 23 August 2026).

Everything about your filing follows from that. Not having service is not, by itself, the thing you are disputing. What you are disputing is a claim about what would happen if you asked. So the evidence the rule wants from a consumer is the asking: the date, the method, the content of your request and the provider's response, or evidence showing no availability at that location. If you have not yet turned the map pin into a request for service and a written answer, you do not have a challenge yet. You have a grievance.

Ten reason codes, and two of them are not challenges

The portal makes you pick one. The list, as the help article describes it:

1. Provider can connect the location, but not within 10 business days of a request.
2. Provider did not install the service at the agreed-upon date.
3. Provider requested more than the standard installation fee to connect this location.
4. Provider does not offer any service at this location, including with the selected technology.
5. Provider does not offer the selected technology for purchase, or reported the wrong technology.
6. The reported maximum advertised speeds are not available for purchase at this location.
7. Actual Speed Lower than Advertised.
8. No wireless or satellite signal is available at this location, or the service is oversubscribed in the area.
9. Provider needs to construct new, non-standard equipment to connect this location.
10. Missing Provider.

Number seven is the trap. It reads like the most honest description of what a lot of people are living with, and the help article says outright that submissions in that category are treated by the FCC as a consumer complaint, because the map reports availability rather than delivered performance. If that is the real problem, the tool is a week of logged tests and a complaint, not a map correction. Number ten does not create a challenge either — a missing provider is taken in as crowdsourced data, which under 47 CFR 1.7006(b) can trigger a verification inquiry but obligates the named provider to nothing.

Two more get mixed up constantly. Code nine is for satellite and fixed wireless construction costs; a wireline construction quote belongs under code three. And code eight covers a fixed wireless signal that is not there or a sector with nothing left to sell, which is the same phenomenon behind a covered address that gets refused at sign-up.

What the form asks, in the order it asks it

Seven steps, spread across tabs.

• Contact information. Name and email are required so that the FCC and the provider can reach you; phone is optional. You also state what type of filer you are. If that email has not been verified before, a link arrives by mail and the filing waits until you click it.
• Challenge, or feedback. The next tab offers "Challenge the selected provider" or "Just giving feedback." The second is not a softer version of the first — it is filed as crowdsource data, is not sent to the provider as a challenge, and starts no clock.
• Provider and technology. You select the provider whose reported service you are disputing, and its technology. The unit being challenged is that provider-and-technology row, so a company reported at your address under both fiber and fixed wireless is two separate decisions.
• Reason code, plus how you know. Each code opens its own follow-up fields, and there is a place to say where your information came from — the provider's website, a phone call, and so on.
• Evidence upload. This is Tab 4. Documents, screenshots, files.
• Privacy Act statement and certification. You tick a box certifying that, to the best of your actual knowledge, the statements of fact are true and correct. That certification is in the rule, at 1.7006(d)(1)(ix), not merely in the interface.
• Submit.

The evidence has to match the code you picked

The FCC published tips for bulk filers that are just as useful to one household, because reviewers apply the same logic to both. The blunt one: if you select one code and your evidence supports a different code, the submission will likely be rejected. Their own example is choosing "reported speed not available for purchase" and attaching an invoice that actually supports an excessive connection charge (How to Submit a Successful Fixed Availability Challenge, updated 22 October 2024).

The next tip is more encouraging. Evidence does not need to be elaborate — expensive site surveys are explicitly not necessary. Screenshots of a provider's order page, emails, chat transcripts, a copy of an installation quote, or a narrative giving the date and time of the request and what came back can each carry a challenge. What will not carry one is a single unsupported sentence saying there is no service here.

There is a reason the bar sits where it does for you specifically. Under 1.7006(d)(7) a consumer must make an initial showing by a preponderance of the evidence; under (d)(8) a government or other entity must show inaccuracy by clear and convincing evidence. The FCC's tips add that a local official filing individual submissions across a municipality is treated as a bulk filer and reviewed at the higher standard. Filing about the address you live at is the cheapest seat in this process.

Nothing starts until a person reads it

FCC staff screen the submission first, which the help center says can take up to a few days. Filings get rejected at that stage when they look like a quality-of-service or billing complaint, when they should have been a Location Challenge about the address record itself, or when the description or evidence is insufficient or unrelated to availability (What to Expect after Filing an Availability Challenge, updated 31 March 2025). Acceptance arrives as an email with a unique challenge ID.

After that, the clocks in 47 CFR 1.7006(d) (read 23 August 2026) take over:

Run the arithmetic on a filing accepted this week. The provider's reply is due in late October 2026. A denial pushes the resolution window into late December. If that ends without agreement, a decision inside the Commission's 90 days lands around late March 2027 — and that 90-day figure is statutory, from the Infrastructure Investment and Jobs Act at 47 U.S.C. 642(b)(5)(C)(i). The FCC confirmed in its June 2026 order that the deadline attaches to availability challenges and not to Fabric challenges (91 FR 37831, effective 24 July 2026). Throughout, the public map carries the rule's own label on your address: "in dispute/pending resolution."

Ten business days that belong to you

One deadline in this process is yours to miss, and it is short.

When a provider replies, it can record in the BDC system that it reached a "challenger concurrence" with you — that you agree with its response and the matter is settled. If you do not agree, you have 10 business days from the provider's Final Response date to say so. Sign in, open the Availability Challenge tab, check the box beside the challenge ID, and pick Dispute Concurrence from the Action menu. Disputing it sends the challenge to FCC adjudication instead of letting it close (How to View and Manage Location, Availability and Mobile Challenges, updated 24 March 2025).

That screen only exists if you hold an FCC user account created with the same email address you typed into the challenge form. A different address means no status, no withdrawal, no concurrence dispute. Make the account the day you file, not the day something goes wrong.

A correction attaches to one data vintage

Winning does not retire the question. Since 29 April 2026 there has been a separate filing track for putting removed coverage back: when a provider uploads and certifies availability data that includes a location taken off the map by a challenge, verification or audit, that upload creates a coverage restoration request, decided on infrastructure data rather than on your evidence (DA 26-630, released 26 June 2026). Nothing in it reopens the vintage you corrected. What it means is that your correction has a date on it, that a later filing round can put the same provider back at your address, and that the folder you built is worth keeping rather than deleting the week the challenge closes.

Availability challenges have no filing window, so file the day the evidence is in hand. The other kind does have one. If your problem is the address record rather than a service claim, that is a Fabric challenge, and DA 26-630 sets its cutoff at 1 September 2026 for review ahead of the December 2026 Fabric revision. The same notice closes the June 2026 provider filing window on that date, which is why the two dates land together.

The folder comes before the form

The filing takes twenty minutes. The week in front of it decides the outcome.

Ask each provider you intend to name for an installation date at published rates, and keep the answer in the shape 1.7006(d)(1)(v) asks for: when you asked, by what method, what you asked for, what came back. Screenshot the map with the address, provider, technology, advertised speeds and vintage label visible. Create the FCC user account under that same email. Then pick the one reason code your folder actually supports, file separately for each provider-and-technology row, and mark the sixtieth day in the calendar the hour your challenge ID arrives.