Skip to content
One-PagerReviewed

F0079: Capex Allocation Gate Framework

A decision-ready template derived from the framework.

Name variants

English
F0079: Capex Allocation Gate Framework
Katakana
ゲート
Kanji
設備投資配分 / 枠組

Quality / Updated / Source / COI

Quality
Reviewed
Updated
COI
none

Context

Context: A fixed capex envelope forces trade-offs between mandatory compliance work and growth investments. Finance, engineering, and operations interpret cash-flow timing, downtime, and throughput impact differently, which stalls approvals. A shared gate record makes the capital discipline versus growth optionality trade-off explicit and preserves the rationale for later audits or board reviews.

Options

  • Option A: Fund only mandatory and sustaining capex this cycle and defer growth projects.
  • Option B: Stage growth capex in phases tied to throughput milestones and covenant headroom.
  • Option C: Commit to a full growth program now, accepting higher leverage and execution risk.

Decision

Decision: Choose Option B. Stage growth investments by quarter so early phases validate capacity gains and cash-flow assumptions, and pause if hurdle-rate or covenant thresholds are breached. Assign gate owners, document dependencies, and schedule a formal post-investment review.

Rationale

Rationale: Option B preserves safety and compliance requirements while testing growth returns before full commitment. Phasing protects balance-sheet discipline, surfaces downtime risk early, and keeps sequencing flexible if demand softens. The gate record also satisfies audit and board expectations for capital governance.

Risks

  • If financial cases underestimate downtime or ramp-up, phased approvals may still over-allocate the envelope.
  • Delayed reviews can cause mandatory projects to slip, creating compliance exposure.

Next

Next: Confirm the capex envelope, hurdle rate, and covenant limits; finalize project financial cases and dependency maps; and lock the quarter-by-quarter gate schedule. Define post-investment review owners and publish the decision log.