Make-Ready Engineering, Joint Use & Permitting

What make-ready actually means

A pole is shared infrastructure. Power is at the top, communications attachments are below it, and between and around them are clearances that exist so people can work on the structure safely. When a new attachment will not fit within those constraints as the pole currently stands, work is required to make it fit. That work is make-ready.

In the mildest cases it means re-arranging existing communications attachments to open space. In the harder cases it means relocating equipment, and in the hardest it means replacing the pole. Pole replacement is the outcome every program tries to minimize, because it carries cost, schedule and coordination with every other attacher on the structure.

Make-ready engineering is the analysis that determines which of those a given pole needs. It requires accurate pole and attachment data, clearance and loading analysis against the National Electrical Safety Code and the pole owner's construction standards, and a proposed attachment position that actually works.

The framework the process runs inside

For facilities subject to FCC Section 224 jurisdiction, federal pole-attachment rules establish access and make-ready requirements and timelines. The governing rules sit at 47 CFR Part 1, Subpart J, and they matter to a program schedule in concrete ways.

Section 1.1411 establishes the timeline framework for access — the periods within which a covered pole owner must survey, respond, and complete make-ready. Where they apply, those periods are the floor of a program's permitting schedule, and no amount of urgency compresses them.

Section 1.1412 provides self-help remedies where a pole owner does not complete make-ready within the applicable period, which is a meaningful lever on stalled queues when the conditions for it are met.

Not every pole owner sits under that framework. State-certified jurisdictions run their own regimes in place of the federal one, and cooperatives, municipal and other government-owned utilities, and other excluded pole owners may operate under different rules, tariffs, agreements, or timelines. Knowing which framework governs a given market — and what the specific pole owner's process is on top of it — is part of the work, not an afterthought.

Joint use and coordination with other attachers

A pole rarely has one other tenant. Power, incumbent telco, one or more cable operators, sometimes municipal fiber or traffic systems all share the structure. Make-ready that requires moving an existing attachment requires that attacher to act, on their own schedule and priorities.

This is where programs stall in ways that look like nothing is happening. Coordination means knowing who is on each structure, what they need in order to move, and following the work through — not filing an application and waiting.

BOGO runs that coordination as an active process: tracking applications by structure, chasing the specific blockers, and escalating where a queue has stopped moving. It is unglamorous, and it is frequently the difference between a market that completes on schedule and one that does not.

Municipal permitting and utility coordination

Alongside pole attachment, most routes require permission from the jurisdictions they cross. Right-of-way permits, street opening permits, traffic control plans, restoration standards, and occasionally moratoria that close a street to work for a season — the requirements vary by municipality and are discovered rather than assumed.

Underground work adds utility coordination: locating existing infrastructure, working within the requirements of the utilities that own it, and satisfying restoration obligations afterwards. Both are covered under BOGO's permitting scope.

The practical discipline is starting early and submitting accurately. A permit package returned for correction does not resume where it left off — in many jurisdictions it re-enters the queue, which converts a small documentation error into weeks.

What BOGO controls, and what it does not

It is worth being explicit, because this is an area where vendors overpromise.

BOGO does not grant, guarantee, or accelerate regulatory approval. Pole owners decide attachment applications. Municipalities decide permits. Utilities decide their own coordination requirements. No engineering firm can commit to those outcomes, and one that implies otherwise is selling something it cannot deliver.

What BOGO does control is everything that determines how the queue treats you:

• Make-ready engineered correctly the first time, against real field data
• Applications that are complete and accurate on submission
• Submissions sequenced so the queue is fed continuously, not in one batch
• Active tracking and follow-through per structure
• Escalation where an applicable timeline has passed without a response
• Design changes handled by the team that drew the design — see OSP engineering

That last point is the one operators feel most. When a pole comes back unusable on a multi-vendor program, the re-route crosses a company boundary and re-enters a design queue. With BOGO holding both, it is a same-team re-issue.

Sequencing permitting into the program

The most common structural mistake in a modernization program is treating permitting as a phase that follows design. It is not a phase; it is a pipeline with a fixed throughput, and the goal is to keep it full from the earliest possible moment.

That means releasing design in a sequence that feeds permitting continuously rather than completing all design and then submitting everything at once. It also means starting field data collection on the structures that will need make-ready before the rest of the design is finished, because those applications are the longest lead item in the program.

This is exactly what the Signal Chain is arranged to do, and the practical version is set out in our network modernization playbook. From approved make-ready, work moves into construction coordination.