Keep one calm planner surface in charge of the day.

What the scheduler controls now

1. Use the scheduler as the office source of truth for assignment, timing, backlog pressure, and release into live field work.
2. Keep one dominant planner surface on screen. Secondary surfaces such as the planner list, activity rail, map, and advanced filters should support the decision rather than compete with it, and they should reopen collapsed by default when you return.
3. Treat engineer cards and job cards as part of the same planning language: compact, dense, and easy to scan without opening a second desk. Engineer cards are informational surfaces, while the job card body is the quickest way into quick view.
4. Use quick view to inspect and edit the visit in place when you do not need the full record screen, whether you open it from a job card or from the planner list.

Start with the backlog and planning horizon

1. Begin with the backlog strip above the workspace so unscheduled work stays visible without drowning the day view.
2. Use the backlog to decide what needs assignment, what needs a date, and what should remain planner-only until the office is ready to release it.
3. Keep the strip compact by default and expand it only when you need to work a larger unscheduled queue or drag several visits into the live planner surface.
4. Keep the top cockpit light but informative: counts, attention chips, and status signals should tell you where the pressure is without turning the planner into a dashboard wall.
5. Open advanced filters only when you need a sharper slice by engineer, site, or status. The default state should stay clean.

Use the right planner view for the decision

1. Use Board when you need to rebalance workload, move jobs across engineers, and work the backlog quickly.
2. Use Week timeline when the question is capacity across several engineers or several days, not same-day sequencing.
3. Use Day timeline when sequence, spacing, and same-day workload matter more than the broad weekly picture.
4. Use Map as a secondary geographic aid rather than a co-primary control surface.
5. Use the planner list as a secondary slide-open pane for inspection and quick review, not as the main planning desk. A row click should help you jump into quick view rather than pull you out of the scheduler.

Move work through draft, ready, and deployed states

1. Keep new or incomplete work in draft while the office team is still shaping assignment, timing, or visit details.
2. Treat ready work as scheduler-approved but not yet released. This is the staging point before the field sees the visit.
3. Treat deployed work as released field work. This is the moment the visit becomes part of the live engineer picture.
4. Keep the line between planner-only work and engineer-visible work explicit so the office can prepare visits without creating noise in the mobile day-run.

Deploy work and understand engineer visibility

1. Use the sticky command bar for selection-driven actions such as deploy, bulk update, and run-building rather than hunting for commands around the page.
2. Deploy only the work that is genuinely ready. Engineers should see released visits, not half-prepared planner drafts.
3. Use the activity rail to review recent changes and deployment history without interrupting the main workspace.
4. Remember that the scheduler can keep its last primary view, but secondary panels should reopen collapsed so the next session starts clean.
5. Keep run builder selection-driven as well. If nothing is selected, the main workspace should stay the focus instead of opening extra tooling by default.

Adjust live work without losing control

1. Open quick view from the job card body when you need to inspect or edit the visit without leaving the current planner slice.
2. Use quick view for the common edits: assignee, date and time, duration, status, and priority where that applies. Save explicitly when you are happy with the change, then use full record navigation only for the heavier admin work.
3. Expect ordinary edits to keep the planner context stable. The day or week surface should stay in place rather than visibly reloading after every small change.
4. If an edit moves a job out of the current slice, let it leave the view and confirm the outcome with a toast instead of trying to hold stale context on screen.
5. Use moderate keyboard support where it speeds the desk up: Enter opens quick view on a focused card, Escape closes dialogs or drawers, and the desk should stay usable without extra pointer travel.

Close the loop with inspections, defects, and follow-on work

1. Once a visit is completed, move into the inspection desk to confirm output, certificate quality, and any operational gaps that still need follow-through.
2. Use defects as the remediation queue, not as a historical note archive. Open issues should flow into real operational or commercial next actions.
3. When work becomes remedial or commercial, move cleanly into quotes, work orders, and finance rather than leaving follow-up trapped inside the scheduler.

Troubleshooting