As of 13 August 2026, AI can only partly assign engineers to service visits.

What to actually do

1. Use a tool built for this

   The route this page recommends

2. Do it yourself

   Second choice

   A chat interface, chat-fluent skill, and roughly 30 minutes until you can act on the result.

   How to actually do it

   1. Open your current engineer rota, leave record and skills or certification list, then copy the relevant data into the engineer section of the prompt.
   2. Open the service-management system, diary or spreadsheet for the target date and copy each visit's ID, location, appointment window, duration, required skills, priority, parts and fixed commitments into the visit section.
   3. Add the working hours, maximum daily hours, depot or base locations and any rules about travel, breaks, overtime or customer priority that the model must obey.
   4. Paste the completed prompt into a chatbot and ask it to produce the draft assignment, keeping every missing or estimated field marked as unverified.
   5. Compare every assignment against the live rota, leave record, skills and certification register, and remove any assignment that breaks a hard constraint.
   6. Check travel feasibility and visit order in your mapping or service-management system, replacing any unverified travel assumption with a confirmed route and time.
   7. Ask an operations colleague to approve the remaining conflicts, then enter the agreed assignments into the live scheduling system and send the confirmed visits to engineers and customers.

   Prompt

   Assign the service visits below to the available engineers and produce a draft schedule for [DATE]. Use only the information supplied. Do not invent availability, skills, travel times, visit durations, parts, priorities or customer requirements.
   
   Engineer data:
   [PASTE ENGINEER NAMES OR IDS, BASE LOCATIONS, WORKING HOURS, LEAVE, SKILLS, CERTIFICATIONS, MAXIMUM DAILY HOURS, AND ANY OTHER HARD CONSTRAINTS]
   
   Service visit data:
   [PASTE VISIT IDS, CUSTOMER LOCATIONS, APPOINTMENT WINDOWS, ESTIMATED DURATIONS, REQUIRED SKILLS OR CERTIFICATIONS, PRIORITIES, PARTS, AND ANY FIXED ASSIGNMENTS]
   
   Rules:
   1. Treat appointment windows, leave, working hours, required skills and certifications as hard constraints.
   2. Do not assign an engineer who lacks a required skill or certification.
   3. Prefer fewer and shorter journeys, but never break a hard constraint to reduce travel.
   4. Keep working hours and maximum daily hours within the supplied limits.
   5. If travel times are not supplied, do not estimate them. Mark travel feasibility as unverified.
   6. If a visit cannot be assigned safely or confidently, leave it unassigned and state the exact reason.
   7. Flag every assumption, conflict, missing field and assignment that needs a manager's decision.
   
   Return:
   - a table with visit ID, customer location, appointment window, assigned engineer, planned order, duration, required skill, and verification status;
   - each engineer's total assigned hours and visit list;
   - unassigned visits and the reason for each;
   - conflicts, missing data and assumptions;
   - a short checklist for a manager to verify before sending the schedule to engineers or customers.
   
   Use plain British English. Separate facts from assumptions and do not claim that the schedule is final.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.

3. Hand it to a person

   The distant third

   A person who owns the outcome does this end to end, worth it when the failure is dear.