Great field operations start with clear guidance

What this guide covers

This guide explains how to coordinate time, assignments, and dispatch flow for Create and Manage Schedule Events. 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 /schedule and confirm you are operating in the intended workspace and environment.

Route checklist

• /schedule
• /schedule/new
• /schedule/[id]/edit

Step 2: Complete the core workflow action

Use /schedule/new to create an appointment, use the event detail sidebar on /schedule to open Edit Event, or drag an existing appointment directly on /schedule to reschedule it.

• Dragging snaps to 15-minute increments.
• While you drag, the calendar shows a lighter projected placeholder so you can confirm the exact drop target before release.
• Existing appointments can now be moved anywhere on the daily grid from 12:00 AM through 11:45 PM, and long appointments keep their full duration even when they continue overnight or into the next day.
• The Address input on /schedule/new and /schedule/[id]/edit now searches existing properties first and then falls back to additional address matches, while still allowing manual typing when you need to enter a brand-new location.
• Shared address suggestions now finalize on the first click or tap, so schedule and Find a Time address picks close cleanly as soon as the structured location is applied.
• The schedule event form now separates Start Date, End Date, Start Time, and End Time, so overnight and multi-day work can be saved explicitly instead of relying on one shared service date.
• The Start Date, End Date, Start Time, and End Time fields on /schedule/new, /schedule/[id]/edit, and Find a Time now use the same shared picker pattern: open the calendar or time dropdown for fast selection, or type the value manually when you already know it.
• The summary card on /schedule/new and /schedule/[id]/edit now includes the current event title alongside type, date range, time, and color so you can review the whole appointment at a glance before saving.
• /schedule now uses the header New Event action as the primary create path, so you no longer need a separate floating + button in the lower-right corner of the schedule board.
• The More menu on /schedule now supports a branded Print action that opens a print-friendly schedule document without the dashboard controls, and Settings now routes directly to /settings/scheduling. Export is not currently offered from this menu.
• Weekly and monthly /schedule views now tighten their column spacing on tablet and desktop widths so all seven day columns stay visible on screen instead of forcing oversized calendar panes.
• /schedule now stays inside the dashboard shell with one intended schedule scroll surface, which removes the redundant double-right-scrollbar behavior and keeps the bottom horizontal scrollbar out of normal day, week, and month usage.
• Creating or saving an event now returns you to /schedule focused on the saved start date, and unassigned events render on the calendar immediately instead of disappearing from the grid.
• After you drop the appointment, the move saves in place without reopening the event detail sidebar, and the UI shows an Event moved toast when the update succeeds.
• Assigned team members receive an email notification when a schedule move changes their assigned event time.
• From the event detail sidebar, Edit Event now opens /schedule/[id]/edit with the current event loaded, uses a cache-first active team-member list for assignment, shows cached avatars/names/email addresses immediately in both the create and edit assignee picker, keeps assignment in one dropdown that shows either the selected team member or Unassigned, lets you clear the assignee from that same dropdown, includes an Add New Team Member shortcut to /team/new, respects the company time-format default from /settings/company/regional, and saving returns you to /schedule with the updated title, time, assignment, and location.
• Find a Time now uses the same shared address-search behavior for the service-address field, so travel-time slot suggestions and the final saved schedule location use the same address source.

Step 3: Validate downstream impact

After the main action completes, verify that related modules reflect the update. When rescheduling by drag-and-drop, confirm the appointment card shows the updated start and end time immediately, continues onto the next day when the duration crosses midnight, and still matches after a page refresh. When creating an event without an assignee, confirm it still appears on /schedule right away, remains visible in weekly, daily, and monthly views for the saved date, and the Team filter keeps Unassigned enabled. When you clear an assignee on /schedule/new or /schedule/[id]/edit, confirm the same dropdown immediately switches to Unassigned and the saved event stays unassigned after refresh. Confirm the assignees on the event receive the schedule-update notification if the time changed. When editing through /schedule/[id]/edit, confirm the updated event details appear on /schedule immediately after save and still match after a refresh. Confirm the calendar popover still opens from both date fields, the time fields still work with both dropdown selection and manual typing, and overnight work now saves with the correct next-day end date before you hand the appointment off. If you selected an address suggestion, confirm the saved event location still matches after a refresh and that Find a Time recalculates availability when the service address changes. On narrower desktop or tablet widths, confirm both the week view and month view still keep all seven day columns visible before you hand work off to the field team. Confirm the schedule view now scrolls through one intended vertical calendar surface instead of showing an extra nested scrollbar on the right. If you use More > Print, confirm the print preview shows company branding at the top, excludes dashboard chrome, and fits the current schedule view cleanly before saving as PDF. The expected downstream impact for this area is higher on-time performance and fewer overlaps.

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. If a drag-reschedule snapped back, refresh once and confirm the appointment still reflects the last dropped time. For overnight events, verify the continuation block appears on the next day instead of collapsing to a 15-minute card at the bottom of the first day.

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

• Use Team Filters and Dispatch Mode
• Add and Manage Team Members