Fiber Done Right
Posts
The Roles Involved (Part 2)

The Roles Involved (Part 2)

Geoff Rottmayer
July 11, 2025

Inspection & Testing

By the time you reach inspection and testing, most of the physical work is already done. The conduit has been installed, the vaults are in place, the fiber has been pulled, and splicing is nearly wrapped up. On the surface, everything might look finished, but until this phase is complete, the job isn’t considered done. This is the part where the project gets verified, measured, and either approved or kicked back for correction.

It doesn’t matter how hard the crew worked or how fast the job was completed. If the work doesn’t meet spec, it doesn’t move forward. Inspection and testing care about whether what was built will actually perform.

This is where everything gets checked against real conditions. Not plans. Not assumptions. Not verbal signoffs. Real numbers, real standards, and real conditions.

The Two Halves

It’s easy to group inspection and testing together, but they are two different steps in the quality control process.

Inspection is the physical walkthrough. Someone looks at the install with their own eyes. They open vaults, check hardware, verify materials, and compare what’s in the ground or on the pole to what was in the drawings. They’re checking for accuracy, consistency, and build quality. It’s a detailed review of whether things were installed correctly and safely.

Testing, on the other hand, is where performance is measured. It’s not about what looks good, it’s about whether the fiber actually works. Technicians use tools like OTDRs and power meters to check for signal loss, reflectance, and continuity. These tests show whether light can travel from point A to point B without unnecessary loss or interruption.

You can pass a visual inspection and still fail testing. Likewise, a perfect test result can be held up if the installation itself wasn’t done properly. Both matter, and both are required to close out the job.

What Field Crews Should Expect to Be Checked

The inspection process is thorough because once the job is closed out, it’s often handed off to a long-term operator. At that point, it has to work and it has to last. That’s why these are some of the most common things inspectors look for:

Handholes and Vaults must be at the correct depth, properly leveled, and free from standing water or debris. Inspectors check for access, label visibility, slack coil availability, and whether the lid seats properly. Too deep? Too shallow? That’s a correction order.
Conduit and Pathway routes are verified against the drawings. If the field crews made a change but never marked it on the redlines or updated the plan set, it can cause major confusion. What’s shown on the map must match what’s in the ground.
Aerial Installations are reviewed for proper clearances, sag, grounding, and tension. If cables are too low, incorrectly guyed, or installed in a way that violates pole owner standards, they will not pass.
Closures and Splice Cases are physically opened to confirm the splicing was done cleanly, the fibers are secured, the trays are properly routed, and no seals are compromised. A messy tray or an unsealed closure is a redo.
Bonding and Grounding systems are checked with continuity testers. This is not optional. Missed bonds or grounding errors can cause outages, create safety hazards, and void warranties, especially in aerial builds.
Slack Storage is examined to ensure that there is enough usable slack for future maintenance. If you coiled slack inside a handhole with no room to work or skipped it altogether, you’re setting up the next crew to fail and it will get flagged.

Fiber Testing

Once the physical build is inspected, the testing process begins. This is where the numbers have to back up the work.

Using an OTDR (Optical Time-Domain Reflectometer), the splicing and testing techs shoot light down each fiber route and measure how the signal behaves. They look at:

Loss Across Splices: Think of each splice like a bridge connecting two sections of road. If the bridge is misaligned or full of debris, cars (or light) slow down or don’t make it across at all. A little loss is expected. But if the drop is too sharp, it means the connection wasn’t clean, the alignment was off, or the fiber got damaged during fusion.
Reflective Events: A reflection is like a head-on collision on the road something’s bouncing traffic back the wrong way. In fiber, it usually means a dirty connector, a cracked end face, or a splice that wasn’t fused properly. These reflections confuse the signal, reduce bandwidth, and can knock service offline especially in high-speed networks.
Breaks or Severe Bends: Imagine a garden hose that’s been folded in half. Water can’t flow, and pressure builds up behind the kink. That’s what a fiber break or tight bend does to light. The OTDR will spike or go flat telling you exactly where the damage is. Most of the time, these show up because someone buried a crushed duct, pulled too hard, or made a turn too sharp with no sweep.
Power Levels: Power levels are like water pressure at the faucet. It doesn’t matter if everything upstream is working, if you’re not getting enough at the endpoint, the whole system suffers. That’s why power meters are used at both ends to confirm that the signal arriving is strong enough to support the intended services. If it’s too low, the light won’t carry far enough. If it’s too high, it can fry sensitive equipment.

Testing is not a formality. It’s the proof that everything upstream, from the engineering to the trenching, actually worked. And it’s the only way to know, with certainty, that the customer will get reliable service.

Where Most Field Crews Get Caught

A lot of test failures and inspection flags are avoidable. They come from overlooked details or bad assumptions.

Here’s what trips up most crews:

Handholes with no drainage: You might’ve set the vault perfectly, but if water pools every time it rains, you’re going to be asked to dig it back up and fix the base.
No slack at the closure: If the splicer can’t pull enough fiber to work, or if the inspector can’t open the closure without breaking tension, the job fails.
Labeling issues: Mislabeling a fiber tube or failing to mark a duct at a crossing might not seem like a big deal in the moment, but it causes huge headaches during testing and operations. What’s labeled must match what was built.
Unrecorded field changes: A common one. The crew moved a route to avoid a utility conflict or changed a depth, but never updated the as-built. Now the inspector is comparing apples to oranges.
Non-compliant grounding: Bonding and grounding aren’t just for looks. They are safety-critical and required by code. Skip it, and you’re risking not only inspection failure, but serious liability.

Why Inspection Shouldn’t Be Feared, But Used

Some crews see inspectors as the enemy. But the truth is, a good inspection protects everyone. It gives you a chance to catch problems before the job gets buried. Once the network is turned up and handed off, fixing anything becomes ten times harder and far more expensive.

A failed inspection in the field is a fixable delay. A failed connection in a live network is a public problem that costs reputation, time, and money. So don’t fear inspection. Use it.

What You Can Do Differently Today

If you’re a foreman or crew member in the field, start thinking one step ahead. Ask yourself:

Will someone be able to access this closure five years from now?
Is the cable labeled in a way that someone else can follow?
Did I leave enough working slack for maintenance or future upgrades?
Would I be proud to open this handhole in front of an inspector?

If you’re a PM or in the office, stop treating inspection as a box-checking formality. Schedule real time for it. Build in buffer to fix what gets flagged. Talk to your inspectors and understand their expectations. It’s not about winning points, it’s about finishing strong.

Turn Up & Closeout

At this point in the project, everything should be built. The fiber is in place. The splicing is complete. The testing is done. But the job isn’t finished until one final step happens: the network goes live.

Turn-up and closeout is where everything gets validated one last time, not by the contractor, not by the splicer, not by the PM, but by the customer. It’s where the service provider runs their own tests, pushes signal through the system, and decides whether what they paid for is what they got.

This isn’t just a technical milestone. It’s the moment the work leaves your hands and becomes someone else’s responsibility. And if anything is wrong, from missing documentation to performance issues, the job doesn’t close. It hangs. And that means you don’t get paid.

What Actually Happens During Turn-Up

Turn-up is the phase where the network is energized. The core equipment, usually housed in a cabinet or central office, is connected, powered, and begins pushing light through the new fiber routes. It’s the point where signal flow starts and services can begin.

Here’s what typically happens:

The active electronics are connected to the fiber and powered on.
Test signals are injected from one end and verified at the other.
All splice points, routes, and cabinet feeds are rechecked to ensure there’s continuity throughout the entire path.
The operations team from the provider confirms that signal strength, latency, and throughput meet the service level agreement (SLA).
Final validation tests are performed to confirm readiness for customer connection.

If all of that goes well, the network is accepted and scheduled for service rollouts. If something fails, the build gets flagged for correction and the clock keeps ticking.

More Than Just Paperwork

Closeout is the administrative, documentation-heavy part of the phase and it’s where most contractors get tripped up. While it might seem like a back-office task, closeout is how the work gets certified, paid for, and archived.

Here’s what’s typically required for a successful closeout:

Redlined as-builts that reflect exactly what was built, not just what was planned. These must match the actual field install, down to route changes, splice counts, and slack locations.
Test results from OTDRs and power meters, clearly labeled and organized by segment, showing pass/fail results for every fiber path.
Photos and documentation of all critical components, including handholes, cabinets, closures, and pole attachments.
Permits and approvals showing that all work was legally completed and cleared by the necessary jurisdictions.
Sign-offs from field inspectors or representatives confirming that the physical install meets all specs.

This package gets handed to the customer, whether it’s an ISP, a city, or a private client, and becomes their official record of the build. If it’s incomplete, messy, or full of inconsistencies, the customer can delay acceptance or reject the project entirely.

Where Things Fall Apart

Many jobs stall in this phase because the documentation was bad.

Here’s what that looks like in the real world:

The route was changed in the field, but the redlines weren’t updated. Now the GIS records are wrong.
The fiber tested clean, but no one labeled the OTDR traces. The customer can’t match the results to the correct segments.
The vaults are in place, but there’s no photographic proof. The inspector won’t sign off without it.
The splicing passed, but the cabinet wasn’t bonded. It gets flagged during turn-up and has to be reworked.
The crew finished the job, but the PM never uploaded the permit approvals. Now the customer is legally blocked from turning up the service.

This phase is about alignment, making sure the people in the office, the people in the field, and the people at the provider all agree on what’s been done. And that only happens when the records are clean, accurate, and complete.

Why This Phase Feels Like a Squeeze

By the time you get here, everyone’s tired. The crews are ready to move on. The budget’s nearly spent. The client wants to light customers. The GC wants to bill out. And suddenly, all eyes are on this final step, the smallest, least visible part of the whole build.

That pressure creates bad habits:

Rushing documentation
Skipping final walkthroughs
Submitting half-complete test reports
“We’ll fix it later” thinking

But here’s the truth: how you finish determines whether the customer trusts you again. Anyone can start a job. Only the best finish it clean.

What You Need to Know

If you’re in the field:
Finish it. Label your vaults. Take the photos. Keep track of what you build. Don’t wait for someone else to chase you down for info you could’ve captured in the moment.

If you’re the splicer:
Save your test files. Name them clearly. Document what was out of spec and what got fixed. And don’t fudge results to make things pass, that always comes back to bite the entire team.

If you’re a PM or office lead:
Own the closeout package. Track what’s missing. Double-check every permit, test file, and redline. Review the customer’s required format before the final day, not after.

This isn’t busywork. It’s the proof that you actually delivered what you said you would.

Why Closeout is the Beginning of the Next Job

Most contractors treat closeout like the end. But the people hiring you are watching to see how you handle it. If you deliver a tight, clean, complete closeout, they remember that. It builds trust. It sets you up for the next contract.

If your paperwork’s a mess, your test results are mislabeled, and your redlines are full of guesswork, you become a risk, even if your work in the field was solid.

Clean closeout builds long-term relationships. And in this industry, relationships are worth more than footage totals.

Maintenance & Repair

Maintenance and repair aren’t just about fixing things when they break. They’re about keeping the network stable, minimizing downtime, and making sure the system keeps delivering the service it was built for. And how easy (or painful) that is depends almost entirely on how well the job was built in the first place.

If construction cut corners, this is where those shortcuts show up. If documentation was sloppy, this is where crews waste hours trying to trace the path. If closures were buried without slack or mislabeled, this is where you pay the price.

The repair team doesn’t get to start fresh. They inherit everything that was done before them, good or bad.

What This Phase Actually Involves

Maintenance isn’t reactive. At least, it shouldn’t be. The best crews stay ahead of issues before they turn into outages. That means:

Routine inspections of cabinets, closures, and handholes
Looking for signs of water ingress, cracked lids, loose grounds, or critter intrusion.
Re-testing fiber paths in high-risk areas
Especially after road construction, severe weather, or new utility work nearby.
Sweeping for degradation in signal quality over time
Light levels change, especially in longer runs or poorly spliced segments. You catch it early, or you deal with it when the customer calls angry.
Fixing cuts, crushed ducts, and failed hardware
Which often means middle-of-the-night dispatches, emergency locates, and pulling permits under pressure.

It’s not glamorous. It’s not fast. And it rarely gets the attention that construction does. But this is the phase that keeps the network alive.

What You See When the Build Was Done Right

A well-built network is a dream to maintain. Closures are labeled and accessible.
Slack is available in the right vaults. Documentation matches what’s in the field.
Bonding is tight. Cabinets are clean. Paths are traceable.

It doesn’t mean things won’t break. They will. But when they do, they’re easy to locate, diagnose, and fix. You’re not cutting in a new splice just to add 4 feet of slack. You’re not calling the city because someone buried a handhole under a sidewalk without marking it. You’re not tracing mystery fiber routes that were never redlined after field changes.

When a job was done right, maintenance is just that, maintenance.

What You See When It Was Built Wrong

On the other hand, a rushed or sloppy build turns every repair into a forensic investigation.

There’s no slack in the vault, so you’re cutting back 100 feet just to get working length.
The fiber was pulled too tight, so you’re dealing with microbends that degrade performance but don’t show up on a visual inspection.
You pop a handhole lid and find a flooded mess with no label, no tray, and no logic to how anything was routed.

And that’s when it’s still in service. In some cases, the plant is already compromised, cracked splice trays, corroded lugs, strand breaks, or duct crushed under a new driveway pour. Now instead of a 2-hour repair, you’ve got a 2-day rebuild. And all because no one thought maintenance would ever have to touch it again.

What You Need to Know

If you're the one maintaining the network:

You’re the lifeline. Your job isn’t just to fix, it’s to preserve. Document what you find. Flag what wasn’t built to spec. And when you fix something, do it clean, not quick. You’re not just closing a ticket, you’re setting the standard for the next crew.

If you're the one building it:

Understand that the install isn’t the end. Someone will have to access what you place. Don’t bury closures in concrete. Don’t skip slack because you’re short on time. Don’t label tubes with Sharpie that fades in the first rain. Build it like you’re going to be the one who has to come back and fix it in six months.

If you're the one managing the project:

Track post-completion issues. Where do repairs keep happening? Are they isolated, or do they trace back to a crew, a vendor, or a region? Patterns reveal problems. And problems left unresolved keep eating margin long after the job is “done.”

Why This Phase Is the Measure of All the Others

Maintenance is where you find out what kind of build you really have.

Because once the crews are gone, the trucks are moved, and the job is paid for, the only thing that matters is whether it still works. Good maintenance starts with good construction. Good repairs start with accurate documentation. And long-term network health starts with crews who cared enough to do it right the first time.

This phase is proof. Not of what you planned. Not of what you designed.
But of what you actually built.