FOAK Risk Moves in Cascades

First-of-a-kind projects combine technology novelty with site, market, regulatory and execution uncertainty. Traditional risk registers often list these risks in separate rows, giving each an owner and mitigation. The format is useful but can hide causality. A change in feedstock quality can affect process performance, equipment design, energy demand, emissions, product specification, operating cost and the bankability of supply and offtake arrangements. The risks are not adjacent; they are connected.

A Risk Cascade Register starts with the triggering event and follows its propagation. For each step it records the affected baseline, evidence, decision owner, time consequence and control. This makes second- and third-order effects visible before they become independent crises. It also shows where one timely intervention—such as revalidating a mass balance—can prevent several downstream workstreams from progressing on false assumptions.

The method is particularly valuable during amendments and transitions. A site change may trigger a FEED reset, which changes CAPEX, which affects financing needs, which delays FID and Financial Close, which then alters the implementation schedule and milestone feasibility. Recording only the site issue understates the decision. Recording the cascade gives the consortium and granting authority a realistic basis for the revised plan.

Risk cascades should be connected to formal gates. A gate is released only when the critical chain has been closed, accepted or bounded through an authorised scenario. This prevents local optimism from concealing programme-level exposure. It also improves contingency design because management can allocate time and capital to named pathways rather than applying an undifferentiated percentage to every uncertainty.

The deeper lesson is that FOAK governance must be systemic. Innovation risk cannot be eliminated, and public programmes exist partly because markets alone may not absorb it. But uncertainty can be made more governable through traceability, dependencies and decision rights. A project becomes more credible when it can explain not only its principal risks, but how those risks travel and where the cascade will be stopped.