Six views, one dataset
Day, week, month, technician columns, dispatch grid and map. Change something in one and it is changed in all of them, live over WebSocket.
Dispatch & scheduling
The board your dispatcher actually wants
One surface for the whole day — drag work between technicians, watch the trucks move, and see the conflicts before the customer calls about them.
Scheduling that knows the job
Durations come from the pricebook and the assigned technician's pace, so a slot is the length the work actually takes rather than a default hour.
AI that suggests, never decides
The scheduler scores technician-to-job fit on skills, location and history and proposes a plan. A dispatcher approves it.
What's in it
- Drag-and-drop and drag-to-resize scheduling
- Recurring jobs with a proper recurrence model, not copied rows
- Route optimisation and turn-by-turn via Google Maps
- Live GPS tracking with vehicle overlay on the board
- Capacity planner forecasting demand thirty days out
- Time-off requests that block the board
- Batch edit across many jobs at once
- Weather-aware rain-friendly flagging
- Colour the board by status, technician, team or service
- Saved views per dispatcher
Questions
Does everyone see the same board at once?
Yes. The board is fed over WebSocket, so a change one dispatcher makes appears on every other open board without a refresh.
Can technicians see their own schedule?
Technicians get the crew app at /field, which shows their day only. They never see the full dispatch board.
See it running on your own numbers
Twenty minutes, screen-shared, your trade's pricebook already loaded.