What the Scheduling pages are for
Four views of the same pending work, each suited to a different way of planning: one day on a map, a week across the team, a month on a calendar, and a route the computer proposes.

Every scheduling page draws from one list: jobs that have no scheduled date yet. Drag a job out of that list onto a technician and it is scheduled; the other three views see it immediately. Pick the view that matches the question you are asking. "Who is free at nine tomorrow?" is a Dispatch question. "Can we absorb next week's contract work?" is a Team Scheduling question. "Where is the quiet week this month?" is the calendar. "What is the shortest way to cover all of it?" is the Routing Workbench.

Scheduling Team Scheduling Monthly Schedule Routing Workbench

Scheduling

Open Scheduling
Who it is for
The dispatcher, running today and tomorrow.
Without it
A day is planned on a whiteboard or a spreadsheet with no idea where the jobs actually are. Two jobs an hour apart get the same technician, and a job across town gets whoever was free on paper.
What it shows
A dispatch board for one day. A toolbar with Office, Priority, Type, Attribute and Metro filters and day navigation with a Today button. A split pane: a map (Map or Satellite, Fit to all jobs) showing the day's jobs and technicians, and beneath it a grid with a technician list on the left and a time grid on the right, with a resize handle between them. A Pending Jobs panel on the right lists unscheduled work with its own filters, a search box, an anticipated-start-date filter and a colour legend for status, priority and attributes. Jobs are dragged from the panel onto a technician's row; the panel collapses when the map needs the room.
What it is worth
  • Geography on the board. The map and the grid are the same day, so a job is placed by where it is, not just when.
  • Drag, and it is scheduled. Dropping a job onto a technician's row sets the date, the time and the assignee in one motion and moves the job from Pending to Scheduled.
  • The pending list is filtered the way you work. One office, one metro, one priority, and the panel shows only what you are placing today.
Pays for itself the first time a job is dragged onto the technician who is already on that street rather than the one who was free on paper.

Team Scheduling

Open Team Scheduling
Who it is for
The dispatcher or office manager planning the week ahead.
Without it
A day view cannot show that Tuesday is empty and Thursday is double-booked. Balancing a week means paging day by day and holding the picture in your head.
What it shows
The same drag-and-drop against a multi-day grid: day headers across the top, a row per technician, previous and next week. A pending-jobs sidebar on the left with Office, Priority, Attribute, Type, Metro and Anticipated Start Date filters and a search box. When the filters leave nobody, the grid says "No Technicians Available" rather than rendering an empty board.
What it is worth
  • The week in one glance. Light days and heavy days are visible side by side, so work can be moved to balance them.
  • Per technician, per day. A row per person shows who is loaded and who has room, across the whole week.
  • Same pending list, same drag. Nothing new to learn after Dispatch; only the horizon changes.
Pays for itself the first Friday the following week is already balanced before anyone leaves.

Monthly Schedule

Open Monthly Schedule
Who it is for
The office manager placing contract work and multi-week commitments.
Without it
Contract inspections arrive in batches with a due month, not a due day. Placing them a week at a time hides the month's shape, so the quiet week goes unused and the busy week gets busier.
What it shows
A month calendar with the pending-jobs sidebar on the left, filtered by Office, Priority, Type, Attribute, Metro and Technician plus anticipated start date. Dropping a job onto a day opens an Assign popover asking for the technician and the time. Days with more jobs than fit show a "+N more" popover. Previous month, next month and Today navigation.
What it is worth
  • The month's shape. Which weeks are full and which are open, before anything is placed.
  • Assign on drop. The popover asks for technician and time at the moment of placement, so a day-level plan still lands as a real appointment.
  • Filter by technician. See one person's month to find the gap that fits a long job.
Pays for itself the first month a batch of contract inspections is spread across four weeks instead of stacked into the last one.

Routing Workbench

Open Routing Workbench
Who it is for
The dispatcher with a backlog of pending jobs and a window of days to fit them into.
Without it
Routing by hand optimises one technician at a time and never sees the whole board. Drive time is the cost nobody measures, and the technician who can do the hard work spends the morning on jobs anyone could do.
What it shows
A toolbar in two rows. What to route: search plus the same Office, Priority, Type, Attribute and Metro filters as Scheduling, with inspection and service type so a plan can be, say, only fire alarm inspections. How to route it: Schedule From and Schedule Through dates, a Drive Cap in minutes per day, and a Senior Preservation toggle. Solve produces a proposed plan with the drive-time savings on screen; jobs it could not place appear in their own list with the reason. Pin a stop to lock it to that technician and day, change a setting, and solve again. Publish writes the plan and produces a per-job report. A How This Works modal explains the model.
What it is worth
  • Drive time becomes a number. The savings figure is on screen before anything is committed.
  • Nothing is saved until you publish. Solve, pin, re-solve and compare, then publish the plan you like.
  • Senior people kept for senior work. Senior Preservation holds your most capable technicians free for the jobs only they are qualified to do.
  • Existing appointments are respected. Jobs already on a calendar appear greyed as Already Scheduled: they keep their times, count toward capacity and driving, and are never moved.
Pays for itself the first published week whose savings figure is more than one technician-day of driving.

Where to go next

  • The Routing Workbench can only place a job on a technician whose capabilities cover it. Capabilities are maintained under Technician Capabilities, and where each technician's day starts and ends under Work Day Locations. An empty grid there means the router places nothing, which is correct rather than broken.
  • For whether the team has the hours for the months ahead, see Workload & Capacity under Analytics. Its supply line is the same work-week and PTO model the router uses.
  • For contract occurrences that are inside their lead time with no job yet, see the Obligations Calendar.

Good to know

  • Pending means no scheduled date. All four views feed from jobs with no scheduled date. Scheduling one on any view removes it from the pending list on all of them.
  • Publishing a plan flips Pending to Scheduled, the same status change Dispatch makes when you drag a job onto a technician.
  • Completed and cancelled jobs are not obstacles. They keep their date and assignee for the record but take up no room on any board.
  • A job that needs more than one day is not routed. The workbench leaves it unplaced with an Exceeds One Day reason; place it by hand on Team or Monthly Scheduling.
  • A technician with an early fixed job still gets new work. An existing 8:00 appointment no longer blocks the rest of that technician's day in the router.