Pre-investment technical due diligence: what is usually NOT checked

Pre-investment technical due diligence: what is usually NOT checked

In many energy, waste, and industrial investment projects, technical due diligence is treated as a formal checkpoint — a necessary step before moving forward. Calculations are reviewed, technologies are compared, and assumptions are documented.

And yet, despite “successful” due diligence processes, projects still struggle once they move into reality. CAPEX increases, OPEX remains structurally high, flexibility is limited, and business cases fail to deliver what was expected.

From experience, the reason is rarely a missing calculation.
Much more often, the real risks sit outside the assumed scope of early-stage technical reviews.

The most critical issues are not hidden in spreadsheets — they are hidden in questions that were never asked.


Technical due diligence: verification versus reality

In its common form, pre-investment technical due diligence focuses on verification:

  • Does the proposed technology exist?
  • Are reference plants available?
  • Do the nominal performance figures match the design assumptions?
  • Are the basic mass and energy balances consistent?

All of this is necessary — but it is not sufficient.

What is often missing is a system-level assessment of how the project will actually behave over time, under real operational, market, and organizational conditions.

Technical systems do not operate in isolation. They operate as part of a broader ecosystem that includes feedstock variability, energy markets, human operation, maintenance realities, and regulatory drift.

This gap between verification and reality is where most long-term risks originate.


What is usually NOT checked: operational assumptions

A major theme across all speakers:
One of the most underestimated areas in early-stage assessments is operation.

Feasibility studies and investment models often assume:

  • stable feedstock quality,
  • steady operating conditions,
  • continuous availability,
  • ideal load profiles.

In practice, none of these assumptions hold over the full lifetime of a complex installation.

What is rarely examined in sufficient depth:

  • How does the system behave at partial load?
  • What happens during frequent start-ups and shut-downs?
  • How sensitive is performance to feedstock variability?
  • Which subsystems become limiting factors under non-ideal conditions?

Operational reality is dynamic, while early models are static.
The mismatch between the two is a major source of disappointment later on.


System interfaces: where most problems actually appear

Complex projects are not collections of machines.
They are networks of interacting subsystems.

And most failures do not occur inside individual components, but at their interfaces.

Typical blind spots include:

  • pre-treatment interacting with core processes,
  • energy generation linked to variable industrial loads,
  • fuel logistics affecting availability,
  • dispatch strategies conflicting with physical constraints.

These interactions are often nobody’s explicit responsibility.
They fall between contractual scopes, organizational silos, and disciplinary boundaries.

From a system perspective, however, they define whether a project can operate reliably — or not.


System boundaries that exist only on paper

In industrial facilities across Europe, energy storage provides value far beyond self-coAcross EuAnother recurring issue in pre-investment assessments is the way system boundaries are defined.

In many projects, boundaries are set by:

  • EPC contract scope,
  • organizational responsibility,
  • financing structures.

Rarely are they set by physical or operational logic.

Risks, however, do not respect contractual boundaries.
If a bottleneck exists upstream or downstream of the “defined system,” it will still affect availability, performance, and economics.

A robust technical due diligence must therefore challenge not only what is included — but also what has been conveniently excluded.


CAPEX is reviewed. OPEX dynamics are assumed.

CAPEX usually receives detailed attention during due diligence.
OPEX, by contrast, is often reduced to a simplified line in a financial model.

What is frequently underestimated:

  • maintenance-driven availability losses,
  • performance degradation over time,
  • sensitivity to operational strategy,
  • dependence on skilled operators and organizational discipline.

Most investment models implicitly assume stability in systems that are inherently dynamic.
This assumption alone can invalidate an otherwise “sound” business case.


The risk created by the decision itself

An often-overlooked aspect of pre-investment risk is that the investment decision itself creates new risks.

Once a project receives a GO decision:

  • design freezes occur,
  • flexibility is reduced,
  • future adaptations become costly.

Fuel switches, capacity extensions, regulatory changes, or new market conditions then have to be absorbed by a system that was never designed with sufficient margins or adaptability.

From experience, many of the most severe problems emerge after the decision — not before.


Why an independent helicopter view matters

What ties all these issues together is not a lack of expertise or technology.
It is a lack of independent, system-level perspective at the right moment.

Before optimization.
Before implementation.
And sometimes before enthusiasm.

Complex energy, waste, and industrial projects benefit most from a technical assessment that is:

  • independent of vendors and EPC contractors,
  • detached from execution pressure,
  • focused on how the system will actually behave over time.

Not to stop projects — but to ensure that decisions are made with a clear understanding of their technical consequences.


This type of experience-based reflection is part of WEProS Insights — a place where we share independent observations from real projects and investment decisions across complex energy and industrial systems.


Leave a Reply

Your email address will not be published. Required fields are marked *