Dispatch coordinator dashboard
The dispatch coordinator dashboard in Thermal shows the live board a dispatcher works from all day — today's schedule, technician windshield time, and SLA countdown timers for every open work order, in one screen instead of a spreadsheet and three browser tabs.
The tiles.
- Live scheduleToday's assignments and technician availability, updated as jobs move.
- Windshield timeDrive time next to each assignment so a bad routing decision is caught before the tech is on the road — see windshield time.
- SLA countdownA response or resolution clock on every work order with a commitment attached, tied to schedule adherence.
- RoleThe board a dispatcher works from all day — the same jobs as the full dispatch screen.
How it's used.
What dispatchers see here
A dispatcher's job is to keep the schedule full, techs moving efficiently between jobs, and commitments to customers on time. This dashboard is built around those three jobs: a live schedule view, a windshield-time strip showing drive time between stops, and an SLA countdown for every work order with a response or resolution commitment attached.
It's the same board a dispatcher uses to assign and reassign work throughout the day, not a separate reporting layer — moving a job on the schedule updates the dashboard immediately, and a technician running late updates the SLA countdown the same way.
Schedule adherence and windshield time
Schedule adherence measures how closely technicians are hitting their promised arrival windows — the number that predicts angry customer calls before they happen. The dashboard flags a job as at-risk before it's late, giving a dispatcher time to call ahead or reassign rather than explain after the fact.
Windshield time — the drive time between jobs — is the other lever dispatchers pull constantly. A schedule that looks full on paper can still be inefficient if technicians are crossing town twice a day. The dashboard shows drive time next to each assignment so a dispatcher can spot a bad routing decision before committing to it, not after the tech is already on the road.
Working SLA commitments in real time
Dispatch efficiency depends on knowing which jobs have a contractual response or resolution clock running and which don't. The dashboard surfaces SLA countdowns pulled from the same service agreement records Thermal's agreement engine tracks, so a dispatcher isn't cross-referencing a separate contract spreadsheet to know which job needs to move first.
The SLA compliance report extends this into a rollup view — which agreements are at risk this month, which branch is missing the most commitments — for a service manager or ops lead who needs the trend, not just today's board.
How this fits the rest of the schedule
The dispatch coordinator dashboard is a lens on the same scheduling engine that powers Thermal's dispatch board — it doesn't hold separate data. A dispatcher working from this dashboard and one working from the full dispatch screen are looking at the same jobs, updated the same way, in real time.
Questions about this dashboard.
What's the difference between this dashboard and the full dispatch board?
This dashboard is a focused summary view — schedule, windshield time, and SLA status — built for a quick daily check. The full dispatch board at /dispatch is where a dispatcher does the actual scheduling and reassignment work.
How does the dashboard calculate windshield time?
It uses the drive time between a technician's consecutive stops for the day, based on the addresses on each work order and service site.
What happens when a job is at risk of missing its SLA?
The dashboard flags the job before the SLA window closes, based on the commitment on the linked service agreement, so a dispatcher can reassign or call the customer ahead of a miss instead of after one.
Does this dashboard work across multiple branches?
Yes. A dispatcher can filter to their own branch or see cross-branch coverage when a job needs to move between them.
These views, on your own branch.
If you want to see what they look like with your backlog, utilization, and agreement data loaded, that's a demo.