Running the Scheduler Day to Day

Start from backlog, not from an empty calendar

Open the backlog strip first so unscheduled work is visible before you drag anything into the planner.
Triage whether each item belongs in the current day, later in the week, or still needs more site context before deployment.
Keep the backlog visible instead of hiding demand in external spreadsheets.

Use Target month when the office knows the service month but not the exact day yet.
Treat month-planned work as planning demand, not as field-ready deployment.
Do not force these jobs onto the last day of the month just to keep them visible.
When the planner gains a real day and time, convert the record to Exact date by dragging it onto the planner or saving a real scheduled slot.
If a row still reads Planned for ..., engineers should not treat it as a committed visit.

Treat the field-work toggle as the boundary between office coordination and live field assignment.
Only members with field work enabled should appear in assignment pickers for inspections, scheduler tasks, day runs, recurring imports, and work orders.
If a coordinator needs scheduler access but should never be dispatched, keep scheduler access on and field work off.
When a member disappears from the planner lanes, check workspace membership and field-work status before assuming the planner data is wrong.

Use day or week timelines when timing and crew capacity matter.
Use list or compact views when you are cleaning up many records quickly.
Use map context when site location and travel friction are the real scheduling constraint.

Use quick view to confirm dates, assignment, visit context, and deployment intent without leaving the main planner.
Choose either Exact date or Target month. Exact-date edits must include a scheduled date and time; target-month edits must include a month.
Use quick view for one-job changes only: assignee, scheduling intent, booking status, engineer visibility, duration, task status, and priority where that job type supports it.
Record customer appointment notifications only when the visit has an exact date, customer email, and booking status of Date offered or Confirmed.
Use Full edit when you need operational metadata, schedule windows, flex days, crew size, equipment, or out-of-hours flags.
Keep the main workspace dominant while supporting panels collapse out of the way when they are not active.

Draft work is planning state.
Deployed work is what field resources should trust.
Make the transition deliberately so the mobile team is not reacting to half-finished office edits.
Month-planned work should stay draft until an exact slot exists, even if the month itself is already known.
Use Ready to deploy for records that have an assigned engineer, exact date and time, active status, and no blocking warnings.
Re-deploy after changing the date, assignee, or duration on deployed work because those changes return the job to draft and reset acknowledgement.

Once a visit is complete, hand review into inspections, reports, or commercial follow-up instead of leaving the job stranded in scheduling state.
Keep a clean link between the scheduled work, the returned inspection, and any defect or remedial action that follows.

Problem	What to check
The planner feels cluttered	Collapse secondary panels and switch to the view that matches the decision you are making.
Unschedule demand keeps disappearing from sight	Return to backlog and confirm work is not being hidden in draft-only records.
The team is booking everything on month-end as a reminder	Replace that workaround with `Target month`, then convert to an exact date only when the visit is genuinely booked.
The right person is missing from the assignment controls	Check whether the member is office-only or has field work enabled in the workspace.
Field resources act on the wrong version of the job	Confirm whether the record was still draft or had already been deployed.
A target-month job will not deploy	Convert it to an exact scheduled date and time first; target-month work is planning demand, not field-ready work.
A locked visit cannot be moved in bulk	Check whether the booking status is `Do not move` and review the bulk preview blockers.
A customer notification button is disabled	Confirm exact date, customer email, and booking status `Date offered` or `Confirmed`.

Use Scheduling for the planner, backlog, deployment, and assignment mechanics behind this daily-ops guide.
Use Planner Control and Capacity for booking status, buckets, visibility, customer notifications, bulk preview, and PPM forecasting.
Use Dashboard and Map when day-run triage starts outside the scheduling desk.
Use the Admin Route Interaction Matrix to trace where a scheduled record flows next after deployment or completion.