OSP Engineering Services Pricing Per Mile: What Drives the Cost and What to Budget

I get asked some version of this question at least twice a week: "What does OSP engineering cost per mile?" My honest answer is $1,162 to $4,224, and that range isn't me being vague — it's what the actual invoices show across different project types. The reason quotes differ so wildly is that "OSP engineering" describes a collection of distinct services, and which ones you need, how complex your route is, and what your permitting environment looks like determines where you land in that range.

What I want to do in this piece is be direct about the numbers — not aspirational, not worst-case, but the actual ranges we see across the projects Draftech runs. If you're an ISP, an EPC contractor, or a BEAD subgrantee trying to build a defensible project budget, you need real numbers. So let's go through it service by service and then talk about the variables that push you toward either end of the range.

Why OSP Engineering Quotes Vary So Much

The most common situation I see: an ISP gets three quotes for the "same" project and they come back at $1,100, $1,800, and $3,200 per mile. All three firms are real, experienced outfits. The ISP assumes the variance is padding or margin and picks the low number. Six months later they're issuing change orders and wondering why the project is over budget.

The quote variance is almost never about margin. It's about scope and assumed complexity. The firm at $1,100 may be quoting field survey and HLD only — no pole loading, no LLD, no permitting packages. The firm at $3,200 may be pricing full-scope end-to-end engineering including pole loading analysis in O-Calc Pro, complete permit packages for each jurisdiction, and construction-ready LLD. Those are not the same service. You can't compare them on price per mile without understanding what's behind the number.

Build complexity is the other major variable. A 40-mile aerial route through flat agricultural land in the Midwest is fundamentally different from a 40-mile suburban build through three counties with active railroad crossings and a state DOT corridor. Same miles on a map, 3–4x different in engineering cost. I've seen this play out enough times that I've stopped being surprised by it — but ISPs who haven't done this before consistently underestimate how much the specific characteristics of their route drive the number.

The Per-Mile Cost Breakdown by Service

These ranges reflect typical project conditions across five core engineering services. Rural RDOF/BEAD and dense urban markets price out very differently, so we've broken them out separately. Pole loading analysis is billed separately at $45–$75 per pole and is not included in the per-mile totals below.

Aerial vs. Underground: How Build Type Drives Engineering Cost

This is the most straightforward split in OSP engineering pricing. Aerial routes cost less to engineer than underground — sometimes significantly less — and the reason is the complexity of the deliverables.

Aerial engineering centers on pole-by-pole design: attachment heights, strand placement, lashing specifications, mid-span clearances, make-ready sequences. It's detailed work, but the output is predictable. Underground engineering involves conduit system design, duct bank configurations, HDD bore profiles and crossing calculations, structure sizing and spacing, vault placement, and construction-plan-level detail that's more similar to civil engineering than telecom drafting. The deliverables are more complex, the field conditions create more uncertainty, and the permit packages are thicker.

Rule of thumb: underground LLD costs roughly 40–70% more per mile than aerial LLD on equivalent routes. Underground permitting often costs more too, particularly in urban corridors where cut-and-cover work intersects with traffic management, utility coordination, and municipal right-of-way processes that each have their own timeline and fee structure.

Mixed builds — aerial on the backbone, underground in downtown cores or at road crossings — are common and are usually priced by splitting the mileage and applying the appropriate rate to each segment. Don't let a firm quote blended rates on a mixed build without seeing the split. It almost always obscures cost in the underground segments.

What Pole Count and Density Do to Your Budget

For aerial routes, the true cost driver isn't miles — it's poles. Everything that happens on an aerial build is organized around individual poles: the field survey collects data at each pole, the LLD places attachments and designs make-ready at each pole, the pole loading analysis runs calculations for each pole, and the permit packages document each pole with the owning utility.

Rural routes typically run 8–12 poles per mile. That's the classic agricultural environment where pole spacing is wide and the main span lengths are long. Suburban residential routes — the kind of build you see in small cities and ring suburbs — typically run 22–35 poles per mile. Dense urban areas can push past 40.

On a per-pole basis, pole loading analysis runs roughly $45–$75 per pole depending on complexity and attachment type. LLD design runs $60–$140 per pole on aerial routes. Permit processing runs $20–$45 per pole for standard utility application processing, more when pole-specific remediation designs are required.

Do that math at 10 poles/mile vs. 30 poles/mile and you understand why a suburban route costs 2–2.5x a rural route per mile even when the terrain and permit environment are similar. The poles multiply everything.

Permit Complexity: The Wildcard Line Item

If I had to identify one line item that generates the most budget surprises on fiber projects, it's permitting. Not because it's the most expensive — it's usually not — but because the range is enormous and the high end catches people off guard.

Standard utility pole attachment permitting in a cooperative utility territory: $20–$45 per pole, straightforward process, predictable timeline. That's what most ISPs budget for. Then the route hits a railroad corridor.

Railroad crossing permits are a different category entirely. The engineering package required by Class I railroads includes bore profile calculations, encasement specifications, cathodic protection design, and detailed construction drawings in the railroad's specific format — each railroad has different requirements. The permit fee itself can run $4,000–$18,000 per crossing, plus the engineering to prepare the package. A project with six railroad crossings can have $80,000–$140,000 in railroad permit costs before construction starts. Per mile, on a 50-mile route with six crossings, that's $1,600–$2,800 per mile added to your permit line item from railroad crossings alone.

State DOT right-of-way permits add similar complexity. Encroachment permits, traffic management plans, crossing method specifications, bonding requirements — the documentation burden varies significantly by state. Some state DOTs have streamlined fiber permit processes. Others treat each application as a first-time occurrence regardless of how many times you've filed.

Waterway crossings, tribal land, and federal land add yet another layer. On routes that cross navigable waters, Army Corps of Engineers coordination may be required. On tribal land, tribal council review processes have their own timeline that isn't on anyone else's schedule. I've seen tribal land permit processes add 14 months to a project. You cannot shortcut that. You can only budget for it and plan around it.

Our detailed guide on ROW permitting delays goes deeper on these categories and the realistic timelines for each.

What Cheap OSP Engineering Actually Costs You

I want to address this directly because I see it cost ISPs real money on a regular basis. The instinct to optimize on engineering cost is understandable — engineering is often 8–15% of total project cost, and a $300/mile saving per mile looks significant on a 200-mile project ($60,000). The problem is that low engineering cost has downstream consequences that dwarf the upfront savings.

The first consequence is rework. Engineering deliverables that skip field verification, that rely on utility GIS records instead of actual pole data, that don't model make-ready requirements accurately — those deliverables generate construction change orders. Not occasionally. Consistently. Change orders on fiber construction run $2,000–$8,000 each for scope that should have been designed correctly upfront. On a project where the engineering saved $60,000 but generated 40 change orders, you've lost $20,000–$260,000 net. That's not a hypothetical — it's a pattern I've seen repeatedly.

The second consequence is rejected permit packages. Utilities, railroads, and DOTs reject permit packages that don't meet their submission requirements. Resubmission takes time — often 60–120 days on railroad crossings, depending on the railroad's workload. On a project with a BEAD construction deadline, a rejected railroad crossing permit that slips three months can put your entire award at risk.

The third consequence is what I'd call the construction crew problem. When LLD quality is poor — missing notes, incorrect attachment heights, incomplete make-ready sequences — construction crews hit the field and find that the drawings don't match reality. They either stop and call for field direction (which costs you project management time and schedule), or they make judgment calls (which creates liability). Either way, it's a consequence of the engineering, and it shows up in your construction cost, not your engineering invoice.

Our post on how to choose an OSP engineering partner covers the qualitative evaluation criteria in more depth. Price per mile is one dimension. Deliverable quality and downstream performance are the more important ones.

How to Scope and Budget Correctly From the Start

The most consistent mistake I see in project budgeting is treating OSP engineering as a single line item with a single rate rather than a collection of services with different rates that vary by project-specific variables.

To build a defensible budget, you need to know — or estimate — the following before you go out for engineering quotes:

• Route miles, broken down by aerial and underground. If you don't know the split yet, use your best estimate and flag it as an assumption.
• Pole count or density estimate. Even a rough estimate — "rural, probably 10–14 poles per mile" — is better than no assumption.
• Permit jurisdiction inventory. List every permit type the route will require: utility pole attachment, state DOT, railroad crossings (name the railroads), waterway crossings, municipal ROW, any federal land.
• Deliverable format requirements. GIS-ready shapefiles for BEAD closeout, specific CAD standards required by the state broadband office, utility-specific permit formats — these affect engineering cost and need to be in scope before you get quotes.
• Construction timeline constraints. If you need engineering complete by a specific date to meet a BEAD construction window, that affects staffing requirements and potentially cost.

With that information in hand, an experienced OSP engineering firm can give you a quote that's actually defensible. Without it, you're getting a number based on assumptions — and the assumptions may not match your route.

On BEAD-funded projects specifically, I'd add one more item: understand your state's as-built documentation requirements before you scope engineering. Some state broadband offices have specific GIS data schemas and photo documentation requirements for project closeout. Engineering that doesn't account for those requirements will generate a change order at the end of the project — the worst possible time to discover a gap in scope.

The fiber network design cost guide on our blog breaks down design-phase costs in more detail if you want to go deeper on the HLD and LLD components specifically.

Getting a Per-Mile Estimate for Your Project

Draftech runs end-to-end OSP engineering across all 50 states — field survey, HLD, LLD, pole loading analysis, permitting, CAD/GIS, and as-built documentation, all self-performed by our 600+ person team. We don't subcontract core engineering phases. That matters for quality control and for the continuity of your project data from survey through as-builts.

If you're budgeting a project and want a real per-mile estimate rather than a ballpark, reach out with your route details. We'll ask you the questions above, spend an hour understanding your specific project, and give you a number you can put in a budget with confidence — not a rate card pulled from a PDF.

The make-ready cost per pole guide and OSP fielding cost per mile guide are good companion reads if you're building out the full project cost picture. Engineering is 8–15% of what a fiber build costs. Understanding it in detail helps you understand where the other 85% goes too.

Contact us at info@draftech.com or through the form on our site. We're active in 22 states right now and have teams deployable anywhere. If your project is real, we'll give you a real number.