Daily sequencing
Reorder and retime one crew and day without changing the master recurring schedule.
The maths behind a better recurring pattern.
You don't need this page to run intuós — it's here because software that plans your week should be able to explain itself. The model covers capacity, travel, crew make-up, recurring preferences, locks, service evidence, labour and the cost of change.
Explore the modelOptimise the right layer.
A daily route decision is not the same as redesigning a recurring schedule. intuós separates the layers so a small operational adjustment does not accidentally rewrite the future.
Route rebalancing
Move flexible work between crews and days inside a controlled window.
Strategic pattern
Recalculate the preferred week, day and team behind future recurring work.
The objective is broader than kilometres.
The strongest plan balances travel efficiency with labour, capacity, service requirements, schedule stability and complete demand coverage.
TravelRoad time and distance
+LabourCrew time and cost
+InstabilityUnnecessary change
+Coverage riskUnserved or incomplete work
=Operational scoreA plan you can actually run
Subject to the constraints that make the business real.
The solver is useful because it respects the things a simple nearest-neighbour route cannot see.
Time and capacity
Workday minutes, service duration, route travel, breaks, slack and controlled overtime.
Crew reality
Working days, availability, leave, labour rates, solo or paired work and team exclusions.
Schedule stability
Protected work, freeze windows, recurring preferences and the operational cost of unnecessary change.
Demand integrity
Every visit accounted for, with incomplete or dropped scenarios blocked before they can be applied.
Plan with service-time evidence, not a hopeful average.
Reviewed GPS stops build separate solo and paired duration models. intuós uses a conservative planning percentile and keeps confidence, sample counts and outliers visible before an estimate is changed.
- Separate solo and paired work
- Planning percentile rather than simple mean
- Visible confidence and sample size
- Outlier review before estimates change
P80 planning time
Solo visits Paired visits
- Solo P80
- 74 min
- Paired P80
- 48 min
- Reviewed samples
- 31
Know when the route uses road evidence and when it estimates.
Travel provenance records the solve, methodology and fallback edges used in a route. Operators can distinguish a road-backed plan from one that contains estimated legs.
- Solve kind and run time
- Road matrix and fallback diagnostics
- Warnings when estimated travel is used
- Protected work and lock provenance
Compare complete scenarios on equal demand.
Migration analysis normalises the work first, then evaluates the current run, a guarded transition and the optimised pattern. A scenario that loses work is not allowed to look efficient.
| Scenario | Demand covered | Drive | Labour | Schedule change | Ready to apply |
|---|---|---|---|---|---|
| Current run | 100% | 19h 42m | $8,920 | Baseline | Yes |
| Guarded transition | 100% | 16h 08m | $8,140 | 12 changes | Yes |
| Optimised pattern | 100% | 14h 51m | $7,780 | 28 changes | Yes |
The best mathematical answer still waits for an operational decision.
Bring the operational constraints. Keep the decision.
intuós makes the model visible, preserves the work and gives the office a controlled path from evidence to action.