// principles

Show your work

A compliance finding can cost a carrier a safety rating or a driver a job. Software that produces one has to be able to explain itself. That is the idea behind everything Justin Seyl's team at Waypoint True builds.

Rules you can read

The Hours of Service rules are precise: 11 hours of driving, a 14-hour window, a 30-minute break after 8 hours of driving. Precise rules deserve precise checks. Verity's rules engine is deterministic: given the same logs it always reaches the same result, and each check is tied to the section of 49 CFR Part 395 it enforces. AI helps where it is good at the job, such as reading a scanned paper log or a crumpled receipt. It does not decide whether a driver broke a rule.

Evidence with every finding

A finding without evidence is just an accusation. Every possible violation comes with the times, the log events and the documents behind it, lined up so an auditor can see in seconds why it was flagged.

A person makes the call

Logs have context that software cannot see: a weather delay, an exemption a carrier qualifies for, an unusual load. So Verity never closes a finding on its own. An auditor confirms or dismisses each one. The software does the hour of tedious cross-checking; the professional does the judgment.

Earned trust

Waypoint True measures its software against audits whose answers were confirmed by experienced staff auditors, and blocks any change that would contradict one of those confirmed rulings. The goal is simple: the tool should be at least as careful as the people who use it.

These principles come from Justin's years running compliance companies where the work was done by hand. For plain-English explanations of the rules themselves, see justinseyl.info.