Physical constraints
The report should separate mapped flood and wetland context from contamination-source context while making both easy to review.
Data-source guide
Flood and wetlands context can change field timing, site access, client questions, and lender review before environmental work is scoped.

Physical context belongs next to regulated-source context because both can change the work plan.
The report should separate mapped flood and wetland context from contamination-source context while making both easy to review.
Missing local or stale mapped data should be visible as a gap, not hidden in a disclaimer.
Shows flood-hazard context around the site.
Limitation: Mapped flood context may not resolve parcel-specific constraints.
Flags wetland presence for review and timing questions.
Limitation: Mapped wetlands may require professional or agency verification.
Corrections and real project outcomes are the fastest way to make these vertical reports useful. Send the exact signal and we will route it into the product feedback loop.
These pages are designed to support the product hub, sample report, and related source guides with clear crawl paths.