Land feasibility study: from a desktop screen to a reviewable plan

A land feasibility study tests a defined development proposal against the evidence available about the site. For a homebuilder, the question is whether the proposed housing program merits further work once planning requirements, physical conditions, service needs, and commercial assumptions are considered together.

A first desktop screen supplies the starting record. Feasibility review goes further: it tests assumptions, identifies the studies and responses needed, and explains what could change the decision. Its output should make those dependencies visible. A parcel map or a concept lot count alone cannot establish an approved development outcome.

This guide is a suggested way to organize that review and hand it to the people responsible for the next decision. Use the desktop land due diligence checklist for the earlier screening stage. Download the feasibility handoff worksheet to keep the evidence, scenarios, and open questions separate.

Start with the project and the same parcel record

Write down the housing product, target market, timing, and decision being considered. “Investigate a single-family community on this tract” gives a reviewer a different brief from “confirm that these lots are ready for construction.” Record the scope before gathering more data.

Carry forward the parcel identifiers, jurisdiction, boundary source, source dates, and reasons the site passed or remained on hold at screening. If the proposal spans several parcels, keep their identities separate and explain the proposed assemblage. Resolve mismatches before a concept drawing, market comparison, or cost estimate silently uses a different site.

Keep reported gross acreage labeled with its source. The deeded-versus-GIS acreage method shows why two fields can produce different screening decisions. Neither figure supplies a survey or a finished land allocation for the project.

Establish the local planning questions

Identify the responsible jurisdiction and the documents or staff responses needed for the proposed housing program. Record the questions about permitted use, subdivision, dimensions, access, and the applicable review path. Keep the source and date beside any answer, including its conditions and the proposal it covers.

Austin's subdivision application process illustrates why these questions need separate answers: the city distinguishes subdivision from zoning and explains that subdivision approval does not itself authorize construction. That is an Austin example, not a national approval sequence. Check the process applicable to the actual site rather than transferring one city's requirements to another market.

An unanswered planning question should remain in the review record. If the proposed use or layout changes, check whether the earlier answer still applies to that proposal.

Keep concept scenarios attached to their inputs

A conceptual site plan can help a team compare arrangements before commissioning or completing more detailed work. Retain the boundary and planning inputs with each version so the reviewer can see what changed.

For each scenario, record:

• The boundary and acreage basis used.
• Housing product and lot-dimension assumptions.
• The space assumed for roads, drainage, open space, and other relevant uses.
• The lot arrangement and the questions its geometry leaves open.
• The source of each requirement or assumption, and which inputs still need verification.

Keep gross acreage, modeled allocations, and any proposed lot count in separate fields. Subtracting overlapping map layers can count the same area more than once. A scenario should explain its geometry and allocations rather than presenting a map subtraction as confirmed buildable acreage.

A concept remains an input for review. It does not supply a survey, engineering design, or entitlement approval. If another tool or reviewer changes the boundary, dimensions, or circulation assumptions, give the result a new scenario name and retain the previous version for comparison.

Turn site concerns into scoped follow-up work

Carry the screening concerns into the fuller review, with a question, responsible person, and evidence needed for each one.

For flood information, keep the map reference and its status. FEMA's flood-map product guidance distinguishes effective, preliminary, and historic products. The reviewer needs to know which product informed the observation and which site or design questions remain.

For wetlands, the U.S. Fish and Wildlife Service's NWI guidance explains that its mapping uses a biological definition and does not determine regulatory jurisdiction. Mapped overlap or an apparently clear area needs to be interpreted within the appropriate site review; it is not a completed jurisdictional finding.

Keep environmental-condition assessment separate from those map checks. EPA's All Appropriate Inquiries guidance describes a distinct assessment process involving environmental professionals. Identify the appropriate environmental work for the acquisition with the responsible reviewer rather than marking that work complete because a layer was inspected.

Access and utility service also need their own evidence. Record the proposed access connection and the question to be resolved. For a service inquiry, retain the proposed housing program, the provider's response, its date, and any studies or conditions still outstanding. A nearby road or line is location evidence; the review still needs an answer about the proposed project.

Test commercial assumptions against the same scenario

Keep the land-price assumption, comparison records, scope of cost estimates, and timing assumptions tied to the scenario being evaluated. A cost figure based on one layout should not quietly carry into a changed road or lot arrangement.

When comparing land evidence, separate asking prices from completed transactions and preserve the acreage basis. Note differences that limit the comparison instead of treating proximity as proof that two sites are equivalent. The acreage comparison method can help document the denominator used in a per-acre comparison.

For a preliminary cost input, record who supplied it, when, what scope it covers, and what it excludes. Identify the quantities and service or design questions that could change it. Keep an unpriced workstream visible instead of entering zero and treating the project cost as complete.

This organizes the evidence for commercial review; it does not establish a valuation, financeability, or investment result. Have the responsible team assess the actual acquisition and development assumptions.

Worked example: separate a scenario from a decision

Consider a fictional team reviewing a proposed single-family community. Every number and project detail in this example is illustrative; no site was researched, layout generated, or customer outcome measured.

1. Recorded observation in the example: the team's parcel record reports 24 gross acres. The worksheet identifies the record's source and date, with boundary verification still open. Gross acreage supplies one input, not a lot count.
2. Scenario inputs: the team labels one concept “A: 72 lots” and another “B: 60 lots.” These are invented planning scenarios for this example, not calculated yields or approved layouts. Each needs its own boundary, dimensions, land allocations, and geometry before a reviewer can assess it.
3. Unresolved evidence: utility service for the housing program and the access arrangement have not been confirmed. The preliminary cost note excludes those unresolved workstreams. The team keeps them marked unknown in both scenarios.
4. Next action: assign the scoped service inquiry and access review, then ask the responsible planner or engineer to evaluate the concept inputs. Preserve each response with the scenario it addresses.

The decision record is “hold the development conclusion while these questions are resolved.” That still allows the team to undertake scoped research. It does not support reporting 72 saleable lots or using the incomplete cost note as a settled project budget.

The worksheet makes the distinction explicit: an observed record belongs in the evidence section, an untested layout belongs in the scenario section, and a missing response belongs in the open-questions section. When an answer arrives, update the affected scenario and explain whether it changes the decision.

Hand off the evidence and the next decision together

Give the next reviewer the parcel record, source files, named scenarios, relevant responses, and unresolved questions. State the decision they are being asked to support, who owns each follow-up, and what evidence could change the current conclusion.

Use the feasibility handoff worksheet to prepare that packet. Keep it with the earlier desktop screening record, so a colleague can follow how an initial observation became a question, a tested assumption, or a remaining dependency.