Make-Ready Engineering: A Complete Guide

What make-ready actually is

Make-ready is the work required to prepare an existing pole so a new attachment — most often a telecom or fibre line — can be added safely and to code. It sits between two parties: the pole owner (usually the electric utility) and the attacher who wants space on the structure.

The term covers both the engineering (deciding what has to change) and the construction (doing it). The engineering half is where design firms add value: turning a field survey and a structural model into a clear, buildable scope of changes.

When make-ready is required

Make-ready is triggered whenever a new attachment would violate a clearance or overload the structure. Adding a fibre line changes the pole's loading, its mid-span sag and the vertical separation between communication and power — any of which can push the structure out of compliance with the governing code.

• The pole fails a load case once the new attachment is added
• Vertical or mid-span clearances would be violated
• Climbing or working space would be compromised
• Existing attachments need to be transferred to make room

How pole loading analysis drives it

Every make-ready determination starts from a structural analysis. The pole, its framing, existing attachments, guys and anchors are modelled — typically in SPIDAcalc or PoleForeman — and checked against the load cases and safety factors the governing code requires (NESC in the US, CSA C22.3 in Canada).

Where the structure passes with the new attachment, no make-ready is needed. Where it fails, the model becomes the tool for designing the fix: you test transfers, re-tensioning, added guys or a heavier pole until the structure passes, then write that up as the make-ready.

What a good make-ready deliverable contains

A make-ready that a crew can build — rather than a report that bounces back with questions — has a few consistent ingredients:

• A specific action per structure (transfer, re-tension, guy/anchor change, or replacement)
• The framing and clearances that the action achieves
• Cost line items for estimating
• An assumption log for every value that wasn't confirmed in the field

Doing make-ready at scale

Attachment programs run into the thousands of poles, so the real challenge is consistency, not any single structure. That means standardised inputs (one client file, one set of load cases), an independent review of every result, and a defect register so recurring issues are designed out rather than re-explained.

Handled that way, make-ready becomes a repeatable production line: field data in, buildable make-ready out, with a quality record attached to every structure.

Documentation that survives the handoff

Make-ready fails in the field for a boring reason more often than a structural one: the crew can't tell what the engineer intended. A change that reads clearly on the desk becomes ambiguous on the pole when the assumptions behind it aren't written down.

The fix is documentation that travels with the work. Every value that wasn't confirmed in the field is logged as an assumption, so the pole owner's reviewer can see exactly what was taken on faith and challenge it before construction rather than after. A per-structure change list ties each action back to the load case that required it, and photographs or sketches remove any doubt about which attachment moves where.

This is also what makes a make-ready program auditable. When a regulator or a client asks why a pole was replaced rather than guyed, the answer is already in the record — not reconstructed from memory months later.