What 100 Permits a Week Taught Us About OSP Workflow Design

The case for taking permits off your designers' plates, automating the boring parts, and following up at the cadence each agency actually responds to.

If your fiber build keeps stalling at the same step it stalled at last quarter, the bottleneck is probably not your design team. It's permits. DOT, railroads, municipalities. These are the gates between your engineering package and construction, and they don't care about time-to-build or ROI.

We know this firsthand. Our permits team submits 60 to 100 applications a week and gets 40 to 60 approved in the same window. Every one of them takes follow-up that has to happen at the right cadence, with the right contact, with the right details.

This is what we've learned doing it at that volume.

A lot of OSP shops we talk to push permits through whoever happens to be working on the job. The designer flags it, the designer fills it out, the designer follows up. That works at 50 poles a week. It does not work at 5,000. Here's what changes when you treat permits as their own workflow.

See how Katapult Pro maps the full pole-to-permit workflow.

"Permits" Means Two Different Things.

Before we get into how we run them, it's worth defining what people mean when they say "permits," because most rooms have at least two answers in play.

The first is the pole attachment application. Some teams call this "pole permitting" because you're requesting permission from the pole owner to attach. That's a pole-owner workflow, governed by the rental agreement.

The second is right-of-way (ROW) permits for the pole owner's own work. If the utility needs to set a new pole inside a state ROW, they need a state DOT permit. That's not a 3rd party attacher's problem.

Our permits team works that second bucket. 

(There’s also ROW and traffic permits for 3rd party attachers themselves. A surprising amount of this is traffic-related. If the attacher's contractor has to close a lane, flag a road, or stage equipment, they need a permit from whoever owns that ROW. Often that's the state, sometimes a municipality, sometimes a railroad, occasionally the FAA.)

Why Permitting Doesn't Belong on Your Designer's Plate

Here's the operational insight that took us a couple thousand jobs to fully internalize: permitting decisions don't belong with the designer.

A designer working a pole is loaded up with everything that pole needs. NESC clearances, attachment heights, guying, pole class, transfers, grounding. Asking that same designer to also know whether the pole sits within 100 feet of a helipad, or 60 feet of a state road, or 16 to 150 feet of a railroad ROW, or whether the local municipality wants a letter for a gravel-shoulder dig, is asking for misses. Not because designers aren't smart. Because the cognitive load is wrong for that decision.

What we do instead: engineering finishes the job and hands it off. Our permits team takes the whole job at once and runs the investigation pass.

This works for two reasons. First, you can scan a 50-to-100-pole job for permit triggers in a few minutes if you know what to look for. We ran a test recently where three of us each took an untouched job, made our own checklist, marked any pole we thought required investigation, and then swapped to look at each other's work. None of us took longer than seven minutes per job. The whole-job view makes pattern recognition fast in a way that pole-by-pole design doesn't.

Second, judgment calls about state ROW and railroad ROW are deeply situational. State ROW in Pennsylvania can be 60 feet, but in places where coal companies seeded their ROW to the state a century ago, it can be 120 feet. Railroad ROW can be 16 feet or 150. Knowing when to err toward "investigate" versus "skip it" is a pattern-recognition skill built across hundreds of jobs. That's a permits-team skill, not a designer skill.

There's also a sequencing reason. You can't fully know what a job needs to permit until engineering is complete. Make ready calls drive a lot of municipal and traffic permit triggers, and those calls aren't final until the design is final. Pushing permit decisions earlier in the process means revisiting them, or risking acquired permits timing out while Make Ready is completed, which is where the errors creep in.

If your designers are currently making those calls, they're probably making them mostly right. They're also probably eating a measurable percentage of their day on a decision someone else could be making faster.

What Gets Automated, What Stays Manual, and Why That Line Matters

Volume forces honesty about where the real time savings live. We've automated the parts that are formulaic and protected the parts that benefit from judgment.

DOT Submissions are automated. We use API tools that pull segment-and-offset data from PennDOT's public website using the geolocation already stored in Katapult Pro. That means we're not sending a crew out to walk an EOP just to grab the data we need to fill in a form. The form itself? PennDOT's submission packet is generated directly from pole attributes already stored in our project. Instead of someone retyping information into a PDF editor, the export pulls the pole, populates the form, and we submit.

The same goes for the maps state ROW packets require. We've built a PennDOT-style map deliverable that mirrors what their design software produces. Anyone on the team can generate one without specialized CAD training.

Railroad maps are still being figured out. We make maps that include all the information railroads require, but they're not as polished as what a dedicated draftsperson with AutoCAD and a few hours would produce. The trade we've made is real and we'll be honest about it: our maps take an hour, not a day. They contain the required content, but a railroad ROW agent who's used to gallery-quality CAD will notice the difference. We chose accessibility over aesthetics because the speed lets us get more permits moving and lets anyone on the team produce one. We're investing in better visual output, but not at the cost of letting a single map deliverable bottleneck the queue.

Letters of justification are still manual. They could be templated. We have boilerplates we could fire off for NESC violations, ADA conflicts, and the other common categories. We've found that putting actual nuance into a letter of justification produces measurably better outcomes with reviewers. So we generate them by hand in a Google Doc and convert to PDF. Pure speed isn't always the right call.

It's tempting to automate everything you can. Some of what permitting actually requires is human judgment doing the work that gets a permit reviewed favorably. We protect that part of the process from the automation we've built around it.

Drowning in permit follow-up? The patterns that work at scale aren't software-only. They're software paired with the right operational discipline. See how Katapult Pro fits into a permit workflow built for volume.

Schedule a Demo | Explore Workflow Management

The Cadence Trap: Why "Follow Up Every Two Weeks" Fails

The single biggest mistake we see teams make is following up on every permit on the same schedule. Different agencies operate on completely different timelines, and following up too soon costs you credibility with the people who decide your permit's order in the queue.

Here's the cadence we run by permit type, tracked on each pole node so anyone on the team can pick up where the last person left off:

Municipal permits. We contact every two weeks because municipalities vary wildly. Some don't return calls, some respond same-day. Two weeks keeps us top-of-mind without becoming a nuisance.

PennDOT. We do not contact for the first month. PennDOT gives an expected return date that's usually further out than they actually need, which gives them margin. If we call in week two, the answer is "we're working on it" or no response at all. If we wait the first month, they often come back within four weeks of submission instead of six. Letting their built-in buffer work for them makes our contact more productive when we do reach out.

Railroads. We wait three months before any follow-up. Railroad permits take four to six months. Calling earlier doesn't move them. We do contact the right-of-way agent at submission to confirm the application landed, and that's our only touchpoint for the first quarter. After that, we engage on the agent's timeline, not ours.

FAA. Different mechanic entirely. We use a node placed at the center of any airport or helipad with a defined radius around it. Anything within that radius gets marked for investigation. The decision rule is simple, but it's a rule, not a touchpoint. Follow-up cadence varies by the specific FAA office.

The cadence isn't memorized by individual people. It lives in attributes on each node, with a follow-up date that updates every time the team contacts the agency, plus a note explaining what was said. When the team's other priorities pull people in different directions, the workflow tells the next person exactly where each permit stands.

See how Katapult Pro tracks attribute history and follow-ups across the project lifecycle.

Quality Control That Catches What Designers Wouldn't

Most QC catches obvious problems. The QC that protects a permit pipeline catches non-obvious ones.

A few examples of what our team's QC is built to flag:

Municipal weirdness. Some municipalities want a permit even when all the work is in a gravel shoulder and no traffic is being disrupted. Some want a letter rather than a permit, telling them which sections of road might affect emergency vehicle routing. You can't predict that from a designer's checklist. You learn it by getting calls from municipalities who weren't notified and were unhappy about it.

Outstanding permits at package time. Any pole with a non-terminal permit status that has an outstanding permit gets flagged before the package ever moves to delivery. The applicant should never receive a package they don't know is incomplete. This is mechanical, but it's the kind of mechanical check that matters most.

Railroad proximity. We have an API layer for railroads. Any node with medium make ready within 100 feet of that layer gets flagged for investigation. We can't yet auto-detect transmission lines the same way (utilities are protective of that data, for understandable reasons), so the FAA-style radius check is mostly visual on those. Either way, the QC isn't replacing human review. It's making sure the human review knows where to look.

The principle: you don't QC every step in the same way. You QC for the things that, if missed, cost you the most. For permits, that's a permit that didn't get pulled (truck rolls to a site that can't be worked) and a package that went out incomplete (an applicant who can't build).

Where We Want This to Go

Right now, the handoff between engineering and permits relies on status changes and people remembering to check the queue. That's not bad, but it's not great either.

The vision we've been working toward inside Katapult Pro is a dedicated permit workflow. Once engineering finishes a job, the job advances into a permit phase. The permit team gets a job-level view, runs the investigation pass, and either advances directly to package (most jobs) or routes complex items to specialists (medium make ready, railroad crossings, FAA radius checks).

The point isn't adding software for software's sake. The point is that asking a designer to also be a permit expert is a structural mistake at scale. Building the workflow lets you specialize the work without losing the data continuity that makes everything fast.

Most teams don't need a full permits department to benefit from this. A single permits-focused person inside an engineering shop can run the workflow effectively if the QC, follow-up cadence, and form auto-population are doing the heavy lifting. The win is in the structure, not the headcount.

What This Looks Like in Your Shop

If your team is permitting through whoever's closest to the project, here's a starting point.

First, separate the decision. The designer's job ends when engineering is complete. The permit decision (what's required, what's not, what gets investigated) belongs to whoever owns permit delivery. Even if that's the same person wearing two hats, the decision moves to a different point in the process and a different mode of attention.

Second, fix the cadence. Look at your last 50 permits across each agency type. How long did each one actually take? What contact pattern correlates with faster approval? You'll probably find that for at least one agency, you've been wasting effort following up too soon.

Third, automate the formulaic parts. If your team is retyping pole data into PDF forms, you have time left on the table. Pulling segment-and-offset data, populating standard agency forms, generating maps from project attributes. Those are the things that compound. Each saved hour funds the next saved hour.

Fourth, protect what shouldn't be automated. Letters of justification, edge-case municipality calls, anything where a thoughtful response measurably improves your outcome. Don't compress that work to make a dashboard cleaner.

We run our permit team this way because the volume forced us to. If you're not at our volume, you can still capture most of the upside by building the workflow ahead of needing it. The shops we see struggling with permits at 5,000 poles a month are usually the same shops that didn't change anything from when they were at 500.

Frequently Asked Questions

What's the difference between a pole attachment permit and a ROW permit? A pole attachment permit (sometimes called a pole permit or attachment application) is granted by the pole owner under the terms of the rental agreement. It authorizes you to attach to the pole. A ROW permit is granted by whoever owns the right-of-way the pole sits in or your construction crew has to work in. State DOTs, municipalities, and railroads all issue their own ROW permits with their own rules and timelines.

Can a pole owner's ROW permit cover 3rd party attacher work in the same ROW? That's a common interpretation, but it depends on the agency and the project. State DOTs and railroads often require the attacher's contractor to pull their own ROW or traffic permit even when the pole owner already has one. The safe answer is to confirm with the issuing agency before assuming coverage.

How long do railroad ROW permits usually take? Railroad permits typically take four to six months from submission to approval. Following up earlier doesn't accelerate the process. We confirm receipt with the right-of-way agent at submission and then wait roughly three months before any further contact.

Why does PennDOT take longer if you call too early? PennDOT provides an expected return date that's usually padded beyond what they actually need. The padding gives them flexibility on a queue they can't always control. Calling within the first month typically gets a non-answer or a "we're working on it" reply that consumes their time and yours. Waiting the first month tends to result in faster real responses when you do follow up.

Should designers handle permitting decisions or should it be a separate role? At low volumes, a designer can handle permits as part of the engineering workflow. As volume grows, the cognitive load of layering permit-trigger judgment on top of design judgment leads to misses. A dedicated permit role (or even a single person with that explicit ownership) running an investigation pass on completed jobs scales better and catches things designers wouldn't see job-by-job.

What automation actually saves time on permitting? Three things consistently pay back: pulling agency-specific data (like PennDOT segment and offset) from public sources via API rather than field visits, auto-populating standard agency forms from project attributes, and generating standard map deliverables from project data. Letters of justification and unusual edge cases are still better handled manually.

What's the right way to track follow-up across a large permit pipeline? Track it on the asset itself, not in a separate spreadsheet. Every pole node should carry a follow-up date attribute, the agency type, the current status, and a note from the most recent contact. That way the next person picking up the queue can see exactly where each permit stands without asking around.

Ready to Build a Permit Workflow That Scales?

Permits are not glamorous. They are the gates between engineering work and construction work, which means they are the gates between a designer's deliverable and an attacher's revenue. Treating them as a designer's afterthought works fine until you're processing thousands of poles a quarter and the misses start showing up as missed deadlines.

The teams that handle permits well at scale share a few traits. They treat permits as their own workflow with their own owner. They tune their follow-up cadence to each agency's actual rhythm. They automate the formulaic parts and protect the parts that benefit from judgment. They build the QC to catch the things designers wouldn't.

Schedule a call with our team to see how Katapult Pro supports permit-heavy workflows from data collection through delivery.