Sites

A physical service location that belongs to one customer: street address, timezone, access notes, parking, and optional map coordinates. Dispatch geography and Field “today” follow this location — not the customer billing address.

Customers → Sites · /app/w/{workspace}/sites · sites.view / create / update / delete (Archive)

A site cannot exist without a customer. One customer can have many sites. Do not create a new customer merely because the same organization has another building.

A van stock location is not a site.

Create a site

Two equivalent paths. Customer is always required.

1. Global: Customers → Sites → New site. Or from the customer: open the customer → Sites → Add site.
2. Customer (required). Searchable select if not prefilled.
3. Status — Active or Inactive when office creates the site. Portal-created sites start as Pending review (not operational until office approves).
4. Name (required) — what office and Field will see (for example “Main plant”).
5. Service address — Line 1 / 2, City, State / Province / Region, Postal / ZIP, Country. This is the dispatch address.
6. Timezone — defaults to the workspace default. Wrong timezone makes Field “today” and dispatch calendars drift.
7. Latitude / Longitude — optional. On the site profile, Geocode address fills coordinates from the street (not live GPS, not a tracking product). Empty coordinates mean the map pin and travel intelligence have nothing to use.
8. Access instructions and Parking instructions — shown on the Field job. Internal notes stay in the office.
9. Tags and required custom fields. Save.

Profile (no tabs)

Main column typically: Access · Parking · Internal notes · Comments · Files · Activity · Site contacts · Covered by (agreements) · Maintenance plans · Upcoming maintenance · Assets (Add asset) · Service requests · Work orders.

Right column: Site details · Customer · Service address · Coordinates (+ Geocode) · Custom fields.

Portal submissions

When a customer creates a site in the portal, the row exists immediately with status Pending review. Dispatch, booking, and office site pickers ignore it. Notice: This record was submitted from the customer portal and is waiting for review.

Header (and list row) actions with sites.update: Approve / Reject. Confirm: Approve this customer portal submission? Approve sets Active. The same actions exist on the customer profile under Pending portal submissions.

What uses the site

• Work orders and appointments pick a site (recommended, not always required on the form).
• Dispatch map pins and travel use site address and lat/lng when maps/travel settings are on.
• Field PWA uses site timezone for “today”, plus access/parking on the job. Technicians do not edit the site master record.
• Public booking can create or match a site from the guest address.
• Service reports and issued invoices can snapshot the site that was on the job.

There is no live van GPS in this product. Geocode is a one-shot address lookup.

Timezone errors look like missing jobs

Set the site timezone before blaming Field sync. The server sends the site/workspace schedule; the phone’s clock zone is not a second source of truth for “today.”

What-if

If you cannot save: Customer and Name required. There is no orphan site.

If Geocode address fails: check the street/country and maps/geocode settings; you can still type lat/lng.

If you put the street only on customer billing: dispatch and Field miss the location.

If you expect live tracking from a map pin: pins are site coordinates, not vans.

Related: Customers, Contacts, Assets, Dispatch, concept Site.