LANDSHILOH · SITE CONDITIONS AND SOIL RESEARCH
Soil information serves different purposes. A regional soil map, a septic evaluation and a geotechnical investigation should not be treated as interchangeable answers. Start with the decision you need to make and ask the appropriate professional which investigation scope supports it.
Use soil mapping for initial research
USDA NRCS Web Soil Survey provides soil information and interpretations useful for screening and planning. Read the map-unit information, source date and limitations for the area. Mapping does not describe every small variation on a parcel. Use it to identify questions for further investigation rather than claiming it establishes foundation design, wastewater approval or uniform conditions across the site.
Define the project-specific investigation
Explain the proposed structures, grading and site work to a qualified geotechnical professional. Ask what fieldwork, testing, analysis and deliverables are appropriate. Coordinate with the designer and responsible authority so the investigation supports their requirements. A report for a different location or a different building concept may not answer the current project’s questions.
Keep scopes separate and coordinated
Wastewater evaluation, agricultural suitability and structural design can involve different methods and reviewers. Share relevant findings across the team while preserving each report’s purpose and limitations. Ask who will resolve conflicting information or recommend additional work. Store the complete reports, including appendices and plans, instead of relying on a favorable sentence extracted from the conclusions.
Working checklist
Use these headings in your parcel file. For each item, record the source, date, responsible reviewer, outstanding question and next action. Keep confirmed findings separate from estimates and assumptions.
- Decision and project scope
- Soil map source and limitations
- Qualified investigation proposal
- Design-team and authority requirements
- Complete reports and follow-up questions
Practical example
A buyer finds a favorable general soil interpretation and assumes a particular foundation will work. A qualified geotechnical review may require site-specific information before the designer can proceed. The map was useful for research, but it did not perform the design investigation the project needs.
Illustrative scenario only; not a property listing, valuation or assurance of feasibility.
Common question
Can one soil test answer every site question?
Ask what that test was designed to establish. Soil mapping, geotechnical work, agricultural assessment and wastewater evaluation may require different evidence, methods and professional interpretation.
Compare the question each source is meant to answer
| Information or assignment | Useful question to ask | Keep separate |
|---|---|---|
| Published soil survey | What mapped properties and interpretations help frame further research? | A decision about the actual design or approval for a particular site. |
| Proposed geotechnical assignment | What project-specific ground questions should this scope investigate? | Questions outside the agreed assignment. |
| Wastewater-related evaluation | What evidence is needed for the proposed wastewater arrangement? | Assumptions about unrelated structures or uses. |
| Agricultural assessment | What evidence addresses the intended land-management or production question? | A conclusion about a different activity merely because it concerns soil. |
Use this table to organize an inquiry, not to prescribe a universal test package. The appropriate professional should explain what the assignment includes and what further coordination is needed for the specific proposal.
Prepare a project brief before requesting a proposal
Include the parcel identity, the current concept, the approximate locations under discussion and the decision the work must inform. Describe proposed structures or site work at the level currently known, and label assumptions that have not been settled. Attach complete relevant prior records rather than selected favorable extracts.
Ask the prospective provider what additional inputs are needed to scope the work. A proposal prepared around an incomplete description can answer a different question from the one the owner or designer needs resolved. Keep the dated brief with the proposal so later changes are easy to identify.
Review the proposal by scope, not only price
- Which project version and area does the assignment address?
- What work and deliverables are included?
- What information must the owner or design team supply first?
- What assumptions and exclusions affect the proposal?
- How will findings and limitations be communicated?
- What coordination with other reviewers is included?
- What change could require a revised scope or additional work?
When comparing proposals, keep unmatched scope visible. A lower price may describe a narrower assignment. Ask for clarification rather than assuming identical report titles mean identical work. Record what has been quoted, what remains unpriced and which decision each deliverable supports.
Create an investigation scope record
| Field | Working entry |
|---|---|
| Purpose | The specific project question and intended use of the work. |
| Location | The area considered and the relevant plan version. |
| Inputs | Records, plans and assumptions supplied for the assignment. |
| Scope and exclusions | The agreed work and the questions it does not undertake. |
| Deliverable | The complete report, plans and supporting material to retain. |
| Coordination | Who reviews the findings for the current project. |
| Follow-up | Clarifications, recommendations and additional actions still open. |
Keep a report handover separate from a design decision
Receiving a report is a document milestone. Record who needs to review it and what decision follows. Keep conclusions with the relevant assumptions, scope and recommendations. If a finding affects the concept, ask the responsible people how that affects related work rather than treating the report as a general pass-or-fail certificate.
Track recommendations as actions with owners. A report may identify further questions or coordination. Do not hide those items by marking the entire research category complete. Preserve the full document and its supporting location information for the people reviewing the proposal.
Worked example: two assignments with different purposes
A fictional buyer has a broad soil map and an existing report prepared for an earlier proposal. The buyer is considering a different site arrangement. Instead of calling the soil question complete, the buyer prepares a current brief and asks which earlier information remains relevant.
The reviewer identifies the assignment needed for the current question and explains what is outside it. The buyer keeps the map as screening context, the earlier report as historical project evidence and the new scope as a distinct assignment. Other site questions remain with the appropriate reviewers.
The budget records the quoted work and any unpriced follow-up separately. When findings arrive, the design team reviews them in relation to the current concept. The file shows how the evidence informed the decision rather than relying on a generic “soil tested” description.
Recognize changes that deserve a relevance check
Ask about relevance when the intended activity, structure, site-work concept or location changes. Explain the actual change to the appropriate professional. Do not infer that a small change is immaterial or that every change invalidates all prior work.
Keep the response with the revised project version. If additional work is needed, record why, what it will address and which decisions depend on it. This makes the cost and schedule effects visible without guessing at the technical outcome.
What does “soil tested” tell a buyer?
By itself, very little about scope. Ask for the complete record, its purpose, location, date and limitations, then seek the review appropriate to the proposed use.
Can I use a soil-map screenshot as the investigation brief?
It can be supporting context, but add the project description and exact question. Keep the map’s identity, legend and available source information with it.
Reference background
- U.S. Department of Agriculture, Natural Resources Conservation Service. Soil Survey Geographic Database (SSURGO).
- Soil Survey Staff. Web Soil Survey. U.S. Department of Agriculture, Natural Resources Conservation Service. Background reviewed November 6, 2026.
Discuss your land questions with LandShiloh. Share the location, intended use and the questions you want to resolve.
Prepared by LandShiloh for general education. Requirements and conditions vary by property and jurisdiction. Use current records and appropriate qualified professionals for parcel-specific decisions. Publication does not certify a property, approve a use or replace transaction documents.