PortaPro

JOBS & DISPATCH

Schedule from the map.
Optimize after you commit.

Dispatch is a human decision \u2014 “who’s in the area and when can we fit this in?” Jobs & Dispatch gives you the map view, calendar, and per-driver capacity information to answer that question on the phone, without running a solver. Route Plan handles the sequencing after the day is committed.

The mental model

Two tools. Two jobs.

“Who’s in the area and when can we fit this in?” \u2014 that’s a scheduling question. It’s a human decision supported by a map and a calendar. The dispatcher on the phone needs to see where existing jobs are clustered, which drivers are already running near that address, and how loaded each driver is by day. That’s Jobs & Dispatch.

“Given everything scheduled for Thursday, what’s the optimal sequence and assignment across all trucks?” \u2014 that’s route optimization. It runs after scheduling decisions are made, once the day is committed. That’s Route Plan.

If you merged them, you’d be asking a solver to run every time a dispatcher considers a job. Nobody wants to wait five seconds for a computation every time they’re browsing availability on a call. The human does the coarse-grained scheduling with good visual tools. The optimizer does the fine-grained sequencing once the day is locked. That’s how UPS and FedEx Ground operate \u2014 dispatchers build the load plan, then the routing engine sequences it. PortaPro closes the loop between the two surfaces by surfacing a geographic fit callout during job creation \u2014 showing how far a new stop is from a driver’s existing cluster on that day \u2014 without triggering an optimization run.

Dispatch decides what and when
Coarse-grained scheduling with good visual tools — map clusters, driver availability, and capacity bars by day. The dispatcher makes the judgment call on the phone.
Route Plan decides how
Fine-grained sequencing runs once the day is committed. Build & Optimize reads everything assigned to a day and computes the optimal order across all trucks and constraints.
That’s how enterprise logistics works
UPS and FedEx Ground use the same model — dispatchers build the load plan, then the routing engine sequences it. The dispatcher’s geographic intuition gets validated and refined by the optimizer, not replaced by it.
The dispatch map

Four views in one screen

The dispatch map surfaces everything a dispatcher needs to make a confident scheduling decision \u2014 without leaving the job creation flow.

Geographic clustering
See where existing customers and jobs are clustered geographically by day. During job creation, the map shows a geographic fit callout — how far the new stop is from a driver’s existing cluster on that day — so you can make an informed assignment without running a route solve.
Territory view
Sort the map by zip code for a quick per-territory picture, or draw custom polygons directly on the map to define your own service boundaries. Territories persist and are available to every dispatcher.
Driver workload by day
The WeekStrip shows per-driver capacity bars for each day of the week. You can see at a glance that Mike has three stops on Route 82 Wednesday before you commit the new job to his schedule.
Demand heatmap
A density overlay shows where service demand is concentrated across your territory. Useful for spotting natural service corridors and understanding where adding a new stop has the lowest incremental drive cost.

LIVE ACTIVITY

Your operations, updating in real time

Every job update start, progress, completion is visible instantly without calling drivers.

Mike R.

just now

started Job #4821 On-site

System

4 min ago

Route updated 2 stops reordered for traffic

30%

Fewer dispatch calls

Real-time

Live job visibility

Same-day

Adjustments without disruption

Zero

Whiteboards or manual tracking

A dispatch call, start to job

How a single phone call becomes a committed, optimized job

Step 1

Customer calls

They need a portable toilet delivered to a job site on Route 82. Dispatcher opens Jobs & Dispatch and switches to map view.

Step 2

Read the map

Map shows existing stops clustered near that corridor, which drivers are running there by day, WeekStrip capacity bars, and demand density.

Step 3

Make the call

Mike is already running three stops on Route 82 Wednesday. Dispatcher creates the job, assigns it to Mike, picks Wednesday. 30 seconds.

Step 4

Optimization runs

Wednesday morning, Build & Optimize looks at everything assigned to Wednesday — including the new stop — and sequences it optimally across all trucks.

See It In Action

See how dispatch actually works

See how jobs are scheduled, assigned, and updated in real time without calls, spreadsheets, or guesswork.

Try Interactive Demo

Operational Impact

What your team handles without guesswork

✓Map view before scheduling
✓Territory sorting and polygons
✓Live completion tracking

Get Started

Ready to simplify dispatch?

Take control of your schedule, reduce interruptions, and keep every job moving without the chaos.

Try the Demo

Get started in under 2 minutes.