Where CapEx Decisions Begin to Break

Most organizations attribute capital project issues to execution:

• Budgets increase 
• Schedules slip 
• Contractors disagree 
• Change orders accumulate 

These are typically treated as: construction management problems.

At the point of approval, the decision environment often feels unclear:

• Scope is not fully defined 
• Proposals are difficult to compare 
• Each option is built on different assumptions 
• Pricing varies more than expected 
• It is not fully clear what is being approved

Decision-makers are left asking:

• “Are these truly comparable?” 
• “What am I actually committing to?” 
• “Why are the numbers so different?”

In the absence of structure, teams move forward by:

• Comparing proposals in Excel 
• Reconciling differences through email and meetings 
• Relying on internal judgment 
• Deferring to consultants or vendors 
• Aligning just enough to proceed 

The decision gets made. 

These approaches help move the process forward — but they do not resolve the underlying conditions.

Because:

• Scope is not normalized across options 
• Assumptions remain embedded and inconsistent 
• Risk is distributed differently in each proposal 
• Allowances and exclusions mask unresolved work 
• Authority and decision criteria are not fully defined 

As a result:

• Pricing differences cannot be evaluated accurately 
• Tradeoffs are not visible at the time of approval 
• Risk is accepted implicitly rather than intentionally

This is not a bidding problem.
This is not a contractor problem.
This is not an execution problem.

This is a decision problem.

More specifically:

The decision is being made without structural equivalence.

At the point capital is committed:

• Scope is not consistently defined 
• Assumptions are not explicit 
• Risk is not clearly allocated 
• Alternatives are not truly comparable 
• The basis for approval is not fully documented 

 When these conditions exist:

• outcomes appear to change during execution 
• but are often the result of what was embedded in the decision 

Execution reveals the decision.
It does not create the outcome.

Most tools and processes focus on execution.

What is typically absent is a structured layer applied before approval, where:

• scope is defined consistently 
• inputs are normalized 
• assumptions are surfaced 
• decision criteria are made explicit 

When This Layer Is Missing

• decisions rely on interpretation 
• alignment is partial 
• outcomes become difficult to defend 
• the original decision logic cannot be reconstructed 

When This Layer Is Present

• alternatives become directly comparable 
• assumptions can be evaluated explicitly 
• risk is visible at the time of approval 
• decisions can be explained and defended later

By that point, the decision has already been made.