🧭 Overview / What This Guide Covers
In many finance teams, Capex is shorthand for a structured capital approval pack and operating rhythm-essentially, the documents and decisions that turn CAPEX requests into controlled outcomes. This guide walks you through a repeatable capex workflow: what to prepare, how to run a consistent capex review, how to document decisions, and how to keep reporting clean month to month. If you’re still clarifying what qualifies as CAPEX, start with the broader CAPEX meaning guide first. The outcome is faster approvals, fewer surprise overruns, and a clearer decision trail that leadership and boards can trust.
✅ Before You Begin
Before you run a CAPEX cycle, you need the basics in place: a CAPEX intake channel (where requests arrive), a standard request format (objective, cost, timing, owner), and governance rules (approval thresholds, escalation paths, meeting cadence). You’ll also want access to current budgets/forecasts, plus enough operational context to validate the request (capacity constraints, compliance drivers, or performance issues).
To avoid ad-hoc packs, start from a reusable Capex template that includes a one-page summary, project cards, and a decision log. The template matters because it makes your capex review comparable over time and prevents “different format every month” drift. If your organisation is early-stage, make sure the workflow is sized to your reality: founders and operators should be able to complete it in hours, not days. Model Reef is useful here because a shared model + standard outputs reduces manual stitching and keeps requests tied to drivers rather than opinions.
🛠️ Step-by-Step Implementation
🧱 Set the rules of your Capex intake and approval gates
Define what “good” looks like for a Capex submission. At minimum, require: problem statement, proposed solution, total cost, cash timing, owner, and impact (revenue, cost, risk, or compliance). Then set approval gates: what can be approved by a manager, what needs CFO review, and what goes to the board. The goal is to stop low-quality submissions from consuming executive time.
Also define what qualifies as CAPEX vs operating spend so people don’t misclassify purchases to “get approval faster.” Finally, decide cadence: monthly capex review is common, with urgent requests handled via a short exception path. If you’re a small team or a startup, this is even more important: lightweight governance prevents chaos as you scale. If you’re unsure how your company type affects governance design, the Small Business vs Startup guide can help you set expectations for process maturity.
🧾 Build a decision-ready Capex pack (not a data dump)
A strong Capex pack is designed for decisions, not documentation theatre. Start with a one-page dashboard: total requested, total approved, timing by month/quarter, and changes since last review. Then include project cards for each request with consistent fields: cost breakdown, vendor info, assumptions, dependencies, and risks.
Where teams slip is burying the decision in detail. Keep details accessible, but keep the front page simple. If you’re using Model Reef, pull the cash impact directly from your model, so the pack stays consistent with the forecast and updates automatically as assumptions shift. This is also where driver logic helps: when a request depends on growth (sites, hires, volume), you can tie it to operational drivers so leaders understand “if X happens, we need Y.” Driver-based modelling makes that linkage explicit and reduces subjective debate.
🔍 Run the capex review meeting with clear outcomes
Treat the capex review as an outcomes meeting: approve, reject, defer, or request revisions. Start by confirming total capacity (cash headroom, funding constraints), then review the top items first; materiality drives agenda order. For each item, ask three questions:
(1) Is the need real?
(2) Is the timing right?
(3) What would change our decision?
Capture those “decision triggers” in the decision log so you can revisit quickly next month.
If you have multiple entities or departments, standardise how requests roll up. Otherwise, the meeting becomes an argument about definitions instead of value. A consolidation mindset helps even outside formal reporting: align categories, owners, and rollups so the group view is consistent. The output of this step should be a clean approvals list, a deferred list with conditions, and a short set of follow-ups with owners and dates.
🧠 Validate requests with a “minimum viable plan” mindset
Not every request needs a 20-tab model. A practical Capex approach is to validate using a “minimum viable plan” mindset: what’s the simplest evidence that the spend is necessary and timed correctly? For example, for a systems request: what pain is it solving, what’s the operational impact, and what’s the downside risk of delaying? For growth spend: what is the lead indicator (pipeline, demand, utilisation) that justifies it now?
This is where teams sometimes borrow product thinking: define the minimum viable version of the project and scale only if the results validate. If you’re building this muscle, it can be helpful to understand how teams define minimum viable approaches in general planning and execution. The point isn’t to underinvest-it’s to invest with staged confidence. In a capex review, staged approvals often reduce risk while preserving momentum.
✅ Finalise approvals and operationalise the Capex decision trail
After the meeting, lock the outcomes. Update the approved spend schedule, notify owners, and record the decision log (what was approved, why, and under what conditions). Then set up a monthly tracking loop: budget vs actual, timing drift, and scope changes. This is where Capex becomes real: without tracking, approval is just paperwork.
If you run actuals through accounting systems like QuickBooks, make sure your tracking categories align so reporting doesn’t require manual remapping every month. Using a consistent budgeting workflow alongside QuickBooks reduces friction and keeps CAPEX governance tied to actual spend. Finally, maintain a single source of truth. In Model Reef, keeping the approvals list, forecast, and outputs in one place reduces version errors and makes stakeholder updates easier, especially when leadership asks “what changed since last month?”
🧠 Tips, Edge Cases & Gotchas
A few “gotchas” can derail a Capex cycle. First, watch for split purchases (one project broken into smaller invoices to avoid approval thresholds). Solve this with clear aggregation rules and a strict definition of “related spend.” Second, don’t let urgent requests become the default; create a narrow exception pathway, or you’ll train teams to bypass governance.
Third, handle multi-year projects carefully. Approving the full scope upfront can lock cash you don’t need yet, but approving only one stage can create delivery risk. A staged approval model usually works best: approve phase one, define triggers for phase two.
Finally, make your governance proportional to the business. Early-stage companies often need speed; larger organisations need auditability. If you’re still deciding what kind of operating cadence fits your organisation, it’s worth clarifying how you want to run the business long-term-your governance should match that ambition. A good capex workflow feels “lightweight but strict.”
🧾 Example / Quick Illustration
Worked example: a team runs a monthly capex review with three requests. Request A: $40k replacement equipment (maintenance), Request B: $120k new warehouse fit-out (growth), Request C: $25k security upgrade (compliance). In the Capex pack, each request includes timing, owner, and “decision trigger.”
In the meeting, A is approved immediately (critical replacement). C is approved with a timing condition (must be completed before the audit date). B is deferred pending demand confirmation and vendor lead times, with a trigger: “approve when utilisation stays above 85% for 6 consecutive weeks.” The decisions are recorded in the log, the forecast is updated, and owners receive follow-ups within 24 hours. Next month, the same format makes the review fast and comparable, without re-explaining the structure.
🚀 Next Steps
You now have a complete Capex workflow: intake rules → standard pack → capex review cadence → staged validation → tracked decisions. The next step is embedding it into your operating rhythm so approvals automatically update forecasts and reporting, rather than living in meeting notes. Model Reef can help by keeping drivers, approvals, and outputs in one controlled environment, so your team scales the process without scaling spreadsheet complexity.
Back