Hours-of-Service Exception Log

The problem this kills

A driver runs over their hours, an inspection flags a logbook error, or your ELD spits out a violation. Now what? In most fleets the answer is a sticky note, a forwarded email, or a "we'll talk about it" that never happens. Exceptions pile up with no categorization, no coaching trail, and no proof you did anything about them. Then a CSA audit or a roadside inspection turns one missed coaching conversation into a score problem.

The honest issue isn't that safety managers don't care. It's that there's no simple, shared place to log an exception, decide what it is, coach the driver, and prove it was handled. Spreadsheets lose the history. Email loses the approval. And nobody can answer "are violations trending up for this driver or this terminal?" without a painful afternoon of copy-paste.

What you'll build

A small, private web app for your safety and dispatch team:

• Dispatch or safety logs an HOS exception — driver, date, exception type, and notes — by hand or pasted from your ELD export. No ELD API needed.
• It gets categorized against a violation taxonomy you define during setup (e.g. 11-hour driving limit, 14-hour window, 30-minute break, form & manner, false log, personal conveyance misuse).
• The safety manager reviews each exception and approves a specific coaching or corrective action before anything closes — a real human gate, not a rubber stamp.
• A corrective-action record is written with who approved it, what action was taken, and when.
• A trend report shows exceptions by driver, by type, and over time, so you can see CSA risk building before it bites.

What's inside the Implementation Plan

The plan is a complete, paste-and-go runbook for Claude Code. It opens by interviewing you about your fleet — your current process, your ELD (or lack of one), how you name drivers and terminals, your real exception types, your volumes, and your coaching rules — so the tool is tailored to your operation instead of a generic template. The agent reads a short spec back to you and waits for your thumbs-up before it builds anything.

Then it walks you, step by step, through building the database, the login, the logging form, the categorization, the safety-manager approval gate, the corrective-action record, and the trend report — each step ending in a ready-to-paste prompt. It finishes with a verification checklist and a CSV import/export fallback so you can run the whole thing today with zero integration work.

The governance it includes (this is the point)

This isn't a toy logger. The plan bakes in the controls a safety program actually needs:

• Login so only your team can see or touch the data.
• Row-level security so each company only ever sees its own exceptions and drivers.
• A complete audit trail — who logged it, who categorized it, who approved the coaching, and exactly when.
• A human-in-the-loop approval gate — the tool drafts the coaching action, but the safety manager must review and approve before an exception is closed and committed to the record.
• Duplicate guards — a dedupe key of driver + date + exception type stops the same violation from being logged twice when an ELD export and a manual entry overlap.

Who it's for

Safety managers, compliance leads, and dispatchers at trucking and motor-carrier operations who are tired of chasing HOS exceptions across email and spreadsheets and want a defensible, auditable coaching trail — without hiring a developer or buying another enterprise platform.

You've got this. Open the Implementation Plan, paste the first prompt into Claude Code, and answer the interview — the tool will be shaped around your fleet from the very first step.