A feasibility study supports an investment decision before detailed design, procurement or construction creates momentum that is difficult to reverse. Its purpose is not to prove that an initial idea is correct. It is to test whether a defined project is practical, worthwhile and ready for the next decision.
The appropriate depth depends on the scale, complexity and uncertainty of the project. However, a decision-ready study should address the following areas in a connected way.
Define the need and the intended outcome
The study should explain the problem or opportunity in terms that can be tested. It should identify who is affected, what the current condition is and what a successful intervention would change.
This prevents the project concept from being confused with the underlying need. If the proposed solution becomes unworkable, the team can still examine other ways to achieve the intended outcome.
Establish scope and boundaries
Ambiguous boundaries make cost, schedule and risk estimates unreliable. Define what the project includes, what it excludes, which interfaces must be managed and which assumptions still require confirmation.
For an infrastructure project, this may include site boundaries, utilities, access, approvals and connections to existing assets. For a technology project, it may include user groups, integrations, data migration, hosting and operational support.
Compare realistic options
A study is stronger when it compares more than one credible option, including the consequences of doing nothing or deferring the work. Each option should be considered against the same evaluation criteria.
Criteria may include outcome fit, technical practicality, whole-life cost, delivery time, risk, environmental considerations, maintainability and organizational capacity. The preferred option should be traceable to this comparison rather than presented as a predetermined conclusion.
Test technical feasibility
Technical feasibility asks whether the option can perform within its actual environment. It may require surveys, preliminary calculations, system assessments, capacity checks, concept designs or prototype tests.
Identify the standards, operating conditions and performance requirements that apply. Record important gaps as planned investigations, not hidden assumptions. Where an estimate depends on a condition that has not been verified, show the sensitivity of the conclusion to that condition.
Examine commercial and financial assumptions
Cost estimates should state their basis, included items, exclusions, contingency and expected accuracy at the current stage. They should consider acquisition and implementation as well as operation, maintenance, renewal and decommissioning where relevant.
Benefits also need a clear basis. Separate measurable financial benefits from strategic or service benefits, and avoid presenting uncertain benefits as guaranteed savings. Scenario or sensitivity analysis can show which assumptions have the greatest effect on viability.
Identify approvals, stakeholders and constraints
List the regulatory, environmental, land, contractual, safety, security or data obligations that could shape the project. Identify stakeholders whose needs or decisions affect feasibility, including operators and maintainers who will inherit the result.
An option can be technically possible but impractical if approvals, access, resources or operating changes are not achievable in the required timeframe.
Build an initial delivery strategy
The study should outline how the project could move forward. This includes major work packages, dependencies, procurement considerations, indicative milestones, governance, required capabilities and the transition into operation.
The schedule should show the logic behind the dates. A single completion date without approval, design, procurement and commissioning dependencies gives decision-makers little basis for confidence.
Present risk and uncertainty honestly
Create an initial risk register with causes, consequences, current controls, possible responses and ownership. Distinguish risks that can be managed during delivery from uncertainties that must be resolved before approval.
The conclusion should state the confidence level of important estimates and recommend specific next actions. These may include further investigation, a pilot, revised scope, engagement with an authority or a decision to pause.
A decision-ready conclusion
A clear feasibility conclusion should tell decision-makers:
- whether the need is sufficiently defined;
- which option is preferred and why;
- what cost, time and benefit ranges are credible;
- which conditions must be met;
- which uncertainties remain material; and
- what decision or work should happen next.
The value of a feasibility study is not the volume of its report. It is the clarity it creates before the organization accepts larger cost, risk and delivery obligations.
Editorial review: Reviewed by AFAQ Editorial Team. Last reviewed September 23, 2026.
