Before a single line gets drawn, you need to know what's living on the site and how ecosystems function there. Landscape reports and ecological surveys give you that picture. They document vegetation communities, wetland boundaries, wildlife habitats, soil-plant interactions, and ecological conditions that directly shape where and how development can happen.

These reports aren't just environmental paperwork. They tell you which areas are buildable and which are protected. They flag regulatory triggers like wetland buffers, endangered species habitats, or floodplain vegetation that would require permits and mitigation before construction. They also reveal opportunities: mature tree canopies worth preserving, native plantings that reduce stormwater management costs, or ecological features that add real value to a project.

The types of ecological documentation you'll encounter vary widely. Wetland delineations map jurisdictional boundaries and establish setback buffers. Vegetation assessments evaluate plant community health and species composition. Ecological site descriptions classify land based on recurring combinations of soils, climate, and vegetation. Habitat inventories document wildlife presence and potential protected species.

For the ARE, Objective 3.2 asks you to synthesize site reports with other documentation and analysis. That means you need to read an ecological survey, connect its findings to geotechnical data, zoning overlays, and program requirements, then make evaluative judgments about feasibility. You're not just identifying what a report says. You're determining what it means for the project and which consultants need to be brought in to address the findings.