OSP Drafting Outsourcing: What ISPs Need to Know

I've been doing this for 17 years. Running an OSP drafting firm with 600 engineers across 22 states. And the conversation I keep having with ISPs — over and over — is the same one: they think they're buying "CAD files." They're not. They're buying permit approval, construction readiness, and a documentation chain that holds up under regulatory scrutiny. There's a meaningful difference, and if you don't understand it before you sign a contract with an outsourced drafting firm, you'll figure it out the hard way.

This isn't a pitch piece. It's what I'd tell you if you walked into my office and asked how to think about fiber network design outsourcing and specifically OSP drafting. Some of it might sting a little.

What OSP Drafting Actually Covers

Most ISPs come to us with a narrow mental model of what OSP drafting is. They think: AutoCAD drawings, maybe some GIS layers, done. That's maybe 40% of the actual scope on a real fiber build.

The Full Deliverable Set

Here's what OSP drafting actually covers when it's done right:

• AutoCAD permit drawings — aerial and underground route plans, profile sheets, detail sheets, joint use exhibits, and whatever else the utility or municipality requires for permit submission. These need to meet each pole owner's or agency's specific formatting requirements. Not generic. Not templated. Specific.
• MicroStation route design — a lot of electric utilities and many municipal agencies require deliverables in DGN format. If your drafting firm doesn't run MicroStation in-house, you're getting converted files, and conversion artifacts cause permit rejections. More on that later.
• ArcGIS and GIS network mapping — GIS deliverables for as-built documentation, network inventory, BEAD compliance reporting, and utility coordination. This is a distinct discipline from CAD drafting. Not all drafters are GIS technicians. Many firms treat it as an afterthought. It isn't.
• Pole loading input drawings — the attachment geometry and loading data submitted to the engineer running your O-Calc or SPIDAcalc analysis. Bad input drawings produce bad loading results. We see this constantly — and it's almost always because the drafter didn't have field-verified attachment heights.
• As-built redlines — field-marked construction drawings that become the permanent record of what was actually built. In BEAD programs, these are required documentation. In most states, utilities require them before closing out a permit. They're not optional, and they're often treated like an afterthought until they're suddenly urgent.
• Splice schematics — fiber cable splicing diagrams showing fiber count, splice locations, reel assignments, and termination points. These aren't just documentation — they're operational reference documents that your network operations team will use for decades.

That's the full scope. Not "CAD files." A construction-ready document package that survives utility review, permit submission, and BEAD compliance audit.

What ISPs Typically Underestimate

The part that surprises ISPs most? The state-specific permitting knowledge required. Ohio's electric utilities want different attachment exhibit formats than Florida's. California's local agency permitting is a different universe from rural Alabama. A good CAD/GIS documentation standards baseline matters, but state-specific permitting knowledge is what separates firms that clear permits efficiently from firms that spend six weeks in revision cycles.

Why It's More Than Desktop Work

OSP drafting isn't a desktop exercise. It requires understanding what a pole actually looks like in the field — how attachers are stacked, where the power space ends, what a midspan clearance issue looks like versus a bracket conflict. Drafters who've never been on a pole line produce drawings that look fine on screen and fail in the field. That's not hyperbole. It's the single most common source of permit rejections we fix when an ISP brings us in after another firm's drawings got kicked back.

When Outsourcing OSP Drafting Makes Sense

There's no universal answer here. Outsourcing makes sense in specific situations. Knowing which ones apply to your project keeps you from making the wrong call in either direction.

Project Surge and Hiring Constraints

The most obvious case: you can't hire fast enough. An experienced OSP drafter with MicroStation proficiency and real field knowledge isn't walking through your door in six weeks. The talent pool is thin, the training curve is long, and a BEAD construction window doesn't wait. If you've got 14 permit packages due by Q3 and three drafters on staff, you're not staffing your way to that deadline. Outsourcing to a firm with surge capacity is the only real option.

BEAD compliance documentation volume has made this situation acute for a lot of ISPs right now. The as-built requirements alone — GIS shapefiles, splice documentation, photographic records, permit close-out packages — represent a documentation load that most ISPs haven't fully modeled in their project timelines.

Missing Software Expertise

If your in-house team runs AutoCAD but the utility requires MicroStation, you've got a gap. You can try to convert, and sometimes it works. More often it introduces errors that the utility's DGN checker catches, and now you're in a revision cycle that costs more time than just using MicroStation from the start. Same issue with ArcGIS — if how to outsource GIS mapping for telecom projects is a question you're actively asking, it's usually because your team doesn't have the GIS depth to produce compliant deliverables in-house.

State Licensing and As-Built Backlogs

Some states require a licensed PE or a registered firm to submit permit drawings. If you don't have that, you need a firm that does. And as-built backlogs are a real operational problem — construction teams move faster than documentation teams, and the gap accumulates. Getting six months behind on as-builts means six months of network state you don't have accurate records for. That's a business risk, not just a documentation problem.

What to Look For in an OSP Drafting Firm

I'm going to be direct here, because the wrong answer on any of these criteria costs real money.

Multi-Platform Capability — All Three

AutoCAD AND MicroStation AND ArcGIS. Not one. Not two. All three, in-house, with drafters who actually run the production software — not project managers who oversee offshore subcontractors who do the work in whatever platform they have available. Ask specifically: do your drafters produce MicroStation deliverables internally, or do you subcontract that? The answer tells you a lot.

A firm that only knows one platform will route all your work through that platform regardless of what your utilities require. That creates conversion problems, format compliance issues, and re-submission delays that you'll pay for in both time and money.

Real OSP Field Experience

Ask whether their drafters have field experience. Not "have they visited a job site once." Do they understand how attachments sit on a pole, what a midspan clearance measurement means in the field, how construction crews interpret a permit drawing? Desktop drafters who've never been on a fiber build produce drawings that look correct and fail in construction. You want people who've walked the route, not just traced the GIS layer. See also our thoughts on how to hire a telecom drafter — the same criteria apply when evaluating a firm.

Turnaround SLAs and Revision Policy

A firm that won't commit to a turnaround SLA in writing is telling you something. Get the SLA defined in the SOW: from clean field data receipt to submission-ready permit package. Also nail down the revision policy — how many revision rounds are included, what triggers an out-of-scope revision, and what the turnaround is on revisions. The revision policy matters as much as the initial turnaround. Permit packages get kicked back. It happens. What happens next determines whether you hit your schedule.

Pricing and Engagement Models

Here's the actual pricing landscape as of 2026, not the aspirational numbers that show up in proposals.

Hourly and Per-Pole Rates

Hourly rates for OSP drafting services run $65–$95 per hour for most work. AutoCAD permit drawings sit toward the lower end of that range. MicroStation and ArcGIS work pushes toward the upper end — the talent is scarcer and the platforms have higher overhead. Don't be surprised by $78/hr for experienced MicroStation drafters. That's not unusual.

Per-pole pricing for permit packages typically runs $38–$78 per pole depending on complexity, state requirements, and what's included. Always ask what's included. Is QA review included in the per-pole rate? Field coordination support? Permit resubmittals if the first submission gets kicked back? Those answers change the effective cost significantly. We've seen ISPs sign per-pole contracts that looked cheap, then discover that QA review, permit tracking, and resubmittal support were all extra — and the effective cost was higher than an hourly arrangement would have been.

Project-Based SOW and Retainers

For a defined project scope — say, 47 miles of aerial fiber with a known pole count and clear deliverable list — a project-based SOW is usually the right structure. It gives you cost certainty and gives the firm a clear scope to staff against. The SOW should define deliverables, milestones, revision cycles, and what constitutes a change order.

For ISPs with ongoing work across multiple projects, a monthly retainer makes more sense. You're essentially buying dedicated capacity — a number of drafter-hours per month at a committed rate. The advantage is priority access and consistent staffing. You don't get de-prioritized when the firm has a surge from another client. The disadvantage is that you're paying whether or not you have work to push through in a given week. For ISPs actively building, that's rarely a problem.

Common Outsourcing Mistakes ISPs Make

I've watched ISPs make the same mistakes with OSP drafting outsourcing for 17 years. They're predictable, they're fixable, and they keep happening anyway.

Handing Off Incomplete Field Data

This is the one that burns ISPs the most. You hire an outsourced drafting firm, you hand them your field notes — and then you're surprised when the turnaround is slow and the drawings have errors. The problem isn't the firm. It's that the field data was incomplete: attachment heights not measured, span lengths estimated, pole IDs inconsistent between the field sheet and the GIS layer. A drafting firm can only produce what the data supports. Garbage in, garbage out — and you'll pay revision rates to fix what should have been collected correctly in the field. Review your LLD quality control process before you hand anything off.

No Defined Revision Cycles

Scope creep in OSP drafting almost always runs through revisions. You didn't define how many revision rounds are included. The utility kicks back the drawings. You request changes. Then you request more changes when you see the updated version. Then your construction manager has comments. Then the utility has another round of questions. Each of those rounds costs money if they're out of scope. Define the revision cycle in the contract. Three rounds? Two? Whatever it is, write it down.

No QA Checkpoint Before Permit Submission

Sending permit drawings straight from the drafting firm to the utility without an internal QA review is one of the more expensive shortcuts an ISP can take. Permit rejections cost time — 3 to 8 weeks of delay per rejection in most markets, sometimes more. A QA checkpoint that catches a clearance calculation error or a missing attachment height before submission saves that delay. Check your fiber construction package deliverables against the utility's requirements before submitting, every time.

Using a Firm That Only Knows One State

OSP permitting varies enormously by state — and sometimes by county within a state. A firm that does excellent work in Georgia may not know what Michigan's electric co-ops require, or what California's encroachment permit process looks like. If you're building in multiple states — which most ISPs doing BEAD work are — you need a firm with active multi-state permitting experience, not one that's going to be learning your state's requirements on your project's dime.

What Draftech Delivers

I'll tell you what we do, plainly, without the marketing language.

Platform Depth and Team Size

Draftech runs AutoCAD, MicroStation, and ArcGIS in-house. All three. 600 engineers. No subcontracting your drawings to a third party we don't control. When you hand us a MicroStation job, MicroStation-trained drafters do the work. When you need ArcGIS network mapping, GIS technicians who understand telecom OSP do it. That's not universal in this industry — ask before you assume.

We're active in 22 states and available to deploy across all 50. The multi-state permitting knowledge isn't theoretical — we're actively submitting permit packages in those states right now, which means we know what's changed in utility requirements recently, what triggers rejections in each market, and who to call when something's stuck.

Full-Scope Capability

Full scope means: field survey, route design, permit drawings, pole loading analysis inputs, utility coordination support, as-built documentation, splice schematics, GIS deliverables. You don't need four vendors to cover OSP drafting. One firm should be able to handle it end to end, and hand you construction-ready deliverables. That's what we're built to do.

We're MBE-certified. That matters for BEAD compliance and for prime contractors with supplier diversity requirements.

The Comparison That Actually Matters

ISPs frequently ask whether they should hire in-house drafters or outsource. Here's how that decision actually looks when you put real numbers against it:

Neither option is universally right. In-house drafters make sense when you have steady, predictable volume in a single market and the talent is available. Outsourcing makes sense for surge, multi-state work, specialized platforms, or when you want to convert fixed headcount costs into variable project costs. Most ISPs doing serious fiber builds need both — a small in-house team for continuity and an outsourced firm for capacity and platform coverage.