# Operators Brief: Issue #006 *June 1, 2026 · The Weekly Drop*

Direction Drop

Your Inbox Should Sort Itself

Every operator loses the top of the day to the inbox. Supplier pricing sheets, vendor reports, notifications, newsletters, and buried somewhere in the pile the two or three messages that actually need you. Most people manage this by reading all of it. That is not a system. It is a tax you pay every single morning before the real work starts.

The fix is to make the inbox sort itself. Route each message by who sent it, file it, archive the noise, and leave only the handful of things that need a human in front of you. Log the rest so you have a record and a dashboard instead of a black hole. Do that and the morning inbox goes from an hour of sorting to a thirty second glance.

What TNDS is building this week

On the build side, northbound-ai continues its citation-grounding work for the fuel-hauler pilot. This week's teaching piece features a proven build from the toolbox: a Gmail cleanup and dashboard system that reads the inbox, routes each message to the right label by sender, archives everything not on a short protected list, logs every message to a Google Sheet, emails a daily summary, and serves a live dashboard. Standard Google Apps Script, no paid tools, nothing outside your own account touching the mail.

Command Drop

Make the Inbox Sort Itself

*Route by sender, archive the noise, protect the few things that need you, and log all of it.*

Triage before you touch it. In the field you do not treat casualties in the order they arrive. You triage first: who needs help now, who can wait, who is already stable. The inbox is the same. Before you read a single message it should already be sorted, so the few that need you are obvious and the rest are filed and out of the way. Reading everything in arrival order is the slowest possible way to run a busy inbox.

Route by sender, not by reading. The highest-signal fact about most business email is who sent it. A pricing email from a supplier always goes to the same place. A vendor report always goes to the same place. Build one simple map: this sender goes to this label. The machine files it the instant it lands, and you stop making the same filing decision fifty times a day. You made the decision once, when you wrote the rule.

Archive the noise, protect the signal. Most email does not need to sit in your inbox. It needs to be filed and gone. Keep a short protected list of the senders that truly require your eyes, the dispatch alert, the one newsletter you actually read, and let everything else get labeled and archived automatically. Your inbox shrinks to the short list of things a human has to look at, which is the whole point.

Log it so you have a record. Every message that comes through gets one row in a sheet: when it arrived, who sent it, the subject, and where it was filed. Now you have a searchable record and the raw material for a dashboard that shows your top senders and busiest categories. The inbox stops being a hole things vanish into and becomes data you can actually see and defend later.

> BLUE COLLAR AI > > Notice what the routing rules are: a plain list of this sender goes to that label. That same plain list is exactly what an AI tool needs to help you extend the system. Hand an AI your sender-to-label map and a week of the daily summary, and it can spot a sender that is flooding you, suggest a new rule, or draft replies to the three messages that actually matter. The rules file the mail on their own, no AI required. The AI helps you decide what to do about the pile the rules uncovered. And a note on trust: rules you wrote are predictable and private, the mail never leaves your account. An AI agent turned loose on your whole inbox is neither. Let rules do the known work and keep the human in the loop for anything that matters.

Field Build

*This one is from our own shop.*

The inbox behind this build took a daily flood: recurring supplier pricing emails, vendor reports, and system notifications, roughly a dozen repeat senders, plus newsletters and one-off mail, all landing in one place. Every morning started with the same manual sort, read, label, archive, repeat, before any real work could begin. Nothing was logged, so once a message was archived there was no record of what came in or from whom.

| Measure | Before | After | |---------|--------|-------| | Morning inbox triage | Thirty to sixty minutes by hand | Runs on a schedule, inbox arrives sorted | | Filing decisions per day | The same call made fifty-plus times | Made once, in a sender-to-label map | | Record of what came in | None, gone once archived | Every message logged to a sheet, searchable | | Visibility | No idea which senders flood the inbox | Dashboard of top senders and busiest labels |

What changed. Built a Google Apps Script that pulls the latest inbox threads, matches each one against a sender-to-label map, files it, and archives everything not on a short protected list. Every message is logged to a Google Sheet with date, sender, subject, and label. A scheduled run emails a daily summary of the day's activity, a second function rebuilds two dashboard charts, top senders and label frequency, and a web view serves the dashboard with the TNDS footer. Standard Apps Script and Google Sheets. No paid tools, and nothing outside the account ever touches the mail.

Time invested: A first working version in a day, then tuned over a couple of weeks as new senders showed up.

Signal Check

*Three beats worth an operator's attention.*

1. The inbox filled up with AI in 2026, and the safe pattern is clear. Gmail, Outlook, and a wave of paid assistants now offer to triage, summarize, and auto-reply to your mail. The tested-safe way to use them, per the people who deploy these for a living, is rules first and human in the loop: let deterministic rules handle the known senders, keep any AI action in draft or read-only for anything with real stakes, and read the privacy policy before a tool touches your inbox, because some train on your data. Rules you wrote never leave your account. An AI turned loose on the whole inbox is a different risk.

2. Check that your ELD is still on the list. FMCSA has been decertifying electronic logging devices and pulling them from the registered list, forcing affected carriers to swap hardware, and the agency has signaled tighter self-certification for manufacturers ahead. The operator lesson doubles as an inbox lesson: the email from your ELD vendor is exactly the kind of message you cannot afford to auto-archive. Confirm your device is still registered and keep that vendor on your protected list.

3. Your records have a shelf life, and a log is your defense. Carriers must retain electronic records of duty status and their backups for six months, and supporting documents like fuel receipts and bills of lading have to corroborate the logs. A system that stamps every message or transaction with a date and files it is not overkill, it is your audit defense. When an auditor asks what came in and when, the answer should be a search, not a shrug.

Tool of the Week

Google Apps Script

This entire build runs on Google Apps Script, the free automation engine already baked into Google Workspace. It reads Gmail, writes to Sheets, sends mail, and serves a web page, all inside your own account with nothing to install and no outside service in the loop. If you already pay for Google Workspace, you are already paying for this. It is the quiet workhorse behind most of the small automations that save an operator an hour a day, and it does not show up on a single subscription invoice because it is already yours.

Cheaper on-ramp: Already have Google Workspace, or even a free Gmail account. Then you already have Apps Script. Start with one rule that files one noisy sender automatically and build from there. You do not need a developer to route your own mail.

Link: https://developers.google.com/apps-script

Free Drop

The Inbox Triage Starter Map

A plain starter template for the one thing that makes this whole system work: the sender-to-label map. A simple two-column list of who sends it and where it goes, plus a short protected-sender list for the mail that must stay in your inbox. Fill it in for your own operation and you have the blueprint for an inbox that sorts itself, whether you automate it or just build the matching filters by hand.

👉 Reply with the word INBOX and I will send you the starter map and a plain-English setup note.

True North Data Strategies Jacob Johnston | 719-204-6365 | jacob@truenorthstrategyops.com Subscribe: [opt-in link] Unsubscribe: [unsubscribe link]

Back to top