Land due diligence checklist: start with a desktop site screen

A land due diligence checklist helps a team keep evidence and unanswered questions with the site it is evaluating. Start with a desktop screen: confirm the parcel, check the available planning and map records, and decide which questions deserve further work.

This checklist covers that first research stage. A clean-looking map does not establish that a site can support the proposed project. The useful output is a documented decision to investigate, hold, or pass, with the next action assigned.

Where desktop screening fits in land due diligence

Keep the scope of each review visible:

• Desktop screening: inspect available records, identify mismatches and mapped concerns, and decide whether to investigate further. The six fields below keep this work reproducible.
• Feasibility review: test a defined development proposal using the relevant planning, design, engineering, service, market, and cost inputs. Carry the screening questions into that work rather than treating them as answered.
• Purchase and project diligence: identify the surveys, title and access records, environmental work, and other project-specific reviews needed with the appropriate professionals. A desktop checklist does not complete those workstreams.

Environmental assessment has its own scope. EPA's All Appropriate Inquiries guidance describes an environmental-condition assessment process and the role of an environmental professional. Do not relabel a wetlands or aerial-map check as a completed environmental assessment. Which work is appropriate for a particular acquisition needs its own review.

Begin the screening worksheet with the proposed use, minimum requirements, and decision you are trying to make. For a homebuilder, gross-acreage and housing-product criteria can start the search; a minimum lot count still needs the assumptions and review behind it.

Confirm which property you are evaluating

Record the jurisdiction, parcel identifier, address if available, and the boundary source. If your project needs an assemblage, list every parcel separately before treating it as one site.

Keep gross acreage separate from any later estimate of usable area. Do not label a subtraction of mapped constraints “buildable acreage”: overlays alone do not answer design, entitlement, or engineering questions.

Separate zoning observations from a permitted project

Record the mapped zoning designation and link to the relevant local planning source. Then list the questions that matter to the proposed use: permitted uses, overlays, dimensions, parking, and the review process.

Treat those as questions until the applicable documents and responsible jurisdiction support an answer. A label on a third-party map is a starting point. Keep the date checked and the source beside your notes, so the next reviewer can retrace the finding.

When zoning and future land-use labels differ, use the zoning and policy reconciliation method to keep current rules, adopted policy and pending changes separate before asking about the proposed housing scenario.

For a multifamily search, write down the assumptions behind any unit-count scenario. For an industrial search, record the intended operation before assessing whether a zoning category appears relevant. Different projects can raise different questions on the same parcel.

Check flood information and record its status

Use the FEMA Flood Map Service Center to look up the location and available flood mapping. Preserve the map reference and the date or status shown. FEMA distinguishes effective products from preliminary and historic products; those should not be mixed without explanation. See FEMA's map product guidance.

Write your observation narrowly: which mapped area appears to intersect which portion of the parcel. Leave the project implications as a follow-up question for the relevant reviewer.

Treat wetland mapping as a screening input

Record any overlap with National Wetlands Inventory mapping and note its source. The U.S. Fish and Wildlife Service explains that its mapping is biological and does not establish regulatory jurisdiction. See the NWI frequently asked questions.

An overlay is therefore a reason to investigate; it is not a jurisdictional determination. A blank area on the map is not a substitute for the site-specific review your project may need.

Keep access and utilities as separate workstreams

A road next to a parcel raises useful questions about access. It does not, by itself, resolve them. Record the apparent connection and assign the appropriate records or agency follow-up.

For a proposed housing site, use the road frontage and access evidence checklist to separate the route, supporting documents, entrance permission and design questions before handing the site to the next reviewer.

Likewise, distinguish nearby infrastructure from confirmed service for the proposed project. In your notes, separate these fields:

• Infrastructure observed and the source used.
• Potential provider, if identified.
• Service or capacity information actually received.
• Remaining questions, responsible person, and next action.

Leaving a field blank or marked unknown is better than carrying an assumption into a financial model as a fact.

Finish with a short decision record

For every site, keep the same six fields: question, observation, source, date checked, confidence, next action. For example, “mapped wetland overlap at the northern boundary” belongs under observation; “request appropriate site review” belongs under next action. Neither should silently become “unusable northern acreage.”

Choose whether to investigate, hold, or pass, and write down why. If one unresolved issue would determine the outcome, prioritize it before adding detail elsewhere.

Keep confidence tied to the observation. “Recorded in an archived dataset” and “confirmed against the current source” describe different evidence. Neither establishes that the proposed use has been approved. If sources disagree, retain both and make resolving the discrepancy the next action.

Pillar's map layer workflow and layer upload guide can help you bring research into a shared map. Keep source notes with that work so the next person can distinguish mapped evidence from confirmed findings.

Hand the open questions to the next reviewer

For each question that needs fuller review, name the evidence or response needed and who is responsible for obtaining it. “Utilities unknown” is less useful than “confirm the provider and request service information for the proposed housing program.” Record any answer's date, scope, and conditions when it arrives.

Keep the current screening decision separate from a later development or purchase decision. A site can deserve a closer investigation while its layout, service, access, and cost assumptions remain untested. Revisit the screen when a new parcel record, agency response, or site observation changes its basis.

The worksheet includes a handoff section for these open questions. Preserve the parcel IDs and source files with it so the next reviewer can check the same site.

Walk through one actual record before screening a whole list

Start with Adams County, Wisconsin parcel 026008090000. In the public V12 dataset retrieved September 11, 2026, its DEEDACRES field is 10 and its GISACRES field is 9.94. Those are dataset observations, not a survey or a conclusion that the site can be developed.

1. Open the saved public-record sample and locate that parcel ID. Preserve the leading zero; parcel IDs are identifiers, not numbers to round or reformat.
2. Record your criterion: at least 10 acres. A deeded-field filter passes this record; a GIS-field filter does not. Keep the candidate on hold until you decide how to handle this difference. Do not silently replace either value.
3. Locate the same parcel in the current county source. Match county and parcel ID before using a street address or map pin. Record any split, merge, or changed identifier you find.
4. Start separate checks for zoning, flood mapping, wetlands, access, and utilities using the sources above. Leave them unresolved until you inspect them. The acreage record provides no evidence about those questions.
5. Save the source links, dates, and next action with the candidate. In Pillar, use the property search workflow to find the property and the CRM workflow to keep follow-up work with the opportunity. If a current search does not match the record, resolve the identity before advancing it.

For this example the justified decision is hold for acreage and identity verification, not “buy” or “pass.” We have not run a complete feasibility analysis or inspected this site. The acreage comparison method explains exactly what the data check covers.

Download the screening worksheet to repeat the process. A colleague should be able to see which questions you answered and which still need work without redoing the whole search.