Skip to main content
This reference explains how the platform turns a typed address into map coordinates, what happens when that lookup can’t resolve, what the address means for sales tax, and how the address drives driving-distance display and automatic branch assignment for inbound leads. The user-facing roles referenced below are: Admin, Ops Manager, Sales Admin, Sales Member, Client Coordinator, Crew Leader, and Branch Management (Admin, Ops Manager, Sales Admin, and Client Coordinator).

What gets coordinates, and when

Properties, leads, and branch base addresses all carry coordinates

Properties, leads, and a branch’s base address each store a latitude/longitude pair derived from their address. On a property, the coordinates are read-only — they come from the address, not from manual entry.

Coordinates are resolved automatically on save

When you create one of these records, its address is resolved to coordinates automatically. On a later edit, coordinates are only re-resolved when the address actually changes — editing other fields leaves the coordinates as they are. The same rule applies to a branch’s base address: it is re-resolved only when that address changes.

An address needs at least a city or a ZIP to be located

An address can only be placed on the map if it has at least a city or a postal code. With neither, the platform skips the lookup and the record is saved without coordinates.

Picking an address from the suggestions skips the lookup

When you choose an address from the autocomplete suggestions while typing, that selection already carries its coordinates. In that case the platform keeps those coordinates and does not run a separate lookup.

Lookups are limited to the United States

Both the address suggestions and the coordinate lookup are restricted to United States results, and the first matching result is used.

ZIP code input on the create-lead form

On the create-lead form, a postal code must be exactly 5 digits (“ZIP code must be 5 digits”). An empty value is treated as no ZIP rather than an error.

When an address can’t be located

A failed lookup never blocks the save

If an address can’t be resolved to coordinates, the record still saves. The lookup is designed to fail quietly rather than error out — a save is never blocked because the map lookup didn’t succeed.

Existing coordinates are not overwritten on failure

If you edit a record and the new address can’t be resolved, the platform leaves the record’s existing coordinates untouched rather than wiping them. On a brand-new record that can’t be resolved, the record is simply saved with no coordinates.

A property with an unusable address still saves

A property created from free-text with no resolvable city, state, or ZIP is still created. When the address components can’t be determined, placeholder values are stored so the record can exist, and these can be corrected later by editing the property’s address.

Records with missing coordinates can be backfilled

Properties, leads, and branch base addresses that have an address but no coordinates can be filled in later by a maintenance pass that resolves them in bulk. Records that still can’t be resolved are skipped and reported, and one failure never stops the rest of the run.

Pricing an estimate can also fill in a property’s missing coordinates

A property that has an address but no coordinates — most often an imported one — can also get them when an estimate for it is priced and the platform looks up its address along the way. The coordinates are saved only when that lookup lands on a single, precise location and the address still matches the one saved on the property. This only ever fills in coordinates that were missing — it never changes coordinates a property already has.

The address and sales tax

Sales tax isn’t based on the state or ZIP code

The platform doesn’t decide whether a job is taxed from where the property is. Sales tax is always a choice made in the tax selector on the estimate, proposal, or invoice — a saved tax rate, a tax group, TaxJar on branches that use it, or No Tax. A missing ZIP code or state never blocks an estimate from pricing or saving. See Sales tax.

TaxJar is the one place the address matters

On a branch that uses TaxJar, the TaxJar option looks up a rate from the property address. A ZIP code is the minimum it needs; the street, city, and state make the rate more precise. If the property has no ZIP code, TaxJar can’t find a rate. Work isn’t blocked — add the ZIP to the property’s address or pick a saved rate. See When TaxJar can’t find a rate for how each screen handles it.

The address drives driving distance and branch routing

There is no fixed ZIP-to-territory table in the platform. “Territory” here is computed from driving distance to branch base addresses, and a lead is assigned to the nearest branch.

Inbound leads are auto-assigned to the nearest branch by driving distance

When a lead comes into a workspace with more than one branch, the platform measures the driving distance from each branch (those that have a base address) to the lead’s address and assigns the lead to the closest one. A workspace with a single branch skips the distance check — every automated lead that has an address goes to that one branch.

A lead with no address is created without a branch

If a lead has no address, branch matching is skipped and the lead is still created — just without a branch. In a multi-branch workspace, the same goes for an address too vague to locate, such as a street with no city and no ZIP: the lead is created without a branch rather than routed to a guess. Likewise, if no branch can be matched by distance, the lead proceeds without a branch rather than failing. (A single-branch workspace assigns its one branch even when the lead’s address is too vague to place.)

A branch needs a base address to be a routing candidate

When a workspace has more than one branch, only branches that have a base address are considered when matching, and a branch with no base address set can never be the matched branch. Set a branch’s base address under its configuration so it can receive routed leads. The exception is a workspace with a single branch, which receives every automated lead with an address whether or not the branch has a base address.

Driving distance shown on a property

Driving distance is measured in miles from the branch’s base address to the property. On a project’s property details, the directions link appears whenever both the branch and property addresses are present — it is a shortcut to directions, not gated on the mileage. When the driving distance can be worked out, the link is captioned with it (for example, “12 miles from branch”); when it can’t, the link still appears and reads “Directions from branch” instead. “View on map” and “Get directions” links are built from the address text, not from stored coordinates. A maps or directions link only appears when an address is present.

Quick reference

  • What carries coordinates: properties, leads, and branch base addresses — resolved from the address on save, re-resolved only when the address changes.
  • Minimum to locate an address: at least a city or a ZIP. Lookups are United States only.
  • A failed lookup never blocks a save and never overwrites existing coordinates.
  • A property missing coordinates can also get them when an estimate for it is priced, if the address resolves to a single precise location and still matches the property.
  • Sales tax: chosen in the tax selector, not decided by the address. Only a TaxJar rate is looked up from the property address, and it needs at least a ZIP code.
  • Lead routing: in a multi-branch workspace, the nearest branch by driving distance — not by ZIP. A lead with no address, a too-vague address, or no matchable branch is still created without a branch. A single-branch workspace assigns its one branch to every automated lead that has an address.
  • Branch must have a base address to be a routing candidate (in a multi-branch workspace) or to show a driving distance.