Frequently Asked Questions

Parcel boundaries are available nationwide across the US, though attribute completeness (owner, zoning, acreage) varies by county. Detailed, jurisdiction-specific setback data is available for Oregon (Bend and Deschutes County) and Idaho (statewide). Everywhere else — including Washington — SiteFacts applies national default setbacks (roughly 10–15 ft) as a starting point that you can override per parcel.

SiteFacts aggregates trusted public and commercial sources: parcels from Regrid, flood zones from the FEMA National Flood Hazard Layer, wetlands from the USGS National Wetlands Inventory (NWI), and elevation (hillshade and contours) from USGS 3DEP. Addresses are geocoded via Google with US Census and Nominatim fallbacks. Field completeness varies by county and upstream provider.

No. SiteScore is a screening signal to help you compare parcels quickly — a 0–100 buildability score backed by weighted due-diligence factors. It does not replace professional surveys, geotechnical work, engineering, or jurisdiction review. SiteScore and SiteFacts reports are ordered (they consume credits) and are researched and published by the SiteFacts team, not generated instantly. See Reports & SiteScore for the full pipeline.

Yes. SiteFacts uses multi-tenant workspaces with invite-based team management and owner / admin / member roles. Workspace admins invite teammates by email (links are valid for 24 hours), manage seat usage, and track customers and properties together. See Workspaces & Teams for setup.

A developer API on top of the SiteFacts Data Lake is in progress. It will offer programmatic access to the parcel, environmental, and analysis data that powers SiteFacts. See the Data Lake page for what it will cover, and sign up there to be notified at launch.

Head to app.sitefacts.com to request access, or accept a workspace invite from a teammate. Invites arrive by email and are valid for 24 hours. New to the app? Start with the Quick Start.