INTERVIEW | 4 min read

FiberGrid Solutions on the Make-Ready Problems Standard Guidance Misses

Last edited: Oct 28, 2026
Listen
--:--
FiberGrid Solutions on the Make-Ready Problems Standard Guidance Misses hero image

Introduction

FiberGrid Solutions provides specialized OSP engineering support for fiber deployments, make-ready projects, pole analysis, and construction-ready design. The company was recently included in a Peekwire roundup of OSP engineering partners alongside Draftech and CHR Solutions.

In this interview, Jessy of FiberGrid Solutions answers three questions about the practical realities of make-ready and pole analysis work — the situations where standard approaches break down, what general guidance tends to leave out, and the decisions that get made too quickly when pole data is incomplete.

When the Standard Approach Doesn't Cover the Problem

Asked about the last time a make-ready or pole analysis surfaced a problem the standard approach could not resolve, Jessy described a hardware conflict scenario.

"One example is when existing pole hardware creates a conflict with a proposed cable attachment. A placement that looks acceptable on paper may not work because of a through-bolt, an existing riser, or limited usable space on the pole."

The response emphasizes that the answer is not to force the standard solution. Instead, the work involves examining the actual pole configuration, attachment geometry, clearances, and surrounding conditions, then evaluating alternatives.

"Depending on the situation, that could mean adjusting the proposed attachment location, coordinating with the pole owner, or considering a larger design change. The goal is to resolve the conflict without creating a new issue elsewhere on the route."

That last point is worth noting for anyone managing a fiber build: a fix at one pole can create a problem at the next one. The resolution has to be evaluated at the route level, not just the individual structure.

What General Guidance Leaves Out

Jessy identified two recurring gaps between published guidance on make-ready and pole loading and what actually happens on fiber builds.

The first is that poles cannot always be evaluated in isolation.

"A proposed attachment may appear feasible at one location, but adjacent spans, changes in ground elevation, existing equipment, cable sag, or guying constraints can affect the overall design."

This is a familiar issue for anyone who has worked through pole attachment and make-ready processes, where rules and guidance often address individual poles rather than the cumulative effect of a route.

The second gap is field data quality.

"Incomplete or outdated pole information can lead to assumptions that later require redesign. Good OSP engineering involves connecting the field conditions, pole analysis, clearance requirements, and route-level constraints into one coordinated design rather than treating each item as a separate checklist."

The distinction between a coordinated design and a checklist is a practical one. A checklist can be completed while still missing how one constraint affects another.

The Decision People Make Too Quickly

When pole data is incomplete at the scoping stage, Jessy pointed to a specific risk.

"One common risk is assuming that a pole is suitable for a proposed attachment before the necessary information has been verified. Missing attachment details, pole characteristics, existing utilities, or span information can materially affect the design and make-ready requirements."

The recommended approach is to treat missing data as a gap to be resolved, not as implicit confirmation that the design will work.

"Rather than treating missing data as confirmation that the design is feasible, it is better to identify the information gaps, determine which ones affect engineering decisions, and request field verification or additional analysis where needed. This helps prevent premature design decisions, unexpected make-ready work, and avoidable rework later in the project."

For teams scoping fiber deployments, that means separating the data gaps that actually change engineering decisions from those that do not — and pursuing verification on the former before committing to a design.

Takeaways

Three practical points emerge from the interview:

  • Do not force a standard solution when the pole configuration does not support it. Examine the actual geometry and evaluate alternatives, including coordination with the pole owner.
  • Evaluate poles in the context of the route. Adjacent spans, elevation changes, existing equipment, sag, and guying constraints all affect the design.
  • Treat incomplete pole data as a gap, not a green light. Identify which missing details affect engineering decisions and request verification before finalizing the design.

More information about FiberGrid Solutions and its OSP engineering services is available at fibergridosp.com.