The permitting mistakes that turn a 6-week fiber project into a 6-month one

Ask any OSP project manager what actually blew up their schedule, and it's rarely one dramatic challenge. It's usually four or five small process gaps compounding on top of each other, each one adding a review cycle, each review cycle adding two to six weeks.

Sign-offs out of sequence

The most common one we see: right-of-way, DOT, utility, and zoning approvals get requested in whatever order is administratively convenient rather than the order the project actually depends on. A crew shows up ready to bore under a road, only to find the utility locate hasn't cleared, or the municipal right-of-way permit is conditional on an encroachment permit that hasn't even been submitted yet. Every one of those approvals is a route control. If you don't map which ones block which segments of work before you submit anything, you find out the hard way, in the field, on the clock.

Applications and plans that don't match

Design revisions happen. The challenge is when the drawings attached to a permit application reflect one revision and the route actually being built reflects another, because nobody reconciled them before submission. Reviewers don't guess at the intended version — they issue a deficiency notice and the clock resets. The same failure shows up in mapping-heavy programs like the CRTC's Broadband Fund, where attribute data has to match the site and route IDs entered elsewhere in the system; a mismatch anywhere in that chain stops the whole application.

Conditions of approval that never get documented

A permit rarely comes back as a clean yes. It comes back with conditions: restore the boulevard to a specific standard, avoid a tree protection zone, complete work within a defined window. When those conditions live in an email thread instead of a tracked, assigned action item, they get missed in the field, and a missed condition on a completed permit becomes its own re-review.

Environmental and pole issues surfacing too late

Environmental screening requirements and pole make-ready surveys are two of the slowest-moving pieces of a permitting timeline, and they're most damaging when they surface after the route is already locked. A route finalized without an early pass for environmentally sensitive areas, or without checking pole-owner make-ready backlogs on an aerial segment, isn't wrong exactly — it's just built on an assumption that has to be unwound later, usually at the worst possible point in the schedule.

What actually fixes this

The projects that hold close to their original timeline treat permitting as part of route planning, not something that starts after design is final. That means mapping every authority, pole owner, and review trigger against the route before the design hardens; assembling jurisdiction-specific submission packages that get a completeness check before they go in the door; and keeping one system of record — not a shared inbox — that shows who owns every open comment and condition, and when it's due. First-pass completeness, the share of submissions accepted for review without a preventable deficiency, is a genuinely useful number to track project over project, because it's almost entirely within the project team's control, unlike agency review speed itself.