Does it consider real-time traffic?

For day-of routing, optionally yes. For multi-day planning, historical traffic patterns by time-of-day are used; real-time is too volatile for a 5-day plan.

What happens when a job is added mid-day?

Drop it in and the remaining stops re-sequence around it. The engineer sees the updated order on their app straight away.

What about long-distance jobs?

Multi-day jobs and overnight stays are supported. The route engine treats the second day's starting point as the previous night's hotel, not the home base.

Delivery, Project & Service Planning

uScheduler Project / Service / Sales

One plan, one reality — for everything after production.

For the phase after production: delivery, installation, service or project execution. Brings all outbound activities together into an intuitive overview, planned against capacity, skills, geography, deadlines and material availability. One thing we add: we also check whether the needed materials are available at that time of execution. Sales, logistics and engineers all read the same board — so promises get kept and surprises become rare.

Functionalities · 9

Advanced tier

uScheduler P/S/S · Routing & Geography

Routes that respect the map.

When a day's plan includes six addresses, the order matters. uScheduler proposes a route that minimises travel — accounting for traffic patterns, access windows and engineer home base. The saving is shown in time.

Daily route optimisation

Per engineer, per day. The algorithm proposes a sequence that minimises drive time; the planner can pin certain visits to certain times before re-optimising.

Home base in, home base out

Routes start and end at each engineer's home or depot, so the first and last drive of the day are part of the plan — not an afterthought.

Travel savings, measured

After each optimisation, the drive time saved versus the prior order is shown. Boring planning becomes visibly valuable.

What you see

A route is a real number.

A field-service business that ignores routing leaks its scarcest resource: productive time. Every extra hour on the road is an hour not spent on a job. A 12% reduction in drive time on a team of 20 engineers is roughly 2 full FTEs of capacity recovered — without hiring.

Map-aware route building per engineer per day
Traffic-time estimates per time-of-day
Home base and end-of-day return modelled
Pinned visits keep their slot during re-optimisation

When this matters

Signals you'd reach for this.

Engineers build their own routes

When the planner gives a flat list, engineers triage by gut. The result is uneven and unverifiable.

Two engineers drive past each other

Different jobs, same neighbourhood, no co-ordination. A simple cross-engineer check ends this.

Nobody owns the drive time

Travel between jobs is treated as free. It isn't — it's the biggest chunk of unbillable time in the day, and it never shows up in the plan.

Wasted drive time hides the bill

When routes are sloppy, the cost shows up as hours lost on the road — it looks like "the cost of doing business" until somebody charts it.

FAQ

The questions everyone asks first.

Still wondering? Ask us directly →

Google Maps.

See uScheduler P/S/S in a 30-minute demo.

A real screen-share with someone who built it. No slides.

The uTools suite