The day, side by side
Your schedule
- Hours allocated per day
- 48 hrs6 crews × 8 hr benchmark day
- Jobs completed
- 29
- Windshield time
- 15.3 hrs
- Idle / gap time
- 7 hrs
- Time to build this schedule
- ~30 mindispatcher, by hand and by phone
Crisphive rebuild
- Hours allocated per day
- 48 hrssame crew, same shift
- Jobs completed
- 41+12 jobsYour 29 booked stops stay on the schedule — the 12 extra jobs fit into recovered hours only.
- Windshield time
- 6.5 hrs−57%
- Idle / gap time
- 1 hrs−86%
- Time to build this schedule
- 3 secvs ~30 min by phone
Disruptions your dispatcher juggled by phone that day: 1
One vehicle's route, before and after (Vehicle 1)
5 stops · 112 km · 3 hrs driving
7 stops · 45 km · 1.2 hrs driving
Same day, same vehicle — jobs re-sequenced into one zone. ● your original jobs · ● the 2 extra jobs that now fit. Maps are schematic: the stop sequence and zones are real, computed from the job addresses in the schedule you sent.
Recovered hours → dollars
| Drive time recovered across the crew 15.3 hrs windshield time as dispatched − 6.5 hrs after the rebuild | 8.8 hrs |
| Idle / gap time recovered 7 hrs of gaps in your day − 1 hr remaining after gaps are back-filled | 6 hrs |
| Total time recovered 8.8 hrs driving + 6 hrs idle | 14.8 hrs |
| Additional jobs that fit 14.8 recovered hrs ÷ ≈1.2 hr average visit length in your schedule — on top of the 29 already booked | 12 |
| Average ticket used Conservative benchmark — your own export shows $7,706 across 29 completed jobs, ≈$266/ticket. We price below it so every dollar figure errs low; send a different number and it all recalculates. | $250 · based on industry benchmarks |
| Unscheduled revenue in this one day 12 additional jobs × $250/ticket | $3,000 |
| Annualized across the fleet (~250 working days) $3,000 × 250 working days | ≈ $750,000 |
Where the hours were hiding
- Cross-town scheduling and geographic overlap across crew zones45%
Jobs were booked across town from one another, so crews drove through zones where another crew was already working.
- Unfilled schedule gaps from cancellations and wide arrival windows30%
A cancellation or a wide arrival window left a hole in the day, and no nearby job was pulled in to fill it.
- Mid-day supplier runs due to missing inventory on vehicles15%
Trucks left mid-route for parts that could have been staged on the vehicle before the day started.
- Manual dispatch adjustments for emergency calls10%
Emergency calls were squeezed in by phone. The rebuild keeps buffer for them at industry emergency-call rates — the 12 added jobs never assume a disruption-free day.
What we assume about your customers
Customer availability may vary. This rebuild was built on customer availability being a non-factor — it assumes every job could be moved anywhere within the same working day. Real schedules bend around promised time windows, so your recovered hours will land somewhere between the day you ran and the day shown here. Crisphive's live scheduler matches customer availability against business capacity when it builds real routes; this on-paper rebuild deliberately does not, and we would rather say so than defend a number we cannot justify.
Assumptions used
- Average ticket: $250/ticket — conservative; your own export averages ≈$266 across 29 completed jobs
- Working days per year: 250
- Crews on the road: 6 · benchmark working day: 8 hrs per crew (48 crew-hours)
- Distances and drive times: computed from the job addresses in your schedule file
- Customer availability: treated as flexible within the working day (see the note above)
- Disagree with any figure? Send your real numbers and we re-run the audit — the numbers move, the method doesn't.
Confidentiality — your data, one purpose
The schedule file you sent is used for one thing: producing this audit. We do not use it for any other purpose, do not share it, and never sell it to third parties. We do not sell personal information — see Section 4 of our Privacy Policy.