PROPOSED PROJECT
Job Dispatch Planner
Help home-service businesses assign daily jobs using technician skills, addresses, estimated durations, and promised time windows. Turn booking notes into job requirements, compare feasible schedules, and prepare customer updates for the dispatcher to approve.
Give the journey a place in the plan.
Supplied journey times
Assignments awaiting review
Leak repair
Promised window
09:00–10:30
Tap repair
Promised window
10:00–11:30
Home cleaning
Promised window
09:00–12:00
The project in practice.
A fictional plumber T1 leaves the depot at 08:30 for a 30-minute journey to J1, a 09:00–10:00 leak repair inside its 09:00–10:30 window. A 30-minute journey reaches J3 for a 10:30–11:00 tap repair inside its 10:00–11:30 window. Cleaner T2 leaves at 08:40 for a 20-minute journey to J2, a 09:00–11:00 cleaning job inside its 09:00–12:00 window. The plumber is not assigned the cleaning job, and no live traffic information is implied.
WHAT IS USUALLY DONE
Dispatchers fit jobs into a diary by duration and discover later that a technician lacks the skill or cannot travel between appointments in time. Booking notes and customer promises are hard to compare at a glance.
WHAT SOVRUN CAN DO FOR YOU
Sovrun would build a daily dispatch review using job requirements, technician skills, supplied journey times, and promised windows. It compares feasible assignments, highlights uncertain information, and drafts customer updates for the dispatcher to approve. The schedule stays provisional until staff confirm it.
The right skill.
The full service window.
T1 is assigned the two plumbing jobs, with 30 minutes between them. T2 handles the two-hour cleaning job. Every service fits wholly within its stated window; arrival alone is not used as proof that the full job fits.
Leak repair
- Required skill
- Plumbing
- Service duration
- 60 min
- Planned service
- 09:00–10:00
- Promised window
- 09:00–10:30
Tap repair
- Required skill
- Plumbing
- Service duration
- 30 min
- Planned service
- 10:30–11:00
- Promised window
- 10:00–11:30
Home cleaning
- Required skill
- Cleaning
- Service duration
- 120 min
- Planned service
- 09:00–11:00
- Promised window
- 09:00–12:00
Recalculate the downstream service time and check the whole promised window again. If the result no longer fits, return it to the dispatcher with the conflict visible. A model should not silently shorten the job or promise a new time.
A dispatch sheet
that makes the assumptions visible.
The project gives dispatchers a proposal they can verify against skills, job records, and route assumptions before any customer commitment changes.
Work matched to skills.
- T1 / Plumbing
- J1 + J3
- T2 / Cleaning
- J2
- J1 duration
- 60 min
- J3 duration
- 30 min
- J2 duration
- 120 min
Keep the 30-minute journey.
- J1 repair
- 09:00–10:00
- Travel
- 10:00–10:30
- J3 repair
- 10:30–11:00
- Latest J3 finish
- 11:30
Confirm before dispatch.
- Access notes
- Staff check
- Journey assumptions
- Staff check
- Technician review
- Pending
- Customer updates
- Not sent
How we’d make it happen.
Confirm job requirements
Extract the required skill, address, access, duration, and promise from each booking.
Compare workable assignments
Allow time for journeys and apply staff skills and full service-window constraints.
Approve the dispatch sheet
The dispatcher and technicians review the plan, resolve unknowns, and approve any customer update.
Where AI helps
Language models turn booking notes into proposed task requirements. Scheduling code checks skills, travel, job length, and the full promised window. Model suggestions remain grounded in the supplied data and do not assume live traffic or unrecorded qualifications.
What people approve
Dispatchers confirm job scope, skills, access, duration, and travel allowances. Technicians review practical feasibility, and customer messages require staff approval. The tool does not route vehicles or change confirmed appointments automatically.
What we’d need to start
- Job addresses, task requirements, durations, and promised windows
- Technician skills, shifts, and availability
- Supplied journey times, access notes, and dispatch rules
How we’d test it
Test skill conflicts, missing travel times, overlapping jobs, insufficient buffers, and tasks that extend past their window. Independently check each timeline and avoid calling a proposed assignment a confirmed visit.
Prepared for Consumer & local services. We would agree on the work after reviewing your brief, materials, and requirements.
This is a proposed project, not completed client work. The visuals and numbers show example outputs, not measured results.
