15 MINUTES PER DRIVER. NOW ONE REVIEW CARD.

The tab the app opens on. It watches where freight paperwork lands, the dispatch mailbox, the other office mailboxes, and the shared drive, and draws one week of the operations spreadsheet as a board with a section per driver and each load's documents in a drawer. The rate confirmation and everything else that arrived for a load sit on that load instead of in the inbox they came through.

Documents are judged by what their pages say, not by what their filenames claim. A file the tab cannot place is kept and flagged for someone to look at, never silently dropped, and a disagreement between two documents about the same load is surfaced rather than resolved by guesswork.

This is the one tab that writes to the spreadsheet, and it does so three ways, each on a button press: setting a load's stage, saving edited cells on a row the sheet already carries, and adding a whole row for a load it does not. Before every write it re-reads the row and confirms the load number still matches. It refuses by name when it cannot place a row safely, whether the reason is no driver, no block that week, a duplicate load number, or a row that moved. It never inserts rows, never touches the owner's own already-sent marker column, and never writes to the shared drive.

Every afternoon the office builds one email per driver for the next day's load. This tab drafts them. It reads the spreadsheet, finds each driver's next load, takes that load's documents off the Loads board, and uses Claude to read them, classify them, and extract the load details. When the board cannot answer, it falls back to the search that used to mean opening folders, across about 12,000 messages and about 123,000 files per load, without anyone watching it.

Composition follows a strict driver and office split. Drivers get addresses, dates, appointment windows, reference numbers, and equipment requirements. Rates and payment terms never leave the office, and the rate confirmation itself is never attached to a driver email. Every requirement in the email cites the document it came from, and one that cannot is flagged rather than dropped.

Every email lands as an editable review card with plain-language flags, a formatting bar, a computed loaded-miles line, and the tracking-app instruction copied word for word from the spreadsheet. Generating sweeps the mail first, so no email is composed against a stale board. A person reads it, edits it, and sends it. Sends go out through the client's own dispatch mailbox and mirror to Sent, so the audit trail stays where the office already looks for it.

One button replaces the truck-by-truck walk through the fleet portal. A single fleet API call returns every truck. The app pairs each position with that driver's next delivery from the spreadsheet, computes drive time, and shows the appointment and the ETA side by side in the receiver's time zone with Central alongside it, so nobody does time zone math from memory at 5 AM.

A truck that stops reporting gets an amber staleness flag rather than a stale position presented as current. The check reads the pickup date as well as the delivery, so a Friday pickup with a Monday delivery stays on the board all weekend, and it treats a finished load as delivered from the truck's own position, since the fleet provider publishes no delivered signal. Both decisions print their reasoning on the row.

There is deliberately no verdict logic. The tool never declares a truck early or late. It puts the two times next to each other and the dispatcher reads them, because the dispatcher knows about the construction on the route and the receiver who takes trucks an hour before the window. This tab is read-only end to end: nothing reaches the fleet account, the spreadsheet, or the mailbox.

Work orders, estimates, repair invoices, and parts receipts arrive by email, and repair paperwork belongs to a truck, not a load. This tab reads the office mailboxes and lays each document out as a card, grouped into a section per truck.

The truck on each card is resolved in a fixed order: a hand assignment first, then what the pages say checked against the driver roster, then a truck number seen in the subject line or an attachment name. Anything still unresolved waits in a pile marked no truck yet, where a person assigns it with one click. A hand assignment is permanent, and no later sweep can move it.

From the card, a person can open the document, drag it onto a browser upload box, copy the file, or save it into the office filing folder. Nothing is written back to the mailbox or the drive.

Everything that is not a load and not a repair: credit card statements, fuel, tolls, subscriptions. The same cards and the same mechanics as Mechanical, so the person paying the bills opens one tab instead of several mailboxes.

Each card can be opened, dragged, copied, saved, or dismissed, and deleting one takes two clicks so a slip of the hand does not lose a bill. Like Mechanical, this tab writes nothing to the client's Google systems.