Capital Expenditure Request Form: Build a Review-Ready CAPEX Case

A capital expenditure request form gives reviewers one controlled case for deciding whether an investment should proceed. It connects the operational need to alternatives, whole-life cost, expected benefit, risk, funding, authority and a plan for checking results after implementation.

The form is not approval by itself, and calling an item “CAPEX” does not determine its accounting treatment. Apply the organization’s current accounting policy, procurement rules and delegation of authority. Qualified finance, technical, legal, safety, security and operational reviewers should make the judgments relevant to the proposed asset.

Define the request and decision required

State the problem or opportunity in observable terms. Identify the requesting function, sponsor, asset or project, location, affected process and latest useful decision date. Explain what happens if no investment is made, without exaggerating urgency.

Define the exact authorization requested: permission to investigate, issue a tender, reserve budget, commit funds or execute a contract. These are different decisions and may have different authorities. Record whether the request is standalone or part of a larger program so spend is not split into smaller approvals.

Name the form owner, business sponsor and finance reviewer. Assign a version number and evidence cutoff. Reviewers should know which case they are approving and which assumptions remain provisional.

Copy this capital expenditure request form

CAPITAL EXPENDITURE REQUEST

Request ID / version / date:
Requestor / sponsor / business owner:
Asset or project / site / department:
Decision requested / required-by date:
Budget reference / funding source:

NEED AND SCOPE
Problem or opportunity:
Current condition / evidence:
Proposed scope / exclusions:
Do-nothing consequence:

OPTIONS
Option / description / feasibility:
Initial cost / recurring cost / disposal cost:
Benefits / risks / dependencies:
Recommended option and rationale:

FINANCIAL AND DELIVERY CASE
Cost basis / supplier evidence / contingency:
Expected cash-flow timing:
Benefit assumptions / timing / owner:
Approved evaluation method / result:
Implementation milestones / acceptance criteria:

REVIEWS AND AUTHORIZATION
Finance / accounting review:
Procurement review:
Technical / operations review:
Safety / security / privacy / legal review as applicable:
Approver / authority basis / decision / date:

POST-INVESTMENT REVIEW
Measures / baseline / target or expected range:
Benefit owner / review date:
Variance and lessons log:

Tailor the fields to the asset class and local policies. A low-cost standard replacement may need fewer details than a novel, safety-critical or strategically significant investment, but it still needs an attributable decision.

Describe the need with controlled evidence

Use maintenance records, capacity data, quality results, customer requirements, lease conditions or other approved sources to demonstrate the need. Separate current facts from forecasts and stakeholder opinions. If data is incomplete, state the limitation and the check required.

Define the baseline clearly: current output, downtime, operating cost, risk exposure or service level. A weak baseline makes later benefit claims difficult to test. Avoid inventing a quantified loss when only a qualitative concern is supported.

For equipment condition, an equipment inspection checklist can provide structured observations, while a maintenance work order template can show recurring repairs and responsible follow-up. Technical specialists must interpret those records.

Compare realistic alternatives

Include a do-nothing or maintain-current-state option, repair or life-extension options where feasible, rental or service alternatives, and relevant purchase configurations. Do not create a weak comparison solely to make the preferred option look stronger.

For each option, show scope, timing, constraints, initial and recurring costs, operational effect, risks and dependencies. Explain why an option was rejected. Where supplier claims are used, label them and verify critical performance requirements through the appropriate review or testing process.

Use comparable boundaries. One option should not exclude installation, training or disposal costs while another includes them. If estimates have different confidence levels, state that difference.

Build a whole-life cost estimate

Capture purchase price, design, delivery, duties, installation, site preparation, integration, validation, training, spares, software, financing, maintenance, energy and end-of-life costs where relevant. The applicable categories depend on the investment; avoid including irrelevant lines merely to fill the form.

State the source and date for every material estimate. Distinguish quotations, internal estimates, contractual rates and allowances. Show contingency separately with its basis rather than hiding it across line items. Finance should review tax and accounting treatment under approved policy.

The request should show expected payment timing as well as total cost. A project can fit an annual budget yet create a near-term liquidity issue. Record foreign-exchange assumptions and responsibility for changes where cross-currency spend is involved.

Quantify benefits without false certainty

Connect each benefit to an operational driver, baseline, calculation, timing and accountable owner. Distinguish cost avoidance, cash savings, additional contribution, capacity, quality, safety, resilience and compliance-related benefits. Do not add unlike benefits into one total without explaining the method.

Apply the organization’s approved financial evaluation methods. Discount rates, hurdle rates, useful lives and residual values should come from authorized finance policy, not from the requestor’s preferred outcome. Show sensitivity to material assumptions and separate non-cash accounting effects from cash flows.

Use the budget variance report template after approval to compare authorized cost and timing with actual delivery. Variance review should not retroactively rewrite the original business case.

Assess risk, dependencies and controls

Cover delivery, supplier, technical, integration, cybersecurity, privacy, safety, environmental, operational and change risks as applicable. State the risk owner, existing control, required treatment and residual decision. Specialists should assess domains requiring professional competence.

Identify dependencies such as permits, utilities, shutdown windows, data migration, staffing, training, customer approval or landlord consent. A promised implementation date is not credible if a critical dependency has no owner or confirmed lead time.

If a project modifies critical equipment or operations, route it through the organization’s formal change and safety processes. The request form can coordinate evidence, but it must not replace required assessments or authorizations.

Define procurement and supplier review

State the planned sourcing route and why it fits policy. Preserve competition, quotation, exception and conflict checks required by the organization. Do not select a supplier through the investment form before the authorized procurement process is complete.

Use a vendor due diligence checklist to coordinate financial, security, operational and compliance evidence where appropriate. Due diligence scope should reflect risk and policy; completion of a generic checklist is not proof that a vendor is suitable.

Record commercial assumptions, warranty, service support, acceptance terms and ownership of data or intellectual property where relevant. Legal and procurement specialists should review contractual commitments before signature.

Set approval and change-control rules

Route approval according to total commitment, risk, asset class and current delegation rules. Include connected contracts and foreseeable phases when determining authority. The sponsor’s seniority does not replace the required approval path.

Each approval should identify the form version, amount, scope, conditions and date. Silence, attendance or meeting minutes should not be treated as approval unless policy explicitly establishes that effect. Use a decision log to preserve rationale and conditions alongside the formal approval record.

Define when cost, scope, timing or benefit changes require reapproval. Set escalation triggers before work begins. Emergency routes should remain limited to circumstances and authorities recognized by policy.

Plan implementation and acceptance

List major milestones, responsible owners, readiness checks and acceptance criteria. Acceptance should cover the approved functional, quality, safety, security and documentation requirements that apply. Payment milestones should align with verified contractual deliverables where possible.

Do not treat installation as successful merely because equipment arrived. Commissioning, training, data migration, testing and handover may still be incomplete. An equipment commissioning checklist can structure readiness, test evidence, defects and authorization to operate.

Record how operations will continue during delivery and who can stop work if conditions become unsafe or outside approved scope.

Check portfolio capacity and connected commitments

Review the request alongside other approved and proposed investments. Confirm that funding, specialist staff, shutdown windows, site access, technology resources and management attention are available when needed. An attractive standalone case can still be impractical if several projects depend on the same scarce team or operational window.

Identify connected commitments that may sit outside the purchase order: leases, software subscriptions, service agreements, minimum volumes, internal labor, facility changes and future replacement obligations. Show which costs are included in the authorization and which require separate approval. Do not divide a foreseeable program into phases merely to fit a lower threshold.

Where prioritization is required, apply the organization’s approved criteria consistently. Compare strategic need, risk, mandatory timing, return, readiness and resource constraints without presenting a mechanical score as the final judgment. Record deferrals and their consequences, owners and review dates so an unapproved proposal does not quietly become an operational assumption.

Review the case and capture decisions responsibly

Distribute the controlled request and evidence index before the review. Focus discussion on assumptions, alternatives, total commitment, risks, conditions and decision rights. Capture disagreements and unresolved items without converting tentative comments into approvals.

Investment discussions may contain pricing, employee, security or strategic information. Apply participant notice, access control and retention rules to any recording or transcript.

For an authorized CAPEX review with clear participant notice, Kuno can help create draft notes and follow-up actions for verification. It does not validate the business case, select suppliers or grant approval. Explore Kuno

Complete post-investment review

At approval, set review dates, measures, baselines and benefit owners. After implementation, compare actual cost, timing, performance and risk with the authorized case. Explain variances and record corrective actions without changing the original baseline.

Confirm that assets, contracts, manuals, warranties, access rights and disposal obligations are recorded in the appropriate systems. Close residual defects only with evidence and authorized acceptance.

Keep investment discussions connected to accountable follow-through. Kuno supports authorized meeting capture and draft action notes, while qualified owners remain responsible for evidence, technical judgment and approval. See Kuno

FAQ