How Long Does Small Cell Permitting Take in 2026? Shot Clocks, Reviews, and Delays

The permit date shown on a wireless schedule often mixes several decisions that do not share one authority. A local government may be reviewing land use or right-of-way work while a utility evaluates attachment conditions, an owner reviews structural information and the applicant closes completeness comments. Calling all of that one clock hides the real dependencies.

This guide separates the official FCC shot-clock framework from Draftech's planning controls. It does not promise approval by a universal date, and jurisdiction-specific procedures, agreements, tolling, utility work, and other required authorizations remain controlling.

How Long Does Small Cell Permitting Take Under the 60-Day and 90-Day Shot Clocks?

How long does small cell permitting take? The FCC identifies 60-day and 90-day shot clocks for government action on covered small wireless applications: 60 days for collocation on preexisting structures and 90 days for new builds. These are action clocks, not guaranteed permit issuance dates or complete deployment durations.

The named authority is the Federal Communications Commission. Its 2018 wireless infrastructure fact sheet describes the 60-day collocation clock and 90-day new-build clock. We use those official numbers only for the government-action framework they describe, never as a promise that every required review or construction release ends on the same date.

We plan a program through 5 control stages: intake and completeness, jurisdiction action, owner or utility coordination, comment closure and construction release. That five-stage structure is Draftech guidance, not an industry measurement. It helps a team assign evidence and authority to each decision rather than stretching the FCC number over work the shot clock does not control.

How Long Does Small Cell Permitting Take on a Project Schedule?

The honest schedule is a site-specific decision map. We identify structure type, jurisdiction, right-of-way authority, pole or asset owner, application path, completeness rules, utility engineering, required agreements, permit comments and final release conditions. If a required authority is absent from the map, the forecast is incomplete even when one visible permit has a target date.

A complete application matters because tolling and completeness procedures can affect how the clock runs. We do not invent a standard completeness duration or comment count. The controlling FCC rules, local procedure, and applicable agreement determine the actual treatment. Our work is to preserve submission evidence, notices, responses, and dates so the team can tell which clock is active and why.

Draftech performs small cell engineering, pole analysis, design and permitting support in-house. For programs that need design and permit evidence held together, our small cell design services connect the site package to its review path. Full turnkey construction is delivered through Draftech-managed subcontract crews under our QA/QC and safety oversight.

Authority contact records should remain attached to the decision they support. We identify the reviewing organization, submission channel, application identifier, current status, and source document rather than relying on an individual's inbox. This is Draftech record guidance, not a public processing statistic. It keeps staff changes from erasing the evidence needed to explain a classification, notice, comment or release condition.

Separate the authorities. Separate their clocks. Never imply approval.

Separate Jurisdiction Review From Utility and Pole-Owner Work

A jurisdiction and a pole owner can evaluate different rights and risks. The jurisdiction may control land use, right-of-way occupation, aesthetics or construction permits. A utility or other asset owner may control attachment, structural review, make-ready, access and agreements. We track those workstreams separately even when the same drawing set supports both.

That separation prevents a common scheduling error: marking a site permitted when only one authority has acted. A local permit does not itself prove that the pole owner has accepted the attachment or that required make-ready is complete. An owner approval does not itself grant every local construction authorization. The actual release depends on the required authorities for that site.

Structure type also matters to the FCC framework. The official fact sheet distinguishes covered collocation on a preexisting structure from a new build, which is why the named clocks differ. We preserve the classification basis in the site record rather than choosing a clock from the schedule pressure. Classification and completeness must follow the controlling rules and facts.

Pole loading and attachment evidence can become a separate gate. Our small cell pole loading requirements guide explains why structure data, proposed equipment, owner criteria and make-ready dispositions must agree. We do not assign a universal utility review duration because owner queues, requirements, agreements and field conditions vary.

Parallel work is useful only when dependencies are explicit. We may prepare local and owner packages together, but we identify which change to one package must flow into the other. A revised mounting configuration can affect structural review, aesthetics, drawings and the final construction set. Running tracks in parallel cannot mean allowing their technical assumptions to diverge.

The distinction between small cells and other wireless facilities can also affect the path. Our small cell versus macro cell comparison provides the technology context, while the permitting team still applies the actual jurisdiction and owner classifications. Marketing labels do not determine which authority, application or clock controls.

Control the submission record. Dates need evidence. Comments need owners.

Control Completeness, Tolling, Comments, and Resubmittals

Completeness begins with the receiving authority's current requirements. We build a site matrix for required forms, drawings, structural or pole information, photographs, ownership evidence, right-of-way details and other listed items. This matrix is Draftech planning guidance, not a substitute for the jurisdiction's checklist. Every required item needs a source, status and responsible reviewer.

Submission evidence includes the exact package, delivery method, receipt and any completeness notice. Those records matter when a team evaluates tolling or response dates under the controlling process. We avoid characterizing silence as approval or inventing a start date from an internal milestone. The record should show what the authority received and how the applicable rules treat it.

Comments enter one log with the issuing authority, affected site and documents, required response, owner, status, resubmission and disposition. We distinguish a clarification from a technical revision. A response is not closed merely because engineering uploaded a new file; closure requires the receiving authority's process to recognize the accepted response or next status.

Revisions need cross-package control. A moved node, changed equipment arrangement, revised pole result, or altered work area may affect local drawings, owner submissions, traffic controls and construction documents. In-house engineering evaluates design effects, while permitting coordination confirms that every affected authority receives the accepted revision. One stale package can invalidate an otherwise clean site record.

We do not promise that a complete package receives no comments. Completeness and technical acceptance are different decisions. The practical goal is to remove avoidable ambiguity, answer listed requirements with traceable evidence, and keep responses synchronized. That gives the project a defensible schedule record without turning the FCC shot clock into a guarantee it was never designed to be.

Batching can improve administrative control only when site differences remain visible. We can submit common forms or drawing conventions across a portfolio, but each location still needs its structure facts, authority path, owner status, notices, comments and release evidence. A batch response should never overwrite a site-specific condition. Our QA review samples common records and examines every identified exception before reporting status.

Build from gates. Portfolio averages hide blockers. Site records do not.

Build a Site Timeline That Does Not Treat the Shot Clock as Approval

A useful site timeline shows separate gates, not one percentage-complete bar. We display intake, completeness status, applicable government-action clock, owner or utility review, comment closure, required agreements, permit issuance, make-ready status and construction release. The exact fields depend on the program. Draftech's five-stage grouping is guidance for visibility, not a standard approval model.

Dependencies should be tied to decisions. If pole-owner approval is required before final local drawings can be accepted, the schedule should say so. If a jurisdiction review can proceed while owner engineering is open, the parallel relationship should be visible along with the revision risk. We avoid false precision because an unsupported finish date is not better project control.

Program managers also need site-level exceptions. A portfolio total can hide a missing easement, incomplete pole record, owner comment or construction permit at a specific location. We keep the site identifier, blocking authority, required evidence, responsible party and next decision together. Those fields are Draftech guidance and can be mapped to the owner's reporting system.

Cost planning should not create invented permit prices or universal durations. Our small cell fiber backhaul guide keeps cost drivers separate from guaranteed timelines. Here, the schedule should identify work and authority, not convert an unverified queue or potential resubmittal into a public statistic.

The recommendation is direct: report the FCC 60-day and 90-day clocks only for their covered government-action context. Report owner review, utility work, agreements, revisions and construction release as separate workstreams. Combining them may produce a simpler dashboard, but it makes the forecast less accurate and obscures which party can actually move the next decision.

Schedule updates should explain movement. We record the source event, affected gate, responsible authority and consequence for dependent work. That method does not predict how long an external queue will take. It gives decision-makers a defensible reason for the current forecast and shows whether engineering can act, an authority must respond, or the program must revise sequencing around an unresolved site.

A clock can expire. Release still needs authority. Check every source.

A candid limitation of our authority-matrix method is that it improves forecast honesty without making a jurisdiction or pole owner move faster; the record can identify the blocker, yet the approving party still controls its decision. No dashboard fixes that. Our in-house engineering model keeps responses coordinated without promising someone else's date. The matrix earns its keep when a portfolio forecast looks healthy while one site remains blocked by a completeness notice whose response has not reached the pole owner. A program manager should be able to open that row and identify the controlling authority plus source document without asking several teams to reconstruct the submission history. That visibility supports honest sequencing because dependent construction work stays unreleased until the named decision arrives through the channel defined for that specific site record. It also prevents a federal review context from becoming a blanket promise about attachment agreements or utility work that follows an entirely different authority and evidence path. When a revised mounting detail touches both packages, the same site row should show who reviews the local exhibit and who decides whether the owner submission must change.

Release Construction Only When Every Required Authority Agrees

For a single-authority site: use a focused permit path when the owner record is complete and no separate attachment or utility decision blocks construction release. For a multi-jurisdiction portfolio: maintain one site matrix that separates the FCC context from local review, pole-owner action, utility dependencies, comment closure, and the final construction authority for every location.

A permit is not the only release artifact. The site may also require owner acceptance, an attachment agreement, completed make-ready, right-of-way authorization, a construction permit, traffic control approval or another project-specific condition. We do not claim that every site requires the same stack. The controlling jurisdiction, asset owner, contract and approved site matrix define it.

The construction set must match the accepted permit and owner decisions. Before release, we compare site identity, structure, equipment arrangement, mounting details, work limits, notes, revision and open conditions across the approved records. Any mismatch returns to the responsible authority. A crew should never be asked to choose between a permit sheet and an owner-approved attachment drawing.

Release evidence should be retrievable at mobilization. We recommend one site packet or controlled index that points to the accepted permits, owner documents, construction issue, restrictions and open conditions. This is Draftech field guidance rather than an industry format rule. The contractor's approved safety planning and work controls remain separate requirements, but their applicable authorities must agree with the released scope.

Draftech performs engineering in-house and offers full turnkey wireless construction through Draftech-managed subcontract crews under our QA/QC and safety oversight. That model is not management-only, and it is not a claim that all physical work is self-performed today. Our small cell engineering workstream keeps accepted design and field release aligned.

For simple sites with one clear authority and no separate owner work, a focused permit consultant may be enough. For multi-authority portfolios, our recommendation is unhedged: use a site record that separates every clock, decision, revision and release condition. The complexity exists whether the dashboard displays it or not. Hiding it only postpones the conflict until mobilization.

Closeout should preserve the final authority chain after construction as well. Approved changes, inspections, and installed records need the same site identifier used during permitting so operations can understand which authorization supported the work. We do not assume that permit issuance ends every documentation obligation. The contract, jurisdiction, owner, and accepted closeout requirements determine which records remain due after field completion.

Our final release check asks whether a new coordinator can identify every open authority and source record without reconstructing the history from email. That is Draftech guidance, not an industry timing measure.

If your program has uncertain clock starts, mixed owner reviews, or packages that drift during resubmittal, email info@draftech.com. We can review the authority map, engineering inputs, and release logic without promising a date that belongs to a jurisdiction, utility, pole owner or other approving party.