🧭 Overview / What This Guide Covers
Capex planning is the bridge between “ideas” and “approved investment.” This guide shows you how to build a decision-ready capital expenditure plan, complete with priorities, timing, and reporting, so leadership can fund growth without losing control of cash. For context on what CAPEX includes (and what it doesn’t), review the broader CAPEX guide first. You’ll learn how to define a capex strategy, gather inputs, rank initiatives, produce a board-friendly capex report, and run a monthly capex reporting cadence. The outcome is a plan that stays stable as assumptions change, and a workflow your team can repeat every quarter.
✅ Before You Begin
Before you kick off capital expenditure planning, make sure you have the inputs that prevent “plan churn.” You’ll need a strategic roadmap (what the business is trying to achieve), a pipeline of initiatives with rough cost ranges and timing, and clear funding constraints (cash, debt capacity, covenant headroom, or board limits). You also need a governance baseline: approval thresholds, required documentation, and who owns each stage (proposal, validation, approval, tracking).
To speed up alignment, start from a consistent planning pack-one that includes a prioritisation rubric, a cash timing view, and a standard output format for your capex report. You should also confirm how you’ll integrate CAPEX into the broader model: will you plan centrally and push updates into monthly forecasts, or will every business unit maintain its own version? Model Reef works best when your plan lives in one structured model so approvals, changes, and outputs stay consistent across stakeholders.
🛠️ Step-by-Step Implementation
🎯 Define your capex strategy and decision rules
Start capex planning by writing down the “why” and the rules of the game. Your capex strategy should translate company goals into investment themes-capacity, efficiency, compliance, customer experience, or risk reduction. Then define decision rules: minimum ROI threshold (where relevant), payback expectations, security/compliance requirements, and what gets funded automatically (e.g., critical replacements).
This step prevents a common failure mode: comparing projects that aren’t comparable. If every proposal is framed differently, leadership ends up deciding based on storytelling, not economics. Anchor proposals to the same structure: objective, scope, cost range, timing, risk, and dependencies. If revenue growth is a key driver, align CAPEX decisions to your revenue plan assumptions and capacity requirements so the plan supports growth rather than competing with it. Sales planning is often the upstream input that sets those assumptions.
🧱 Build the plan structure with driver-backed categories
Next, create the structure of your capital expenditure plan. Use 4–6 categories that leadership recognises (maintenance, growth, compliance, tech/platform, new locations, and “other”). Then decide what’s project-based versus driver-based. Project-based is for discrete initiatives with clear milestones; driver-based is for scalable spend linked to units, hires, sites, or volume.
This is where Model Reef can remove busywork: with driver-based modelling, you can connect CAPEX to the same operational drivers that feed your forecast, so the plan updates automatically when assumptions change. The goal is to avoid re-keying and reduce version chaos. Output-wise, ensure each category can roll up into a one-page summary for leadership while still preserving detail for finance review. Once this structure is set, the rest of capital expense planning becomes about prioritisation and timing, not reformatting spreadsheets.
🔍 Prioritise initiatives and lock a decision-ready list
Now rank initiatives. Use a scoring model that combines strategic alignment, financial impact, risk reduction, and urgency. Then run a “portfolio check” to ensure you aren’t funding only one theme (e.g., all growth and no maintenance). Good capex planning is portfolio planning.
At this stage, you’ll also set the timing: what must happen in the next 90 days, what can wait, and what is conditional on performance. Document dependencies (hiring, vendor lead times, permitting) so the plan doesn’t collapse when one item slips. For multi-entity groups, align category definitions and rollups before you publish outputs; otherwise, your plan becomes hard to compare across divisions. That’s where a consolidation mindset matters-even if you’re not doing full statutory consolidation, you need consistent aggregation logic across the group. The output of this step is an approved “shortlist” with timing and confidence levels.
🧾 Create your capex report and set capex reporting cadence
Turn the shortlist into a leadership-ready capex report. Keep it simple: a summary page (totals by category, timing, committed vs optional), followed by project cards for the top items. Then define your capex reporting cadence: Monthly is standard, with a deeper quarterly refresh.
Include three tracking views:
(1) approved budget vs forecast vs actuals, (2) timing shifts, and (3) decision log (what changed and why).
This is where most teams lose credibility-numbers move, but there’s no narrative trail. If you’re in retail or inventory-heavy industries, include operational triggers that affect CAPEX decisions (warehouse capacity, replenishment cadence, or store expansion assumptions). Demand planning often determines whether CAPEX is required now or later, so align your planning pack to those operational inputs. A disciplined reporting cadence makes your CAPEX plan a living tool rather than a once-a-year document.
🚦 Stress-test and communicate the plan like a portfolio
Finally, stress-test the plan. Run at least two downside scenarios: delayed revenue, higher costs, or tighter cash. Then define pre-agreed actions: what gets paused, what gets staged, and what remains non-negotiable. This prevents reactive cuts later and keeps the organisation aligned.
Communicate the plan in terms leaders care about: cash impact by month, trade-offs, and what the plan unlocks operationally. If CAPEX decisions affect inventory outcomes (for example, adding capacity or systems), ensure you’re not creating downstream excess stock or bottlenecks. CAPEX can solve problems, but it can also create overcapacity when assumptions are wrong. For fundraising or board contexts, frame the plan as an investable story: “here’s the portfolio, the controls, and how we’ll report progress.” That narrative discipline is what separates planning from spreadsheeting.
🧠 Tips, Edge Cases & Gotchas
A strong capex strategy includes explicit trade-offs. If you don’t define them, the organisation will usually resort to last-minute escalation. Build in “optionality” by tagging projects as committed, conditional, or opportunistic. That makes it easier to protect essentials (maintenance and compliance) while keeping growth moves flexible.
Watch for two common edge cases:
(1) multi-year projects that blow up annual plans, and (2) “hidden CAPEX” that shows up as software, implementation work, or equipment bundled into vendor contracts.
If you can’t see it clearly, you can’t plan it.
Also, be careful with decentralised planning. Business units move faster, but they often create inconsistent assumptions and duplicate spend. If you’re planning in Model Reef, keep category definitions and drivers standardised so a change in one assumption updates the whole capital expenditure plan without rewiring the model. Finally, if leadership asks for investor context, show how disciplined planning supports fundability-predictability, wins trust in board rooms and fundraising cycles.
🧾 Example / Quick Illustration
A simple worked example: a retail group builds a capital expenditure plan for the next 12 months. They allocate $400k to maintenance (store refits, replacement equipment), $600k to growth (two new locations), and $150k to systems (inventory + POS uplift). They tag each item as committed or conditional, then schedule spend by quarter based on vendor lead times and build schedules.
The capex report summary shows totals by category and a monthly cash impact chart, plus a short decision log (“new store #2 moved from Q2 to Q3 due to lease timing”). In the monthly capex reporting cadence, they review “budget vs forecast vs actual,” update timing, and escalate only material variances. This keeps leadership focused on decisions, not spreadsheet archaeology.
🚀 Next Steps
You now have a complete capex planning workflow: strategy → structure → prioritisation → capex report → capex reporting cadence. Your next move is operationalising it-setting a monthly rhythm, locking categories and drivers, and making changes traceable. If you’re using Model Reef, this is where a central driver-based model prevents version sprawl and keeps stakeholders aligned as assumptions shift.
Back