HaulGuard started with drivers. We're now building the broker-facing side: per-load compliance verification and a tamper-evident record that protects you when a load you put on a carrier goes wrong. (Shipper? Your page is haulguard.ai/shipper.)
When a hazmat load is mis-placarded or wrongly combined, the liability doesn't stop at the carrier — under 49 CFR it can reach everyone who touched the shipment. HaulGuard gives you a documented check on every load.
Three layers. Each one has its own job. None of them replaces the next.
Vision model reads printed text, handwritten additions, struck-through lines, and multi-page manifest packets. Confidence is captured on every field so the next layer knows what it has to verify.
Rules engine runs against authoritative tables — 40 CFR 261 hazardous waste codes, 49 CFR 172.101 hazmat table, the 2024 PHMSA ERG index (1,982 entries loaded deterministically). Anywhere there is a published authoritative source, the AI does not get to vote.
Every extracted material is presented for line-by-line driver attestation before any verdict appears. The output is a tamper-evident load record — the papertrail a DOT inspector reads at roadside.
Patterns drawn from our analysis pipeline on real anonymized hazmat manifests. Each is cited to a specific section of 40 CFR (EPA) or 49 CFR (DOT). Tap any finding to expand.
Box 8 (Designated Facility Name and Site Address) had the wrong destination crossed out with diagonal pen lines and the correct one written in by hand below — no initials on the cancellation. Likely auto-populated from the wrong template, then field-corrected. Box 8 is the regulatory authority for who is accepting the waste; visible correction without initials is not a defensible documentation pattern.
Transporter 1 signature dated two days after Transporter 2 took possession — temporally impossible. Likely a handwritten date error on one of the two signatures. The chain of custody on paper does not match the operational reality. If the shipment is later subject to a discrepancy investigation, the inverted dates become evidence of documentation that was not carefully reviewed.
Debris contaminated with methanol and acetonitrile, declared with F002. F002 covers specific halogenated solvents (1,1,1-trichloroethane, methylene chloride, perchloroethylene) — neither methanol nor acetonitrile is in F002. Both are in F003. The codes-vs-constituent check is deterministic against the named-chemical lists; no lab analysis can justify F002 without halogenated-solvent contamination in the description.
Based on a real anonymized scan run by our analysis pipeline. The validation rules above are live in our driver-side workflow today; the broker-facing product is in active development.
Every load you put on a carrier gets verified and sealed into a tamper-evident record — before it ever rolls.
Tell us a bit about you. We're onboarding design-partner brokers and 3PLs now — we'll reach out as access opens.
Thanks — we'll be in touch as early access opens. Questions in the meantime? info@haulguard.ai