--- title: "OSP Engineering Services for ISPs: What's Included, What It Costs, and How to Evaluate a Firm" description: "What OSP engineering services include for ISPs — field survey, route design, permit drawings, pole loading, utility coordination, and how to evaluate a firm before committing." keywords: "osp engineering services for isps" date: "2026-05-23" author: "Julio Martinez" author_url: "https://draftech.com/authors/julio-martinez" canonical: "https://draftech.com/blog/osp-engineering-services-for-isps" image: "https://draftech.com/blog/blog_img_osp_engineering_isps.webp" --- # OSP Engineering Services for ISPs: What's Included, What It Costs, and How to Evaluate a Firm In This Article - What OSP Engineering Actually Covers for an ISP - The Full Deliverable Stack — From Survey to As-Built - How ISP Project Types Drive Engineering Scope - What Per-Mile OSP Engineering Costs for ISPs - Red Flags When Evaluating an OSP Engineering Firm - How Draftech Structures ISP Engagements - Getting a Scoped Estimate I've been doing this for 17 years. In that time, I've watched ISPs sign engineering contracts that looked reasonable on paper and then fall apart mid-construction — not because the ISP made bad decisions, but because nobody explained what they were actually buying. The term "OSP engineering" gets thrown around loosely, and the scope gap between what an ISP expects and what a firm actually delivers can cost six figures in rework, delay, and missed deployment windows. This article is for commercial ISPs — fiber overbuilders, CLECs, cable operators pushing into new territory, fixed wireless providers transitioning to fiber last-mile. If you're evaluating an OSP engineering firm for the first time or replacing a firm that underdelivered, here's what you need to know before you sign anything. ## What OSP Engineering Actually Covers for an ISP The phrase "outside plant engineering" refers to everything that happens between your network's origination point and the subscriber premise — and more specifically, to the engineering work required to design, permit, and document that physical infrastructure. For an ISP, that means the aerial or buried fiber plant, the hardware it rides on, and the permitting ecosystem required to place it. In practice, OSP engineering services for a commercial ISP span several distinct work phases: field data collection, high-level route design, low-level construction-ready design, pole analysis where aerial attachments are involved, permit preparation and submission, utility coordination, and documentation of what was actually built. Most ISPs need all of these. Some think they only need the design portion and discover — usually after a permit rejection or a construction hold — that they need everything else too. What OSP engineering is not: network architecture, IP addressing, active equipment selection, or anything inside the four walls of a hub or headend. The moment fiber crosses a threshold into a building, you're typically into inside plant (ISP) territory. The boundary varies by project type, but outside plant engineers are not designing your OLT configuration or your DWDM link budget. **Worth clarifying early:** Confirm whether your engineering firm's scope includes permit submission and tracking, or just permit package preparation. These are meaningfully different deliverables. Preparation gets you the drawings; submission and tracking means someone is actually following up with the utility or municipality. Some firms do one, not both. ## The Full Deliverable Stack — From Survey to As-Built When an engagement is scoped correctly, here's what the deliverable sequence looks like from start to finish: ### Field Survey Everything starts with ground truth. Field survey captures existing infrastructure conditions along the proposed route — pole numbers, pole heights and classes, span measurements, existing attachment inventory, underground facilities, road crossings, and anything else a designer can't see from a satellite image. A thorough field data collection pass takes 3–7 days per 50 route miles depending on terrain and access. ISPs who skip this step to save time routinely spend more unwinding design errors discovered during construction. ### High-Level Design (HLD) HLD establishes the macro-architecture: route selection, fiber count and type, node and hub placement, topology decisions. This is the document you present to lenders, partners, and internal leadership. It informs your capital cost model. It should be precise enough to make meaningful decisions, but it's not a construction document. Good HLD takes 5–9 business days for a 50-mile project after field data is available. ### Low-Level Design (LLD) LLD is what your crew builds from. It includes strand charts, pole attachment details with heights and clearances referenced to NESC standards, splice diagrams, handhole and vault placement, conduit sizing and routing, and span-by-span measurements. If your contractor picks up the LLD and has questions that require a call to the engineer, the LLD isn't finished. Completed LLD drawings should be self-contained construction documents — period. For more on what separates good LLD from inadequate work, see our LLD quality control checklist. ### Pole Loading Analysis Pole loading analysis is required whenever you're attaching fiber to a jointly-used pole — which is virtually every aerial build in an established right-of-way. Loading analysis calculates whether a pole can support your attachment given existing loads from power, telecom, and cable TV, accounting for wind and ice loading per the applicable NESC grade. If a pole fails analysis, you need a replacement or a transfer of existing attachments. ISPs routinely underestimate how many poles require remediation: on a suburban aerial route, it's not unusual for 18–24% of poles to require some form of make-ready work. ### Permitting and Utility Coordination Permit packages for aerial builds typically include joint-use applications, make-ready engineering submissions, municipality encroachment permits, and state or federal crossing permits for roads, waterways, and railroads. Underground work requires separate excavation permits, 811 coordination, and often traffic control plans. This is where timelines slip. Permitting adds 6–14 weeks to most projects, and that clock doesn't start until the packages are submitted and complete. ### CAD/GIS Deliverables CAD/GIS outputs include georeferenced design files, shapefiles of the proposed route and infrastructure, and as-designed records. If your ISP uses a network management system, your OSP engineer needs to know what format it accepts and deliver accordingly. GIS data quality is often treated as a secondary concern and later becomes a primary problem when network operations can't find a splice point during an outage. ### As-Built Documentation As-built documentation records what was actually constructed — deviations from design, final pole attachment heights, actual splice locations, conduit paths as placed. As-builts are a warranty requirement for many manufacturers, a compliance requirement on funded projects, and your network operations team's most important reference document. Firms that treat as-builts as a post-construction afterthought rather than a parallel workflow consistently deliver incomplete records. ## How ISP Project Types Drive Engineering Scope Not every ISP build requires the same depth of engineering. The project type determines where the complexity lives and where the scope risk is highest. ### FTTH Overbuild Fiber-to-the-home overbuilds in existing aerial rights-of-way are the most common commercial ISP engagement we see. The engineering challenge here is density and make-ready: you're attaching to poles already loaded with power, incumbent telco, and often cable attachments. Pole loading analysis is required on virtually every span. Make-ready timelines are unpredictable — an ILEC with a backlog can hold a project for months. Full-scope engineering on a suburban FTTH overbuild, including survey, HLD, LLD, pole loading, and permit packages, typically runs 10–16 weeks from kickoff to permit-ready packages. ### CLEC Aerial Builds CLECs running fiber in established corridors face similar make-ready dynamics, compounded by tariffed pole attachment processes and utility coordination that involves legal agreements, not just engineering applications. The engineering scope is comparable to FTTH, but the coordination layer is heavier. Budget for 14–18 weeks to permit-ready on a first-time corridor if you don't have existing joint-use agreements in place. ### MDU Fiber Multi-dwelling unit fiber — whether aerial to the building or underground in conduit — compresses geographic scope but increases per-structure complexity. Engineering deliverables include riser diagrams, demarcation documentation, and often coordination with property management for access rights and pathway design. The engineering hours per mile are higher than a suburban aerial build; the permitting is usually simpler. ### Last-Mile Extension Extending an existing fiber plant into underserved adjacent areas is typically the most straightforward ISP engineering engagement in terms of permitting, assuming the extension follows existing ROW. Scope complexity comes from the distribution layer — splitter placement, strand counts, drop engineering. Good LLD here focuses on the access layer design more than the backbone, and as-builts need to integrate cleanly with the existing network records. ## What Per-Mile OSP Engineering Costs for ISPs I'll give you real numbers. The ranges I'm about to share are based on what we see across the 22 states where Draftech is currently active, covering project types from suburban aerial overbuilds to urban underground conduit systems. These assume full-scope engineering — survey through as-built — not design-only. **Full-scope OSP engineering for commercial ISPs runs $800–$2,400 per route mile**, depending on build type, density, permitting environment, and underground vs. aerial mix. Partial-scope engagements (design-only, no survey, no as-builts) will come in lower — but understand what you're giving up. **Aerial suburban overbuild:** $900–$1,340 per mile. Moderate pole loading complexity, standard permitting jurisdictions, accessible terrain. This is the baseline for most FTTH and CLEC aerial builds in established suburban corridors. A 100-mile project in this category runs $90,000–$134,000 in engineering fees before construction. **Aerial rural with low pole density:** $800–$1,100 per mile. Longer spans (averaging 290–360 feet vs. 165–220 feet suburban), fewer poles per mile, and often simpler permitting. What you save on pole loading analysis gets partially offset by longer field survey times per mile. **Hybrid aerial-and-underground:** $1,200–$1,650 per mile. Road crossings, creek crossings, and congested intersections require underground segments that add conduit design, 811 coordination, and separate excavation permits. A route with 30% underground typically adds $280–$420 per mile to a baseline aerial estimate. **Urban underground:** $1,800–$2,400 per mile. Dense permitting jurisdictions, traffic control requirements, utility conflict resolution, and complex conduit routing push costs to the top of the range. Projects in major metro areas with active DOT involvement in permitting are consistently at the high end. Microtrenching-specific design in dense urban environments has its own complexity layer on top of this. What's not in these numbers: make-ready construction costs (the actual pole work, not the engineering of it), permit fees paid to municipalities and utilities, or any active equipment. Those are construction and procurement costs, not engineering costs. For a broader view of what drives fiber network cost, our fiber network design cost guide breaks down the full budget picture. ## Red Flags When Evaluating an OSP Engineering Firm After 17 years, I've seen how this plays out when ISPs choose the wrong engineering partner. Here are the specific signals that should give you pause before signing: ### They Subcontract the Engineering Some firms present as engineering companies but function as staffing intermediaries — they win the contract and send it to a subcontracted firm you've never vetted. Ask directly: who performs the field survey? Who stamps the drawings? Who does the pole loading analysis? If the answer involves a third party you're not contracting with directly, you have a quality control problem waiting to happen. At Draftech, all work is self-performed. No engineering subcontracting. That's not a sales point — it's a structural requirement for consistency. ### The Proposal Has No Milestone Schedule A proposal that lists deliverables without attached timelines is a proposal designed to be unaccountable. Good proposals include: survey completion date, HLD draft date, LLD completion date, permit package submission date. If those dates aren't in the contract, you have no basis for a delay conversation later. We see ISPs accept vague scopes routinely, and they almost always regret it when construction crews are waiting on permit approvals that are still three weeks out. ### They Quote a Flat Rate Per Mile Without Asking About Build Type A firm that gives you a single per-mile rate without knowing whether you're building aerial or underground, in a dense urban environment or a rural corridor, either doesn't understand the cost drivers or is planning to renegotiate after you're committed. The range between an easy aerial build and a complex urban underground build is 3x. Flat rates in OSP engineering are a red flag, not a convenience. ### LLD Samples Look Like Annotated Maps Ask for a sample LLD drawing before you sign. If it looks like a route drawn on a satellite image with some labels attached, it is not construction-ready. Real LLD includes strand assignments, attachment height callouts, pole class confirmations, splice diagram references, and enough detail that a construction foreman can build from it without calling the engineer. If the sample doesn't have all of that, the deliverable you'll receive won't either. ### No Experience With Your Permitting Jurisdiction OSP permitting is intensely local. A firm that has designed 300 miles in Tennessee but never worked in your specific state or utility territory is going to learn on your project's timeline. Ask for references in your state and, ideally, with the specific utilities you'll be dealing with. The difference between a firm that knows a utility's joint-use process and one that's navigating it for the first time can be 6–8 weeks on permit cycle time. ### They Can't Give You a Revision Policy Design revision is a normal part of any OSP project. Utility comment letters, municipality redlines, and field conditions discovered mid-survey all generate changes. A firm that doesn't have a defined policy for how revisions are handled — and at what cost threshold they become change orders — is a firm that will nickel-and-dime you through the design phase. Get the revision policy in writing before you sign the MSA. ## How Draftech Structures ISP Engagements I'll walk you through how we actually run these projects, because the workflow matters as much as the deliverable list. ### Kickoff and Scope Confirmation Every engagement starts with a kickoff call that covers route boundaries, existing records availability, utility territory, permit jurisdiction research, and a confirmed milestone schedule. We don't start field survey until we have a signed scope and a realistic permit calendar. ISPs who push to skip this step because they're in a hurry almost always hit a delay downstream that the kickoff would have prevented. ### Field Survey Mobilization Our field survey teams are self-performed — no subcontracted field crews. On a 50-mile aerial project, we typically mobilize a two-person survey team and complete the field pass in 8–11 business days. All field data is captured in our GIS environment and cross-referenced with utility records and pole ownership databases before design starts. We've designed across 44,000+ miles of network — the field data protocol is tight because we've seen what happens when it isn't. ### Design Phase Cadence HLD is delivered for ISP review within 9 business days of field data completion on projects under 75 miles. We run a structured review cycle — ISP comments back within 5 business days, HLD revision delivered within 3 business days of comments received. LLD follows the approved HLD, with an interim deliverable at 50% completion on larger projects so ISPs can review before the full package is complete. We've found this intermediate review prevents the situation where a full LLD package comes back with a fundamental comment that requires rework across dozens of sheets. ### Permit Package Coordination Permit packages are prepared in parallel with LLD finalization. Our team handles permit submission and tracks status with utilities and municipalities. We maintain open lines with joint-use administrators and can escalate stalled applications with documented correspondence. When a permit comment comes back, the engineering revision cycle is typically 3–5 business days. We track every permit by jurisdiction in a project management system that gives ISP clients visibility into status without needing to email us for updates. ### As-Built Integration As-built collection starts at the beginning of construction, not at the end. Our field teams collect redlines during construction and integrate them into the final GIS record. As-builts are delivered within 15 business days of construction completion sign-off. For ISPs using OSS/NMS platforms, we deliver in the format those systems accept. For a broader look at how we approach partner selection from the ISP's perspective, our article on how to choose an OSP engineering partner covers the evaluation framework in detail. ## Getting a Scoped Estimate I'll say this plainly: a legitimate OSP engineering estimate cannot be delivered in 24 hours without a conversation. If you receive one that quickly, it's a ballpark with a contract attached, not a real scope. What generates a meaningful estimate is a 30-minute call covering route length, build type, aerial vs. underground ratio, state, utility territory, your existing records, and your target construction start date. From that conversation, we can deliver a scoped estimate with a milestone schedule within 3–4 business days. Draftech is MBE-certified, active across 22 states with 600+ engineers, and deployable across all 50. We've designed over 44,000 miles of network for carriers, ISPs, municipalities, and utilities — all self-performed. If you're looking for an OSP engineering partner that will be accountable to a schedule and deliver construction-ready work, we'd like to talk. Reach out at info@draftech.com or through our contact page. Tell us your route length, your target construction date, and your build type. We'll take it from there. If you're still early in your evaluation process, our overview of what OSP engineering is and our notes on OSP engineering outsourcing considerations may help frame your decision before you start taking proposals. ## Frequently Asked Questions --- *Published by [Draftech International](https://draftech.com) — MBE-certified OSP engineering firm. 44,000+ miles designed across all 50 U.S. states.* *Contact: [info@draftech.com](mailto:info@draftech.com) | 305-306-7407*