Skip to content

Daily Driver Run Sheet

Example prompt: "Every morning at 6am, build each driver's run sheet from today's confirmed deliveries in our Google Sheet, email it to them, and post a one-line dispatch summary in #ops on Slack."

The Problem

A small courier desk spends the first hour of every day stitching together what each driver is doing — pulling today's confirmed deliveries out of a sheet, sorting them into a sensible order for the van's route, working out who has special access notes that need flagging, and getting a printable list in front of each driver before they leave the depot. Done by hand, this is 45 to 60 minutes of repetitive sheet-juggling every morning, and it shifts the start of the road day later by the same amount.

How GloriaMundo Solves It

We build a workflow that runs at 6am each weekday. An integration step reads today's confirmed deliveries from our dispatch sheet. A code step groups them by driver and orders each driver's drops using the postcode sort we already use on paper. An LLM step formats each driver's list into a clear run sheet and flags drops with special instructions. An integration step saves the run sheet as a Gmail draft addressed to the driver, ready for the dispatcher to review and send before the 7am briefing. A final integration step logs the day's manifest to a sheet tab — including vehicle_reg and start_mileage so the evening debrief workflow can reconcile against the morning's figures — and posts a one-message summary to the dispatch Slack channel. Glass Box preview shows the run sheets and the summary before any of them reaches the drivers.

Example Workflow Steps

  1. Trigger (scheduled): Every weekday at 6am.
  2. Step 1 (integration): Read today's confirmed and re-attempt rows from the 'Deliveries' tab of the dispatch Google Sheet, and the postcode-area sequence from the 'Postcode Sort Order' tab.
  3. Step 2 (code): Group the rows by driver_name and order each driver's drops by the postcode sequence.
  4. Step 3 (integration): For each driver, look up the assigned vehicle_reg from the 'Driver-Vehicle Assignments' tab and the most recent end_mileage from 'Driver Debriefs' as start_mileage for today.
  5. Step 4 (llm): For each driver, compose a clear run-sheet table — drop number, time window, customer, address, parcels, special instructions.
  6. Step 5 (code, gate): Check the 'Daily Manifest' tab for an existing (driver_name, today's date) row — if one exists, skip Step 6 for this driver so a re-run does not produce a second Gmail draft. Step 7's Slack summary still runs across all drivers (existing + new).
  7. Step 6 (integration): For drivers with no existing manifest row, save each run sheet as a Gmail draft addressed to the driver's work address and append a 'Daily Manifest' row with drop_count, total_weight_kg, vehicle_reg, start_mileage, and gmail_draft_link.
  8. Step 7 (integration): Post a single dispatch summary in #dispatch on Slack at 6:30am with totals and the per-driver breakdown.

Integrations Used

  • Google Sheets — the source of today's deliveries and the manifest log
  • Gmail — the per-driver run-sheet drafts
  • Slack — the daily dispatch summary for the manager

Who This Is For

Small courier and last-mile delivery firms running 4 to 30 drivers a day out of one or two depots, where the dispatch desk currently rebuilds the driver list every morning by hand and the start of the road day slips by an hour because of it.

Time & Cost Saved

Sorting today's confirmed deliveries, grouping by driver, ordering by postcode, formatting a printable list, and emailing each driver takes the dispatcher 45 to 60 minutes most mornings. This workflow reduces that to a 10-minute review of the drafts before they go out — and the drivers leave the depot 30 to 45 minutes earlier than they did before.