Feasibility and Options Appraisal

Introduction

Project initiation is not merely the moment at which an idea receives approval. It is the disciplined process of determining whether the proposed investment is technically possible, operationally workable, economically worthwhile, legally permissible, environmentally responsible, schedulable, and compatible with the sponsoring organisation. Feasibility analysis converts an attractive concept into an evidence-based decision.

Options appraisal complements feasibility analysis. Rather than asking only “Can this project be done?”, it asks “Which feasible alternative creates the greatest value, with acceptable risk and constraint?” The answer may be to proceed, redesign the proposal, defer it, select another option, or terminate it before substantial resources are committed.

At postgraduate level, feasibility should be understood as both an analytical and governance activity. Forecasts are uncertain, criteria may conflict, and apparently objective calculations reflect assumptions about risk, time, benefits, and organisational priorities. A high-quality appraisal therefore makes assumptions visible, tests their robustness, and records who is accountable for each judgement.

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Distinguish technical, operational, economic, legal, environmental, schedule, and organisational feasibility.
2. Structure and compare project alternatives using a weighted decision matrix.
3. Apply cost-benefit analysis, NPV, IRR, payback, sensitivity analysis, and scenario analysis.
4. Interpret quantitative results without ignoring qualitative, ethical, or strategic considerations.
5. Prepare a defensible recommendation for a project sponsor or investment committee.

Feasibility as a Decision System

Feasibility is multidimensional. A project can be technically feasible but commercially unattractive, financially attractive but legally prohibited, or operationally sound but impossible within the required deadline. The assessment should therefore examine interdependencies rather than treat each dimension as an isolated checklist.

Feasibility is not the same as certainty. A feasibility report is a forecast under stated assumptions. Its professional quality depends less on claiming precision than on showing the range of plausible outcomes and the consequences of being wrong.

Defining the Base Case and Alternatives

An appraisal begins with a clear problem statement and a “do nothing” or “do minimum” base case. The base case is not necessarily zero expenditure: it may include continuing operating costs, compliance expenditure, declining service quality, or the opportunity cost of not acting. Benefits and costs of each option should be measured incrementally against this base case.

Alternatives may include:

• internal development versus external procurement;
• purchase, lease, subscription, or partnership;
• phased implementation versus a single deployment;
• a high-capacity design versus a minimum viable capability;
• automation versus process improvement without new technology; and
• immediate implementation versus deferral.

A sound options set is neither artificially narrow nor indefinitely large. Options should be sufficiently different to represent meaningful strategic choices, but each should be described at a comparable level of maturity. Comparing a detailed design with a vague concept creates false precision.

A useful option description specifies scope, output, assumptions, implementation approach, ownership, resource requirements, timing, risks, dependencies, and expected benefits. Exclusions are equally important because unpriced scope is a common source of optimistic appraisal.

Technical and Operational Feasibility

Technical feasibility

Technical analysis addresses whether the proposed solution can meet functional, performance, security, reliability, interoperability, scalability, and maintainability requirements. It should consider the entire life cycle, not only initial construction. Questions include:

• Is the required technology mature enough for the intended use?
• Can existing systems exchange data reliably?
• Are infrastructure capacity, cybersecurity, resilience, and support arrangements adequate?
• Are specialist skills available internally or through suppliers?
• Can performance be demonstrated through a prototype, proof of concept, or reference implementation?

Technical readiness should be distinguished from technical possibility. A solution may be physically possible but immature, expensive to integrate, or dependent on a single supplier. Where uncertainty is high, staged investment and explicit technical exit criteria are preferable to unconditional approval.

Operational feasibility

Operational feasibility concerns the organisation’s ability to use the result effectively after delivery. It includes process fit, staffing, training, support, controls, user acceptance, service continuity, and benefits ownership. A system that works in a test environment may fail operationally if workflows, incentives, responsibilities, or customer behaviour are not changed.

Operational assessment should identify the transition state as well as the target state. Temporary dual running, productivity losses, service disruption, or additional support may create substantial costs that are invisible in a capital estimate. Benefits should have named owners, measures, baselines, and review dates.

Legal, Environmental, Schedule, and Organisational Feasibility

Legal and regulatory feasibility

Legal review should occur early enough to influence design. Relevant issues may include planning permission, intellectual property, licensing, procurement rules, employment law, health and safety, accessibility, competition law, records management, privacy, cybersecurity obligations, and sector-specific regulation. Contractual feasibility includes allocation of liability, service levels, warranties, termination rights, data ownership, change control, and supplier dependency.

A legal constraint is not always a reason to reject a project; it may require redesign, a licence, consultation, or a different contracting route. However, an appraisal should not treat regulatory approval as an unpriced assumption.

Environmental feasibility

Environmental appraisal should consider construction, operation, maintenance, disposal, and indirect effects. Relevant impacts include greenhouse-gas emissions, energy and water use, land, biodiversity, waste, pollution, and climate resilience. Where carbon is quantified, the boundary and measurement method must be stated. For example, an estimate may use:

where E is estimated emissions, usually in kg CO₂e; A is an activity measure such as litres of fuel or kWh of electricity; and EF is the corresponding emission factor in kg CO₂e per activity unit. The equation is applicable only when the activity boundary and emission factor are consistent. It does not by itself capture rebound effects, uncertainty, or avoided emissions.

Environmental feasibility also includes adaptation. A facility, digital service, or supply chain may be technically viable today but vulnerable to heat, flooding, water scarcity, or energy volatility during its operating life.

Schedule feasibility

Schedule feasibility asks whether the required benefits can be achieved by the necessary date with realistic resources and dependencies. The critical path method identifies the longest-duration path through a network of activities. If activity durations are deterministic, the earliest finish of an activity is calculated as:

where EF is earliest finish, ES is earliest start, and d is activity duration, all in the same time unit. For an activity with predecessors, ES is the maximum earliest finish of those predecessors. The critical path is the path with the greatest total duration and normally has zero total float. This calculation assumes defined dependencies, stable calendars, and no unmodelled resource constraints.

A deadline may be feasible in a network model but infeasible when scarce specialists, procurement lead times, approvals, or learning effects are considered. Schedule compression through crashing or fast-tracking should therefore include additional cost and risk.

Organisational feasibility

Organisational feasibility examines sponsorship, governance, decision rights, culture, capability, capacity, and change readiness. A project may compete with other initiatives for the same experts or operational attention. It may also redistribute power, accountability, or resources, creating resistance that a purely technical appraisal misses.

Useful evidence includes a stakeholder map, responsibility assignment matrix, capability assessment, change-impact analysis, and an implementation governance model. Senior sponsorship is necessary but insufficient: operational managers must own adoption and benefits, while project governance must provide escalation and independent challenge.

Weighted Decision Matrices

A weighted decision matrix is appropriate when options must be compared across criteria that include both quantitative and qualitative judgements. First define criteria and weights, ensuring that weights sum to 1 or 100%. Then score each option against every criterion using a documented scale. The weighted score is:

where S_j is the total score for option j, w_i is the weight of criterion i, and r_ij is option j’s rating on criterion i. Ratings must use a common scale, such as 1–5, and higher values must consistently mean better performance. If weights are percentages, divide the resulting total by 100 or use ratings on a compatible scale.

Example: suppose three options are rated from 1 to 5 against strategic fit (weight 0.30), value for money (0.30), delivery confidence (0.20), and sustainability (0.20).

For option C, the score is (0.30×3)+(0.30×5)+(0.20×5)+(0.20×2)=3.90. Option C ranks first, but the result is not an automatic decision. If a rating of 2 on delivery confidence represents an unacceptable safety or compliance risk, a minimum threshold may eliminate the option regardless of its aggregate score.

The method is vulnerable to subjective scoring, double-counting, compensatory effects, and false numerical precision. Good practice includes independent scoring, evidence for ratings, sensitivity testing of weights, explicit non-negotiable criteria, and a record of disagreement.

Economic and Financial Appraisal

Cost-benefit analysis

Cost-benefit analysis compares incremental costs and benefits over an agreed appraisal period. Costs may include capital, implementation, training, transition, operating, maintenance, risk allowances, decommissioning, and external impacts. Benefits may include revenue, avoided cost, productivity, quality, risk reduction, compliance, and social or environmental value.

Avoided costs should be included only when the project genuinely changes the cost. Transfer payments, such as taxes or internal charges, may require special treatment depending on the decision perspective. Costs and benefits should be assigned to the periods in which they occur, and nominal cash flows should be discounted using a rate consistent with their inflation basis.

Net present value

The net present value method expresses future net cash flows in present-value terms:

where CF_t is the incremental net cash flow in period t, r is the discount rate per period, and n is the final period. CF₀ commonly represents the initial investment and is usually negative. NPV is measured in currency units. It assumes cash-flow estimates and the discount rate are defined consistently; a nominal discount rate should be applied to nominal cash flows, and a real rate to real cash flows.

If NPV is positive relative to the chosen base case, the project is expected to create value at that discount rate, subject to risk and non-financial constraints. NPV is generally more theoretically consistent than payback because it recognises the timing and scale of all included cash flows.

Worked example. An option requires an initial investment of £100,000 and produces net cash inflows of £45,000, £50,000, and £40,000 in years 1, 2, and 3. At a discount rate of 10%:

The positive NPV indicates an expected value surplus of approximately £12,284 relative to the base case and discount rate. It does not mean that £12,284 will certainly be realised.

Internal rate of return

The internal rate of return is the discount rate that makes NPV equal to zero:

IRR is useful for communicating a percentage return, but it has limitations. Non-conventional cash flows with more than one sign change can produce multiple IRRs or no meaningful IRR. IRR also assumes reinvestment at the IRR and can rank mutually exclusive projects differently from NPV. For value maximisation, NPV should normally take precedence when the two measures conflict.

Payback period

The payback period is the time required for cumulative cash inflows to recover the initial investment. If annual cash inflows are equal, the simple payback is:

This special case is not valid when inflows vary. In the worked example, cumulative inflows are £45,000 after year 1 and £95,000 after year 2. The remaining £5,000 is recovered during year 3, whose inflow is £40,000:

Simple payback ignores discounting and cash flows after recovery. Discounted payback instead uses discounted cash flows and is more informative about the time needed to recover value in present terms.

Risk, Sensitivity, and Scenario Analysis

Sensitivity analysis

Sensitivity analysis changes one assumption at a time while holding others constant. It identifies value drivers such as demand, price, capital cost, operating cost, schedule, or discount rate. A useful output is the break-even value—the input at which NPV becomes zero. One-at-a-time analysis is easy to communicate but may understate combined uncertainty because real variables often move together.

For example, if the project’s NPV falls from £12,284 to negative £8,000 when demand is 20% below forecast, demand is a material driver. Management may respond through staged capacity, contractual commitments, pilot testing, or a revised business model.

Scenario analysis

Scenario analysis changes several linked assumptions coherently. A plausible set might include optimistic, base, and adverse scenarios, each specifying demand, cost, timing, inflation, and regulatory conditions. Scenarios are not forecasts of precise probabilities unless probabilities are explicitly assigned. They are structured narratives that test strategic resilience.

If discrete scenarios have probabilities, expected NPV can be calculated as:

where p_s is the probability of scenario s, and the probabilities sum to 1. Expected value does not describe the dispersion or downside exposure; decision-makers should also examine the range, worst credible case, and risk appetite.

Monte Carlo simulation may extend this analysis by assigning probability distributions to uncertain inputs and repeatedly sampling them. It is useful only when distributions, correlations, and model structure are defensible. Simulation can produce sophisticated-looking but misleading outputs when assumptions are weak.

Integrating the Appraisal into Governance

The appraisal should culminate in a decision proposition, not merely a spreadsheet. A professional recommendation states:

• the preferred option and the rejected alternatives;
• the problem and base case;
• key assumptions and evidence quality;
• expected costs, benefits, NPV, payback, and risk range;
• legal, environmental, technical, and operational conditions;
• dependencies, decision gates, and tolerance limits; and
• conditions under which the recommendation should be revisited.

A stage-gate approach can link approval to evidence. For example, a concept gate may require strategic fit; a feasibility gate may require validated demand and technical proof; an investment gate may require an approved business case; and a delivery gate may require contracts, resources, and readiness plans. Gates should not become bureaucratic ceremonies: their purpose is to stop, redirect, or condition investment when evidence does not support continuation.

Illustrative Case: Regional Health Information Exchange

Background

A fictional regional health authority is considering a shared information exchange connecting hospitals, primary-care practices, and emergency services. The objective is to reduce duplicated tests, improve medication information, and support faster clinical decisions.

Problem and options

The authority defines a five-year base case in which existing systems remain, interfaces are maintained, and duplication continues. It identifies three options:

• Option A: build an internally managed exchange;
• Option B: procure a cloud-based platform with implementation support; and
• Option C: create a limited pilot linking emergency services and two hospitals before wider deployment.

Analysis

Technical assessment finds that A provides control but requires scarce integration specialists. B has greater vendor dependency but mature interfaces and stronger initial support. C has the lowest technical exposure because scope is constrained, although it may require later redesign.

Operational interviews reveal that clinicians will adopt the exchange only if data quality, response time, and workflow integration are acceptable. The pilot therefore includes usability testing, data-quality thresholds, and named clinical benefit owners.

Legal review identifies health-data privacy, information governance, retention, access control, and supplier-contract requirements. Environmental effects are modest relative to a physical infrastructure project, but data-centre energy use and equipment disposal are included in the life-cycle assessment. Schedule analysis shows that a region-wide launch before the next winter-demand period is unrealistic; a staged pilot is feasible.

The economic model estimates Option B’s initial cost at £2.4 million, with annual net benefits of £0.9 million, £1.2 million, £1.4 million, and £1.4 million in years 1–4, and a residual cost of £0.2 million in year 5 for renewal and transition. At an 8% discount rate, the authority calculates a positive NPV relative to the base case. However, sensitivity analysis shows that benefits fall below the investment threshold if fewer than 60% of participating clinicians use the system. The preferred recommendation is therefore Option C followed by a conditional decision on B, with adoption and data-quality gates.

Outcome and learning points

The case demonstrates that the highest nominal benefit is not automatically the best immediate choice. A staged option can purchase information, reduce irreversibility, and test adoption before full commitment. The recommendation links financial approval to technical, legal, operational, and behavioural evidence. It also makes the main uncertainty—actual use and benefit realisation—visible to governance.

Challenges, Ethics, and Contemporary Practice

The most persistent appraisal problem is optimism bias: sponsors may underestimate cost and duration while overestimating benefits. Other problems include strategic misrepresentation, sunk-cost reasoning, selective evidence, discount-rate disagreement, and treating intangible benefits as either worthless or arbitrarily monetised.

Ethically, appraisal should consider distributional effects. A project may generate aggregate benefits while disadvantaging particular communities, workers, or users with disabilities. Data-intensive projects require proportionality, privacy protection, explainability, and meaningful human accountability. Environmental claims should avoid double counting and unsupported “green” assertions.

Artificial intelligence can support demand forecasting, option generation, risk identification, and scenario modelling, but it does not remove accountability. AI-generated estimates require traceable data, bias testing, validation against expert evidence, protection of confidential information, and human review. A model should not be treated as an independent source of truth merely because it produces precise numbers.

Best practice is to use a transparent assumptions register, independent challenge, reference-class evidence where available, explicit contingency, benefits ownership, sensitivity and scenario testing, and post-investment review. The post-project review should compare forecast and actual costs, schedule, adoption, benefits, and environmental outcomes. This creates organisational learning and improves future appraisals.

Chapter Summary

Feasibility and options appraisal provide the evidence bridge between a project idea and an authorised investment. Feasibility must cover technical, operational, economic, legal, environmental, schedule, and organisational dimensions because weakness in any one can invalidate the proposal. Options should be compared against a clearly defined base case and described at comparable levels of maturity.

Weighted decision matrices integrate diverse criteria but require documented ratings, non-negotiable thresholds, and sensitivity testing. Cost-benefit analysis should use incremental, life-cycle costs and benefits. NPV recognises timing and scale; IRR offers a percentage return but can mislead with unconventional cash flows; payback is simple but ignores later benefits and, unless discounted, the time value of money. Sensitivity analysis identifies key drivers, while scenario analysis examines coherent combinations of uncertainty.

A credible recommendation combines quantitative evidence with legal, environmental, operational, ethical, and strategic judgement. Staged investment, decision gates, independent challenge, and benefits ownership help manage uncertainty. The ultimate purpose of appraisal is not to predict the future perfectly, but to make assumptions explicit, improve the quality of commitment, and preserve the ability to stop or adapt when evidence changes.

Key Terms

Feasibility: The extent to which a proposed project can be delivered and sustained within relevant constraints.

Options appraisal: Structured comparison of alternative ways to address a problem or realise an opportunity.

Base case: The expected future condition against which an option’s incremental effects are measured.

Incremental cash flow: The additional cash flow caused by choosing an option rather than the base case.

Technical feasibility: Assessment of whether the required solution can be designed, integrated, operated, and maintained.

Operational feasibility: Assessment of whether users, processes, resources, and controls can absorb and sustain the outcome.

Legal feasibility: Assessment of compliance with law, regulation, licences, contracts, and rights.

Environmental feasibility: Assessment of environmental impacts, mitigation, and resilience over the life cycle.

Schedule feasibility: Assessment of whether required outcomes can be delivered by the required date.

Organisational feasibility: Assessment of governance, capability, capacity, culture, and change readiness.

Weighted decision matrix: A structured method that multiplies criterion weights by option ratings and sums the results.

Cost-benefit analysis: Comparison of relevant costs and benefits over a defined appraisal period.

Net present value: The present value of incremental future cash flows less the initial investment.

Internal rate of return: The discount rate that makes a project’s NPV equal to zero.

Payback period: Time required for cumulative cash inflows to recover the initial investment.

Sensitivity analysis: Analysis that changes one assumption to examine its effect on an outcome.

Scenario analysis: Analysis of several linked assumptions representing plausible future conditions.

Optimism bias: Systematic tendency to underestimate costs or duration and overestimate benefits.

Decision gate: A formal point at which continuation, redesign, deferral, or termination is decided.

Benefits owner: The person accountable for realising and measuring an intended project benefit.

Review Questions

Short Answer Questions

1. Why should a “do nothing” or “do minimum” base case be defined before comparing options?
2. Distinguish technical feasibility from operational feasibility.
3. State two limitations of a weighted decision matrix.
4. What does a positive NPV indicate under the stated assumptions?
5. How does sensitivity analysis differ from scenario analysis?

Long Answer Questions

1. Explain how legal, environmental, schedule, and organisational feasibility can alter an apparently attractive investment proposal.
2. Discuss the relative strengths and limitations of NPV, IRR, and payback period in project selection.
3. Design a weighted decision matrix for selecting between internal development, procurement, and a phased pilot.
4. Explain how optimism bias and strategic misrepresentation can affect a business case, and propose controls.
5. Discuss how stage gates and benefits ownership improve governance after project approval.

Analytical / Application Questions

1. A project requires £250,000 initially and produces net cash inflows of £90,000, £100,000, and £110,000 in years 1–3. Calculate the simple payback period and NPV at 10%, and interpret both results.
2. An option has a positive base-case NPV but becomes negative when demand falls by 15% and implementation is delayed by six months. Design a sensitivity and scenario analysis that would help the sponsor decide whether to proceed.
3. Using the regional health information exchange case, recommend decision-gate conditions for moving from the pilot to full deployment. Justify the conditions using technical, operational, legal, economic, and organisational evidence.

Multiple Choice Questions with Answers

Question 1

Which statement best describes the purpose of a project base case?

A. It represents the most optimistic possible project outcome.

B. It provides the future reference condition against which incremental effects are measured.

C. It excludes all continuing operating costs.

D. It is the same as the preferred project option.

Correct Answer: B. It provides the future reference condition against which incremental effects are measured.

Question 2

In a weighted decision matrix, what does a criterion weight represent?

A. The monetary cost of the criterion

B. The probability that the option will fail

C. The relative importance assigned to the criterion

D. The number of suppliers available

Correct Answer: C. The relative importance assigned to the criterion

Question 3

An investment has an initial cost of £100,000 and equal annual cash inflows of £25,000. What is its simple payback period?

A. 2 years

B. 3 years

C. 4 years

D. 5 years

Correct Answer: C. 4 years

Question 4

What does a positive NPV generally indicate, assuming the cash flows and discount rate are consistently defined?

A. The project will have no risk.

B. The project is expected to create value relative to the base case at the selected discount rate.

C. The project has the shortest payback period.

D. The project has no operating costs.

Correct Answer: B. The project is expected to create value relative to the base case at the selected discount rate.

Question 5

Which limitation is particularly associated with IRR?

A. It cannot express a percentage return.

B. It ignores the timing of cash flows.

C. Non-conventional cash flows may produce multiple IRRs.

D. It always ranks projects identically to NPV.

Correct Answer: C. Non-conventional cash flows may produce multiple IRRs.

Question 6

Which activity belongs most directly to operational feasibility?

A. Testing whether users can adopt the new workflow and receive adequate training

B. Calculating the legal tax rate

C. Selecting the discount rate only

D. Determining the organisation’s share price

Correct Answer: A. Testing whether users can adopt the new workflow and receive adequate training

Question 7

What is the defining feature of one-at-a-time sensitivity analysis?

A. It changes several assumptions simultaneously.

B. It changes one assumption while holding other assumptions constant.

C. It assigns equal probabilities to all outcomes.

D. It eliminates uncertainty from the model.

Correct Answer: B. It changes one assumption while holding other assumptions constant.

Question 8

A critical path in a project network is normally the path that has:

A. The lowest cost

B. The fewest activities

C. The greatest total duration

D. The most skilled resources

Correct Answer: C. The greatest total duration

Question 9

Which is an appropriate governance response when a project’s benefits depend on uncertain user adoption?

A. Ignore adoption because technical delivery is sufficient.

B. Use adoption thresholds and a decision gate before full deployment.

C. Remove all operating costs from the business case.

D. Approve the project solely because its IRR is positive.

Correct Answer: B. Use adoption thresholds and a decision gate before full deployment.

Question 10

Why should nominal cash flows and a nominal discount rate generally be used together?

A. To ensure consistency in the treatment of inflation.

B. To guarantee a positive NPV.

C. To remove all project risk.

D. To make payback equal to IRR.

Correct Answer: A. To ensure consistency in the treatment of inflation.