Engineering Project Cost Estimation

After decades of working in project risk analysis—and building our own Monte Carlo-based software tool (HawkEye)—I’ve been refining a practical way to bridge the gap between schedule risk and cost risk. That method eventually became RISA: Risk Impact Sensitivity Analysis. In my last article, I focused on schedule risks. But in this new one, I take the next step: 👉 Integrating schedule AND cost risks into one rational, quantitative model. Why does that matter? Because schedule risks don’t just delay projects—they ripple into labor costs, procurement, contracting strategies, and the overall project budget. Yet many teams still treat schedule and cost analysis separately. In this article, I walk through: ⚙️ How to integrate schedule and cost simulations 🎯 How RISA helps prioritize the risks 🛠️ How mitigation strategies change outcomes 📊 How to calculate contingency reserves based on data, not optimism And yes—there’s a real case study to make it practical. Hope you enjoy the read—and I’d love to hear your thoughts or experiences. 📄 Article link below 👇 https://lnkd.in/gi-S7HVg #ProjectManagement #RiskManagement #MonteCarloSimulation #RISA #ProjectControls #CostEngineering #ConstructionProjects #DataDrivenDecisions #PMO #ScheduleRisk #CostRisk #RiskAnalysis #EngineeringManagement #ProjectControlAcademy

Everyone thinks nuclear budgets blow out on site. Concrete. Cranes. Delays. Contractors. That story is comforting. And mostly wrong. Look at the curve below. 👇 By the time construction starts, the money is already gone. Not spent. Committed. This is not a build problem. It is a decision problem. Here’s the part most post-mortems skip 👇 Nuclear cost risk concentrates before ground is broken. If you want to understand why budgets “explode early”, study these five failure modes in your own time: 1️⃣ Design Instability If scope is still moving after contracts are signed, you are no longer estimating. You are negotiating in public. 2️⃣ FOAK Penalty First-of-a-kind systems do not fail slowly. They fail mid-programme, when reversal is politically impossible. 3️⃣ Licensing Iteration Every regulatory rewrite ripples backwards into engineering, procurement, and schedule. Safety cases are not paperwork. They are design. 4️⃣ Vendor Thinness Few qualified suppliers means long lead times, zero redundancy, and price power you do not control. 5️⃣ Political Pricing Early estimates are often shaped to secure approval, not to survive delivery. Optimism becomes contractual fact. The hidden lesson: Construction overruns are symptoms. Commitment decisions are the cause. A useful test for any large capital project: Ask where the “point of no return” really is. Then ask who is accountable before that moment. Most risk enters quietly. Long before the hard hats appear. 💾 Save this for the next time someone says, “we’ll fix it during construction”. 📩 If this kind of thinking is useful, subscribe to my newsletter https://lnkd.in/eE7URUx6 for deeper dives on energy, capital projects, and decision risk. ♻️ Repost if this changes how you think about cost overruns. 👇 I’ve linked the 3 best papers on megaproject risk in the comments.

I just published a research paper that challenges how we model risk. And the result will make most project managers uncomfortable. ↓ Standard Monte Carlo assumes risks fire independently. They don't. They fire in chains. Risk A delays procurement. Procurement delay pushes mobilisation. Mobilisation delay compresses testing. Compressed testing forces rework. Rework blows contingency. That's not bad luck. That's a cascade. And your risk register cannot see it. ━━━━━━━━━━━━━━━━ I spent months building a framework to model exactly this — Probabilistic Chain Analysis (PCA). The result from a UK highways case study: ▸ One pre-mobilisation intervention ▸ £250,000 reduction in P90 cost exposure ▸ £15,000 management cost ▸ 16.7x return on risk management effort Not because we worked harder. Because we looked at the right node. ━━━━━━━━━━━━━━━━ The methodology: → Map risks as a Directed Acyclic Graph (not a flat register) → Assign conditional probabilities using Bayesian Networks → Run coupled Monte Carlo simulation → Identify cascade lift factor — which node is amplifying everything? → Intervene there. Not everywhere. ━━━━━━━━━━━━━━━━ The paper is 27 pages. Open access. No paywall. Validated across 16,000 infrastructure projects across 8 sectors. UK highways. Solar EPC. Hospitals. Power plants. Same pattern every time. The most dangerous risk isn't the most probable one. It's the most connected one. ━━━━━━━━━━━━━━━━ 📄 Full paper (free): in comments ━━━━━━━━━━━━━━━━ Have you ever seen a cascade take down a project that looked fine on paper? Drop it in the comments. I read every one. #ProjectManagement #RiskManagement #MonteCarlo #BayesianNetworks #Infrastructure #EPC #ProjectControls #PMP #Quantitative

What If the Project's Risk Price Exceeds the Base Cost Estimate: A Case Study of a Giga Rial Infrastructure Project The Crossrail project in London, UK is a state-of-the-art railway that serves as a valuable source of lessons learned for planning major infrastructure projects internationally. The15-year program employed an overall workforce of approximately 4,000 full-time equivalents and provided significant long-term benefits to communities. Initially, the project was planned for completion by December 2018, with a budget of £14.8 billion. However, during the late stages of the construction phase, the project encountered numerous issues and risks, including complex interfaces between different sub-projects and systems. These challenges led to an increase in the project cost to £18.8 billion and a revised completion date in May 2022. From 2018, the original completion date, the project went through multiple cycles of re-forecasting, focusing on establishing an achievable baseline for Cost-To-Go. In 2019, Crossrail formed a team of senior executive members to ensure consistency, clarity, and assurance in estimating the Anticipated Final Cost (AFC). It took the team six months to fully understand the complexities and translate them into realistic plans. The attached figure illustrates the proposed P80 Cost-to-Go, established by the end of 2020. The final results at project completion demonstrate that the program team effectively implemented the recovery plan and were able to meet what was planned. The report highlighted that one key driver of success was the acknowledgement of risks and uncertainties facing the program, coupled with realistic and evidence-based forecasting of their impact, adjusted by expert judgment. For example, as shown in the attached figure, 53% of the additional £1.1 billion funding required to complete the project was attributed to risks and uncertainties. As demonstrated in this case study, true and transparent acknowledgement of risks and their corresponding impacts plays a crucial role in successfully delivering mega infrastructure projects. Lessons learned from the Crossrail project emphasize that it is acceptable if risk costs exceed base costs. What is not acceptable is underestimating the impact of risks, overpromising delivery outcomes, and jeopardizing long-term project benefits. This serves as a reminder for public and private sectors that funding contingencies and management reserves based on pre-determined ranges (e.g., AACE recommended ranges) can threaten project success. In your projects, how realistically are the impacts of risks incorporated into forecasts? Your insights are highly appreciated. Source: https://lnkd.in/ghSXeRwu #lessonslearned #riskmanagement #costoverrun #collaboration Hatch Metrolinx Network Rail Toronto Transit Commission (TTC) Infrastructure Ontario Infrastructure New Zealand

Most cost estimators do not fear the numbers. They fear how the client will react to them. That fear is exactly what pushes teams into single-point estimates, softened ranges, and “safe” presentations that hide uncertainty instead of explaining it. And that is where the trouble starts. Clients are not upset by uncertainty. They are upset when it surprises them. Your professional responsibility is not to protect stakeholders from uncomfortable information. Your responsibility is to communicate accuracy honestly, show the range, and explain what drives it. AACE has been clear on this for years: an estimate is a probability distribution, not a promise. When you explain how accuracy behaves When you show P-values instead of one number When you walk the client through why the range exists You move the conversation from defensiveness to decision-making. The irony is that transparency feels risky, but it is the only approach that builds trust. Hiding uncertainty does not protect the client. It only delays the moment they discover it in the field, when it is far more expensive and far harder to manage. This carousel breaks down how to communicate estimate accuracy in a way that is clear, credible, and aligned with our professional duty as estimators. If your stakeholders push for one number… this is what you show them. #CostEstimating #ProjectControls #CAPEXTraining #OPEX #EnergyProjects #AACE #EstimatingAccuracy #RiskAnalysis #ProjectPlanning #PowerToX #CO2Capture #CO2Transport #ConstructionManagement #EngineeringLeadership #InfrastructureDevelopment #emeraldcost