As of 13 August 2026, AI can only partly create a courier dispatch process.

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 a blank document and gather your current delivery promises, collection cut-offs, operating hours, delivery areas, courier list, vehicle limits, booking system details and escalation contacts.
   2. Paste the gathered information into the prompt fields, leaving any unknown item as an explicit unknown rather than asking the model to fill it in.
   3. Paste the completed prompt into ChatGPT, Claude or Gemini and ask it to produce the SOP, responsibility table, decision rules, exception procedures and checklists in separate sections.
   4. Copy the draft into your normal process-document template and replace every marked assumption or management decision with an agreed business rule.
   5. Take several recent delivery jobs, including a late booking, a failed delivery, a vehicle breakdown and a capacity conflict, and run each one through the drafted decision rules to check that the next action and escalation are clear.
   6. Ask an experienced dispatcher or operations manager to compare the process with the live booking, route-planning, proof-of-delivery and customer-notification systems, then correct any step the team cannot perform.
   7. Issue the checked SOP to the dispatch team, run a short trial shift using the checklists, record exceptions, and update the document before making it the controlled process.

   Prompt

   Create a practical courier dispatch process for a UK business using the information below.
   
   Business and service:
   - Business type: [business type]
   - Delivery service offered: [same-day, next-day, scheduled, or other]
   - Operating days and hours: [days and hours]
   - Collection and delivery areas: [areas or postcodes]
   - Delivery promises and cut-off times: [details]
   
   Resources:
   - Couriers and employment status: [employees, contractors, or both]
   - Vehicles and capacity limits: [vehicle types and limits]
   - Dispatchers and their working hours: [details]
   - Booking, route-planning and proof-of-delivery systems: [tools or manual methods]
   
   Rules and constraints:
   - How jobs are prioritised: [rules]
   - Maximum collection or delivery wait times: [rules]
   - Restricted goods, access restrictions or special handling: [details]
   - Customer notification requirements: [details]
   - Escalation contacts and authority levels: [names or roles]
   - Records that must be kept: [details]
   
   Produce:
   1. A clear end-to-end SOP from receiving a delivery request to closing the job.
   2. A RACI-style responsibility table for the dispatcher, courier, customer service team and manager.
   3. Explicit decision rules for prioritising jobs, assigning couriers, grouping deliveries and handling capacity conflicts.
   4. Separate procedures for failed collection, failed delivery, damaged goods, late running, vehicle breakdown, customer cancellation and missing proof of delivery.
   5. A dispatcher opening checklist, live-dispatch checklist and end-of-day checklist.
   6. Required information fields for every job and an audit trail showing who changed what and when.
   7. Escalation times and actions, using placeholders where I have not supplied a rule.
   8. A short training and implementation plan.
   9. Suggested operational measures, without inventing targets or claiming legal requirements.
   
   Use UK English. Do not invent policies, service levels, contact details, prices, routes, legal obligations or system capabilities. Mark every missing fact as an assumption or an item for management decision. Keep the process practical for a small operations team, and flag any point that should be checked against current UK transport, employment, insurance, health and safety or data protection requirements before launch.

   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.