Great field operations start with clear guidance

What this guide covers

This guide explains how to maintain accurate service-location records for Create and Manage Properties. It is written for the current JobsiteOn implementation and avoids assumptions about unshipped behavior.

Before you begin

• Confirm you can access the relevant route(s) for this workflow.
• Use sandbox first when testing a new process or policy update.
• Keep this article open while you execute each step so your team can follow one consistent path.

Workflow overview

1. Open the correct route and confirm workspace context.
2. Complete the core workflow action in order.
3. Validate downstream impact before handoff.
4. Document exceptions and close the loop with your team.

Step 1: Open the correct route and confirm context

Start from /properties and confirm you are operating in the intended workspace and environment.

Route checklist

• /properties
• /properties/new
• /properties/[slug]
• /properties/[slug]/edit

Step 2: Complete the core workflow action

Follow the route sequence above from first screen to final save/submit point. Avoid skipping fields or intermediate review states during first-pass execution.

• /properties/new now uses a shared address-search field for Address Line 1.
• The field searches existing properties first, then Google Places results, and selecting a result fills the street, city, state, ZIP, and line 2 when available.
• Address suggestions now finalize on the first click or tap, so the search menu closes as soon as the structured address is applied.
• Manual entry still works when you need to type a new location directly.
• /properties/[slug] now focuses on Overview, Quotes, Jobs, and Invoices; the old Procedures tab is no longer part of the visible properties workflow.
• /properties/[slug] now shows the full saved address once in the page header, including city, state, and ZIP, instead of repeating the same address block multiple times at the top of the route.
• If a property contact matches an existing contact record, the Manage Contacts action on /properties/[slug] opens that linked /contacts/[slug] record instead of leaving the user on a dead-end button.
• /contacts/[slug] now includes a Properties tab so office staff can jump back to the correlated property detail route from the contact record.
• Use the Edit Property button on /properties/[slug] to open /properties/[slug]/edit, update the saved address/settings fields, and return to the property detail view after save.

Step 3: Validate downstream impact

After the main action completes, verify that related modules reflect the update. If you selected an address suggestion, confirm the property reopens with the same structured address fields after save. The expected downstream impact for this area is reliable scheduling, execution, and billing context.

Step 4: Handle exceptions quickly

If the expected result does not appear:

1. Refresh the current page and confirm the record status.
2. Verify required linked entities (contact/property/team/job/invoice context as applicable).
3. Re-run the action in sandbox if live-state confidence is low.

Step 5: Keep the process repeatable

Capture the final operating sequence for your team and reuse this article as the reference runbook. When behavior changes, update this article in the same change set as the product update.

Validation checklist

• Primary route opened successfully.
• Core action completed without blocking errors.
• Downstream module behavior matches expected workflow.
• Team handoff information is complete.

Troubleshooting

I cannot access one of the listed routes

Confirm account permissions and environment selection. If access is still blocked, route the issue to your admin/support path with the exact URL.

I saved changes but I do not see the result

Reload the route, confirm linked records, and validate whether this workflow is beta-gated in your workspace.

My screen layout looks different

Layout can vary by feature flags or viewport size. Keep following route names and workflow checkpoints from this guide.

FAQ

Is this available in every workspace?

This guide documents generally available behavior in current production routes.

Should we run this in sandbox first?

Yes. Sandbox-first execution is recommended for process changes and first-time team rollout.

How often should this process be reviewed?

Review whenever related auth/onboarding/module/release behavior changes.

Notes

This article covers currently available behavior in active production routes.

Related Articles

• Create and Manage Contacts
• Create and Manage Jobs