# Last-Mile Delivery Analytics: First Attempts, Cost per Drop > Ask route and dispatch data about first-attempt delivery, missed windows, failed stops by reason and cost per drop, then get yesterday's late routes by 06:00. HTML version: https://supaboard.ai/industry/last-mile-delivery **Know why yesterday's stops failed before the vans go out.** Connect your route and dispatch database and ask about first attempts, delivery windows, failed stops and cost per drop in plain English. Yesterday's late routes can be in your inbox before the first van loads. For couriers and parcel delivery companies, grocery and retail delivery operations, and local delivery fleets. ## Every question, by who asks it ### Routes and windows - Routes that ran past their planned finish yesterday, and by how long - Deliveries inside the promised window last week, by client - Stops per hour by driver last week, against their four-week average ### Failed attempts - First-attempt delivery rate by route last month - Failed attempts last week by reason: no one home, no access, wrong address, refused - Addresses with two or more failed attempts in the last 30 days - Deliveries marked delivered yesterday with no proof-of-delivery timestamp ### Cost and complaints - Cost per drop by zone last month, with driver pay and vehicle cost - Complaints per 1,000 deliveries by depot, this month against last - Claims for missing parcels this quarter, by route and driver ## Keep it running - **Yesterday's late routes** (Daily 06:00). Routes that finished past plan, failed attempts by reason and missed windows, in the depot manager's inbox before the vans load. Automation: Timed Start → Query Your Data → Summarize Insights → Send Email. - **Failed-attempt watch** (Every 5 minutes). A SQL check compares each route's failed attempts today with its 30-day average and emails dispatch while the drivers are still out. Automation: Alerts → Send Email. - **Each client's delivery scorecard** (Every week). A private datasite per retail or grocery client, with Google or Microsoft sign-in: deliveries in window, first attempts and failed stops by reason. ## The numbers it keeps watch on | Measure | Definition | Source | In Supaboard | | --- | --- | --- | --- | | First-attempt delivery rate | Deliveries completed on the first attempt ÷ deliveries attempted | Common practice | Daily report, by route | | On-time in window | Deliveries with a proof-of-delivery time inside the promised window ÷ deliveries | Your client SLA | Each client's datasite | | Failed-attempt rate | Failed attempts ÷ attempts, split by reason code | Common practice | Alert when a route jumps | | Stops per hour | Stops completed ÷ hours on route | Common practice | Weekly report, by driver | | Cost per drop | (Driver pay + vehicle cost) ÷ successful deliveries | Common practice | Ask it monthly, by zone | | Complaints per 1,000 deliveries | Complaints ÷ deliveries × 1,000 | Common practice | Ask it weekly, by depot | | Proof-of-delivery capture | Deliveries with a proof-of-delivery record ÷ deliveries marked delivered | Your contract | Daily check | ## Where your data lives - [Postgres](https://supaboard.ai/integrations/postgresql): connects live - [MySQL](https://supaboard.ai/integrations/my-sql): connects live - [SQL Server](https://supaboard.ai/integrations/ms-sql-server): connects live - [BigQuery](https://supaboard.ai/integrations/bigquery): connects live Or attach an export to a conversation, as CSV or Excel: Help-desk complaint exports; Driver pay and vehicle cost sheets. The tables these questions read: Routes and stops, with planned and actual times; Delivery attempts, with failure reasons and proof-of-delivery timestamps; Promised delivery windows, by order; Driver shifts; Complaints and claims, by order; Driver pay and vehicle cost, by day. ## Teach it your definitions once Rules are read with every question, so a term means the same thing in Chat, in Slack and in the Monday report. - Rule: "A delivery is in window only if its proof-of-delivery time falls inside the promised window; early counts as a miss." - Rule: "A first attempt succeeds only when proof of delivery is captured on that attempt." - Rule: "Cost per drop divides driver pay and vehicle cost by successful deliveries, not by stops." [How rules work](https://supaboard.ai/product/knowledge-and-rules) ## Security - **Read-only by construction.** Database and warehouse queries are read-only. We give you the SQL for a read-only user too. - **Credentials stay in the workspace.** Scoped to the one workspace that connected them, never logged and never sent back to a browser. - **SOC 2 Type II.** An organisation-wide audit of the platform, covering every plan. ## FAQ ### Does it work with our routing and dispatch software? If it keeps routes, stops and attempts in a database you can reach, yes: Postgres, MySQL, SQL Server and BigQuery connect live and read-only. Otherwise upload a CSV or Excel export to ask about it in a conversation; for a scheduled report that stays current, keep the data in a database you connect. ### Can each retail client get its own scorecard? Yes. Give each client a private datasite with Google or Microsoft sign-in, and email each one its scorecard on its own schedule. You can also keep one workspace per client. ### Can it include complaints from our help desk? Yes. Export them from your help desk as CSV or Excel and attach the file to a conversation, and Supaboard combines it with the delivery data for that question. Complaints logged in your dispatch database can also go on a schedule. ### How does it know what counts as on time for us? Write it once as a rule, such as "early counts as a miss". The agent reads its rules with every question, so on time means the same thing in Chat, in Slack and in the morning report. ### Can yesterday's late routes be in my inbox before the vans load? Yes. A Timed Start runs the question daily at 06:00 in the depot's timezone, then Supaboard summarises what it found and emails it. ## More in Transportation & Logistics - [Fuel & Propane Distribution](https://supaboard.ai/industry/fuel-distribution): Deliveries, tank run-outs and driver hours, reported before the next shift. - [Trucking & Freight](https://supaboard.ai/industry/trucking): Revenue per mile, empty miles, on-time delivery and detention, by lane and customer. - [Warehousing & 3PL](https://supaboard.ai/industry/warehousing): Orders out on time, pick accuracy, dock-to-stock and storage billed, per client. Supaboard is [the AI data analyst connected to your business data](https://supaboard.ai/). For the background on this industry, read [Logistics analytics: turning supply chain data into action](https://supaboard.ai/blog/logistics-analytics). [All industries](https://supaboard.ai/industry). --- - Site index for agents: https://supaboard.ai/llms.txt - Sitemap: https://supaboard.ai/sitemap.xml - Blog feed: https://supaboard.ai/blog/rss.xml - Product documentation: https://docs.supaboard.ai Any page on https://supaboard.ai is available as markdown: append `.md` to its path, or send `Accept: text/markdown`.