Background:

Long-haul fiber is being built at a pace and scale the infrastructure sector has rarely seen. These programs run across dozens of geographically separated segments, delivered by multiple general contractors working simultaneously inside constrained public rights of way. At Clarisight Consulting (Clarisight), we help owners turn that fragmented picture into a single, predictive view of the program, one that shows which work is actually driving the completion date, and how much time is left to protect it.

A private infrastructure developer building a long-haul fiber-optic network across California, executing through multiple large civil contractors, could not name the segment governing its own completion date. In four weeks, it could.

The Challenge: Contractor Dates, No Program View

Every completion date in the program came from the contractors themselves. Segments were tracked in isolation with no linkage between them, progress was measured by duration rather than installed quantity, and crew commitments were reported but never verified. The owner could not identify which segment governed program completion, could not test whether any contractor date was achievable, and had no defensible basis on which to require a recovery plan. Conversations with contractors were opinion against opinion.

Key challenges included:

• Contractor-supplied completion dates, accepted without independent validation.

• Segments tracked in isolation, with no cross-segment logic or critical path.

• Progress measured by elapsed duration rather than installed footage.

• Crew levels reported but never tied to the schedule.

• No float visibility to rank where recovery effort belonged.

Our Approach: A Four-Phase Program Critical Path Pilot

Clarisight structured a four-phase pilot built entirely from the production data the program was already generating. No new reporting burden was placed on the contractors.

The Process: From Contractor Dates to a Defensible Forecast

Every segment was scheduled on a common P6 template with a shared work breakdown structure, activity coding, and milestone framework, so segment schedules integrate cleanly into the program master. Progress is measured by units complete: footage bored and installed rather than by duration percent, giving a verifiable read on production. Pre-construction activities that routinely govern start dates, including permits, resident-engineer approval, and traffic-control plan approval, are modeled explicitly as predecessors, and long-lead, change-order-prone work such as bridge attachments and bridge-material procurement is tracked separately. Contractor timelines are then challenged against demonstrated production rates drawn from the program’s own field data, so the baseline reflects achievable performance rather than optimism.

The result is not a schedule document. It is a working forecast that refreshes weekly against actual field production, paired with an executive summary that translates it for decision-makers. It comprises:

•  A program critical path linking all 21 segments and naming the one that governs completion.

•  A float register ranking every segment by days ahead or behind target, so attention goes to the segment that is driving the critical path.

•  A resource-loaded forecast that prices crew and production decisions in schedule days before anyone commits to them.

•  A contractor recovery framework requiring a rolling three-week look-ahead and a segment-level recovery plan, measured weekly against achieved production.

The Outcome: A Program That Can See Itself

•  Critical path identified. A single segment was found to govern the entire program, forecasting to mid-June 2027 — 131 days behind target. Before this engagement it was one row among twenty-one.

•  Risk located, not just reported. Exposure was concentrated in two northern routes averaging 71 and 56 days behind target, against 19 to 39 days elsewhere, with a named cause: zero percent complete, latest starts, and the largest remaining footage in the program.

•  Recovery modeled, not negotiated. Doubling crews on the governing segment cuts it from roughly 130 shifts to 65 — close to 13 weeks recovered. Northern routes are modeled at 300 linear feet per crew while southern crews demonstrate up to 600, headroom available without adding a single crew.

•  Accountability established. Crew levels became tracked commitments. If a contractor falls below its assumed 17 crews, production drops proportionally and float goes further negative — immediately and visibly.

Programs of this scale rarely fail because the work is impossible. They fail because the owner learns too late. Delay now shows up as a number, on a named segment, with a named cause, while there is still time to recover.

From Symptom to Root Cause: The Clarisight PMO Maturity Assessment & Benchmark

What surfaced on this program as a schedule problem was, at root, a project controls problem and that is the pattern we see across large capital programs. Clarisight’s PMO Maturity Assessment & Benchmark is the diagnostic we use to find those root causes before they reach the critical path.

Applying our proprietary Project Controls Assessment Roadmap (PCAR), we score an organization’s delivery capability across eight assessment categories — Scope, Cost & Financial Management, Schedule, Integration, Change Control, Risk & Issue Management, Communication, and Procurement & Contracts Management — against phase-gate requirements that ask, gate by gate, whether the controls a program depends on are genuinely designed, documented, and operating. Each requirement is weighted and scored, rolled up into a category maturity rating on a four-tier scale (Informal, Standardized, Monitored, Optimized), and benchmarked against peer programs and industry standards to produce a weighted overall maturity rating and a clear view of where the organization stands against where it needs to be.

That structure is what turns symptoms into recommendations. On a program like this one, a low Schedule Management score traced to missing CPM logic, absent look-ahead and float-path reporting, and no schedule delay analysis explains precisely why a critical path could not be identified. Weak Integration and Communication scores explain why segment-level data never rolled up into a single source of truth for leadership. A gap in Change Control explains why contractor commitments carried no consequence. Because every score is tied to a specific, testable requirement rather than an opinion, the assessment does not stop at a rating. It produces a prioritized, data-driven action plan with measurable steps, sequenced by weight and impact, proven on pilot projects, and sustained through team training and continuous monitoring.

Owners get an early, defensible read on which control gaps are most likely to cost them time and budget, and a roadmap for closing them while there is still an opportunity left to protect.

Conclusion

Whether the immediate need is a program critical path or a full assessment of delivery capability, the objective is the same: give the owner an accurate, forward-looking view of the program and the evidence to act on it. Clarisight helps clients move from reactive project management to a proactive, insight-driven PMO.

Ready to elevate your delivery capabilities? Contact us at npanchal@clarisight.com to explore how we can help you transform your project challenges into strategic opportunities.