Controlling Planner Status, Visibility, and Capacity
Use booking statuses, planning buckets, engineer visibility windows, customer notifications, bulk previews, and workload forecasting to keep the scheduler safe.
Before you start
- Scheduler is enabled for the workspace.
- Scheduled work exists as inspections, work orders, or planner tasks.
- Planners understand draft versus deployed work.
Expected outcome
Planners can control what is provisional, customer-offered, confirmed, locked, field-visible, and ready for capacity review.
Use booking status deliberately
Every scheduled item can carry a booking status.
| Status | Use it when |
|---|---|
Provisional | The office is still planning and should not treat the date as customer-confirmed. |
Date offered | The customer has been offered the appointment but has not fully confirmed it. |
Confirmed | The appointment is agreed and can be treated as customer-confirmed. |
Do not move | The visit is locked and should not be moved through ordinary bulk or drag changes. |
Use Do not move sparingly. It blocks movement previews so planners have to make a deliberate decision before changing a locked visit.
Only Confirmed and Do not move can enter the Ready pipeline. Provisional and Date offered keep the visit in planning even when it already has an engineer and exact time.
Put planning demand into buckets
Planning buckets hold work that needs a lane but not necessarily an engineer yet.
- Use bucket lanes for planning groups such as reactive work, access-dependent work, or work waiting for a specialist team.
- Keep work with no scheduled date in the Work queue.
- Use the Dated work lane, subtitled Needs an engineer, for dated work that has not been assigned to a field resource yet.
- Drag bucketed work onto an engineer lane when it is ready for direct assignment.
- Archive buckets only after active references have been cleared or moved.
Bucketed work appears in the Scheduling Forecast view as bucketed demand, which helps separate capacity pressure from named-engineer assignment.
Control engineer visibility
- Open a job in the Planner quick view drawer or Bulk Update drawer.
- Set
Visible fromwhen engineers should not see the job before a specific time. - Set
Visible untilwhen the job should stop being visible after a specific time. - Save the planner change.
The visibility window must be valid. Visible until cannot be before Visible from.
Engineer visibility is separate from deployment. A job still needs the usual deployment readiness before it becomes trusted field work.
Record customer appointment notifications
- Open a scheduled item in the Planner quick view drawer.
- Confirm the job has an exact scheduled date.
- Set booking status to
Date offeredorConfirmed. - Confirm the customer email.
- Choose appointment confirmed, appointment changed, or appointment reminder.
- Select
Notify customer. - Review notification history in the quick-view panel.
Customer notifications are recorded only for exact-dated work with a customer email and an offered or confirmed booking status. Target-month work is not a customer appointment.
Preview bulk changes before applying
- Select one or more scheduler jobs.
- Click Bulk edit.
- Turn on only the fields you intend to change.
- Click Preview Changes.
- Review valid, warned, and blocked counts.
- Read blocked-job reasons and warnings.
- Review route suggestions when the selected work overlaps route clusters.
- Apply only when there are no blocked jobs.
Bulk preview blocks deployed jobs, locked Do not move movement, and deployment blockers. It also warns when the updated plan still carries non-blocking warnings.
Use Forecast before the pressure becomes urgent
- Open Scheduling and switch to Forecast.
- Review the 12-month planning window.
- Check forecast jobs, estimated hours, unassigned work, and utilisation.
- Use the monthly table to open the matching Scheduling date range.
- Use service-line, region, and site load lists to spot concentrated pressure.
Forecast reads inspections, work orders, and planner tasks by booked date or target month across every accessible site. It does not inherit planner filters. It works best when planners use target months for known future demand instead of forcing every job onto an arbitrary date.
Troubleshooting
| Problem | What to check |
|---|---|
| Bulk apply is disabled | Run preview and resolve blocked jobs first. |
| A job cannot be moved | Check whether it is deployed or marked Do not move. |
| Customer notification is disabled | Confirm exact date, customer email, and booking status Date offered or Confirmed. |
| Engineers see work too early or too late | Check engineer visibility windows and deployment state. |
| Forecast utilisation looks wrong | Check future dates, target months, estimated duration, and field-resource capacity. |
Related guides
- Use Scheduler Quickstart for the planner workflow, deployment, and day-run controls.
- Use the Forecast view in Views and Navigation for capacity forecast detail.
- Use Bulk Operations and Deployment for deployment-specific behavior.
Planning and Operations
Run the scheduler as a daily operations surface — manage the work queue, build day runs, import recurring work, and monitor deployment readiness.
Finding and Booking the Right Slot
Use Find slot, warnings, field-resource profiles, bulk preview, and day-run planning to choose a suitable engineer and time before deployment.