Admin Reference
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
| Item | Details |
|---|---|
| Route id | scheduling |
| Visibility | Customer-facing route, but scheduler capability still governs whether it appears in some workspaces. |
| Capability notes | The route is also sensitive to engineer field-work eligibility and route-aware AI availability. |
| Direct inbound | Shell nav, dashboard, map, inspection and work-order planning handoffs, and site-scoped scheduling launches. |
Main regions, views, and dialogs
| Surface | What it does |
|---|---|
| Planner views | board, timeline, and map answer different planning questions. |
| List mode | Optional list-style queue beside or inside the planner context. |
| Bucket lanes | Planning buckets hold work that is grouped but not necessarily assigned to a field resource. |
| Guidance and activity rail | Surfaces warnings, planner guidance, and current context. |
| Selection region | Appears when jobs are selected for bulk actions. |
| Dialog layer | Warnings, 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 group | Params |
|---|---|
| Date window | start, end, timelineDate, timelineMode |
| Core filters | engineerId, siteId, jobType, status, q, focus |
| View and panels | view, list, listMode, filters, guidance, guide, panel |
| Selection | selected |
focussupports operational slices such asall,blocked,flagged,unassigned,unscheduled,draft,ready, anddeployed.- 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 offeredorConfirmed. - 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.
Inbound links
- Shell
Schedulingnavigation. - Dashboard header and cards.
- Map site popup.
- Work-order or inspection planning prompts.
- Scheduler-aware warning links from site or planner context.
Outbound links
#/sites?siteId=...from warning and context actions- Job
detailHrefroutes into#/inspections?...and#/work-orders?... #/ai-assistantwith 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
| Symptom | What to check |
|---|---|
| A field user is missing from the assignee picker | Confirm field work is enabled. This is often an eligibility rule, not a user-sync problem. |
| A deploy action is blocked | Review warning and deploy-preview guidance first. |
| The wrong slice keeps reopening | Check the hash state for saved view, focus, and date params. |
| Jobs are visible in the planner but not to engineers | Confirm assignment, deployment state, and the correct workspace membership. |
| A customer notification cannot be recorded | Confirm exact scheduled date, customer email, and booking status Date offered or Confirmed. |
| A bulk move is blocked | Check deployed state, Do not move booking status, and deployment blockers in preview. |