Crew + van as paired resources
Schediq treats the crew and the van as a single dispatch decision. Both are reserved at the same time, with no risk of one being phantom-available while the other isn't.
What we hear from tradies
The scheduling problems that compound.
- Wrong crew sent to a job because the schedule didn't know about an in-progress callout nearby.
- Vans listed as available even though the part needed for the job is on a different van.
- After-hours callouts eating into pre-booked work because nobody could see the real schedule.
- Customer disputes about timing — with no record to settle them.
Where the deterministic engine pays off
Built for how tradies actually run.
Travel-time matters
Configure Schediq to penalise dispatches that need over an hour of travel. Same job, same conditions, same crew gets picked — every time.
Emergency fallback ladder
Set up an escalation order for emergency callouts: on-call crew first, nearest available next, senior crew willing to swap last. The fallback path is visible to everyone.
Dispatch receipts
When a customer asks 'why did your competitor get there first?', you click the job. You see every crew that was considered, why this one was picked, and when the dispatch happened.
The flow
From customer intent to audit-grade decision in seconds.
- 1
Job booked or called in
Customer books online or staff captures a phone job. Travel-time + skill requirement attached automatically.
- 2
Schediq picks the right crew
Every available crew/van pair is scored against the job. The best fit wins — with the reasoning recorded.
- 3
Crew + van locked
Both reserved at the database level. Double-assignment is impossible.
- 4
Crew dispatched
Confirmation pushed to crew's phone. Optional webhook fires for any custom dispatch system you already use.
- 5
End-of-week audit
Look back at every assignment. Click any job to see exactly why it was dispatched the way it was.