⚙️ Hand-coded rules engine · Third time building this · Still not tired of it

HOS planning for people
who'd rather not read CFR 395.

A visual Hours of Service planner that shows your drive time, rest windows, and resets before you find out the hard way.

(Built by someone who has written this rules engine twice professionally and apparently couldn't leave it alone.)

HOS Planner — live violation detection on the timeline

Why does this exist?

In the 1990s I built the HOS rules engine for RapidLog — one of the first electronic logbook products for commercial drivers. Then I built it again in the early 2000s for Logbook.com. Two full professional implementations, from scratch, against the actual regulation.

Then the industry moved to ELDs, the products moved on, and I moved on with them. But the problem never quite left me. The regulations kept changing — the sleeper berth split rules alone have been revised more times than I care to count — and I kept finding myself reading the updated CFR sections out of what I can only describe as habit at this point.

So I built it a third time. Not for a product. Not for a company. Just because I enjoy it, the developer tools are better than they were in 2002, and there was a gap in the market for a planner that actually gets the edge cases right. This one runs on Windows and in a browser, with iOS and Android on the way — which is something neither of the previous two managed.

It won't file your logs. It won't talk to your ELD. It's a planning tool — a way to think through your day before you start the engine. Third time building the engine. First time doing it purely for the love of the problem.

— The Meddling Idiot  ·  Veteran regulation implementer, current hobbyist, apparently incapable of leaving this alone

What the obsession built

Every feature exists because the regulation said it had to, or because someone on the road actually needed it. Usually both.

📋

Visual HOS Timeline

Drag-and-drop duty status markers on a scrollable timeline. Segment durations update live. See your whole day at a glance without doing the math in your head.

The math is done for you. All of it.

⚠️

Live Violation Detection

Colored violation bands appear instantly as you plan — 11-hour driving limit, 14-hour shift window, 8-hour unbroken driving, and 60/70-hour cycle all checked in real time.

Because finding out at the weigh station is not ideal.

💤

Rest Target Indicators

Markers show exactly when you hit a Global Reset, a Minimum Full Rest, or a valid Sleeper Berth Split — including paired split detection for team drivers.

Yes, the paired split logic is correctly implemented. It took a while.

🗺️

Route on the Timeline

Imported directions are overlaid directly on the timeline so you can see your position, your remaining hours, and your next rest window all at once.

Turns out knowing where you'll be is more useful than knowing where you were.

Axis Fuel Stop Search

Tap your route at any point to search the Axis network for nearby fuel stops. Fuel planning and HOS planning on the same screen.

Added because having to open a second app felt wrong.

📊

7-Day Recap

A running recap of hours used in your current cycle window. Always know exactly how much time remains before your 60-hour clock resets.

The rolling 7-day window is calculated correctly. I checked -- several times.

📎

Exceptions & Extensions

Log Shift Extensions, Agricultural Exceptions, and Adverse Conditions directly on the timeline with a long-press drag. Each one adjusts your limits accordingly.

Nothing says "I actually read the whole regulation" quite like implementing the ag exception without being asked.

👥

Multi-Driver Support

Manage multiple drivers, each with their own trip history and ruleset. Switch between them instantly — handy for small dispatch offices or team-driving households.

Data lives on-device. No cloud account, no drama.

🌙

Dark & Light Mode

A proper dark theme for nighttime cab use and a clean light theme for daytime. Toggle with one tap. Your eyes will thank you either way.

The dark mode was built first. Make of that what you will.

🧠

About the rules engine

The HOS logic is hand-coded from the regulation — not a lookup table, not a duct-taped set of if-statements. It's a proper timeline navigator that evaluates duty status sequences, computes running totals, detects qualifying rests, resolves split pairings, and flags violations. This is the third time The Meddling Idiot has written this engine from scratch — the first two shipped commercially as RapidLog and Logbook.com in the 90s and 2000s. This one is just for fun. and it's the best of the three.


Your route.
Your stops.
One screen.

Import driving directions and your full turn-by-turn route appears overlaid directly on the HOS timeline — so you can see exactly where on the map each hour of your drive lands.

Tap any point along the route to search the Axis fuel network for nearby stops. Prices, locations, and network details — right there, without opening a second app.

Because knowing you'll hit your 11-hour limit somewhere in the Nevada desert is a lot more useful if you already know where the fuel is.

HOS Planner route map with nearby fuel stops

Four steps. No manual required.

If you've ever used a calendar, you can use this. The regulations are complicated. The app doesn't have to be.

1

Add Your Driver

Name, ruleset, done. No account, no email address, no terms of service scroll.

2

Start a Trip

Set your origin and destination. Import a route to get driving directions on the timeline.

3

Plot Your Day

Drag markers onto the timeline to build your planned log. Violations flag the moment you cross a limit.

4

Relax Knowing

You've already seen your rest windows, your reset time, and your fuel stops. Now go drive.


The rules, correctly.

Select your ruleset and every limit, rest target, split calculation, and violation check adjusts automatically. These numbers come directly from the regulation.

US 60 Hours in 7 Days

The standard property-carrying ruleset for drivers operating on a 7-day cycle with a 60-hour limit.

US 70 Hours in 8 Days

Same rules as the 60-hr property ruleset but on an 8-day rolling cycle with a 70-hour limit.

US Bus 60 Hours in 7 Days

Passenger-carrying ruleset on a 7-day cycle — same driving and shift limits, adjusted rest and split rules for bus operations.

US Bus 70 Hours in 8 Days

Passenger-carrying ruleset on an 8-day cycle with a 70-hour window.

US Oilfield 60 Hours in 7 Days

The 60-hr property ruleset with support for the Oilfield exception, including Off Duty / Waiting at Well Site as a qualifying rest status.

US Oilfield 70 Hours in 8 Days

Same Oilfield exception support on an 8-day / 70-hour cycle.

US Sleeper Pilot 60 Hours in 7 Days

The 60-hr ruleset with the modified sleeper berth split rules — any combination of qualifying periods adding up to 10 hours, with no minimum larger split required.

US Sleeper Pilot 70 Hours in 8 Days

Same flexible sleeper berth split rules on an 8-day / 70-hour cycle.


Works wherever you are.

Because apparently writing one codebase that compiles to multiple platforms is exactly the kind of thing The Meddling Idiot finds relaxing.

🪟 Windows
🌐 Web Browser
🤖 Android coming soon
📱 iOS coming soon

Same app, same rules engine, same data — on every device you own.


Questions you might have

Answered with the candor of someone who has no marketing department.

Is this an ELD replacement?

No. Absolutely not. This is a planning tool. It helps you think through your day before you start driving. Your ELD records what actually happened — this helps you figure out what should happen. Use both.

Are the rules actually correct?

The rules engine has been written by the same person three times — once for RapidLog, once for Logbook.com, and now this. On more than one occasion, that same person has cited chapter and verse of CFR Part 395 to a DOT officer who turned out to be wrong about their own regulation. It was, frankly, quite fun. That said, regulations change, hobbyists are not compliance attorneys, and you should always verify anything that actually matters against the current regulation (49 CFR Part 395) or a qualified professional. But the engine itself? It's probably fine.

What does it cost?

Your first 8 trips are free — no credit card, no commitment, just use it. After that it's $3.99/month or $30/year. Cheaper than the ticket you'd get for going over hours.

Where does my data go?

Nowhere. It stays on your device. There's no account, no server, no analytics, no cloud sync. Your logs are yours.

Will you add more rulesets?

Probably. There are always more edge cases to implement. Reading another section of the regulation for the fourth time is apparently what passes for entertainment around here.


Know your hours before you leave the yard.

First 8 trips free. Then $3.99/month or $30/year. No surprises.

Android & iOS coming soon  ·  Your data stays on your device


An unhandled error has occurred. Reload 🗙