Property_info and mailing_address are stored as structured fields (line1, line2, city, state, zip) with optional lat/lng, alongside a legacy single-line `address` kept readable for older submissions. The contract's address formatter prefers structured fields and falls back to the legacy line, so old form_data still renders cleanly.
Also called: job site address · no street address yet · map pin for the build site · delivery address
- 1The form uses AddressAutocomplete for both the mailing and site address.
- 2Coordinates come from 'Google Places autocomplete OR a manually dropped map pin (for build sites with no street address yet)'.
- 3fmtContractAddress() joins line1 / line2 / 'city, state zip' onto separate lines for the contract, falling back to `address` when structured fields are absent.
- 4The site address state also drives the governing-law state on the contract.
Post-frame buildings routinely go up on parcels with no street number. The type carries the reason in its own comment — lat/lng is 'from Google Places autocomplete OR a manually dropped map pin (for build sites with no street address yet)' — and the formatter's fallback exists so older contracts written against a single-line address keep rendering.
- Sites on bare land that can't be described by a street address
- Mailing and job site conflated into one field
- Address typos propagating from intake into the contract
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →