The date that matters most on a wireless application
A wireless application has two lives at a town hall. One is the planning review everyone expects: setbacks, design, notice, a hearing. The other is a federal deadline that starts the day the application is submitted, runs whether or not anyone has looked at it, and can only be paused in ways the rules spell out. Planners who treat the second as a detail of the first are the ones who end up explaining a missed date to council.
The good news is that the clock is mechanical. The categories are defined, the day counts are fixed, and the pause rules are specific. A town that classifies each application correctly on intake and writes the dates down the same day almost never misses one.
Where the clock comes from
Section 332(c)(7) of the Communications Act preserves local authority over the placement, construction and modification of personal wireless service facilities, with limits. A town may not unreasonably discriminate among providers of functionally equivalent services. It may not prohibit, or have the effect of prohibiting, the provision of personal wireless services. It must act on a request within a reasonable period of time. Any denial must be in writing and supported by substantial evidence in a written record. And it may not regulate placement on the basis of the environmental effects of radio frequency emissions when the facility complies with FCC emission rules.
The FCC has defined "a reasonable period of time" through presumptive deadlines, now codified at 47 CFR 1.6003. These are the shot clocks. They cover every authorization the town must issue before the facility can be built. The FCC's definition of authorization expressly includes zoning approval and building permits, so the clock is not just the planning department's clock. It is the town's.
The four clocks
The rule sorts every application into one of four categories based on two questions: is it a small wireless facility, and is it going on an existing structure or a new one?
| Application type | Presumptive period | Rule |
|---|---|---|
| Collocate a small wireless facility on an existing structure | 60 days | 47 CFR 1.6003(c)(1)(i) |
| Collocate any other facility on an existing structure | 90 days | 47 CFR 1.6003(c)(1)(ii) |
| Deploy a small wireless facility on a new structure | 90 days | 47 CFR 1.6003(c)(1)(iii) |
| Deploy any other facility on a new structure | 150 days | 47 CFR 1.6003(c)(1)(iv) |
Small wireless facility is a defined term in 47 CFR 1.6002. In short, it covers facilities on structures of 50 feet or less, or no more than 10 percent taller than adjacent structures, or that do not extend an existing structure above 50 feet or by more than 10 percent, whichever is greater. Each antenna must be no more than three cubic feet, and all other associated equipment no more than 28 cubic feet. The definition has further conditions, including that the facility does not require antenna structure registration and is not on Tribal lands. Read the full definition before classifying a close case.
Batching has its own rule. A single application for several small wireless facilities that all fall in the same category takes the period for one facility in that category. A batch that mixes collocations on existing structures with new structures takes 90 days for the whole application. The rule also says a town may not refuse to accept a batched application.
Classify on day one, in writing
The single most useful habit at intake is to write down the classification and the reason for it on the day the application arrives. "Small wireless facility, collocation on an existing streetlight pole, antenna volume per sheet A-2, equipment volume per sheet A-3, 60-day clock." That one line decides every later date.
The close calls are predictable. Is a replacement pole an existing structure or a new one? Does the equipment volume include the pre-existing equipment already on the pole? It does, by the definition's own terms. Is the tower being modified eligible for the separate track discussed below? When the answer is genuinely unclear, apply the shorter clock until the question is resolved. Being early costs nothing. Being late on a clock you guessed was longer costs the application.
Counting the days
The rule counts calendar days, starting the day after the application is submitted. Note the word submitted: the clock starts when the application is filed, not when staff decides it is complete. If the town requires a pre-application meeting or review, the rule counts that period too. If the last day falls on a federal holiday or a legal holiday in your jurisdiction, the shot clock date moves to the next business day.
Two practical consequences follow. First, the clock runs over weekends and through staff vacations, so the intake desk must log the date the application actually arrived, including electronic submissions that land after hours. Second, a pre-application requirement does not buy time. If your process requires one, the clock may already be running before the formal application exists.
Pausing the clock: the two incompleteness rules
The only unilateral way to stop the clock is a written notice that the application is materially incomplete. The notice must clearly and specifically identify the missing documents or information and cite the specific rule or regulation that requires them. A generic "application incomplete, see checklist" does not meet that standard.
The timing and the effect differ by application type, and confusing them is the most common error.
Small wireless facilities reset; everything else tolls
For an initial application for small wireless facilities, a compliant notice sent on or before the 10th day after submission resets the clock: it restarts at zero when the applicant submits everything the notice identified. For all other initial applications, a compliant notice sent on or before the 30th day after submission tolls the clock: the days between the notice and the complete resubmittal do not count. After a resubmittal, the town has 10 days to send a second notice that the submission still does not supply what the original notice listed, and that notice tolls the clock again. A written agreement between the town and the applicant can change these periods.
Read the last sentence of the resubmittal rule carefully. A second notice can only point to items the first notice asked for. A town that discovers a new missing item on the second pass cannot use it to stop the clock. This is why the first completeness review must be thorough, and why it should be done by whoever will do the technical review, not by a clerk with a generic checklist. The completeness notice is the only tool the town controls, and it works only if it is specific, cited and on time.
The 10-day window for small wireless applications is short. It includes weekends. A town that routes small cell applications to an outside reviewer needs that reviewer under contract and able to return a completeness screen within a few days, because a notice on day 11 has no effect on the clock at all.
What happens when the date passes
A town that fails to act by the shot clock date is presumed not to have acted within a reasonable period of time. The presumption is rebuttable, but rarely rebutted in practice. Under Section 332(c)(7)(B)(v), an applicant adversely affected by a failure to act may sue in any court of competent jurisdiction within 30 days, and the statute directs the court to hear and decide the case on an expedited basis.
For small wireless facilities, the FCC went further in its 2018 order. It treated a missed shot clock as a presumptive prohibition of service under Section 332(c)(7)(B)(i)(II), said the applicant would then have a straightforward case in court, and anticipated that courts would typically find injunctive relief warranted absent extraordinary circumstances. The FCC declined to make applications deemed granted when the clock runs out, so the remedy is a lawsuit, not an automatic permit. That distinction does not help the town much. Defending a missed date is expensive, and the likely outcome is a court order to issue the permits.
Acting means deciding. Denying an application within the clock is acting, but the denial must be in writing and rest on substantial evidence in the record. A denial issued on the last day without the findings to support it trades one problem for another.
The separate track: eligible facilities requests
Some applications are not on these clocks at all. Section 6409(a) of the Spectrum Act requires a town to approve an eligible facilities request, which is a modification of an existing tower or base station that does not substantially change its physical dimensions. Those requests run on a separate 60-day period under 47 CFR 1.6100, with their own tolling rules, and a request not acted on in time is deemed granted once the applicant gives written notice after the period expires.
Applicants usually say in the cover letter when they are filing under Section 6409(a). Your intake desk should still check every modification against the substantial change tests, because the deemed-granted consequence makes that track less forgiving than the Section 332 clocks.
Building an intake desk that never misses a date
The process below is built around one principle: every date is computed and written down the day the application arrives, and every later step is measured against those dates rather than against the planner's sense of how long things usually take.
Intake to Decision, Small Wireless Collocation on a 60-Day Clock
Illustrative schedule. The 60-day period and 10-day notice window come from 47 CFR 1.6003; the internal targets are ours and leave a buffer before the shot clock date.
Notice that the internal targets finish before the deadline. A hearing continued by one meeting, or a building permit that sits in another department, will consume any buffer you leave. Plan to finish the whole authorization, every permit included, five business days before the shot clock date.
The desk needs a short, fixed routine. These are the items that separate a town that never misses from one that misses once a year.
- A dated receipt for every submittal, including email and portal uploads, recorded with time of arrival
- The classification written on day one, with the sheet references that support it and the clock it triggers
- Every deadline computed at intake: notice deadline, shot clock date, holiday adjustment, internal targets
- A published submittal list in which every item cites the code section that requires it, so a notice can cite it too
- A notice template that forces the reviewer to list each missing item and its legal basis
- A single log shared by planning, building and public works, so every authorization is tracked against the same date
- A named backup for the intake planner and for the technical reviewer, so absences do not stop the clock work
- A written record of every tolling agreement, signed by both sides, with the new date stated
Where towns lose the clock
Waiting to start until the file is complete. The clock starts at submittal. A town that logs applications only after a clerk confirms completeness has already lost days it cannot recover.
A notice that is late, vague or uncited. A notice that misses the window, lists "additional information as needed," or does not name the rule requiring each item may not toll anything. Treat the notice as a legal document, because that is how a court will read it.
Forgetting the other permits. Planning approves on day 50 and the encroachment permit sits in public works until day 70. The clock covers every authorization, and the applicant will count from the original submittal.
Relying on informal extensions. An applicant's engineer saying "take the time you need" on a phone call is not a tolling agreement. Put any extension in writing with the new date, signed by someone with authority to bind the applicant.
A note on the rules themselves
The periods and tolling rules described here are those in 47 CFR 1.6003 as currently codified. The FCC opened a rulemaking in September 2025, WT Docket No. 25-276, that asks whether its wireless siting rules should change, including whether to revisit a deemed-granted remedy. Rules in this area have changed before through FCC orders and court decisions. Have your attorney confirm the current text when you set up the process, then check it each year when you review your submittal list.
Frequently asked questions
No. Under 47 CFR 1.6003 it starts the day after the application is submitted. Incompleteness is handled through a written notice that resets or tolls the clock, and only if the notice is sent within the required window and identifies each missing item and the rule that requires it.
Yes. The tolling rules apply unless a written agreement between the applicant and the town provides otherwise. Put any extension in writing, state the new date, and have both sides sign.
Not under the Section 332 shot clocks as currently codified. The applicant's remedy is a lawsuit, filed within 30 days, which courts hear on an expedited basis. Eligible facilities requests under Section 6409(a) are different: those can be deemed granted after the applicant gives written notice.
Yes. The FCC defines authorization to include any approval the town must issue before deployment, including zoning approval and building permits. Track every required permit against the same shot clock date.