Site Feasibility
November 03, 2026

What Should a Real Estate Feasibility Report Include?

A useful real estate feasibility report should show what a site appears capable of supporting, the zoning and site assumptions behind that conclusion, the buildable envelope and development metrics, major constraints, evidence, uncertainty, and the next steps required before committing more capital.
Anatomy of a real estate feasibility report showing site information, zoning, buildable envelope, 3D massing, development metrics, constraints, assumptions, evidence, risks, and next steps.

A real estate feasibility report should explain what a site appears capable of supporting, the rules and assumptions behind that conclusion, the constraints that could change the outcome, and the issues that still require verification. The strongest reports combine parcel and zoning information with a buildable scenario, development metrics, source-backed evidence, and a clear list of risks and next steps.

For a developer, the report should answer a simple question:

“What can I reasonably build here, how confident am I in that answer, and what do I need to verify before committing more capital?”

What should a feasibility report include? The short answer

A useful phase-zero real estate feasibility report should include:

  • an executive summary and go/no-go context;
  • site identification and parcel information;
  • the intended development program;
  • zoning district, overlays, and source references;
  • permitted use and key dimensional controls;
  • a buildable envelope or preliminary 3D massing;
  • development metrics such as floor area, FAR, height, coverage, and estimated yield;
  • major site and environmental constraints;
  • parking, access, and infrastructure assumptions;
  • one or more development scenarios where uncertainty exists;
  • verified facts, assumptions, and items needing further verification;
  • key risks, data gaps, and diligence priorities;
  • and recommended next steps.

The report should be concise enough to support an acquisition decision but detailed enough that another team member can understand how the conclusion was reached.

Workflow for creating a real estate feasibility report, from site and zoning inputs through buildable geometry, massing, development metrics, risk review, and recommended next steps.
A decision-useful feasibility report connects site and zoning inputs to buildable geometry, preliminary massing, development metrics, risk review, and clear next steps.

1. Executive summary

The report should begin with the conclusion, not force the reader to reconstruct it from zoning tables.

A strong executive summary should state:

  • the property being analyzed;
  • the intended use or development program;
  • the preliminary development potential;
  • the most important zoning and site constraints;
  • the major assumptions;
  • the most material unresolved risks;
  • and the recommended next step.

If the analysis supports multiple scenarios, the summary should identify which scenario appears strongest and why.

The goal is to help a principal or acquisition team understand the decision in a few minutes before reading the supporting analysis.

2. Site identification and parcel information

The report should clearly identify the property being analyzed.

At minimum, include:

  • street address;
  • parcel or tax-lot identifier;
  • lot area;
  • lot dimensions;
  • frontage;
  • lot type where relevant;
  • and a map or aerial showing the subject parcel.

If the development site includes multiple parcels, show how they are combined and whether the analysis assumes assemblage, merger, subdivision, or another parcel configuration.

Housing Toolbox's predevelopment guidance similarly recommends documenting site boundaries, topography, neighboring uses, access, utilities, current zoning, and areas affected by wetlands or setbacks as part of preliminary site assessment. Its site-assessment guidance shows why parcel context belongs near the beginning of a feasibility analysis.

3. Intended development program

A feasibility report should state what is being tested.

Examples include:

  • multifamily residential;
  • mixed-use residential and retail;
  • adaptive reuse;
  • industrial or logistics;
  • hotel;
  • office;
  • or another specific development concept.

Where appropriate, document assumptions such as target unit count, approximate unit sizes, ground-floor uses, parking approach, or building type.

Without a stated program, the report may describe zoning capacity without answering whether the site fits the actual investment strategy.

4. Zoning district and regulatory sources

The report should identify the zoning district and the authoritative source used to determine it.

Also include any:

  • overlays;
  • special-purpose districts;
  • historic or design review areas;
  • waterfront or environmental zoning layers;
  • transit-related provisions;
  • or other jurisdiction-specific regulations.

Do not rely solely on a third-party zoning label if the decision is material.

The report should identify the underlying zoning map, zoning text, ordinance, agency record, or other authoritative evidence supporting the analysis.

For the difference between identifying the district and applying it to a development scenario, see Zoning Lookup vs. Development Feasibility Analysis.

5. Permitted use and entitlement path

The report should state whether the intended use appears:

  • permitted as-of-right;
  • conditional;
  • subject to administrative approval;
  • dependent on a variance or special permit;
  • or dependent on a rezoning or other discretionary action.

If the conclusion depends on an interpretation that is not fully verified, say so explicitly.

A higher-yield scenario that requires a difficult entitlement path should not be presented as equivalent to an as-of-right scenario.

6. Key zoning and dimensional controls

Summarize the zoning controls that materially shape the site.

Typical metrics include:

  • FAR or density;
  • maximum permitted floor area;
  • height limits;
  • base-height requirements;
  • front, side, and rear setbacks or yards;
  • upper-level setbacks;
  • lot coverage;
  • open-space requirements;
  • parking and loading requirements;
  • and other use- or district-specific bulk controls.

The report should explain which controls actually drive the result rather than reproducing every rule in the code.

7. Buildable envelope

A good feasibility report translates zoning into geometry.

The buildable envelope should show how setbacks, height, lot coverage, and other dimensional controls define the three-dimensional area where development may potentially occur.

This can be communicated through:

  • a plan diagram;
  • a section;
  • an axonometric or isometric diagram;
  • a translucent 3D zoning envelope;
  • or a combination of these.

EPA's reuse-planning guidance recommends documenting viable property scenarios with sketches, renderings, or plot plans and explicitly calls out maximum lot coverage, maximum height, FAR, setbacks, and parking as relevant site-planning inputs. EPA's Reuse Plan guidance supports this kind of visual documentation.

For more detail, see What Is a Buildable Envelope?.

8. Preliminary 3D massing

The buildable envelope shows the regulatory volume. A preliminary massing scenario shows how an actual development program might fit inside it.

The massing should be conceptual—not presented as final architecture.

It should help answer:

  • how many floors appear plausible;
  • how the footprint changes with setbacks or upper-level step-backs;
  • whether the theoretical FAR can physically fit;
  • how parking, access, or open space compete with the building;
  • and whether the proposed program appears spatially realistic.

Housing Toolbox notes that conceptual site designs can be useful during predevelopment, while warning that early building configurations should be treated as a starting point rather than final design. That distinction is important in a phase-zero report.

9. Development metrics

The report should convert the massing into decision-useful numbers.

Depending on the project type, include:

  • lot area;
  • theoretical permitted floor area;
  • preliminary achievable floor area;
  • permitted FAR;
  • FAR used;
  • maximum and modeled lot coverage;
  • maximum and modeled height;
  • number of stories;
  • estimated unit count;
  • parking count;
  • commercial, residential, amenity, or other program-area breakdowns;
  • and other project-specific yield metrics.

Where possible, distinguish theoretical zoning capacity from the capacity captured by the tested scenario.

Sample feasibility dashboard summarizing development metrics such as floor area, FAR, lot coverage, building height, stories, unit yield, parking, and major site constraints.
A compact feasibility dashboard should surface the metrics that matter to the acquisition decision, including floor area, FAR, coverage, height, stories, yield, parking, and major constraints.

For FAR-specific interpretation, see Floor Area Ratio (FAR): What Developers Need to Know.

10. Site and environmental constraints

The report should identify constraints that may reduce buildable area, change cost, or require deeper diligence.

Examples include:

  • flood-hazard areas;
  • wetlands;
  • topography or steep slopes;
  • environmental conditions;
  • easements;
  • utility corridors;
  • existing structures;
  • access limitations;
  • and other parcel-specific conditions.

EPA's reuse-assessment guidance recommends documenting property constraints, the risks or liabilities associated with them, and any missing information or data gaps. It also notes that constraints can change as due diligence improves. EPA's guidance is a useful model for how a feasibility report should communicate uncertainty.

For a focused framework on regulatory overlays versus parcel-specific constraints, see Zoning Overlays & Site Constraints.

11. Access, parking, utilities, and infrastructure

A building may fit geometrically but still face operational or infrastructure limitations.

Where relevant, document:

  • street frontage and access;
  • curb cuts;
  • parking assumptions;
  • loading;
  • fire access;
  • water and sewer availability;
  • power or other utility assumptions;
  • and known infrastructure-capacity issues.

San Diego County's Development Feasibility Analysis separates infrastructure analysis from land-use, market, and financial feasibility, reinforcing that infrastructure is a distinct component of the development question. The County's DFA structure is a useful example.

12. Scenario comparison

If the site has meaningful uncertainty, the report should not force one false-precision answer.

Instead, compare scenarios such as:

  • as-of-right versus entitlement-dependent;
  • base FAR versus bonus FAR;
  • surface parking versus structured parking;
  • residential-only versus mixed-use;
  • lower-risk versus higher-yield massing;
  • or different assumptions about a site constraint.

For each scenario, use the same metrics and clearly identify what changed.

This makes tradeoffs visible and prevents a single optimistic configuration from becoming the only development narrative.

For a practical framework for comparing multiple opportunities using consistent assumptions and metrics, see How to Compare Development Sites Before Acquisition.

13. Verified facts, assumptions, and items needing verification

Every feasibility report should make uncertainty visible.

A simple three-part classification works well:

  • Verified: supported by an authoritative map, zoning text, agency record, survey, or other reliable source.
  • Assumed: temporarily used for screening but not yet confirmed.
  • Needs verification: material to the conclusion and requiring additional professional or jurisdictional review.

This is especially important when the modeled yield depends on an unverified parking interpretation, lot dimension, entitlement, floor-area exclusion, utility condition, or environmental assumption.

For a full diligence framework, see Zoning Due Diligence Checklist for Developers.

14. Evidence and source references

A defensible report should show where the important conclusions came from.

Useful evidence may include:

  • zoning-map references;
  • zoning-text sections;
  • parcel records;
  • agency records;
  • official flood maps;
  • survey information;
  • environmental reports;
  • or other supporting documentation.

The report does not need to reproduce every source in full, but another reviewer should be able to trace material conclusions back to their basis.

This is one of the clearest differences between a decision-ready feasibility report and an unsupported online zoning summary.

15. Data gaps and risk flags

Do not hide missing information.

Instead, identify it explicitly.

Common data gaps include:

  • uncertain lot dimensions;
  • unverified easements;
  • pending survey information;
  • unknown utility capacity;
  • unresolved environmental conditions;
  • unclear parking or use interpretations;
  • pending zoning changes;
  • or entitlement assumptions that require counsel or agency confirmation.

EPA specifically recommends identifying missing information as data gaps and obtaining additional information when those gaps affect the evaluation of opportunities or constraints. The Reuse Assessment framework supports making those gaps visible rather than implying certainty.

16. Recommended next steps

A feasibility report should end with actions, not just findings.

Examples include:

  • obtain a boundary or ALTA survey;
  • confirm a zoning interpretation with counsel or the jurisdiction;
  • commission environmental due diligence;
  • verify utility capacity;
  • test parking or access with a civil engineer;
  • advance the preferred massing with an architect;
  • obtain preliminary construction-cost input;
  • or begin financial underwriting on the preferred scenario.

The next-step list turns the report into a diligence roadmap.

What a phase-zero report should not pretend to be

A preliminary site-feasibility report should not be presented as:

  • final architecture;
  • a permit approval;
  • a legal opinion;
  • a boundary survey;
  • an environmental assessment;
  • a structural or civil engineering design;
  • a guaranteed unit count;
  • or a complete investment underwriting model.

Those disciplines may become necessary later.

The value of phase-zero feasibility is that it identifies whether the opportunity appears strong enough to justify those deeper costs.

Site feasibility report vs. full financial feasibility study

These are related but different deliverables.

A site feasibility report focuses primarily on what the property appears capable of supporting physically and regulatorily.

A full financial feasibility study goes further into development prototypes, rents or sales, hard and soft costs, financing, operating assumptions, residual land value, returns, and other economic variables.

San Diego County's Development Feasibility Analysis illustrates this separation by publishing distinct land-use, infrastructure, market, and financial analyses rather than treating them as one undifferentiated report. The County's DFA report structure is a useful example.

A developer may use the phase-zero site report to decide which scenario deserves detailed underwriting.

What does a decision-ready report look like?

A decision-ready report should make it easy to answer five questions:

  • What can I build?
  • What controls that answer?
  • What assumptions were used?
  • What could materially change the result?
  • What should I do next?

If the report cannot answer those questions clearly, more pages do not necessarily make it more useful.

Decision-ready feasibility report framework answering what can be built, what controls the result, which assumptions were used, what could change the outcome, and what to do next.
A decision-ready feasibility report should make the development conclusion, controlling factors, assumptions, material risks, and recommended next actions immediately clear.

How Dwellci structures phase-zero feasibility

Dwellci AI is designed around the phase-zero decision point: understanding development potential before committing significant capital or detailed design effort.

A useful Dwellci-style feasibility output connects parcel intelligence, zoning analysis, site constraints, zoning-backed 3D massing, development metrics, and evidence so teams can understand both the result and the basis for it.

The goal is not to replace architects, engineers, attorneys, surveyors, environmental professionals, or financial underwriting.

It is to help developers decide earlier which opportunities deserve those deeper investments.

For the broader concept, see What Is Real Estate Site Feasibility? A Developer's Guide.

FAQ

How long should a feasibility report be?

There is no universal page count. A phase-zero report should be as short as possible while still documenting the site, governing rules, development scenario, key metrics, assumptions, constraints, evidence, and next steps. Clear visuals can often communicate more effectively than additional narrative.

Should a feasibility report include financial analysis?

It depends on the scope. A site-feasibility report may include preliminary land-basis or high-level financial assumptions, but a complete financial feasibility study usually requires a separate pro forma with market, cost, financing, revenue, timing, and return assumptions.

Should a feasibility report include 3D massing?

For many development sites, yes. A simple 3D massing can show whether FAR, setbacks, height, lot coverage, and site constraints work together in a physically plausible way. It should be labeled as preliminary rather than final design.

What is the most important part of a feasibility report?

The most important part is the connection between the conclusion and its evidence. The reader should be able to see what appears buildable, which rules and assumptions produced that result, and what unresolved issues could change it.

When should a feasibility report be prepared?

Ideally during initial site screening and acquisition due diligence, before significant capital is committed to detailed design, consultants, entitlements, or closing.

Make smarter development decisions from day one

Request access to start evaluating sites with speed and confidence