CHASEENERGY.IO
Direct Answer
A development feasibility report organizes the facts and assumptions that determine whether a site and concept are worth advancing. It connects land use, zoning, physical constraints, utilities, access, infrastructure, preliminary program, cost, schedule, and market logic into an early decision framework. It is not a permit or guarantee; it is a disciplined way to reduce avoidable uncertainty.
The questions before design
What can legally be built? What can physically fit? How will the site obtain water, wastewater, power, drainage, and access? What environmental or flood conditions matter? Which approvals control the schedule? What budget and exit assumptions must hold for the project to work?
A useful report structure
The report should state the proposed program, sources, known facts, unresolved questions, assumptions, constraints, preliminary options, cost ranges, decision gates, and the professionals or tests needed next. It should separate verified information from estimates and clearly date time-sensitive inputs.
Feasibility as an operating process
The strongest reports remain connected to the project. New surveys, utility responses, design decisions, pricing, and agency feedback update the model rather than disappear into separate files. That creates a decision history and helps prevent old assumptions from silently controlling new work.
Evidence levels inside the report
Each material input should be labeled by authority: official record, licensed-professional work, utility or agency response, owner-supplied information, market quote, preliminary estimate, model assumption, or unresolved question. The report should not present a map observation or AI summary as equivalent to a survey, title report, zoning determination, geotechnical investigation, or utility commitment.
Source dates matter. Parcels change, codes change, connection capacity changes, quotes expire, and project programs evolve. A decision log helps the team understand which conclusions remain valid when an assumption changes.
Connecting feasibility with cost and capital
The early cost model should separate land, site development, utilities, foundation, building, soft costs, financing, contingency, owner items, and schedule-sensitive assumptions. A range is more responsible than false precision when design and site information remain preliminary.
Feasibility should also identify the capital decision. Is the next spend a survey, utility study, zoning opinion, geotechnical report, concept design, pricing exercise, or site-control agreement? The report earns value when it directs the next dollar of diligence toward the uncertainty most capable of changing the decision.
From report to project knowledge
A static PDF can become obsolete as soon as new information arrives. The underlying question register, source library, assumptions, decision log, and cost model should remain available to the project team. New evidence can then update the canonical view rather than create a second disconnected answer.
Direct Answers
Frequently asked questions
Who should prepare a feasibility report?
The coordinating report may be assembled by an owner advisor or development team, but authoritative legal, zoning, survey, environmental, engineering, utility, cost, and market conclusions require the appropriate sources and professionals.
How detailed should the first report be?
Detailed enough to identify fatal constraints, major cost drivers, missing evidence, plausible options, and the next decision. It should not pretend to be completed design.
What is a fatal flaw?
A condition that prevents the intended project or changes the economics or timeline enough that the current concept should not advance without revision.
How are assumptions handled?
State them explicitly, identify their source and owner, show sensitivity where material, and create a plan to verify the assumptions capable of changing the decision.
Can the report support investors or lenders?
It can organize early evidence and risks, but each capital source will require its own underwriting, third-party reports, approvals, and documentation.
Sources & Method
This page combines first-hand operating experience supplied by Stephen Chase with the Chase Knowledge Architecture. It distinguishes experience-led analysis from external facts, avoids unsupported claims, and is reviewed as projects, regulations, costs, and capabilities change.
Read the editorial and evidence standards