← Back to Help

Site Survey — slow / megasite checklist (field operators)

Use this when a property is very large (e.g. multi‑acre turf, HOA‑scale, or millions of sq ft), when the map or AI step feels “stuck,” or when you are on weak LTE. The product is built to finish these jobs; these habits avoid duplicate work and false “failures.”

Before you scan

  1. Confirm the address in the search box, then press Scan once. Wait for the geocode / property confirmation step before scanning again — double Scan starts duplicate work.
  2. Stable connection — start the heavy AI step on Wi‑Fi or solid signal if possible; satellite + vision pulls a lot of data.
  3. Pick the right path — single property (one parcel / one estate) vs community (subdivision / HOA list) vs batch (many parcels). Megasites are usually single property or one community footprint, not dozens of rapid re‑fires.

During the AI / map phase

  1. Let the first run finish — large sites can take several minutes (imagery + models). If the UI shows progress or phase text, wait at least ~2 minutes before assuming a hang.
  2. Do not hammer buttons — repeated Scan, Measure zones, or back/forward while a run is active can queue extra requests and make the session feel worse than it is.
  3. Community footprint — after loading a subdivision, the app may auto‑start a community AI scan. That is one long request; if it errors, read the message (timeout vs network), then retry once after a short pause — not five rapid retries.

If something errors

  1. Read the error text — “timeout,” “too many requests,” “cost cap,” and “maps key” mean different fixes (wait vs admin vs settings). Note what you were doing (single vs community vs batch).
  2. One clean retry — refresh the page, re‑enter the address, single Scan → confirm → proceed. If it fails twice the same way, capture address (or community name), rough acreage, time, and hand to admin — do not loop all day on cellular.

After measurements appear

  1. Spot‑check turf / hardscape on the map against what you see on the ground before Send to Quote Lab — megasites are where manual zone tweaks matter most.

Internal ops note — Genesis / Field Ops. For technical limits and rate behavior, see docs/HARDENINGSERVICEROLEANDRATE_LIMITS.md.