INSTIG8.

Kit 359 November 2026

Operations, courier and same-day delivery, a regional courier of about 90 employees

The 22 miles nobody claimed

A starter kit for keeping every driver DOT-compliant. Make it yours, then build it with your AI.

Lost: a false-log violation on the record, and a driver coached for sun glare. An example: how it goes today

Sources
Research only
Run
Not yet
Built clean
Not yet
The capabilityKeeping every driver DOT-compliant

Approval limits

What needs a yes, and what happens when it fails?

The kit says: Never: change a log

Rules from builds that went wrong

  • Settle every unassigned stretch within a day, with the record that shows who moved the truck.
  • Propose a driver only when the dispatch board, the login and the time agree, and hold every other stretch for the specialist.
  • Rank the camera events so the worst are watched first, and count the ones never opened.
  • Never count a clip against a driver until a person has watched it.
  • Never change a log; send every proposed change to the driver to accept, with its evidence.
The kit's whole answer
It never
Change a log; assign drive time without the driver accepting; dismiss or confirm a camera event; message a driver about their driving; write a note saying a non-driver moved a truck; answer an inspector or auditor.
Waits for a person
The specialist watches every clip before it counts against a driver, settles every held unassigned segment and writes any note that a non-driver moved a truck, holds every coaching talk and records what was agreed, and each working day spends 15 minutes on the list: 5 proposals beside their evidence, and the bottom of the camera ranking for anything misplaced.
It tells you when
Alerts go to the specialist, and to the head of Fleet Services for anything open past 3 days. Unassigned driving open past 24 hours; a proposal a driver rejected; a driver with 3 or more serious camera events in a week; a violation with no coaching record after 3 working days; a driver's medical card or licence check due within 30 days; the workflow not running, or the logging software not answering; monthly runs past 2,000; and the wrong-but-green count: proposals a driver accepted that the specialist later found wrong, and events ranked in the bottom half that the specialist judged serious.
When it breaks
What you see: no morning list, unassigned driving piling up, or proposals going to drivers who were not on the truck. Check first: the API key for the logging software still works; the dispatch board still exports; a driver or truck number has not changed. Safe fix: turn off the workflow; the specialist works the queues in the logging software by hand, as today.
Switching it off
Turning off one switch, the workflow, in the software that runs the steps. No days are pulled, no proposals go to drivers, no events are ranked. The logging devices and cameras keep recording as before, and the specialist works the queues in the logging software by hand, as today. It takes under a minute. Try it once in week one.

0 of 8 answers made yours

Free for your email. Your changes go into the build prompt, and the next kit comes each weekday.

How it goes today

A courier company of about 90 employees, with about 30 trucks under federal driving rules, is hiring one person to read every driver's logs and camera clips. Here is how a record goes unexplained while the queue waits, what went wrong for others, and a build that sorts and files every morning but changes no log on its own.

On 27 August 2026 a courier company in Indianapolis, over 40 years old and running 24/7, posted a job for a DOT safety and compliance specialist. The list starts with the daily review: “Review daily Hours of Service (HOS) violations and identify non-compliance trends.” Then: “Review and assign unassigned driving events to the appropriate drivers for verification and approval,” and “Review inward and outward-facing camera events to identify coaching opportunities”. The same person also runs yard inspections, onboarding and the safety reports.

Here is how it goes without help. At 5:40am on a Monday a driver starts truck 14 before logging in and drives 22 miles to the first pickup. At 7:15am the cab camera flags the driver as distracted. It was sun glare. The specialist is at a yard inspection, with the weekend's clips still waiting.

On Thursday afternoon the specialist reaches Monday. The 22 miles are under nobody's name, and the driver cannot remember the drive, so the note says “driver error”. The glare clip gets a coaching talk. Three weeks later a roadside inspector sees the unexplained miles and writes a false-log violation.

Nobody here is careless. One person reads about 750 driver-days a month in the order they arrived, between other duties, so Monday's miles wait until Thursday and every clip looks as urgent as every other. Federal rules say each unassigned stretch must be given to a driver or explained, and an incomplete record can be fined up to $15,846 (the maximum).

Truck 14, the times, the glare and the citation are an example. The 750 driver-days and the 80 hours a month are estimates the company's own counts replace.

Who it needs

Owns it: The safety specialist, with the head of Fleet Services. Nobody holds this? Konstellation starts with the expertise, not the build

Runs it day to day: The safety specialist. Nobody to run it? A part-time operator through INSTIG8

What went wrong for others (5)
  • “The inspector found unassigned driving time on the ELD and assumed the driver was trying to hide moving miles” A trucking compliance consultant, on a driver's roadside citation, October 2026. Read it
  • “A fleet should not clear the queue simply to make a dashboard look clean.” A logging device maker's review guide, May 2026. Read it
  • “when a manager has to open fifty files to find one genuine tailgating incident, the alerts lose their urgency.” A telematics maker, on safety teams and camera alerts, July 2026. Read it
  • “An automated alert starts the review; it does not settle the finding.” A vehicle safety supplier's coaching guide, October 2026. Read it
  • Edits that reduce automatically recorded driving time “are not allowed” A fleet telematics guide to log audits, May 2026. Read it
Sources (20)

Read 9 November 2026 unless a date is given.

  1. The job posting: NOW Courier, DOT Safety & Compliance Specialist, Indianapolis, posted 27 August 2026 and still open on 9 November 2026; quoted above
  2. The company's site: "Over 40 years in business and more than 4 million deliveries per year"; 24/7 across Indiana, including Cincinnati and Louisville (undated)
  3. FMCSA registration, Now Expedited LLC doing business as Now Courier, USDOT 4334025: 21 power units, 27 drivers (MCS-150 updated 2 April 2026; FMCSA data through 15 September 2026)
  4. FMCSA registration, NOW Courier Inc, USDOT 517485: 9 power units, 9 drivers (MCS-150 of 24 October 2024)
  5. US Bureau of Labor Statistics, wages for May 2025: compliance officers, median $38.81 an hour, $80,730 a year
  6. 49 CFR Part 386, Appendix B, penalty schedule (eCFR as of 19 February 2026): records $1,584 a day up to $15,846; carriers' non-recordkeeping violations up to $19,246
  7. LegalClarity, FMCSA civil penalties, 15 May 2026: 2025 penalty levels continue for 2026 (OMB M-26-11)
  8. Fleet Regulators, "ELD Unassigned Driving Time: Rules", 30 July 2026: 49 CFR 395.32, assign or annotate, keep six months
  9. George Schlachter, a trucking compliance consultant, on LinkedIn, 7 October 2026: a driver cited for a false log over unassigned miles, removed on a DataQs challenge
  10. Factor ELD, "Unassigned Driving: A Fleet Review Guide", 29 May 2026
  11. Geotab, "From video archives to active prevention", 22 July 2026
  12. AlwayCare, "Driver Event Review and Coaching", 9 October 2026
  13. Gridline, "Roadcheck 2026 ELD Log Audit", 14 May 2026: edits that reduce recorded driving time are not allowed
  14. Samsara developer docs: hours-of-service violations, and safety events with video (undated) and https://developers.samsara.com/reference/getsafetyeventsv2stream
  15. Motive developer docs: HOS violations, logs and log suggestions; assigning unidentified driving refuses logbook drivers (undated) and https://developer-docs.gomotive.com/reference/overview-hos
  16. Synchron Safety, Compliance Monitor: $125 a unit a month, per driver or truck whichever is greater, daily ELD and HOS log auditing (undated)
  17. Lili Safety pricing: HOS and ELD log review, $49 a driver a month, sample review (undated)
  18. Johnson DOT Services: driver log book auditing, $15 a driver a month, monthly (undated)
  19. Building it, the workflow runner: Starter, 20 euros a month billed annually, 2,500 workflow executions a month (n8n pricing, as read 5 November 2026)
  20. Building it, the model: $2 per million tokens in, $10 out for Claude Sonnet 5.5 (Claude API pricing, read 6 November 2026)

Estimates name their figures: about 36 drivers and 30 trucks (sources 3, 4); about 750 driver-days (the same, 21 working days); about 80 hours and $3,100 a month (assumed counts and minutes, source 5); the $15,846, $19,246 and $31,700 (sources 6, 7); the 190-hour ceiling (the same at 30 days and higher rates); about 25 hours redrawn and $25,600 a year freed (assumed holds and checks, source 5); about $35 a month and 750 runs (sources 19, 20); $4,500, $1,764 and $540 a month for services (sources 16, 17, 18 at 36 drivers).

Next job: Turning work order PDFs into jobs at a tile and shower repair company of just under 200 people: about 125 hours of office time a month, and about $8,300 a month of jobs that go to someone else while orders wait. Ask for a kit