Demand connections — queue discipline is now a corporate risk

Large demand users (data centres, electrification) face rising connection uncertainty. Queue discipline and evidence requirements can create contractual and reputational exposure if delivery promises are made too early.

Reader guide

How to read this Signal

Evidence → Uncertainty → Trigger → Decision implication

Each Signal separates the sourced change from what remains uncertain, identifies the trigger to watch and states why it matters to a decision.

See the full Approach →

Key points

What the evidence indicates for the decision.

  • →Demand projects can become ‘stranded’ if connection assumptions fail.
  • →Counterparty claims about connection dates require evidence, not assertions.
  • →Insurance and contracting terms should reflect connection uncertainty explicitly.

Actions

Practical next steps if this Signal touches your mandate.

  1. 01Add ‘connection date evidence’ as a condition precedent in major contracts.
  2. 02Use scenario ranges for connection dates in board materials.

Sources and evidence

Publication and access dates are shown with the source record.

Discuss how this affects your decision

We can pressure-test assumptions and map the next verification steps.