Key Takeaways
- Define the project’s goals, scope, users, and expected outcomes.
- Assess real market demand and competition before investing.
- Build a financial model covering costs, funding, revenue, and risks.
- Review economic, community, environmental, and operational impacts.
- Test different scenarios to understand possible risks and delays.
- Use clear evidence to decide whether to proceed, pause, redesign, or stop.
A major project can look compelling long before it is ready to build. Whether the proposal involves real estate, infrastructure, manufacturing, energy, transportation, or community development, feasibility work tests whether the idea can deliver a useful result within realistic limits of cost, time, demand, and risk. A disciplined review gives sponsors and decision-makers a clearer basis for action. Teams that need support interpreting data, defining assumptions, or presenting a decision-ready case may work with Stratford Analytics while keeping the central question in view: Can this project succeed under conditions that are likely to occur?
Why Feasibility Matters Before Approval
Feasibility is not a search for reasons to approve a preferred concept. It is an early test designed to expose weak demand, incomplete funding, delivery barriers, and risks that could change the outcome. An appealing idea may still be impractical if it cannot secure permits, attract users, control operating costs, or withstand delays. A feasibility study assesses whether a project appears workable. A business case explains why a selected option deserves investment. A final investment decision comes later, after the responsible parties have reviewed evidence, commitments, and remaining uncertainty. Keeping these stages separate prevents preliminary estimates from being treated as promises.
Define The Project Before Testing It
Research is only useful when the project itself is specific. Start with a one-page brief that names the problem, proposed solution, location, target users, estimated schedule, owner, and measures of success. It should answer five basic questions:
- What problem will the project solve?
- Who will use, pay for, fund, or benefit from it?
- What will be built, changed, or delivered?
- Where will the work and operations occur?
- What should be visibly different after one, five, or ten years?
A clear scope also creates useful boundaries. If a project includes several components, such as site preparation, a new facility, utility upgrades, and workforce development, define which costs and outcomes belong to each component before combining them into one case.
Measure Real Market Demand
Demand should be supported by evidence rather than enthusiasm. Review relevant population, employment, household income, industry, and location trends. Compare the proposed offering with existing supply, competing projects, vacant capacity, and clearly documented unmet needs. The market research and competitive analysis guidance from the U.S. Small Business Administration reflects the same basic principle: customer behavior and market conditions should inform a plan before capital is committed.
Look For Commitment, Not Just Interest
Surveys and interviews can help, but stated interest is not the same as willingness to pay. Where appropriate, seek stronger evidence such as pre-sales, waitlists, letters of intent, reservations, leases, supply agreements, or signed contracts. Also test whether demand is seasonal, location-specific, or tied to a short-lived trend. A practical stress test is simple: if demand falls by 10% or 20%, does the project still cover its obligations and meet its purpose? If the answer is no, the scale, timing, price, or funding structure may need to change.
Build A Clear Financial Case
A sound financial model captures the full lifecycle, not just the opening budget. Include land or site costs, design, permitting, construction, equipment, financing, staffing, utilities, insurance, maintenance, replacements, and cash reserves. Then identify every expected source of revenue or support, including sales, user fees, leases, grants, tax support, debt, and equity. Show assumptions in plain language. Decision-makers should be able to distinguish quoted costs from estimates, recurring revenue from one-time funding, and committed financing from anticipated financing. Identify the break-even point, expected cash needs, and the period in which revenue is expected to begin.
Estimate Wider Economic Value
Financial viability answers whether the project can pay for itself or sustain its funding plan. Wider economic value answers how the project may affect users, businesses, public services, and the surrounding area. Possible effects include construction employment, long-term jobs, supplier activity, household spending, travel conditions, land use, tax receipts, and demand for utilities or public services. Separate direct effects from indirect and induced effects. This avoids counting the same activity more than once and makes claims easier to review. For public projects, a systematic process for comparing expected benefits and costs can help distinguish financial impacts from broader public value.
Review Risks, Constraints, And Delays
Create a risk register before approval. For each issue, record its likelihood, likely financial effect, timing, owner, and response. Common categories include market risk, cost escalation, financing changes, permitting, utility connections, supply shortages, legal disputes, labor availability, climate exposure, and community opposition. Schedule risk deserves special attention because a delay can increase carrying costs, delay revenue, and alter the market conditions that supported the original plan. Resilience planning should also consider whether heat, flooding, drought, storms, wildfire, or service interruptions could affect construction or long-term operations.
Include Community And Stakeholder Input
Engagement should begin before a formal hearing. Identify affected residents, workers, nearby businesses, agencies, landowners, service providers, and potential users. Share understandable information about expected jobs, traffic, costs, environmental issues, construction disruption, and public funding. Document what people raise and explain which changes were made in response. Community input is not simply an approval requirement. It can reveal access problems, operational conflicts, local needs, and design opportunities that do not appear in a spreadsheet.
Use Scenarios Instead Of One Forecast
One forecast can create false confidence. Test at least three cases:
- Base case: Reasonable demand, costs, financing, and schedule assumptions.
- Downside case: Lower demand, higher costs, delayed approvals, or slower revenue growth.
- Upside case: Stronger demand, efficient delivery, and better operating performance.
Then test individual variables. Consider what happens if construction costs rise by 15%, occupancy reaches only 70% of its target, revenue begins a year later, or interest rates remain higher than expected. Ranges are more honest and more useful than precise-looking figures that hide uncertainty.
Create A Go, Pause, Or Stop Framework
End the process with a decision rule that decision-makers can apply consistently:
- Go: Demand is supported, funding is credible, risks are manageable, and the project meets its stated goals.
- Pause: The concept has potential, but requires more data, design work, approvals, funding, or stakeholder input.
- Redesign: The project may work after changes to scale, location, timing, target users, or financing.
- Stop: The project remains financially weak, legally difficult, or unable to deliver meaningful value.
Before approval, confirm that the problem is clear, the demand is evidenced, the assumptions are visible, the public costs and benefits are separated, the affected groups have been heard, and the downside case remains survivable. Approval should follow evidence, not excitement. When a feasibility review reveals a weakness, adjusting the project early can protect capital, strengthen trust, and produce a more durable result.
Conclusion
A feasibility study helps turn a promising project idea into a decision based on evidence rather than assumptions. By defining the scope, testing demand, reviewing finances, identifying risks, and considering community and economic impacts, decision-makers can better understand what the project may require. Scenario planning also helps reveal how changes in costs, demand, financing, or timing could affect the outcome. The goal is not simply to approve or reject an idea, but to determine whether it can work under realistic conditions. When weaknesses are identified early, the project can be adjusted, delayed, or stopped before greater resources are committed. A clear and well-supported feasibility process provides a practical foundation for making informed project decisions.
