# Fuel and Propane Delivery Reporting: Trucks, Tanks, Drivers > Ask your dispatch database about deliveries per truck, tank run-outs and driver hours, then schedule the end-of-day report and the run-out alert. HTML version: https://supaboard.ai/industry/fuel-distribution **Every truck, tank and driver, reported before the next shift.** Connect your dispatch database and ask about deliveries, run-outs and driver hours in plain English. Then put the end-of-day report, the run-out watch and the hours check on a schedule. For fuel and propane distributors, and the dispatch, operations and safety teams that run their trucks. ## Every question, by who asks it ### Deliveries - Gallons and stops per truck yesterday, and who came back with product on board - Loaded against delivered gallons per truck, where the variance is over 0.5% - Yesterday's deliveries not yet invoiced ### Tanks and run-outs - Tanks reaching 20% within three days that aren't on tomorrow's route - Run-outs and near run-outs this month, auto-delivery against will-call - Average drop as a % of tank, by route - Accounts with three or more small deliveries this quarter ### Drivers - Drivers within two hours of their 60-hour limit - Breaches of the 14-hour window or the 30-minute break last week - Gallons per hour by driver, against the same week last year ## Keep it running - **End-of-day deliveries by truck** (Daily 05:30). Gallons, stops and product left on board for every truck, in the dispatch manager's inbox before the first load. Automation: Timed Start → Query Your Data → Summarize Insights → Send Email. - **Tank run-out watch** (Every 5 minutes). A SQL check flags any tank heading under 20% that isn't on a route, and emails dispatch while there's still time to add it. Automation: Alerts → Send Email. - **The dispatch board** (Every morning). A datasite on the dispatch screen with today's routes, tanks at risk and trucks out, read from the database. ## The numbers it keeps watch on | Measure | Definition | Source | In Supaboard | | --- | --- | --- | --- | | Gallons per truck per day | Metered gallons delivered ÷ trucks out | Your delivery tickets | End-of-day report | | Stops per hour | Stops ÷ hours on route | Common practice | Ask it weekly, by driver | | Drop size | Gallons delivered ÷ tank capacity | Common practice | Route review | | Near run-outs | A delivery above 75% of tank capacity | Common practice | Monthly question | | Days to empty | Current level ÷ average daily usage | Your tank readings | Run-out watch | | Load reconciliation | Loaded per bill of lading, against metered delivered and left on board | Your loads | End-of-day report | | Driver hours | 11 hours driving, a 14-hour window, 60 or 70 hours in 7 or 8 days, a 30-minute break | FMCSA, 49 CFR 395 | Weekly hours report | ## 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 Or attach an export to a conversation, as CSV or Excel: Timecard exports. The tables these questions read: Orders and delivery tickets, with meter readings and timestamps; Loads and bills of lading; Trucks and compartments; Tank-level readings landed in a table; Driver shifts and timecards. ## 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 near run-out is a delivery above 75% of tank capacity." - Rule: "The delivery day runs from 5 am to 5 am, depot time." - Rule: "Gallons means metered gallons, never ordered gallons." [How rules work](https://supaboard.ai/product/knowledge-and-rules) ## Already running on it A fuel-delivery operation runs its end-of-day deliveries by truck, tank run-out alerts and driver-hours reports on Supaboard, straight from its own Postgres database, and shares them through dashboards and datasites. (A Supaboard customer, described without its name.) ## 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 ### Can it read our dispatch database directly? Yes. Postgres, MySQL and SQL Server connect live, so the end-of-day report reads the same tickets your dispatch software wrote. The connection is read-only. ### Can the report go out at our time? Yes. Scheduled automations take a timezone, so a 05:30 report arrives at 05:30 at the depot. ### How does the run-out alert work? You write the check as SQL, or ask Supaboard to write it. It runs every 5 minutes by default and emails or calls a webhook when it finds a match. ### Can dispatchers see reports without an account? Yes. Publish a datasite. It can be public, or private with Google or Microsoft sign-in. ### Can we include tank-monitor readings and timecards? Yes. Readings and timecards landed in tables beside your dispatch data are queried with it, and can go on a schedule. A timecard export attached to a conversation works too: Supaboard combines it with the dispatch data for that question. ## More in Transportation & Logistics - [Trucking & Freight](https://supaboard.ai/industry/trucking): Revenue per mile, empty miles, on-time delivery and detention, by lane and customer. - [Last-Mile Delivery](https://supaboard.ai/industry/last-mile-delivery): Stops, failed attempts, delivery windows and cost per drop, by route and driver. - [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`.