Deucalion Docs
Admin Reference
ReferenceAn information-oriented lookup resource. Use it to find specific values and definitions.
adminschedulingplannerdeploymentday-run

Scheduling Route Reference

Understand the planner’s board, timeline, map, selection actions, quick-view tools, and dynamic handoffs into sites, inspections, work orders, and AI context.

Before you start

  • You need the route-level planner behaviors behind Deucalion’s scheduling workflows.

Expected outcome

You can use the scheduler deliberately across board, timeline, and map views, and understand how deployed work reaches the engineer app.

What this route is for

Scheduling owns planning, assignment, booking status, engineer visibility windows, customer notification records, deployment, backlog review, bucket lanes, day-run construction, and fast drill-in to inspection and work-order detail routes.

Visibility and capability notes

ItemDetails
Route idscheduling
VisibilityCustomer-facing route, but scheduler capability still governs whether it appears in some workspaces.
Capability notesThe route is also sensitive to engineer field-work eligibility and route-aware AI availability.
Direct inboundShell nav, dashboard, map, inspection and work-order planning handoffs, and site-scoped scheduling launches.

Main regions, views, and dialogs

SurfaceWhat it does
Planner viewsboard, timeline, and map answer different planning questions.
List modeOptional list-style queue beside or inside the planner context.
Bucket lanesPlanning buckets hold work that is grouped but not necessarily assigned to a field resource.
Guidance and activity railSurfaces warnings, planner guidance, and current context.
Selection regionAppears when jobs are selected for bulk actions.
Dialog layerWarnings, engineer rules, quick view, task, bulk update, customer notification, day run, recurring import, and batch inspection workflows.

Key actions

  • Reassign, reschedule, or drag work across the planner.
  • Open quick view for one job without leaving the planner.
  • Set booking status to provisional, date offered, confirmed, or do not move.
  • Set engineer visibility windows for individual or bulk jobs.
  • Record customer appointment notifications for exact-dated offered or confirmed visits.
  • Build day runs.
  • Run batch inspection planning.
  • Maintain engineer rules.
  • Start recurring imports.
  • Preview bulk edits before applying them.
  • Export scheduled work.
  • Refresh the scheduler workspace.
  • Launch AI Assistant with the current slice or selected jobs.

Filters and URL state

State groupParams
Date windowstart, end, timelineDate, timelineMode
Core filtersengineerId, siteId, jobType, status, q, focus
View and panelsview, list, listMode, filters, guidance, guide, panel
Selectionselected
  • focus supports operational slices such as all, blocked, flagged, unassigned, unscheduled, draft, ready, and deployed.
  • Quick view and bulk edit can update booking status and engineer visibility, but customer appointment notifications require an exact date and a booking status of Date offered or Confirmed.
  • Scheduler state is heavily hash-backed so office teams can reopen the same planning slice directly.

Outputs and side effects

  • Changes assignment, scheduling, deployment, selected-job state, booking status, bucket assignment, engineer visibility windows, and customer notification history.
  • Opens and completes planning workflows such as day runs, recurring imports, and bulk updates.
  • Bulk preview returns valid, warned, and blocked jobs plus route suggestions for the selected work.
  • Sends live work visibility to engineers once jobs are deployed and assigned correctly.
  • Exports scheduled work for external coordination.
  • Shell Scheduling navigation.
  • Dashboard header and cards.
  • Map site popup.
  • Work-order or inspection planning prompts.
  • Scheduler-aware warning links from site or planner context.
  • #/sites?siteId=... from warning and context actions
  • Job detailHref routes into #/inspections?... and #/work-orders?...
  • #/ai-assistant with planner context

Indirect handoffs

  • Engineer rules and field-work eligibility control who can appear as an assignee.
  • Site completeness and access notes shape whether the planner can be used confidently.
  • Deployed work becomes the engineer app’s live day-run reality, so scheduling errors propagate fast.

Troubleshooting

SymptomWhat to check
A field user is missing from the assignee pickerConfirm field work is enabled. This is often an eligibility rule, not a user-sync problem.
A deploy action is blockedReview warning and deploy-preview guidance first.
The wrong slice keeps reopeningCheck the hash state for saved view, focus, and date params.
Jobs are visible in the planner but not to engineersConfirm assignment, deployment state, and the correct workspace membership.
A customer notification cannot be recordedConfirm exact scheduled date, customer email, and booking status Date offered or Confirmed.
A bulk move is blockedCheck deployed state, Do not move booking status, and deployment blockers in preview.

On this page