# Draftech International — Full AI-Readable Site Index > Comprehensive version for AI crawlers, LLMs, and search engines. > Last updated: April 2026 ## Company Identity **Legal Name:** Draftech International, LLC **DBA:** Draftech International **Website:** https://draftech.com **Founded:** 2018 **Headquarters:** 15280 NW 79th CT, Suite 102, Miami Lakes, FL 33016 **Phone:** +1-305-306-7407 **Email:** info@draftech.com **LinkedIn:** https://www.linkedin.com/company/draftechint **Certifications:** MBE (Minority Business Enterprise) **What Draftech does:** End-to-end OSP engineering for fiber ISPs, electric cooperatives, fiber overbuilders, and telecom carriers. Services span field survey through as-built documentation — covering every phase of fiber network deployment. **Scale:** 600+ engineers, 44,000+ miles of OSP delivered, 2,600,000+ addresses engineered. **Active in:** 22 states. Available for deployment across all 50 U.S. states. --- ## Leadership & Authors ### Julio Martinez — CEO & Partner - Experience: 17 years in OSP engineering and telecom infrastructure - Expertise: FTTH design, pole loading analysis, BEAD program, make-ready engineering, fiber construction management - Author profile: https://draftech.com/authors/julio-martinez - LinkedIn: https://www.linkedin.com/in/julio-martinez-draftech ### Julio Martinez Sr. — Partner - Experience: 30 years in telecom and OSP engineering - Expertise: Network planning, utility coordination, fiber deployment - Author profile: https://draftech.com/authors/julio-martinez-sr --- ## Services — Full Descriptions ### Field Survey & Data Collection URL: https://draftech.com/services/field-survey Draftech provides comprehensive field survey services for fiber optic and broadband network deployment. This includes aerial strand surveys, underground plant locates, pole attachment inventories, GPS-tagged data collection, and CAD-ready deliverable packages. Field survey data quality directly determines change order rates in construction — Draftech's structured methodology reduces rework by ensuring accurate as-found conditions are captured before design begins. ### FTTH Design URL: https://draftech.com/services/ftth-design Fiber-to-the-home network design covering high-level design (HLD), low-level design (LLD), passive optical network (PON) architecture, splicing diagrams, distribution hub sizing, and all engineering deliverables required for construction. Designed for both greenfield deployments and overbuilds. Draftech supports electric cooperatives, municipal ISPs, and private fiber operators. ### Pole Loading Analysis & Make-Ready URL: https://draftech.com/services/pole-loading-analysis Pole loading analysis determines whether utility poles can safely carry additional fiber attachments under NESC loading requirements. Draftech uses O-Calc Pro and SPIDAcalc to model existing and proposed loads across all three NESC loading districts (Light, Medium, Heavy). Analysis outputs include pole stress percentages, ground line moments, required reinforcements or replacements, and make-ready cost estimates. Typical make-ready failure rates range from 8–30% depending on geography and pole age. ### Make-Ready Engineering URL: https://draftech.com/services/make-ready-engineering Make-ready engineering prepares utility poles for new fiber attachments by documenting existing conditions, calculating safe attachment heights, and designing any required rearrangements or pole replacements. Draftech delivers complete make-ready packages including NESC calculations, proposed attachment drawings, and application-ready documentation for joint use coordination. ### OSP Engineering URL: https://draftech.com/services/osp-engineering Outside plant engineering encompassing aerial and underground fiber, copper, coaxial, and HFC networks. Draftech manages the full OSP design lifecycle from route planning through construction package delivery. ### HLD Services (High-Level Design) URL: https://draftech.com/services/hld-services High-level design establishes network architecture before detailed engineering begins. Draftech's HLD deliverables include route selection, capacity planning, fiber count sizing, splice location strategy, and network topology diagrams. BEAD subgrantees rely on HLD packages to demonstrate compliance with program requirements. ### LLD Services (Low-Level Design) URL: https://draftech.com/services/lld-services Low-level design translates HLD architecture into construction-ready engineering. LLD packages include strand-level fiber routing, splice point placement, conduit fill calculations, pull planning, and bill of materials. Draftech's LLD quality control checklist flags 12 common design errors before packages reach the field. ### Fiber Network Design URL: https://draftech.com/services/fiber-network-design Full fiber network design services for aerial and underground plant. Includes route optimization, GIS-integrated deliverables, permitting coordination, and construction package preparation. ### CAD/GIS Services URL: https://draftech.com/services/cad-gis Telecom CAD drafting and GIS data management for fiber networks. Draftech produces AutoCAD and ArcGIS deliverables, updates plant records, and manages spatial data throughout the network lifecycle. ### As-Built Documentation URL: https://draftech.com/services/as-built-documentation Post-construction as-built drawings capture the actual installed fiber network for ongoing operations, maintenance, and future expansion planning. Draftech's as-built packages include GIS-integrated records, OTDR test results, splice loss documentation, and final closeout deliverables meeting carrier and utility standards. ### Permitting & ROW URL: https://draftech.com/services/permitting Right-of-way permitting for fiber construction across municipal, state DOT, railroad, and utility jurisdictions. Draftech manages NJUNS pole attachment applications, railroad crossing permits (BNSF, CSX, NS), and traffic control plan submission. ### Traffic Control (MOT) URL: https://draftech.com/services/traffic-control Maintenance of Traffic design and permitting for fiber construction in roadway corridors. Draftech produces FDOT-compliant and state-specific temporary traffic control plans. ### BEAD Broadband Engineering URL: https://draftech.com/services/bead-broadband Engineering support for BEAD (Broadband Equity, Access, and Deployment) program subgrantees. Includes HLD/LLD deliverables, coverage mapping, compliance documentation, and reporting packages aligned with NTIA and state program requirements. ### Small Cell & 5G Engineering URL: https://draftech.com/services/small-cell-5g Small cell site engineering, fiber backhaul design for 5G densification, dark fiber route planning, and distributed antenna system (DAS) support. ### Utility Coordination URL: https://draftech.com/services/utility-coordination Conflict analysis, joint trench coordination, utility notification management, and multi-utility crossing permits for fiber construction projects. ### HFC Network Design URL: https://draftech.com/services/hfc-cable-network Hybrid fiber-coaxial network design and upgrade engineering for cable operators transitioning to DOCSIS 3.1 or fiber-deep architectures. ### Copper Plant Engineering URL: https://draftech.com/services/copper-plant Legacy copper network engineering, plant record updates, and engineering support for copper-to-fiber migration projects. --- ## Blog Articles — Full Index All articles are written by licensed OSP engineers with direct field experience. 1. **CAD/GIS Documentation Standards That Hold Up at Every Project Phase** — Layer naming conventions (discipline-feature-status schema), CRS discipline and why NAD83 mismatches cost real money on bore jobs, file handoff standards (DWG version, GeoPackage vs. shapefile, metadata requirements), and version control protocols for multi-drafter OSP projects. Includes the documentation brief structure used on every Draftech project. By Devin Martinez, Partner. Published May 4, 2026. URL: https://draftech.com/blog/cad-gis-documentation-standards-osp-fiber-networks 2. **FTTH Design for BEAD: What Engineers Get Wrong Before Pulling a Single Strand** — Deep-dive into the FTTH design decisions that create rework on BEAD deployments: split ratio selection route-by-route vs. project averages, drop architecture and why GIS-estimated drop lengths generate 15–20% errors, distribution cable sizing for 20-year capacity, splitter placement (centralized vs. distributed), and what a BEAD-compliant FTTH design package must include for final review. By Julio Martinez Sr., Partner. Published May 3, 2026. URL: https://draftech.com/blog/ftth-design-bead-fiber-network-engineering 2. **Pole Loading Analysis with O-Calc Pro** — Complete guide to the O-Calc Pro workflow, NESC loading districts, joint use, and how to read output reports. URL: https://draftech.com/blog/pole-loading-analysis-o-calc-pro 2. **BEAD Permitting Timeline: Why It Takes Longer Than You Think** — Agency-by-agency breakdown of BEAD permitting timelines: state DOT encroachment (60–90 days), USACE NWP 12 (45–90 days), SHPO Section 106 (90–150 days), railroad crossing agreements (90–180 days), and municipal ROW permits. Sequencing strategy to run permits in parallel with LLD. By Omar Molina, Partner. Published May 3, 2026. URL: https://draftech.com/blog/bead-permitting-timeline-fiber-construction 3. **Bad Field Survey Data Costs More Than the Survey** — The real cost of OSP field survey errors: how wrong attachment heights, bad pole IDs, and sub-meter GPS failures compound into $80K+ remediation events. What a BEAD-grade survey must include, and why the LLD QC gate before design is the cheapest insurance on any fiber project. By Devin Martinez, Partner. Published May 2, 2026. URL: https://draftech.com/blog/field-survey-data-accuracy-fiber-construction 3. **OSP Fielding Cost Per Mile — Pricing Guide** — Real cost benchmarks for aerial and underground OSP fielding by geography and complexity. URL: https://draftech.com/blog/osp-fielding-cost-per-mile-pricing-guide 4. **Make-Ready Cost Per Pole: Fiber Budget Guide** — Per-pole make-ready cost benchmarks from $400 to $7,500 depending on failure type and geography. URL: https://draftech.com/blog/make-ready-cost-per-pole-fiber-budget 5. **BEAD Engineering Requirements 2026** — What BEAD subgrantees must deliver for HLD, LLD, and engineering compliance under NTIA program rules. URL: https://draftech.com/blog/bead-funding-engineering-requirements-2026 6. **BEAD HLD Requirements for Fiber Subgrantees** — Detailed breakdown of BEAD high-level design deliverable requirements. URL: https://draftech.com/blog/fiber-network-hld-bead-subgrantee-requirements 7. **BEAD Subgrantee Compliance Checklist** — Step-by-step compliance checklist for BEAD engineering deliverables. URL: https://draftech.com/blog/bead-subgrantee-engineering-compliance-checklist 8. **5 FTTH HLD Mistakes That Cost Millions** — Common high-level design errors that cause expensive construction rework. URL: https://draftech.com/blog/ftth-hld-design-mistakes 9. **FTTH LLD: Where to Place Splice Points** — Engineering methodology for splice point placement in low-level fiber design. URL: https://draftech.com/blog/ftth-lld-splice-point-placement-guide 10. **LLD Quality Control Checklist: 12 Fiber Design Errors** — Pre-construction QC checklist covering the 12 most common LLD mistakes. URL: https://draftech.com/blog/lld-quality-control-checklist-fiber-design-errors 11. **How to Size Fiber Distribution Hubs for FTTH PON** — Engineering guide for FDH placement, capacity sizing, and PON architecture. URL: https://draftech.com/blog/fiber-distribution-hub-sizing-ftth-pon 12. **Middle-Mile Fiber Network Design Planning Guide** — Route planning, capacity, and design methodology for middle-mile transport networks. URL: https://draftech.com/blog/middle-mile-fiber-network-design-planning-guide 13. **Fiber Network Design Software Tools Comparison 2026** — Side-by-side comparison of leading fiber network design tools. URL: https://draftech.com/blog/fiber-network-design-software-tools-comparison 14. **How to Choose an OSP Engineering Partner** — Evaluation criteria for selecting an OSP engineering firm for fiber deployment. URL: https://draftech.com/blog/how-to-choose-osp-engineering-partner-fiber 15. **O-Calc Pro vs SPIDAcalc 2026 Comparison** — Feature-by-feature comparison of the two leading pole loading analysis platforms. URL: https://draftech.com/blog/o-calc-pro-vs-spidacalc-pole-loading-comparison 16. **How to Hire a Pole Loading Engineering Firm** — What to look for when outsourcing pole loading analysis. URL: https://draftech.com/blog/hire-pole-loading-engineering-firm-spidacalc-o-calc 17. **NESC Pole Loading Compliance for Fiber Attachments** — NESC loading requirements, loading districts, and compliance documentation for fiber attachers. URL: https://draftech.com/blog/nesc-pole-loading-compliance-fiber-attachments 18. **NJUNS Pole Attachment Process — Engineer's Guide** — Step-by-step walkthrough of the NJUNS pole attachment application and tracking process. URL: https://draftech.com/blog/njuns-pole-attachment-application-process 19. **OTMR for Fiber: What Qualifies & What Doesn't** — One-touch make-ready eligibility rules and field application guidance. URL: https://draftech.com/blog/one-touch-make-ready-otmr-fiber-guide 20. **Aerial vs Underground Fiber Construction Cost** — Cost comparison of aerial and underground fiber deployment by geography and soil type. URL: https://draftech.com/blog/aerial-vs-underground-fiber-construction-cost 21. **Microtrenching vs Traditional Trenching for Fiber** — Engineering and cost comparison for urban fiber installation methods. URL: https://draftech.com/blog/microtrenching-vs-traditional-trenching-fiber 22. **Overlashing Fiber on Existing Strand: Field Guide** — Engineering requirements and field process for overlashing new fiber on existing aerial strand. URL: https://draftech.com/blog/overlashing-fiber-cable-existing-strand-guide 23. **Fiber Construction BOM Guide — Complete Template** — How to build a complete bill of materials for fiber construction packages. URL: https://draftech.com/blog/fiber-construction-bom-template-guide 24. **Fiber Construction Package Checklist** — All deliverables required in a complete fiber construction package. URL: https://draftech.com/blog/fiber-construction-package-deliverables-guide 25. **Fiber Reel Length Planning — Splice Cost Guide** — How reel length selection affects splice count, splice cost, and construction efficiency. URL: https://draftech.com/blog/fiber-cable-reel-length-planning-splice-cost 26. **GIS Fiber Planning Cuts Costs 30%** — How GIS-integrated network planning reduces design and construction costs. URL: https://draftech.com/blog/gis-fiber-network-planning-cost-reduction 27. **Fiber As-Built GIS Standards** — Industry standards for GIS-integrated as-built documentation in fiber networks. URL: https://draftech.com/blog/fiber-network-as-built-gis-documentation-standards 28. **Telecom CAD Drafting for ISPs: What Good Looks Like** — Quality benchmarks for telecom CAD deliverables from engineering firms. URL: https://draftech.com/blog/telecom-cad-drafting-services-isps-fiber 29. **Co-op Fiber Network Design: Rural FTTH Guide** — Engineering considerations for electric cooperatives building FTTH networks in rural areas. URL: https://draftech.com/blog/fiber-network-design-electric-cooperatives-rural-isp 30. **Fiber Construction Workforce Shortage in 2026** — Impact of the labor shortage on fiber deployment timelines and how to mitigate it. URL: https://draftech.com/blog/fiber-construction-workforce-shortage-bead-2026 31. **Make-Ready Engineering Timelines** — Realistic timelines for each phase of make-ready engineering and pole attachment approval. URL: https://draftech.com/blog/make-ready-engineering-timeline-fiber-deployment 32. **ROW Permitting Delays Killing Fiber Builds** — Why ROW permitting is the leading cause of fiber construction delays and how to accelerate it. URL: https://draftech.com/blog/row-permitting-delays-fiber-deployment 33. **Railroad Permits: BNSF vs CSX vs NS** — Comparison of railroad crossing permit processes and timelines for major Class I railroads. URL: https://draftech.com/blog/railroad-crossing-permits-fiber-optic-construction 34. **Utility Coordination for Fiber Construction** — How to manage utility conflicts and coordination for aerial and underground fiber builds. URL: https://draftech.com/blog/utility-coordination-fiber-construction-process 35. **Small Cell 5G Fiber Backhaul Engineering Guide** — Engineering requirements for small cell fiber backhaul in 5G densification projects. URL: https://draftech.com/blog/small-cell-5g-fiber-backhaul-engineering 36. **OTDR Splice Loss Acceptance Criteria Guide** — Acceptable OTDR splice loss thresholds and testing procedures for fiber construction acceptance. URL: https://draftech.com/blog/otdr-testing-acceptance-criteria-fiber-splice-loss 37. **Strand Mapping Field Process** — Step-by-step field methodology for aerial strand mapping and plant inventory. URL: https://draftech.com/blog/strand-mapping-aerial-plant-assessment-process 38. **Fiber Construction Safety: OSHA Guide** — OSHA requirements and safety best practices for fiber optic construction crews. URL: https://draftech.com/blog/fiber-optic-construction-safety-osha-requirements --- ## Frequently Asked Questions **What states does Draftech International operate in?** Draftech is actively deployed in 22 states and available for deployment across all 50 U.S. states. **What pole loading software does Draftech use?** Draftech uses O-Calc Pro and SPIDAcalc for NESC-compliant pole loading analysis. **Does Draftech support BEAD program engineering?** Yes. Draftech provides HLD, LLD, coverage mapping, and compliance documentation for BEAD subgrantees. **Is Draftech a certified MBE?** Yes. Draftech International is a certified Minority Business Enterprise (MBE). **What types of clients does Draftech serve?** Regional fiber ISPs, electric cooperatives, fiber overbuilders, cable MSOs, and municipal broadband programs. **How do I contact Draftech for a project?** Email info@draftech.com, call 305-306-7407, or submit a request at https://draftech.com/contact. --- ### Fiber As-Built Documentation for BEAD Grant Closeout URL: https://draftech.com/blog/fiber-as-built-documentation-bead-grant-closeout Author: Julio Martinez, CEO | Published: April 28, 2026 Summary: BEAD subgrantees need GIS-compliant as-built documentation to close out grants. Covers required GIS projections (NAD83/WGS84), mandatory attribute fields (cable type, strand count, conduit size, splice points), the three most common failure points (incomplete attribute population, missing splice records, coordinate drift), and why as-built tracking must start before construction begins—not after. Includes state-by-state closeout examples from VA, NC, KY, and TN. Primary keyword: fiber as-built services for grant compliance ### OSP Engineering Outsourcing for Rural ISPs: What It Costs, How It Works, and When It Makes Sense URL: https://draftech.com/blog/osp-engineering-outsourcing-rural-isp Author: Julio Martinez Sr., Partner | Published: April 30, 2026 Summary: Rural ISPs scaling fiber builds under BEAD can't always hire fast enough. Covers the engineering capacity gap, what OSP outsourcing actually includes (field survey, HLD/LLD design, permitting, as-builts), three engagement models (project-based, staff augmentation, program rate), what to look for in a partner (MBE/DBE certification, GIS deliverable standards, BEAD experience), and how to structure a SOW for a rural broadband outsource engagement. Primary keyword: fiber deployment engineering support for rural ISPs ### Conduit Fill Ratio Design Guide for Fiber Networks: Sizing, Standards, and Common Mistakes URL: https://draftech.com/blog/conduit-fill-ratio-design-guide-fiber-networks Author: Devin Martinez, Partner | Published: April 28, 2026 Summary: How to calculate conduit fill ratio for fiber optic networks. Covers NEC/NFPA 70 maximum fill rules, HDPE vs. PVC conduit inner diameter calculations, the 40%/53%/31% fill rules by cable count, common oversizing and undersizing mistakes, real-world BEAD project examples, and why leaving reserve capacity saves $8,000–$47,000 in future relief bore costs. Includes a worked calculation table for 1" to 4" HDPE SDR-11 conduit. Primary keyword: conduit fill ratio design guide fiber ### 7 Ways BEAD Projects Stall Before Construction Starts URL: https://draftech.com/blog/bead-projects-stall-before-construction Author: Julio Martinez, CEO | Published: May 1, 2026 Summary: BEAD subgrantees stall before construction for 7 predictable reasons. Covers permitting delays, BEAD fabric mapping errors, incomplete field surveys, pole attachment backlogs, material lead time traps, incomplete construction packages, and ROW conflicts. Includes real OSP field examples, timeline benchmarks, and checklist-driven mitigation strategies for ISPs and subgrantees managing BEAD deployments. Primary keyword: why BEAD projects stall before construction ### Fiber Route Optimization Techniques for ISP Networks: Cut Miles, Cut Cost URL: https://draftech.com/blog/fiber-route-optimization-techniques-isp-networks Author: Omar Molina, Partner | Published: April 30, 2026 Summary: How ISPs cut fiber route miles by 30–40% using GIS analysis, terrain routing, and infrastructure reuse. Covers satellite/aerial imagery analysis for straight-run identification, existing infrastructure reuse (co-op lashing, conduit reuse), ArcGIS/QGIS least-cost path scoring formula, ROW conflict cost thresholds (railroad, water crossing, highway), and a full Midwest BEAD project case study: 47.6 miles optimized to 31.3 miles saving $2.1M on a $6.8M project. Primary keyword: fiber route optimization for isp networks ## BEAD OSP Engineering Hub URL: https://draftech.com/bead-osp-engineering Type: Service Hub Page Published: 2026-05-03 Draftech International's central BEAD engineering resource page. Covers all OSP engineering services for BEAD-funded broadband deployments: field survey and data collection, FTTH high-level design (HLD), low-level design (LLD), ROW permitting, pole loading and make-ready, CAD/GIS documentation, and as-built closeout packages. Key page content: - 7 engineering bottlenecks that stall BEAD projects before construction (bad field data, permitting delays, make-ready surprises, HLD/LLD gaps, CAD quality issues, fragmented teams, closeout risk) - 7 service cards: field survey, HLD, LLD, permitting, pole loading/make-ready, CAD/GIS, as-builts - 6-step process: free review → field survey → HLD → permitting → LLD/CAD → as-builts - 6 differentiators: MBE certified, 22 states active/all 50 available, 44,000+ miles, 2.6M+ addresses, 600+ engineers, BEAD closeout ready - State coverage grid linking to all 50 state pages - 6 FAQ questions with schema markup - Free BEAD Design Readiness Review CTA throughout Stats featured: 44,000+ miles designed, 2.6M+ addresses, 22 active states, all 50 U.S. states available, MBE certified, 600+ engineers. ## State Engineering Guides — Batch 4 (Published April 29, 2026) ### Alabama Fiber Optic Engineering URL: https://draftech.com/states/fiber-optic-engineering-alabama BEAD Allocation: $1.4B — Final Proposal approved March 23, 2026 by NTIA. 63 awarded projects totaling ~$460M. Average cost <$5,000/location — well below national average. Key utilities: Alabama Power (Southern Company), Alabama Fiber Network (3,400+ miles of middle-mile across 65/67 counties). Terrain: Black Belt clay soils, Appalachian ridges (northeast), forested rural terrain. Key permitting: ALDOT. Primary ISPs: Comcast ($132M), AT&T ($73M), ZiTEL, Yellowhammer Networks, Windstream. State program: ADECA BEAD. ### Louisiana Fiber Optic Engineering URL: https://draftech.com/states/fiber-optic-engineering-louisiana BEAD Allocation: $1.355B — First state in the nation with NTIA Final Proposal approval (November 18, 2025). First to access BEAD funds; $43M disbursed by February 2026. 80.6% fiber-to-premises. Key utilities: Entergy Louisiana, Entergy Gulf States, Cleco Power, DEMCO. Terrain: coastal wetlands/marshland (no-road-access areas in Plaquemines, Terrebonne parishes), high water table, subsidence, hurricane-resilient construction requirements (Category 4+ wind ratings). Key permitting: DOTD. State program: ConnectLA. ### Missouri Fiber Optic Engineering URL: https://draftech.com/states/fiber-optic-engineering-missouri BEAD Allocation: $1.736B — 3rd largest nationally. Final Proposal approved January 6, 2026. 204,366 eligible locations; 82% fiber technology mix. Average BEAD cost: $3,877/location. Saves ~$945M from original allocation. Key utilities: Ameren Missouri, Liberty Utilities, rural electric cooperatives (SEMO Electric, White River Valley). Terrain: Ozark limestone plateau (challenging HDD), river bottom alluvial soils, forested Ozark highlands. Key permitting: MoDOT. State program: OBD/Missouri DED. ### Indiana Fiber Optic Engineering URL: https://draftech.com/states/fiber-optic-engineering-indiana BEAD Allocation: $868M — Final Proposal approved December 2, 2025. 144,478 eligible locations; ~80% fiber mix. Total BEAD outlay: $486M. Average ~$3,700/location. Key utilities: AES Indiana, Duke Energy Indiana, Indiana Michigan Power (AEP), rural REMCs (Paulding Putnam Electric, Decatur County REMC). Terrain: glacial till (flat, productive farmland — easier bore), with some limestone karst in south. Key permitting: INDOT. State program: Indiana Broadband Office (IBO). ### Wisconsin Fiber Optic Engineering URL: https://draftech.com/states/fiber-optic-engineering-wisconsin BEAD Allocation: $1.056B — Final Proposal approved December 2, 2025; NIST approval February 9, 2026; 23 grant agreements executed by March 2026. 175,464 eligible locations; 76% fiber. Average BEAD cost: $4,019/location. Key utilities: Wisconsin Public Service (WPS/WEC Energy), Xcel Energy, Alliant Energy, numerous rural electric cooperatives (East Central Energy, Marquette-Adams). Terrain: northern Wisconsin lake country with rocky glaciated ground, frozen-ground bore planning required. Key permitting: WisDOT. State program: Wisconsin Broadband Office (PSC/WBO). ### New Jersey Fiber Optic Engineering URL: https://draftech.com/states/fiber-optic-engineering-new-jersey BEAD Allocation: $263.7M — Final Proposal approved December 26, 2025. 11,479 eligible BSLs. Total BEAD outlay: $62.2M (saves ~$201M). Average BEAD cost/location: ~$5,421. Key utilities: Jersey Central Power & Light (JCP&L/FirstEnergy), PSE&G, Atlantic City Electric (Exelon). Terrain: Highlands (Morris, Sussex, Warren counties) — rocky glaciated granite/quartzite; Pinelands/Pine Barrens (Burlington, Ocean) — sandy soil but Pinelands Commission environmental permitting. Post-Sandy resilience standards apply coastally. Key permitting: NJDOT + Pinelands Commission. State program: NJBPU/OBC. ### Massachusetts Fiber Optic Engineering URL: https://draftech.com/states/fiber-optic-engineering-massachusetts BEAD Allocation: $147.4M — Final Proposal approved December 19, 2025; formal award February 6, 2026. 3,808 eligible BSLs; 5 subgrantees. Total BEAD outlay: $18.8M (saves ~$128.6M — among highest savings rates nationally). Key utilities: Eversource Energy (dominant New England utility), National Grid Massachusetts, 41 municipal light plants (MLPs). Terrain: rocky glaciated terrain, dense suburban utility corridors. Key permitting: MassDOT. State program: Massachusetts Broadband Institute (MBI/MassTech). ### Maryland Fiber Optic Engineering URL: https://draftech.com/states/fiber-optic-engineering-maryland BEAD Allocation: $267.7M — Final Proposal approved February 4, 2026 (announced by Governor Wes Moore). 9,014 BOTB eligible locations. Total BEAD outlay: $79.1M. Average BEAD cost/location: $8,092 (among the highest nationally — reflects difficult terrain). Technology mix: 44% fiber, 32% HFC, 24% LEO satellite. Key utilities: BGE (Exelon), Pepco (Exelon), Delmarva Power (Exelon), Potomac Edison (FirstEnergy/Allegheny Power). Terrain: Western Maryland Appalachian mountains (Garrett, Allegany counties — hardest ground in state), Eastern Shore coastal/tidal soils. Key permitting: SHA. State program: OSB/Connect Maryland (DHCD). ### Nevada Fiber Optic Engineering URL: https://draftech.com/states/fiber-optic-engineering-nevada BEAD Allocation: $416.7M — Final Proposal approved January 8, 2026. 26,236 eligible BSLs. Total BEAD outlay: $170.7M (saves ~$246M). Average cost: $6,529/location. Technology mix: 64.9% fiber, 28.2% LEO satellite, 4% FWA, 2.9% HFC. Key utilities: NV Energy (Berkshire Hathaway Energy). 18 awarded providers including Cox, AT&T, Anthem Broadband, Commnet. Terrain: Basin and Range desert hardrock (basalt, caliche, granite), extreme temperature swings (-20°F to 115°F), BLM federal land ROW covers most of rural Nevada. Key permitting: NDOT + BLM. State program: OSIT High Speed Nevada Phase III. ### Utah Fiber Optic Engineering URL: https://draftech.com/states/fiber-optic-engineering-utah BEAD Allocation: $317.4M — Final Proposal approved December 19, 2025. 30,215 eligible BSLs. Total BEAD outlay: $207.4M. Average cost: ~$6,867/location. Technology mix: 54.3% fiber, 26.8% LEO satellite, 18.9% FWA. Key utilities: Rocky Mountain Power (PacifiCorp/Berkshire Hathaway Energy) — serves ~95% of Utah electric customers; Dixie Power, Moon Lake Electric Association. Terrain: high desert plateau, Uintah Basin, canyon country with extreme elevation changes, BLM federal land ROW. Top subgrantee: Strata Networks ($49.6M). Key permitting: UDOT + BLM. State program: Utah Broadband Center (UBC). ## Sitemap Full sitemap: https://draftech.com/sitemap.xml ## Alaska — Fiber Optic Engineering URL: https://draftech.com/states/fiber-optic-engineering-alaska BEAD Allocation: $1,017,139,672 | NTIA Approved: February 24, 2026 Total BEAD Awards: $629,172,951 | Eligible Locations: 46,192 Key Subgrantees: Alaska Communications ($124M+, fiber/fixed wireless), GCI ($121.2M, AIRRAQ Network Western Alaska), Quintillion ($48M, submarine fiber) Technology: 51% fiber, 34% LEO satellite (SpaceX), 15% fixed wireless Admin Agency: Alaska Broadband Office (ABO) | Regulator: Regulatory Commission of Alaska (RCA) Key Terrain: Permafrost (interior/north), mountainous (south), tundra (west); 3-4 month build season Key Utilities: Alaska Power & Telephone (AP&T), GVEA, Matanuska Electric Association, Chugach Electric Engineering Challenges: Permafrost thermopile systems required, -40°C fiber specs, ANCSA corporation land consultation, barge-season material staging, DOT&PF + BLM + USFS + Corps permitting ## Arkansas — Fiber Optic Engineering URL: https://draftech.com/states/fiber-optic-engineering-arkansas BEAD Allocation: $1,024,303,994 | NTIA Approved: November 25, 2025 Total BEAD Awards: $305,491,845 (saved $718,812,149 — one of nation's largest savings rates) Eligible Locations: 79,293 | Avg Cost/Location: $3,866 Admin Agency: ARConnect (Arkansas State Broadband Office) | Regulator: Arkansas Public Service Commission (APSC) Key Terrain: Ozark Mountains (limestone karst, sinkholes), Ouachita Mountains (sandstone/shale), Arkansas Delta (flat alluvial, high water table), coastal plain south Key Utilities: Entergy Arkansas (dominant IOU), rural electric cooperatives (South Central, Four County, Tri-County) Engineering Challenges: Ozark karst pre-bore GPR investigation, Delta conduit buoyancy in high water table cotton fields, ARDOT + USFS dual permitting, Q2 2026 construction start ## Connecticut — Fiber Optic Engineering URL: https://draftech.com/states/fiber-optic-engineering-connecticut BEAD Allocation: $144,180,793 | NTIA Approved: November 18, 2025 Total Deployment Cost: $7,215,750 | Eligible Locations: 1,782 (717 identified as hardest-to-connect in 76 towns) Admin Agency: CT DEEP (Department of Energy and Environmental Protection) | Regulator: PURA Key Terrain: Metacomet Ridge (basalt traprock — expensive excavation), Western Uplands (granite/gneiss), Connecticut River valley (flat, sandy), coastal lowlands (tidal wetland permitting) Key Utilities: Eversource Energy (dominant), United Illuminating (Avangrid subsidiary, New Haven area), Frontier Communications Engineering Challenges: Traprock rock excavation, PURA joint-use tariff process, DEEP inland wetland permits, colonial town center archaeological review, ConneCTed Communities prior work means BEAD covers only hardest remaining locations ## Delaware — Fiber Optic Engineering URL: https://draftech.com/states/fiber-optic-engineering-delaware BEAD Allocation: $107,000,000+ | NTIA Approved: January 14, 2025 (one of first 2 states approved) Total Deployment: $17.4M | Eligible Locations: 5,721 (New Castle: 554, Kent: 1,720, Sussex: 3,447) Subgrantees: Verizon and Comcast (all-fiber to all 5,721 locations) | Technology: 100% fiber Admin Agency: Delaware Broadband Office (DBO/DTI) | Regulator: Delaware PSC Key Terrain: Flat throughout; Piedmont (northern New Castle County); Coastal Plain (rest of state); Sussex County flat sandy coastal plain, high groundwater Key Utilities: Delmarva Power & Light (Exelon/Pepco subsidiary), Delaware Electric Cooperative (Sussex County) Engineering Challenges: High groundwater in Sussex County, DNREC tidal wetland permitting, Chesapeake & Delaware Canal crossings (Army Corps), municipality-by-municipality ROW permitting ## Hawaii — Fiber Optic Engineering URL: https://draftech.com/states/fiber-optic-engineering-hawaii BEAD Allocation: $149,484,494 | NTIA Approved: November 18, 2025 / confirmed December 23, 2025 Total Deployment: $30,672,750 | Eligible Locations: 7,033 Technology: 81.7% fiber (Hawaiian Telcom, 4-yr period) | 18.3% LEO satellite (Amazon Leo, 10-yr period) Avg Cost/Location: $4,361 | Savings: $118,811,744 Admin Agency: University of Hawaiʻi Broadband Office (UHBO) — "Connect Kākou" program | Regulator: Hawaiʻi PUC Key Terrain: Volcanic basalt (all islands — expensive drilling), steep topographic gradient, lava tube voids, inter-island requires submarine cable Key Utilities: HECO (Hawaiian Electric), Maui Electric, KIUC (Kauai Island Utility Cooperative), Hawaiian Telcom Engineering Challenges: Basalt rock excavation, DLNR Conservation District permitting, SHPD/OHA cultural review, Jones Act submarine cable engineering, inter-island connectivity ## Iowa — Fiber Optic Engineering URL: https://draftech.com/states/fiber-optic-engineering-iowa BEAD Allocation: $415,331,313 | NTIA Approved: November 24, 2025 Admin Agency: Iowa Department of Management (DOM) via NOFA #009 | Regulator: Iowa Utilities Commission (IUC) Key Terrain: Flat agricultural (Des Moines Lobe glacial till, most of state); Driftless Area northeast (limestone bluffs/karst, Mississippi River corridor); Loess Hills west Key Utilities: MidAmerican Energy (Berkshire Hathaway, central/western IA), Alliant Energy/IPL (eastern IA), rural electric cooperatives, Iowa RLECs own telco poles Key Subgrantees: Rural telephone cooperatives (Shellsburg Cablevision, Ace Telephone, Webster-Calhoun, Miles Communications, Sully Telephone), SpaceX Iowa ($5.7M total) Engineering Challenges: Agricultural tile drainage systems (undocumented, liability if severed — must locate before trenching), Iowa DOT + county secondary road board permitting (variable quality), Driftless Area karst vs. flat agricultural terrain divide ## Kansas — Fiber Optic Engineering URL: https://draftech.com/states/fiber-optic-engineering-kansas BEAD Allocation: $166,600,000 | NTIA Approved: December 5, 2025 Eligible Locations: 26,673 | Technology: 30% fiber, 67% fixed wireless, 3% LEO Savings: 63% reduction from original allocation | Private Match: $61.3M | Avg Cost/Location: $6,791 Key Subgrantees: 3JL Holdings ($58.6M), IdeaTek Telcom ($43.4M), Resound Networks ($13.9M), Giant Communications ($18M), Pioneer Telephone ($7.8M) Admin Agency: KOBD (Kansas Office of Broadband Development) | Regulator: Kansas Corporation Commission (KCC) Key Terrain: Great Plains/High Plains (flat, caliche/limestone, few poles in west), Flint Hills (chert formations — destroys boring equipment), river valleys (floodplain permitting) Key Utilities: Evergy (dominant IOU, eastern/central KS), Kansas Electric Cooperatives (Sunflower Electric, Prairie Land, Lane-Scott), rural telephone companies Engineering Challenges: Flint Hills chert boring costs, District C NESC wind loading (highest in continental U.S.), Ogallala Aquifer caliche in west, agricultural tile drainage in east, KDOT permitting ## Mississippi — Fiber Optic Engineering URL: https://draftech.com/states/fiber-optic-engineering-mississippi BEAD Allocation: $1,203,561,563 | NTIA Approved: February 9, 2026 Total BEAD Awards: $508M+ | Private Match: $321M | Eligible Locations: 93,283 Subgrantees: 12 providers (C Spire, TEC/Telepak Networks, Swyft Fiber, TVI Fiber, Bruce Telephone, and others) Admin Agency: BEAM (Office of Broadband Expansion and Accessibility of Mississippi) | Regulator: Mississippi PSC Key Terrain: Mississippi Delta (flat alluvial floodplain, heavy swelling clay, high water table, levee roads), Loess Hills (erosion-prone loess bluffs), Central Hills (rolling red clay), Piney Woods (sandy soils), Gulf Coast (hurricane design standards) Key Utilities: Entergy Mississippi (central/western MS), Mississippi Power (Southern Company, SE MS), numerous rural electric cooperatives Engineering Challenges: Delta swelling clay (conduit lateral pressure, corrosive to metallic hardware), elevated levee/causeway roads with limited ROW, MDOT permitting + slow Delta county capacity, Gulf Coast hurricane loading requirements ## Nebraska — Fiber Optic Engineering URL: https://draftech.com/states/fiber-optic-engineering-nebraska BEAD Allocation: ~$324.5M | NTIA Approved: December 3, 2025 Total BEAD Deployment: $44.5M federal + $21M private (covers last ~2% of state still unserved) Admin Agency: Nebraska Broadband Office (NBO) | Regulator: Nebraska Public Service Commission Key Terrain: Nebraska Sandhills (north-central — grass-stabilized sand dunes, Western Hemisphere's largest; aerial preferred to avoid dune destabilization), Loess Hills (eastern), agricultural Great Plains Key Utilities: Nebraska Public Power District (NPPD — public power, not IOU, serves most rural NE), Lincoln Electric System (municipal), OPPD (Omaha area), Norris Public Power District, rural electric cooperatives Engineering Challenges: Sandhills aerial construction logistics (few paved roads, remote camp), public power district attachment processes (different from IOU), high wind loading in western NE, agricultural tile drainage in eastern NE, NDOT permitting ## Oklahoma — Fiber Optic Engineering URL: https://draftech.com/states/fiber-optic-engineering-oklahoma BEAD Allocation: ~$428M grants | NTIA Approved: April 22, 2026 (one of last 3 states) Total Investment: $574M | Eligible Locations: 40,509 | Coverage: All 77 counties Technology: 70%+ fiber, 20% fixed wireless, <10% LEO | Subgrantees: 24 (75% local OK-based) Admin Agency: Oklahoma Broadband Office (OBO) | Regulator: Oklahoma Corporation Commission (OCC) Key Terrain: Ouachita Mountains (SE — sandstone ridges), Ozark Plateau (NE — limestone karst), Cross Timbers (central — dense root systems), Red Bed Plains, Wichita Mountains (SW — granite plutons), Great Plains (west) Key Utilities: PSO/AEP (eastern OK), OG&E (central OK), Western Farmers Electric Cooperative, Grand River Dam Authority (GRDA), numerous rural electric cooperatives Engineering Challenges: Tribal sovereign ROW coordination (Cherokee, Choctaw, Chickasaw, Creek/Muscogee, Osage and more — more tribal land than any state), Cross Timbers root systems complicate trenching, Wichita Mountains granite excavation, Red River USACE permitting, Grand River reservoir crossings ## Rhode Island — Fiber Optic Engineering URL: https://draftech.com/states/fiber-optic-engineering-rhode-island BEAD Allocation: $108,718,821 | NTIA Approved: November 18, 2025 Total Deployment: $10,566,150 | Eligible Locations: 2,622 Technology: ~81% fiber, remainder LEO/other | Avg Cost/Location: ~$4,030 Admin Agency: Rhode Island Commerce Corporation (RICC — quasi-public economic development agency) | Regulator: RI PUC Key Terrain: Blackstone River Valley (northeast — granite/gneiss, mill towns), Western RI (shallow ledge rock — granite at/near surface), Narragansett Bay coast (tidal wetlands), South County coastal lowlands, Block Island (offshore — submarine cable from Point Judith, 13 miles) Key Utilities: National Grid (UK-owned, dominant electric utility), Cox Communications (dominant cable ISP), Verizon (ILEC, telco poles) Engineering Challenges: Western RI ledge rock excavation, Block Island submarine cable (full marine engineering project), CRMC Narragansett Bay coastal permitting, National Grid joint-use (UK administrative culture), RIDEM inland wetland permits, historic district archaeological review (Providence area) --- ## What Is a Pole Loading Analysis? NESC Compliance Explained **URL:** https://draftech.com/blog/what-is-a-pole-loading-analysis **Published:** 2026-05-26 | **Author:** Julio Martinez Sr., Chairman & Partner **Category:** Pole Loading A pole loading analysis is a structural engineering calculation that determines whether a utility pole can safely support a new fiber cable attachment under NESC standards. Required before any utility will approve a make-ready application. Uses O-Calc Pro or SPIDAcalc to model vertical, horizontal, and transverse loads. Output is a PE-stamped report with per-pole capacity percentages and remediation recommendations for failing poles. Cost: $45–$75 per pole. Results directly determine make-ready scope and budget. --- ## What Is Make-Ready Engineering in Telecom? The 5-Phase Process Explained **URL:** https://draftech.com/blog/what-is-make-ready-engineering-telecom **Published:** 2026-05-27 | **Author:** Omar Molina, Managing Director **Category:** Make-Ready Engineering Make-ready engineering prepares utility poles for new fiber attachments through a 5-phase process: (1) field survey documenting all poles and existing attachments, (2) pole loading analysis identifying rearrangement needs, (3) make-ready application filed with each pole owner, (4) physical rearrangement of existing attachments by utility or OTMR contractor, (5) final clearance inspection and as-built documentation. Timelines range from 60 days to 18+ months depending on pole ownership and utility response windows. The new fiber attacher pays all costs. --- ## OSP Engineering Services for Rural Electric Cooperatives: What Co-ops Need to Know **URL:** https://draftech.com/blog/osp-engineering-services-for-rural-electric-cooperatives **Published:** 2026-05-28 | **Author:** Julio Martinez Sr., Chairman & Partner **Category:** Rural Broadband Electric cooperatives building fiber face a unique engineering environment — they own the poles, operate the network, and serve members simultaneously. OSP engineering for co-ops covers joint-use analysis on co-op pole infrastructure, USDA ReConnect GIS and documentation compliance, NRECA broadband standards, and make-ready coordination with third-party cable/telephone attachers on co-op poles. Full scope: field survey, route design, permit drawings, pole loading analysis, utility coordination, and construction-ready deliverables in USDA-compliant format. --- ## Fiber As-Built Services for Grant Compliance: NTIA Schema, GIS, and PE Sign-Off **URL:** https://draftech.com/blog/fiber-as-built-services-for-grant-compliance **Published:** 2026-05-29 | **Author:** Devin Martinez, COO & Partner **Category:** As-Built Documentation Grant-compliant fiber as-builts require NTIA Broadband Data Collection GIS schema compliance (location IDs, technology codes, deployment status, speed attributes), PE-stamped record drawings, GPS-tagged photo documentation at each infrastructure element, and program-office-specific submission formatting. Most common rejection triggers: GIS attribute schema errors, PE stamp on wrong document version, photo documentation gaps, and as-built drawings that don't reflect final construction. Contractor as-builts are a starting point — not a finished grant deliverable. Spec as-built services before construction begins, not at closeout. ## OSP Engineering Services for ISPs: What's Included, What It Costs, and How to Evaluate a Firm URL: https://draftech.com/blog/osp-engineering-services-for-isps Author: Julio Martinez | Published: 2026-05-23 | Publisher: Draftech International Description: 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. ### FAQ --- ## HLD Design Services for FTTH Networks: What's Included and What to Expect URL: https://draftech.com/blog/hld-design-services-ftth-networks Author: Julio Martinez | Published: 2026-05-24 | Publisher: Draftech International Description: What HLD design services actually include for FTTH builds — feeder routing, node placement, fiber count decisions, BEAD compliance, and how to evaluate what you're getting from an engineering firm. IN THIS ARTICLE - What an HLD Actually Is — and What It Isn't - What's Included in a Full HLD Design Service - FTTH-Specific HLD Considerations - HLD for BEAD Projects — What State Offices Actually Want - The 5 Things a Bad HLD Gets Wrong - What the HLD-to-LLD Handoff Should Look Like - How Draftech Delivers HLD Services - Starting an HLD Engagement I've been doing OSP engineering for 17 years, and one pattern I see constantly: ISPs and electric cooperatives commissioning an HLD for an FTTH build without a clear picture of what the deliverable should actually look like. They engage a firm, receive a PDF with some colored lines on a county map, and assume that's what an HLD is. Then construction starts, costs blow out, and the post-mortem reveals that the "HLD" never answered the questions it was supposed to answer. This post is for anyone who is about to commission an HLD — or who has received one and isn't sure whether it's any good. I'll explain what a proper HLD design service actually delivers, what FTTH-specific decisions it must address, and what the failure modes look like when firms cut corners on the work. ## What an HLD Actually Is — and What It Isn't The term "high-level design" gets used loosely enough that it's worth being precise. An HLD for an FTTH network is a decision-making document. It answers the architecture questions that every downstream engineering task depends on: where the fiber routes go, how many fibers are on each segment, where nodes and hubs are positioned, how the PON splits are structured, and which sections go aerial versus underground. Every one of those decisions has cost implications, and most of them are expensive to change once LLD begins. An HLD is not a sketch. It is not a preliminary route map drawn over a satellite image. And it is not a redline of someone else's cable TV plant. I've seen all three delivered as HLDs. The difference between a sketch and an HLD is that the HLD is a structured engineering analysis — it documents not just what the network will look like, but why it's designed that way, with the technical and economic logic behind each major choice. **How this relates to LLD:** If you want to understand the formal distinction between HLD and LLD before going deeper here, our post on the difference between HLD and LLD in fiber design covers the conceptual framework. This post focuses specifically on what a good HLD design service includes — what the firm does, what the outputs are, and what bad HLD work looks like. ## What's Included in a Full HLD Design Service A comprehensive OSP engineering HLD for an FTTH network covers several distinct work areas. Here's what each one entails. ### Feeder Route Development The feeder layer is the backbone of your FTTH plant — the high-fiber-count cables running from your central office or hub sites to the distribution areas. Feeder route planning involves identifying the optimal path from the hub to each distribution zone, considering existing pole infrastructure, underground conduit availability, ROW access, and topographic constraints. On a typical rural FTTH build, feeder cables run 144 to 288 fibers. Getting the route wrong adds cost in two ways: mileage and make-ready. Every extra quarter-mile of feeder is real money, and every extra pole attachment you don't need is a permit you didn't have to pull. ### Node Architecture and Placement An HLD defines the distribution node structure — where optical amplification or splitting occurs, how many serving area interfaces (SAIs) or fiber distribution hubs (FDHs) are needed, and what their geographic footprint is. Node placement drives splice count, drop cable length, and the overall cost per passing. Poorly placed nodes are one of the most common sources of budget overruns in FTTH builds. I've reviewed HLDs where the node placement was based on aesthetics rather than subscriber density — the engineer drew equally-spaced circles on a map instead of modeling where the actual served locations are. ### Fiber Count Decisions This is one of the most consequential decisions in the HLD, and one of the most frequently underspecified. The HLD must define fiber counts for each segment: the feeder, the distribution cables, and the drop allocation. These counts need to be derived from subscriber density modeling and PON architecture, not guessed. Over-fibering wastes capital. Under-fibering means expensive rip-and-replace when you hit capacity. On a 1,200-subscriber rural deployment I worked on in Tennessee, the initial HLD specified a uniform 96-fiber distribution cable throughout — the engineer had just picked a number. Our revised design ranged from 48 fibers in low-density areas to 144 fibers approaching the town center, cutting cable cost by 18% while adding enough capacity headroom for the growth projections. ### Splice Point Placement The HLD defines where splices occur: at node locations, at direction changes, and at the transition from feeder to distribution. Splice spacing matters because each splice enclosure is a cost item in construction and a maintenance point for the life of the network. Good HLD work establishes splice intervals based on cable reel length (typically 3,000–5,000 feet depending on cable type), minimizes unnecessary mid-span splices, and positions splice points at accessible locations — poles rather than mid-span, manholes rather than mid-duct. ### Aerial vs. Underground Route Decisions The HLD should make explicit, documented decisions about construction method for each route segment. These decisions depend on existing infrastructure (is there usable strand?), terrain, ROW type, and cost modeling. Underground routes in soft soil can cost $40–$80 per foot to install. Aerial on existing strand can be a fraction of that. But underground protects against storm damage and often has lower long-term maintenance cost. A proper HLD doesn't leave this to the LLD engineer — it establishes the method and documents the rationale, so construction budgets can be built on real data rather than assumptions. Our field survey data feeds directly into this analysis; you can't make good aerial vs. underground decisions without current conditions on the pole plant. ### Route Feasibility Assessment The HLD must flag obvious obstacles: railroad crossings, river crossings, congested aerial plant where make-ready will be heavy, underground segments where existing conduit occupancy is unknown. These items belong in the HLD because they affect the budget estimate and the project schedule — not as surprises during LLD or construction. ## FTTH-Specific HLD Considerations FTTH on a passive optical network has design constraints that don't exist in point-to-point or legacy copper plant. The HLD has to address these explicitly. ### PON Architecture Selection The HLD should specify whether the deployment uses GPON, XGS-PON, or another standard — and document why. This isn't a procurement decision; it's an engineering decision that affects the optical link budget, the split ratios the design can support, and the capacity available per subscriber. XGS-PON at 10 Gbps symmetrical has different design implications than GPON at 2.5/1.25 Gbps, even when the physical plant looks identical. The HLD needs to model both directions. ### Split Ratio Modeling A standard GPON network supports up to 128:1 splitting, but deploying at 128:1 means every subscriber on that PON shares a 2.5 Gbps downstream pool. Most operators target 32:1 to 64:1 in practice, depending on their service tier commitments and subscriber density. The HLD must define the split ratios for each distribution area, because split ratio determines how many OLT ports you need, how many FDH enclosures you'll deploy, and what the optical power budget is at the subscriber's ONT. Get this wrong in the HLD and you're either over-provisioning OLT capacity or discovering at activation that your link budget is 3 dB short. ### FDH and FDT Placement Fiber distribution hubs (FDHs) and fiber distribution terminals (FDTs) are the physical manifestation of your PON split structure. Their placement drives drop cable length, which drives per-subscriber cost. The HLD should model FDH locations to minimize weighted average drop distance across all subscribers in each serving area. In a rural deployment with dispersed housing, this analysis can significantly reduce drop cable cost — sometimes by several hundred dollars per subscriber compared to a layout that wasn't optimized. For more on FDH sizing specifically, our post on fiber distribution hub sizing for FTTH PON covers the sizing methodology in detail. ### Subscriber Density Modeling Good HLD work is grounded in real subscriber location data, not county parcel counts or census estimates. We geocode actual addresses, identify the served locations in the project footprint, and model the distribution design around where people actually live. In rural areas, this often produces a fundamentally different distribution design than one based on population density maps — because the real locations are clustered in ways that don't show up in aggregate data. ## HLD for BEAD Projects — What State Offices Actually Want BEAD-funded deployments have specific HLD requirements that commercial builds don't face. If you're a subgrantee preparing your engineering package, the HLD is a compliance document as much as a design document. Our post on fiber network HLD requirements for BEAD subgrantees goes into this in full detail, but the key points: ### NTIA-Aligned Documentation The NTIA's Notice of Funding Opportunity and state-level program requirements don't use the term "HLD" explicitly, but the engineering content they require is HLD work: network topology documentation, technology selection justification, coverage area definition with BSL (Broadband Serviceable Location) mapping, and cost modeling tied to the engineering design. Your HLD package needs to be structured so that a state broadband office reviewer can trace the engineering logic from subscriber location to network architecture to cost estimate. ### GIS Deliverables Every BEAD state program I've worked with requires GIS deliverables formatted to their specific schema. This is not a conversion from AutoCAD at the end of the project. The HLD should be developed natively in GIS — ArcGIS or equivalent — so that the spatial data is accurate and complete from the beginning. State schemas vary, but typically require fiber route centerlines with segment attributes, node and hub points with equipment specifications, splice locations, and service area polygon coverage tied to the BSL fabric. For more on the engineering requirements tied to BEAD funding, see our full post on BEAD engineering requirements in 2026. ### PE Review Triggers Some state BEAD programs require PE (Professional Engineer) review and stamp on the engineering package before subgrant execution. The HLD is typically included in that review. This means it needs to be a real engineering document — not a colored route map and a narrative. If you're working with an engineering firm that can't produce a PE-stamped HLD package, that's a problem you'll discover at the worst possible moment. **BEAD timeline trap:** State broadband offices are seeing HLD packages submitted in AutoCAD DWG format when their schema requires ESRI geodatabase. The conversion isn't trivial — it introduces attribute errors and geometry issues. Build GIS-native from day one, or plan for a rework cycle that costs you schedule time you don't have. ## The 5 Things a Bad HLD Gets Wrong After reviewing a lot of HLD packages — both ones my team produced and ones clients brought to us after getting burned — I've seen the same failure modes repeat. These aren't opinions about style. They're problems that translate directly into construction budget overruns and project delays. Our post on common FTTH HLD design mistakes covers some of these with more depth, but here's the core list: ### 1. No Fiber Count Logic The most common deficiency I see: fiber counts specified as round numbers with no derivation. "144-fiber feeder" because that's a standard cable size, not because anyone modeled the subscriber density and PON architecture. Fiber count decisions in an HLD should be traceable — you should be able to see the subscriber count, the split ratio, the distribution architecture, and the resulting fiber demand on each segment. If you can't, the number is a guess. ### 2. Node Placement Based on Geography, Not Demand Drawing node locations on a map based on geographic centrality rather than subscriber clustering produces a design that looks balanced but performs poorly on cost. Nodes should be positioned to minimize weighted drop cable length across the actual served locations. In terrain-constrained areas, this sometimes means a non-obvious node location that significantly reduces construction cost compared to the "obvious" spot in the center of a serving area. ### 3. Missing Route Feasibility Flags An HLD that doesn't identify railroad crossings, river crossings, or segments with heavy make-ready burden gives the client a false cost picture. These obstacles don't disappear; they just show up later as change orders. Part of the HLD work is reviewing the route against known permit and construction constraints and flagging anything that carries above-average cost or schedule risk. ### 4. Aerial vs. Underground Left Ambiguous When the HLD says "aerial or underground TBD per field survey," that's not a design decision — it's a deferral. The cost difference between aerial and underground can be $50–$150 per foot. If you're building a budget estimate from an HLD that hasn't made this call, your estimate has a very wide error bar. Good HLD work makes the call, documents the basis, and flags any segments where field survey data needs to be collected before the decision can be finalized. ### 5. Optical Link Budget Never Modeled On a PON network, the optical link budget determines whether your design will actually work. It's the calculation that accounts for fiber attenuation (typically 0.35 dB/km for single-mode at 1310 nm), splitter insertion loss (typically 3.6 dB for a 1:2 split, cumulative for cascaded splits), connector losses, and the optical power budget of the OLT and ONT equipment. An HLD that specifies 1:64 splitting without verifying the optical link budget on the longest drop in each serving area is a design that may fail in the field. I've seen this exact problem — an operator activates service and discovers that subscribers at the edges of a serving area have 3–5 dB of margin deficit. The fix at that point is either cascaded amplification (expensive) or network redesign (worse). ## What the HLD-to-LLD Handoff Should Look Like The quality of the HLD determines how smoothly LLD proceeds. A clean HLD-to-LLD handoff has specific characteristics: - **Defined route centerlines in GIS** — not sketched on PDF, but spatially accurate lines that LLD engineers can place poles and splice points along without reinventing the routing. - **Fiber count tables per segment** — so LLD engineers know exactly what cable to specify without re-deriving the fiber demand. - **Node and hub locations with equipment specs** — what equipment goes where, so LLD can start placement drawings from a defined starting point. - **Construction method specified per segment** — so LLD engineers know whether they're designing aerial or underground construction details. - **Risk flags documented** — railroad crossings, utility conflicts, make-ready-heavy sections flagged so LLD can sequence those tasks first. A messy HLD handoff forces LLD engineers to re-answer questions the HLD was supposed to settle. That's wasted time, and it introduces inconsistency — two LLD engineers interpreting an ambiguous HLD often produce different answers. Our fiber network design cost guide covers how this re-work compounds throughout the project budget. **Real-world consequence:** On a mid-Atlantic FTTH project we reviewed, the client's HLD had been produced by a firm that delivered route lines on PDF and a narrative document. When LLD began, engineers spent three weeks resolving ambiguities in fiber counts and node placement before they could start drawing. That's engineering time that added directly to project cost — and pushed the permit application start by almost a month. ## How Draftech Delivers HLD Services Our HLD workflow is self-performed — no subcontractors, no outsourced GIS processing. The team that does the field survey is the same team feeding data into the design, which eliminates the data translation errors that occur when survey data gets handed off between firms. ### Workflow and Timeline A typical FTTH HLD engagement at Draftech runs 5–8 weeks for a deployment in the 1,500–3,500 subscriber range. Week one is data intake: existing infrastructure data, subscriber location list, any prior survey or engineering records the client has. Weeks two and three are route development and architecture design — feeder routing, node placement, fiber count modeling, PON architecture. Weeks four and five are deliverable development: GIS package, design narrative, cost estimate basis document, and the review cycle. We build in one round of client review with a comment resolution period before final delivery. Larger projects — multi-county BEAD deployments, projects over 5,000 subscribers, or builds with complex terrain — run 10–14 weeks. We staff projects based on scope, not a fixed team size; on a large BEAD HLD, we'll typically have three to five engineers on the project simultaneously working different geographic zones in parallel. ### Deliverable Format Our standard HLD deliverable package includes: - ESRI File Geodatabase with all route, node, and subscriber data - PDF map set at county and project-area scale - Fiber count matrix by segment - Node and hub schedule with equipment specifications - Splice point list with coordinates - Optical link budget worksheets for each PON segment - Design narrative documenting major decisions and their basis - Preliminary cost estimate by segment and construction type For BEAD projects, we format the GIS deliverables to the applicable state broadband office schema as part of the standard package — not as an add-on that gets tacked on at the end. ### Revision Cycles One revision cycle is included in our standard HLD engagement. Revisions requested after the HLD is finalized — because the client's service area changed, or because a competing route was identified after delivery — are scoped and priced separately. We're clear about this upfront because scope creep on HLD work is real, and ambiguous revision policies are one of the most common sources of cost disputes between clients and engineering firms. ## Starting an HLD Engagement If you're preparing for an FTTH build — whether it's BEAD-funded, electric co-op broadband, or a commercial ISP deployment — the HLD is the foundation everything else is built on. The decisions made in the HLD determine construction cost, LLD scope, make-ready requirements, and whether the network actually performs at the subscriber level once it's built. We work with ISPs, electric cooperatives, and BEAD subgrantees across 22 active states, with our teams deployable to all 50. Projects range from 500-subscriber rural builds to multi-county deployments with 15,000+ subscribers. If you're ready to start an HLD engagement, or if you have an existing HLD you want a second opinion on before LLD begins, reach out at info@draftech.com. Tell us the project size, the target service area, and where you are in the project timeline — we'll respond with a realistic scope and schedule. More context on our full engineering process is at our OSP engineering services page. If you're budgeting for the full design cycle, our fiber network design cost guide breaks down what to expect across HLD, LLD, and construction support phases. ### FAQ --- ## OSP Engineering Services Pricing Per Mile: What Drives the Cost and What to Budget URL: https://draftech.com/blog/osp-engineering-services-pricing-per-mile Author: Julio Martinez | Published: 2026-05-25 | Publisher: Draftech International Description: Real per-mile pricing for OSP engineering services — what aerial vs underground costs, what pole loading and permitting add, and what factors drive the range from $600 to $3,200/mile. IN THIS ARTICLE - Why OSP Engineering Quotes Vary So Much - The Per-Mile Cost Breakdown by Service - Aerial vs. Underground: How Build Type Drives Engineering Cost - What Pole Count and Density Do to Your Budget - Permit Complexity: The Wildcard Line Item - What Cheap OSP Engineering Actually Costs You - How to Scope and Budget Correctly From the Start - Getting a Per-Mile Estimate for Your Project I get asked some version of this question at least twice a week: "What does OSP engineering cost per mile?" My honest answer is $600 to $3,200, 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 $780, $1,340, and $2,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 $780 may be quoting field survey and HLD only — no pole loading, no LLD, no permitting packages. The firm at $2,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. **Quick sanity check:** If a quote looks significantly lower than others you've received, ask the firm to list every deliverable included in the per-mile rate before you sign anything. The gap usually becomes obvious within about 60 seconds of that conversation. ## The Per-Mile Cost Breakdown by Service Here's how the individual services price out when broken down separately. These ranges reflect typical project conditions — not the cheapest possible execution and not nightmare-complexity builds. Service Per-Mile Range Notes Field Survey $120–$380/mile Wider range for terrain, pole density, deliverable format High-Level Design (HLD) $80–$180/mile Lower end for straightforward routes; higher for complex splits Low-Level Design (LLD) $220–$580/mile Biggest driver is pole count and underground complexity Pole Loading Analysis $140–$420/mile Per-pole rate × poles per mile; aerial routes only Permitting $180–$600/mile Railroad crossings, DOT corridors, waterways push toward top As-Built Documentation $90–$250/mile Higher for BEAD-compliant GIS deliverables Full-scope from survey through as-builts: **$600–$3,200 per mile**. The low end assumes a clean aerial route, low pole density, a single permitting jurisdiction with a cooperative process, and standard deliverable formats. The high end reflects underground construction, high pole density with a meaningful percentage of overstressed poles, multiple permit types including railroad and DOT, and enhanced GIS deliverables for grant closeout. On a typical 50-mile rural aerial project — something we'd see from a smaller RDOF or BEAD subgrantee — the blended all-in engineering cost tends to land around $1,100–$1,600 per mile when the scope is properly defined upfront. Suburban projects with more permit complexity run $1,600–$2,400. Mixed aerial/underground with railroad crossings and DOT corridors: $2,100–$3,000. ## 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 $14–$38 per pole depending on complexity. LLD design runs $9–$22 per pole. Permit processing runs $8–$18 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. **Practical implication for budgeting:** If you're getting per-mile quotes for an aerial project, ask each firm what pole density they're assuming. A firm assuming 12 poles/mile on a route that actually runs 28 poles/mile will deliver a quote that's off by a factor of two — not because they're dishonest, but because they're estimating differently than your route requires. ## 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: $8–$18 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. ### FAQ ---