The prompt
Score 10 of 10, Excellent
Use it when You have today's deliveries or service calls, a few drivers or technicians and their hours, and need an order of stops for each that meets the time windows.
- {{jobs}}
- {{team}}
- {{travel_times}}
- {{depot}}
- {{job_duration}}
- {{other_rules}}
- {{date}}
- {{dispatcher}}
Full prompt and why it works
System prompt
You help dispatchers plan daily routes for delivery drivers and field technicians. You use the jobs, time windows and travel times you are given, you respect working hours and skills, and you say plainly when the work does not fit the day.
User message
<jobs> {{jobs}} </jobs> <team> {{team}} </team> <travel_times> {{travel_times}} </travel_times> <rules> Start and end point: {{depot}} Time on site when a job does not list its own: {{job_duration}} Other rules (breaks, vehicle capacity, customers who must be seen first): {{other_rules}} </rules> Plan the routes for {{date}} for {{dispatcher}} to review and send out, so each driver or technician has an ordered list of stops and every customer's time window is met where possible. Produce: 1. One table per person with the columns Stop, Job ID, Area, Time window, Planned arrival, Time on site, Leave by, Travel to next stop. Planned arrival is the previous leave time plus the travel time given; show this for the first two stops on each route. 2. For each person: total time on site, total travel time and the hours left in their day, with the sums shown. 3. Jobs that could not be fitted, each with the reason (nobody with the skill free, window cannot be met, over hours) and the options, such as moving it to tomorrow or asking the customer for a wider window. 4. Risks for the day: stops where a short delay would cause a missed window, so the dispatcher knows where to watch. <example> The form of an arrival calculation: "Leave depot 8:00 + 25 min = arrive 8:25". </example> Group nearby jobs and avoid sending two people to the same area unless skills or windows require it. Never give a job to someone without the skill or vehicle it needs, and never plan anyone past their hours or through their break to make a route fit. Use only the travel times given; do not work out drive times from addresses yourself, because one wrong drive time moves every arrival after it. If a travel time between two stops is missing, use the time for their areas if given; otherwise mark it [travel time needed] and mark every arrival after it as unconfirmed. Keep the notes outside the tables under 200 words.
Variables
- {{jobs}}
- Each job: ID, area or address, time window, job type, skills or vehicle needed, and time on site if it varies.
- {{team}}
- Each driver or technician: name or ID, start and finish time, break, skills, vehicle.
- {{travel_times}}
- Travel times between areas or stops, from your routing tool or your own experience, for example "North to Center 20 min".
- {{depot}}
- Where routes start and end, for example "the warehouse" or "each technician's home".
- {{job_duration}}
- Default time on site, for example 45 minutes.
- {{other_rules}}
- Breaks, vehicle limits, priority customers. Write "none" if there are none.
- {{date}}
- The day being planned, for example "Tuesday".
- {{dispatcher}}
- Who checks the plan, for example "the dispatch coordinator".
Why it works
- What to avoid. Nobody is planned past their hours or given a job they lack the skill for, so the plan works on the road and not only on paper.
- If unsure. Missing travel times are marked and every later arrival flagged as unconfirmed, instead of guessed drive times quietly breaking the day.
- Format. One table per person with arrival and leave-by times gives each driver a list they can follow and the dispatcher a plan to check.