SchedulePortal · dispatch and optimisation
Every job on the board. Every board under control.
Built to the standard of enterprise field service schedulers: crew and vendor capacity, SLA clocks and jeopardy, coverage-aware dispatch on a live map, and an optimisation engine that places the whole backlog when you ask it to.
The board
People and vendors across daily, weekly, fortnightly or monthly horizons. Utilisation against capacity, rostered shifts and leave inline, travel time between jobs, and drag-and-drop placement from a queue you can sort, filter and reshape.
Jeopardy, before it bites
SLA timers run from your contract targets. At-risk work floats up in amber before it breaches; the jeopardy page buckets breached, at-risk, due-soon and unscheduled-too-long work with reassignment and clock controls right there.
The map is part of the schedule
Jobs plotted with jeopardy colouring, vendor depots, custom service regions, and ABS statistical-area highlighting. Dispatch suggestions rank vendors by who actually covers the job's area, at what price, with what track record.
The optimiser
Ask the engine to place every open job. Hard rules keep it legal (capacity, skills, coverage, leave, pinned work untouched); weighted objectives make it good (priority, SLA urgency, vendor ranking, travel, fairness). Every placement explains itself, and nothing is written until you apply it.
Objectives you control
Weight what matters per objective profile, and bind profiles to customers so each contract optimises to its own priorities. Different schedulers can live in their own saved views: their region, their customers, their horizon.
Rostering built in
Presence-based work schedules here too: recurring shift patterns, one-off cover, open shifts staff claim themselves, and leave that blocks both the roster and the board.
Scheduling is one workspace of five
Everything the board dispatches was scoped and priced upstream, and everything completed flows to invoicing downstream. One record the whole way.