Turn capital budgeting outputs, sensitivity, and qualitative factors into a course of action.
A capital budgeting recommendation converts financial analysis into a course of action. The answer should not stop at NPV, IRR, payback, or a sensitivity table. It should state whether management should accept, reject, defer, revise, stage, or gather more evidence.
The Finance elective rewards recommendations that integrate metrics, assumptions, feasibility, risk, tax, strategy, and implementation. A project can be financially attractive but too risky, strategically necessary but under-supported, or promising enough to revise rather than reject.
Recommendation questions often provide a project summary and ask for a decision. Use the metrics as evidence, then decide what management should do next.
| Recommendation | When it fits |
|---|---|
| Accept | Metrics are favourable, assumptions are supportable, risks are manageable, and strategy fits. |
| Reject | Value is negative or risks and constraints outweigh benefits. |
| Defer | Critical information, approval, funding, or market evidence is missing. |
| Revise | Project is promising but scope, timing, financing, or risk controls need change. |
| Stage or pilot | Uncertainty is high but learning value supports a smaller commitment. |
| Replace alternative | Another option better fits value, risk, or strategic constraints. |
A recommendation should identify the margin of safety:
[ \text{Headroom} = \text{Base-case NPV} - \text{Downside-case NPV} ]
Headroom helps explain whether the project can absorb downside. If the base case is barely positive and a realistic downside case is negative, the recommendation should be cautious even when base-case NPV is above zero.
Sensitivity tables are decision tools. They show which assumptions deserve management attention before approval.
| Sensitivity finding | Recommendation implication |
|---|---|
| Sales volume has the largest effect on NPV. | Require stronger demand evidence, customer commitments, or staged launch. |
| Cost overrun turns NPV negative. | Require fixed-price contracts, contingency, or revised budget. |
| Delay materially reduces value. | Confirm permits, supplier timing, and implementation resources before approval. |
| Tax incentive is essential to positive NPV. | Confirm eligibility before committing capital. |
| Salvage value drives the conclusion. | Obtain valuation support or treat terminal value cautiously. |
| Project remains positive in downside case. | Proceeding may be supportable if strategic and financing constraints are acceptable. |
The key is to translate sensitivity into an action, not merely identify the sensitive variable.
Capital budgeting tools can point in different directions. The recommendation should explain which metric deserves more weight.
| Conflict | Stronger interpretation |
|---|---|
| Positive NPV but long payback. | Project may create value but strain liquidity; assess cash constraints. |
| High IRR but low NPV. | Project may be small; compare total value and capital allocation. |
| Short payback but negative NPV. | Quick recovery does not justify destroying value unless non-financial need is compelling. |
| Strategic fit but weak NPV. | Consider whether benefits are omitted, project should be revised, or strategic need justifies cost. |
| Positive base case but negative downside. | Recommend conditions, staging, or further evidence. |
| Best financial project conflicts with capacity. | Choose feasible option or revise implementation plan. |
Metrics are evidence, not the recommendation itself.
Deferral is appropriate when the project may be worthwhile but the decision cannot be supported yet.
| Missing evidence | Why deferral may be better |
|---|---|
| Market demand support | Sales forecast drives NPV but is unsupported. |
| Financing terms | Project cannot proceed without knowing cost, covenants, or availability. |
| Tax eligibility | Tax benefit is material and uncertain. |
| Regulatory approval | Timing and permission affect feasibility. |
| Supplier or technology proof | Implementation risk is too high for full commitment. |
| Asset valuation or salvage support | Terminal value materially affects the decision. |
| Capacity analysis | Labour, facility, or system constraints may prevent benefits. |
Deferral should be specific. State what evidence is needed and how it will change the decision.
A strong recommendation has four parts:
For example: “Approve the project only after customer commitments are obtained. The base-case NPV is positive, but the sensitivity analysis shows that a modest volume shortfall makes the project uneconomic. Management should secure contracted demand or stage the investment before committing to full capacity.”
This is stronger than writing only: “The NPV is positive, so accept.”
Capital budgeting recommendations should include implementation controls when the project proceeds.
| Control | Purpose |
|---|---|
| Approved budget and contingency | Controls cost overruns. |
| Milestone reporting | Tracks timing and completion risk. |
| Benefit realization tracking | Compares actual savings or revenue with assumptions. |
| Risk owner | Assigns responsibility for key uncertainty. |
| Change approval | Prevents scope creep from weakening economics. |
| Post-completion review | Improves future capital budgeting decisions. |
| Exit or stop-loss trigger | Limits losses if assumptions fail. |
Use this structure for recommendation cases:
| Pitfall | Correction |
|---|---|
| Equating positive NPV with unconditional approval. | Check assumptions, sensitivity, feasibility, funding, and strategy. |
| Ignoring what sensitivity analysis says to do. | Convert the sensitive variable into a condition or risk response. |
| Treating deferral as indecision. | Defer when specific missing evidence prevents a supportable decision. |
| Forgetting implementation controls. | Include budget, milestones, risk ownership, and post-completion review. |
| Failing to reconcile conflicting metrics. | Explain which metric matters most for the decision context. |