The $5,000 Permit Problem: What FBA's New Study Means for Your Fiber Build Schedule
Mission-ready means a fiber project has more than crews, materials, and a construction plan. It has permits assigned to owners, deadlines built into the schedule, and a clear path to resolve delays. That discipline matters because permitting is now one of the most consequential variables in fiber deployment, not background paperwork.
A new Fiber Broadband Association (FBA) and Cartesian economic analysis finds that certain state and local permitting practices can make wireline deployments economically unviable. FBA is asking the FCC to address permitting barriers under Section 253. Its recommendations are proposals, not nationwide rules in effect. But their benchmarks give contractors and municipalities a practical starting point for discussions, and a reason to manage permitting as a project control.
Treat permit cost as schedule risk, not an accounting line
Permitting affects both what a build costs and when it can produce. Excessive or unpredictable fees can weaken project economics. Slow reviews can hold up construction, disrupt crew assignments, and push work into a less favorable operating window.
The Cartesian analysis modeled how common permitting practices can reduce a project’s return. In its sample, a project starting at an 11% internal rate of return against a 10% hurdle fell below that hurdle under several scenarios. Recurring per-linear-foot right-of-way charges had the most severe modeled effect. Sequential reviews and contingent approvals also reduced returns. These are modeled outcomes, not predictions for every project; the takeaway is that local permitting terms can influence whether an investment remains viable.
Teams should translate that exposure into project controls:
Assign a permit owner for every jurisdiction and application.
Put application, review, inspection, and approval milestones on the integrated schedule.
Record dependencies that could prevent work from starting, even if another permit is approved.
Escalate delays while there is still time to protect construction sequencing.
For example, a build may have funding, materials, and an available crew but still be unable to start a route segment because one jurisdiction’s review remains open. A permit register makes that constraint visible before it becomes a field disruption.
Build a jurisdiction-by-jurisdiction permit baseline
FBA’s proposed cost-based standard offers a benchmark to evaluate permit budgets. It recommends no per-linear-foot or revenue-based fees, a safe harbor of $200 per permit, and a cap of $5,000 per jurisdiction for large multi-site projects. Smaller projects would have proportionately lower charges. These are recommended limits, not a current universal fee schedule or legal cap.
Create a baseline for each jurisdiction before mobilization:
Count the anticipated permits and note the type, route segment, and responsible authority.
List the fee components: application review, inspection, restoration, degradation, and any requested in-kind contribution.
Compare the proposed charges with FBA’s recommended $200-per-permit and $5,000-per-jurisdiction safe harbor.
Normalize the jurisdiction total per planned route mile as an internal comparison tool. This is a budgeting measure, not a recommended per-mile fee.
Document exceptions and assumptions, including what triggers additional inspections or charges.
FBA also recommends that degradation fees apply only when a jurisdiction can show empirical evidence that the work materially reduces street lifespan. It says in-kind compensation should be quantified and counted toward cost-recovery limits. Teams can use these points in fee discussions while keeping a record of the jurisdiction’s stated basis for each charge.
Run the permit log as a project artifact
A permit log should be a live management tool, not a final spreadsheet assembled after a delay. Track each application’s submission date, completeness status, reviewer, open questions, fee, next action, and effect on the construction schedule.
Set internal aging thresholds that trigger action. For example, a team might require a receipt confirmation within five business days, flag an application without a completeness determination after 15 business days, and escalate an application with no substantive movement by day 30. At 60 days, the project manager can review the schedule impact with leadership; at 90 days, the team can prepare a formal escalation path. These are suggested management thresholds, not legal deadlines.
Define each escalation tier in advance:
Application owner: Confirm receipt and resolve missing information.
Project manager: Contact the reviewer, record the response, and assess schedule impact.
Program lead or executive sponsor: Coordinate with jurisdiction leadership and update stakeholders.
Legal or regulatory advisor: Evaluate formal dispute-resolution options where appropriate.
A useful log records the next action and its owner, not just a color-coded status. For broader telecom project management, this makes permit risk visible across multiple sites and accountable across teams.
Sequence applications to prevent contingent-approval stalls
Sequential and contingent approvals can turn independent workstreams into a bottleneck. FBA identifies these practices as major sources of delay. Teams should map every approval dependency before submitting and ask whether applications can be reviewed in parallel.
Use a permitting sequence that:
Identifies prerequisites, such as route design, traffic-control plans, or site-specific exhibits.
Submits complete applications as soon as required inputs are ready.
Requests parallel review where authorities can evaluate separate components independently.
Separates construction authorization from later inspections or closeout requirements where permitted.
Records each contingent approval and the exact condition that must be met to release it.
For example, a municipality may require one review to finish before it will begin another. The project manager should confirm whether that sequence is mandatory, identify the decision-maker, and show the resulting impact on the critical path. The goal is not to bypass legitimate review; it is to prevent avoidable waiting caused by unclear handoffs.
Model the 120-day clock, and compare markets
FBA recommends a 120-day presumptive shot clock for reviews, inspections, and approvals on large projects, with shorter periods for smaller builds. It has supported FCC action under Section 253, but the 120-day period is a proposal and should not be represented as a final nationwide requirement. FBA’s September 2026 comments to the FCC provide further detail.
For planning, teams should treat 120 days as an outer scheduling scenario, not as a guaranteed approval date. Add a permit-review activity with a clear start date, planned response milestones, and a contingency path. Use actual local history where available, and model a faster case and a slower case for jurisdictions with uncertain requirements.
Market selection can also account for permitting readiness. Compare fee transparency, published procedures, review sequencing, expected response times, and escalation channels, not just construction cost. This is particularly relevant as the supplemental BEAD round targets some of the hardest and most expensive unserved locations on a roughly nine-month approval runway. Schedule assumptions should be validated against current program guidance and local permitting conditions.
Protect crew utilization while permits are pending
A permit stall costs more than a fee. It can leave crews, vehicles, and equipment waiting; force re-mobilization; or cause a team to miss a construction window. In a market where skilled fiber technicians and project managers are also in demand for AI data-center builds, avoidable idle time can make workforce planning harder.
Structured fiber optic project management and telecommunication construction management protect utilization by connecting permit readiness to crew assignments and field milestones. Use a jurisdiction-level look-ahead to match approved segments with available work. Maintain alternate work fronts where the project allows, and avoid dispatching crews to a segment without confirmed access and approvals.
Use the permit wait to prepare the workforce
The permit wait is often the least disruptive window to prepare people and materials. Organizations can use it to train entry-level technicians, refresh safety practices, verify tools and equipment, stage materials, and prepare crew leads to execute the first approved work packages.
This applies at every level, from new technicians learning installation fundamentals to experienced veteran crew leads reviewing production plans and documentation standards. ATR’s careers page provides information for people exploring fiber and telecom roles.
A crew that is trained, briefed, and staged can move into authorized work sooner once approvals land. Training does not eliminate permitting uncertainty, but it turns some waiting time into workforce readiness.
Apply veteran-led project discipline to permitting
Veteran-led project management brings structure to a process that can otherwise rely on informal follow-up. The approach is straightforward: assign responsibility, establish escalation tiers, report what work happened, and close out records completely.
Use defined escalation tiers so reviewers and internal stakeholders know who acts next.
Separate activity reporting from status reporting. “Called the permit office” is an activity; “review remains pending, next response due, and route milestone at risk” is decision-useful status.
Capture daily production and constraints so field progress, permit readiness, and crew utilization remain aligned.
Complete closeout documentation, including inspections, as-built records, and outstanding conditions.
Contractors and municipalities can use FBA’s recommendations as a negotiating checklist:
Are fees tied to actual, direct cost recovery?
Are per-linear-foot and revenue-based charges excluded?
Can the parties use the proposed $200-per-permit safe harbor and $5,000 large-project jurisdiction cap as a reference point?
Are in-kind demands quantified and counted toward the cost-recovery limit?
Are degradation fees supported by empirical evidence?
Are procedures published, consistent, and clear about application completeness?
Is there a defined review clock and a process to resolve stalled approvals?
Turn permit lessons into long-term improvement
Treat permitting as a managed project workstream, and the team can see risk earlier, plan crews more realistically, and discuss costs with better documentation. FBA’s proposals provide useful benchmarks, but each project still needs a jurisdiction-specific baseline and schedule.
After each build, conduct a lessons-learned review: compare planned and actual review times, identify recurring documentation gaps, measure the effect of contingent approvals, and update the jurisdiction playbook. That is strategic project management in practice, using evidence from one deployment to improve the next. Organizations seeking support with permitting coordination, workforce planning, or project management consulting can also explore ATR’s services and blog for additional deployment guidance.
Long-term growth depends on more than getting one permit approved. It depends on continuous improvement across the portfolio: better forecasts, clearer stakeholder accountability, stronger crews, and reliable closeout from one build to the next.
Comments