FTTH design, OSP engineering, pole loading, and permitting across Ohio — northern flatlands, Appalachian foothills, and metro fringe. BroadbandOhio BEAD-ready. AEP, FirstEnergy, and Duke territories. 600+ field engineers.
Ohio's $793 million BEAD allocation is administered by BroadbandOhio, the state's broadband program office. Ohio ran one of the more efficient state BEAD programs in the country — the subgrantee selection process ran in Summer 2025, and the Final Proposal was submitted to NTIA on September 4, 2025, ahead of most states. Approximately 117,000 locations are targeted statewide. One distinctive element of Ohio's BEAD landscape: after Starlink/SpaceX was awarded $51.6 million to serve roughly 31,000 homes with fixed wireless satellite service, Ohio's net fiber deployment requirement was reduced. Spectrum and AT&T received awards for fiber projects covering a meaningful share of the remaining locations.
For subgrantees with Ohio BEAD awards in hand, the engineering clock is running. The program's efficient administration means there's less runway between award and construction start than in slower-moving states. Engineering packages need to be mobilized quickly — HLD, LLD, permitting, cost models, and NEPA documentation — and they need to meet both NTIA's baseline requirements and BroadbandOhio's state-specific design documentation standards. Our team can move from project kickoff to HLD deliverable in a compressed timeline when the schedule demands it.
Ohio's BEAD Final Proposal was submitted September 4, 2025 — one of the earliest in the country. Subgrantees with awards have a compressed window to mobilize engineering. We maintain available capacity for Ohio BEAD projects and can discuss timeline expectations before you commit to a construction schedule.
Ohio's terrain is more varied than its Midwest reputation suggests, and the differences matter for construction method selection, bore cost estimation, and schedule risk. Getting terrain right at the HLD stage — before bore methods are locked and BOM quantities are committed — is the difference between a defensible cost model and a budget problem waiting to happen at LLD.
Northern Ohio — the Lake Erie Plain from Toledo east through Cleveland and into the northeast corner of the state — is excellent territory for FTTH deployment from a construction standpoint. Glacial outwash soils are consistent and bore-friendly. Existing utility corridors along state routes and county roads carry established aerial plant, which means make-ready scope is identifiable and manageable. Address densities in suburban Lake County, Cuyahoga County, and Ottawa County are high enough to support competitive per-home-passed costs on aerial builds. Toledo, Sandusky, and Cleveland metro fringe areas are among the most economically viable BEAD deployment zones in the state.
Central Ohio — the Columbus metro and surrounding counties — is characterized by rapid suburban growth pushing into previously agricultural land. Franklin, Delaware, Licking, Fairfield, and Pickaway counties all have active fiber deployment activity. The mix of mature aerial plant in established subdivisions and new underground conduit requirements in greenfield residential development creates a planning challenge: aerial and underground methods often both appear on the same route within the same project area. Underground bore in central Ohio glacial till is generally workable at $25–45 per linear foot in rural and suburban areas, though urban Columbus segments with pavement restoration requirements run higher.
Southeastern Ohio — Athens, Hocking, Vinton, Morgan, Meigs, and adjacent Appalachian counties — is where the engineering assumptions change. Rolling hills, hollows, and exposed sandstone and shale outcrops make route selection more deliberate and bore resistance less predictable. A bore job that takes four hours in Hancock County can take a day and a half in Athens County if you hit unexpected rock. Field survey data is especially important here — desktop route planning from satellite imagery doesn't reveal what's under the surface in Appalachian hill country. Our field survey team captures the ground-truth data that keeps bore cost estimates honest.
River valleys running through all three terrain zones — the Scioto, Muskingum, Hocking, Olentangy, and their tributaries — create waterway crossing requirements that appear throughout the state. Crossings in jurisdictional waters require USACE Section 404/10 coordination, and in some cases individual permits rather than Nationwide Permits. Identifying crossings early and building the USACE coordination into the project's permitting matrix is standard practice on any Ohio route with river valley segments.
Ohio's utility landscape includes three major investor-owned utilities plus a significant rural electric cooperative presence in the eastern and southeastern parts of the state. Each operates under different regulatory frameworks, which affects how make-ready processes are managed and what timelines are realistic.
AEP Ohio serves most of central and eastern Ohio, including Columbus and a broad swath of the Appalachian region. AEP's joint-use program is well-established and AEP operates under FCC pole attachment rules, which provides a defined process and remedies if the timeline goes unreasonably long. Make-ready in AEP territory in southeastern Ohio can surface significant structural issues — poles in the Appalachian counties have high exposure to ice loading and the structural condition of older wood varies considerably. Our pole loading analysis team performs NESC-compliant assessments and flags replacement candidates before they become field surprises.
FirstEnergy operates three Ohio subsidiaries: Ohio Edison (northeast Ohio), Cleveland Electric Illuminating Company (the Cleveland metro), and Toledo Edison (northwest Ohio). FirstEnergy's northeast Ohio territory has a significant population of older poles, some in areas where the incumbent telco has already overlashed or the pole is operating near capacity. Our make-ready engineering process captures actual attachment height data via field survey before scoping pole transfers or replacements — a step that saves significant cost compared to discovering the issue during construction.
Duke Energy Ohio serves the southwestern corner of the state, including Cincinnati metro fringe areas in Hamilton, Warren, and Clermont counties. Duke's joint-use process is structured and follows FCC rules. Cincinnati metro fringe deployment — the suburban belt between the urban core and rural Clermont and Warren counties — is among the most active fiber construction zones in Ohio.
Eastern Ohio's rural electric cooperative territory operates under a distinct regulatory structure. The Public Utilities Commission of Ohio (PUCO) governs pole attachment rates and processes for co-op-owned poles in Ohio — the FCC's one-touch make-ready rules do not apply to these poles. Co-ops like Buckeye Rural Electric, Guernsey-Muskingum Electric, and Carroll Electric have established joint-use processes, but the timeline and dispute resolution framework differs from FCC-regulated IOU poles. If your BEAD route crosses into co-op territory in eastern Ohio, build the PUCO framework into your project schedule. Treating co-op poles like IOU poles is a common scheduling error on first-time Ohio builds.
The Ohio Department of Transportation (ODOT) issues utility encroachment permits for work within state highway right-of-way. Ohio's major interstate corridors are significant constraints on BEAD deployment routes in several parts of the state. The I-71 corridor running north-south from Cleveland through Columbus to Cincinnati bisects the state and crosses multiple BEAD target areas. I-75 runs through Toledo and Dayton. I-70 connects Columbus to the West Virginia border through eastern Ohio's most active BEAD deployment zone.
ODOT encroachment permits require scaled construction drawings, traffic control plans that conform to ODOT's OMUTCD standards, and in some cases engineer's stamps. Application timelines vary by ODOT district — Districts 4 (Cleveland), 6 (Columbus), and 8 (Cincinnati) see higher application volumes and correspondingly longer review times in peak construction season. Aerial crossings of ODOT maintained roads often require a joint-use agreement in addition to the encroachment permit. Our permitting team handles ODOT applications as part of the full permit matrix built at project start, so these items are in the critical path from day one rather than being discovered later.
Railroad crossings in Ohio require separate licenses from CSX and Norfolk Southern, which are both active in the state. CSX has major freight corridors running east-west across northern Ohio, and Norfolk Southern has significant presence in eastern Ohio's Appalachian region. Processing times for railroad crossing licenses run 3–8 months from application to executed agreement — they need to be submitted as soon as the route is locked. See our analysis of make-ready engineering timelines in fiber deployment for how railroad items affect overall project schedules.
Ohio's BEAD deployment is concentrated in specific geographic zones: the suburban fringe of Columbus, Cleveland, and Cincinnati metros; the Appalachian Southeast; the northwest lake plain; and rural agricultural counties with established co-op infrastructure. Each zone has different engineering parameters — address density, terrain, utility landscape, and permitting complexity — and each needs a design approach calibrated to those realities.
Our Ohio-active services include FTTH design (HLD and LLD), OSP engineering, pole loading and make-ready analysis for AEP, FirstEnergy, Duke, and PUCO co-op territories, full permitting services including ODOT encroachment, railroad crossings, and USACE waterway permits, and field survey for route data capture across northern flatlands and southeastern Appalachian terrain. We operate across all 48 continental U.S. states and maintain active project coverage in Ohio. Certified MBE.
Draftech International is a Certified Minority Business Enterprise (MBE). If your BroadbandOhio BEAD award or project has supplier diversity requirements, we satisfy them. Our MBE certification covers substantive engineering delivery: 600+ field engineers, 44,000+ miles designed, 2.6M+ addresses engineered across all 48 continental U.S. states.
For Ohio project inquiries, reach us at info@draftech.com or 305-306-7406. We reply within one business day. Our team can also review an existing Ohio design package or permitting plan and provide an independent technical assessment if you've inherited a project and need a second opinion before construction mobilizes.
Relevant engineering context for Ohio projects: our guide on ROW permitting delays in fiber deployment covers the ODOT, railroad, and USACE timeline dynamics that affect Ohio builds. For BEAD documentation requirements applicable to BroadbandOhio subgrantees, our breakdown of BEAD engineering requirements in 2026 is the most thorough public treatment of what NTIA expects. And for the aerial-versus-underground cost decision that appears on nearly every Ohio mixed-terrain route, see our analysis of aerial versus underground fiber construction costs.
Ohio received $793 million in BEAD funding administered by BroadbandOhio. The program ran one of the more efficient state processes — subgrantee selection occurred in Summer 2025 and Ohio's Final Proposal was submitted to NTIA on September 4, 2025. About 117,000 locations were targeted statewide, though the net fiber requirement was reduced after Starlink received $51.6 million to serve approximately 31,000 homes with satellite service. Spectrum and AT&T received fiber project awards covering a meaningful share of remaining locations. Engineering requirements follow NTIA's baseline — HLD, LLD, cost models, NEPA documentation, as-built deliverables — plus BroadbandOhio's state-specific documentation standards. Because Ohio's program moved fast, subgrantees with awards need engineering capacity mobilized quickly. We maintain available project capacity and can discuss realistic timelines before you commit to a construction start date.
Northern Ohio — the Lake Erie Plain from Toledo through Cleveland — is among the easiest terrain in the Midwest for FTTH construction. Glacial till soils, flat topography, and established utility corridors make bore and aerial work predictable. Southern and southeastern Ohio is materially different: Appalachian foothills in Athens, Hocking, Vinton, Morgan, and Meigs counties introduce rolling terrain with exposed sandstone and shale outcrops that increase bore resistance and require careful route selection. A bore that takes four hours in northwest Ohio can take a day and a half in southeastern Ohio if you hit unexpected rock. River valleys throughout the state — the Scioto, Muskingum, Hocking — create waterway crossing requirements that appear on routes in all terrain zones. Any cost model applying a single per-mile unit cost statewide will produce unreliable results for southeastern Ohio project areas.
Most of Ohio's major IOUs — AEP Ohio, FirstEnergy subsidiaries (Ohio Edison, Cleveland Electric Illuminating, Toledo Edison), and Duke Energy Ohio — fall under FCC pole attachment rules, which provide defined processes and remedies. Rural electric cooperatives in eastern Ohio are different: the PUCO (Public Utilities Commission of Ohio) governs pole attachment rates and processes for co-op-owned poles, not the FCC. Co-ops like Buckeye Rural Electric, Guernsey-Muskingum Electric, and Carroll Electric have their own joint-use processes that operate outside the FCC one-touch make-ready framework. If your BEAD route crosses into co-op territory, the PUCO regulatory framework needs to be built into your project schedule and cost model. Treating co-op poles as FCC-governed IOU poles is one of the most common scheduling errors on first-time Ohio Appalachian builds.
ODOT issues utility encroachment permits for any work within state highway right-of-way, including Ohio's major interstate corridors — I-71, I-75, and I-70 — which cross multiple BEAD deployment zones. Applications require scaled construction drawings, ODOT-compliant traffic control plans, and sometimes engineer's stamps. Timelines vary by ODOT district and season, with Districts 4 (Cleveland), 6 (Columbus), and 8 (Cincinnati) seeing higher volumes and longer review cycles during peak construction months. Aerial route crossings may also require a joint-use agreement separate from the encroachment permit. These items need to be in the project's critical path from the start — not treated as routine approvals after design is complete. We build the ODOT permit matrix at project kickoff alongside the railroad and USACE items so nothing becomes a surprise schedule constraint later.
Whether you're engineering a BroadbandOhio BEAD project, scoping make-ready in AEP or FirstEnergy territory, or need permitting support for ODOT and railroad crossings — our engineering team is ready to discuss your project. We respond within one business day.
Contact Our Engineering Team