Key points
- Owners of complex CAPEX projects often depend on EPCM partners for controlling the schedule, managing progress, and ensuring actual delivery. That trust is necessary, but it should be supported by independent evidence.
- An independent health check can reveal structural weaknesses in the project schedule’s network logic that distorts data-driven decision-making.
- Visualizing that health check in an interactive reportingHUB, combined with expert risk workshops, and target-specific Monte Carlo simulation turns the project schedule from a static Gantt-chart to a practical steering tool.
- The CAPEX Schedule Intelligence package enables better governance: the owner can ask sharper questions, challenge assumptions constructively, and understand if key milestones are really threatened.
In our experience, schedule control in complex industrial CAPEX projects is far more than a technical problem, it sits at the core of the overall project governance. Even for strategically critical investments, the owner’s project management team is often thinly staffed, while the detailed project schedule sits mainly with an external delivery partner. The owner’s team can become dependent on monthly steering meeting presentations, static schedule extracts, and the delivery partner’s delivery narrative being the project’s single version of the truth.
In a complex capacity-increase project at an existing Italian pharmaceutical production site, Tenseventy Advisors delivered an independent schedule intelligence approach to support the owner’s project steering. The aim was not to replace the delivery partner, which in this case was an EPCM provider, or to duplicate the scheduler’s role. Instead, we created an independent, evidence-based review of schedule quality, dependency logic, field-level risks, and milestone exposure.
Why owners need independent schedule intelligence
Large CAPEX projects are often governed through schedules that look precise. At least from the beginning of the detailed design phase, they contain thousands of activities, and milestones, with their possible dependencies, connection logic, resource allocation and external constraints. Yet the appearance of precision does not automatically mean that the schedule is reliable as a decision model.
A schedule often contains missing links, unusual relationship types, excessive lags/leads, constraints that artificially hold dates in place, or activities with very high float because of incomplete downstream logic. It can also be structurally sound in one area and weak in another. Most importantly, even a technically maintained schedule may not fully reflect what the execution teams see on site: contractor congestion and limitation of physical space, brownfield surprises, interface issues between contractors or the project and the running site, late design clarifications and change orders, weather exposure or pace of work reduced due to more-difficult-than-expected working conditions.
For an owner organization with limited internal project controls capacity, this creates a difficult position. The owner must trust the EPCM provider but also needs enough independent insight to challenge the schedule narrative and ask the right questions. In a multi-hundred-million-euro industrial investment, the cost of discovering weak logic or misunderstood risk too late can be substantial.
This kind of independent schedule intelligence provides the second view owners often need. It does not start with the assumption that the EPCM reporting is wrong. It starts from a more useful premise: trust is good, and an evidence-based external review is better.
The delivered approach
The solution in this project was built around a monthly cycle aligned with the EPCM provider’s reporting schedule. Each cycle combined schedule data, structural checks, expert input, and simulation results into a practical steering view, tailored to the project leadership’s requirements. The components were designed to answer different questions and reinforce each other while simultaneously improving communication between the parties – instead of trying to prove the EPCM provider wrong or to find holes in their data, we were validating their assumptions, improved their forecast accuracy and provided direct recommendations for implementation.
1. reportingHUB: making the schedule usable for humans
reportingHUB provided a browser-based interface to explore project progress and schedule logic through the project’s work breakdown structure (WBS). Instead of treating the schedule as a file that only specialists could interpret or a high-level offline summary that provides too little details to ask questions about, reportingHUB was made to provide a balance between these two extremes: key views accessible to a broader owner and project leadership audience.
The platform supported progress visualization, drill-down by WBS component, dependency checks, delay hypothesis testing, and critical-path-to-target analysis. Users could ask practical questions: If I delay the delivery of this component due to a late change request, what else will be delayed downstream? Is installing these pipes in ‘Area A’ direct or indirect prerequisite to complete the pre-commissioning in ‘Area B’? Which open activities sit on the critical path leading to the tests we planned in the fixed outage window next quarter?
This mattered because the steering problem was not only about knowing the latest finish date. It was about understanding the logic behind the forecast and whether that logic could be challenged.
2. Monthly schedule health check: testing the mechanics
Alongside reportingHUB, we performed a recurring schedule health check. It was a simplified, practical version inspired by the logic of full DCMA-style schedule assessments. The objective was to detect mechanical issues in the schedule structure and make them visible for discussion and eventual correction.
The checks included areas such as multi-connections between activities, missing predecessors or successors, constraints, connection types, evaluation of leads and lags, and other indicators that affect whether the network can be trusted as a true representation of reality. These checks do not replace engineering judgement. They cannot determine whether roof erection logically belongs after foundation completion. What they can do is identify where the schedule mechanics may be too weak, too artificial, or too ambiguous to support reliable steering and forecasting.
This created a recurring owner-side challenge list for monthly governance.
3. Risk workshops: bringing field reality into the schedule
The second layer was human and very operational. Structured risk workshops brought together the owner, EPCM provider, and key contractors to identify and quantify time-related risks. The purpose was not to assign blame or solve every issue in the workshop. The purpose was to capture what experienced people saw in reality and connect those risks back to the schedule.
Risks were clarified, assigned to relevant schedule activities, and quantified where it is possible to provide input for the MC simulation. Risks could also:
- remain in backlog if they were not yet specific enough,
- be closed when mitigated or already reflected in the schedule, or
- be treated as non-simulation risks when Monte Carlo modeling was not appropriate
This risk lifecycle was important. It avoided the common trap of treating the risk register as a static list and the workshop as a compliance obligation. In practice, the recurring format gave all parties a better way to monitor risks, close outdated concerns, and raise new issues before they became steering-level surprises.
4. Target-specific Monte Carlo simulation: forecasting the milestone that matters
The final layer was the Monte Carlo simulation. The simulation used the current schedule with its calendars, dependencies, plus the list of quantified risks to run thousands of futures and observe the movement of selected target milestones.
The key differentiator was target selection. Instead of focusing only on final project completion, the simulation could be directed at a specific milestone or phase gate somewhere inside the project. For the owner, this was critical. The steering committee did specifically care about production start of the first phase of capacity increase. Owners may take interest in mechanical completion of a specific area, the end of a phase, readiness for a shutdown, or start of production. These targets can matter more than a distant final completion date our method allowed the team to freely select any relevant target within the project schedule.
The simulation also helped distinguish between risks that were operationally concerning and risks that were schedule-critical. Some risks looked serious but had little or no impact because they sat far from the relevant critical path. Other risks had a direct effect on the selected milestone and changed the forecasted critical path in almost any simulation scenario.
How it changed steering conversations
The solution included an elaborate dashboard, and monthly predicted forecasts dates, but the strongest benefit was the quality of the monthly conversation that it was driving. Before an evidence layer is in place, steering discussions often focus on status: what is late currently, what has just changed, what does the latest forecast say? With schedule intelligence, the discussion can move to the drivers behind that forecast:
- Which parts of the schedule logic are structurally weak?
- Which constraints or logic flaws may hide real issues?
- Which risks do people, who are every day on the site, consider?
- Which of those risks actually move the selected milestone in simulation?
- Which under-the-radar activities may need mitigation before they become critical?
- Which assumptions should be challenged before the next schedule update?
This gave the owner a constructive way to challenge the EPCM narrative. Our point was not to create conflict, it never is. Tenseventy’s concept, and my own philosophy, is to make the steering more data-driven, transparent, and focused on the decisions that could protect critical milestones.
We all know that it is difficult to maintain a multi-thousand-line, continuously adjusted schedule correctly. These monthly health checks and the arising discussions gave both parties the ability to quickly fix the logical issues, and to detect risks that would have been lurking under the surface otherwise.
And when real delays became inevitable, they did not come as a surprise. The discussion could focus on recovery instead of assigning blame.
From project experience to CAPEX Schedule Intelligence
Based on this delivered project experience, Tenseventy has packaged the approach as CAPEX Schedule Intelligence: an independent schedule, risk, and milestone intelligence product for owners of complex CAPEX projects.
CAPEX Schedule Intelligence is modular. Depending on the maturity of the project controls setup, it can include a schedule health check, a live reportingHUB, recurring risk workshops, target-specific Monte Carlo simulation, and monthly steering-ready insights. The package is especially relevant when the owner’s organization is lean, the project is complex, and the delivery model requires strong reliance on external EPCM or contractor partners.
The product is designed to support better owner governance. It does not replace the project schedule, the EPCM provider, or the contractor management process. It strengthens the owner’s ability to interpret, challenge, and act on the schedule.
Final thoughts
Complex projects do not fail because a progress dashboard is missing. They fail because signals are misunderstood, risks are kept hidden until it’s too late, or schedule assumptions remain unchallenged until they become unchangeable facts on site.
Independent CAPEX Schedule Intelligence helps owners move from trust-based reporting to evidence-based steering. It brings together the schedule mechanics, the field reality, and the probabilistic milestone view needed to govern complex industrial projects with confidence.
For companies managing major CAPEX projects with lean internal teams, the message is simple: you do not need to distrust your EPCM partner to need an independent view. You need it because the investment is too important to steer without one.
