Placards · Segregation · Audit trail — cited to 49 CFR

Less risk. More margin.
Every hazmat load.

A wrong placard can shut you down at the scale — out-of-service, cited, and a shipper who finds another truck. Snap the Bill of Lading. Review what it found. Get the placards 49 CFR requires before the wheels turn — plus an inspection-ready Evidence Packet you keep.

1 free scan · no card required
Built by an 8-year hazmat CDL driverUSPTO Patent PendingSHA-256 audit ledger · verify it yourself
Why operators pay for it

The two things that matter to you

Getting hazmat compliance right, fast, is what protects the load — and the premium freight that pays for it.

Shippers prepare freight that won't bounce at the dock. Brokers get a defensible record on every hazmat load they move.

Shipping hazmat? For shippers →  ·  Brokering freight? For brokers →

Less risk

Catch it before the scale house
  • Right placards, cited to 49 CFR. Catch a wrong or missing one before it's a roadside violation.
  • Segregation conflicts flagged before you load — not discovered at the dock.
  • Inspection-ready, tamper-evident record — defensible at the scale house and after an incident.
§172.504 · §172.505 · §177.848 — every decision cited

More margin

Fewer failures, faster turns
  • A compliance check in under a minute instead of a manual reg lookup.
  • Avoid the costly failures — DOT fines, out-of-service, detention, dock rejections.
  • Take on and keep the hazmat freight that pays a premium.
Compliance that moves at the speed of the dock

HaulGuard documents and assists — your verification is the legal record. It catches, flags, and reduces risk; it does not certify compliance.

< 1 min
BOL snap to cited placards
100%
placard decisions cited to 49 CFR
0 bars
needed to capture — scans upload when coverage returns
1 QR
lets an inspector verify your record — no account
USPTO Patent Pending
Application No. 64/048,483
Lawyer-drafted policies
Terms · EULA · Privacy
Live system status
status.haulguard.ai
Independently verifiable
SHA-256 hash-chained audit ledger
How It Works

Three steps from cab
to Evidence Packet.

You just watched the scan. Here's the step that makes it a legal record — you verify, then hand it over. Built for a driver at a truck stop with one hand on the wheel.

1

Scan

Snap the Bill of Lading or hazmat manifest — the AI reads every material and cites the 49 CFR section behind each placard. (That's the demo above.)

2

Verify

This is where HaulGuard earns its keep. You check every extracted row against the paper; every correction is captured with full provenance — what the AI read, what you changed, and why. You're still the verifier — HaulGuard makes sure you're verifying against the right answer, and gives you the record to prove it.

3

Hand over

Inspection-ready PDF Evidence Packet generates with the placard determination, your attestations, your CDL credentials, and a SHA-256 hash linking everything to the tamper-evident audit chain. Hand it to a DOT officer at roadside.

What You Get

Inside your
Evidence Packet.

A single PDF that compiles everything a DOT inspector or post-incident auditor would ask for. Generated for every scan, downloadable and emailable.

Cover
Scan ID, timestamp (UTC + local), driver name, carrier, scanned-by attribution.
Materials
Every material extracted from the BOL — UN number, proper shipping name, hazard class, packing group, weight, ERG guide reference.
Required Placards
Each placard with the controlling 49 CFR section (e.g., 49 CFR § 172.504(e)) and the reason it was triggered.
Driver Attestations
Per-material verification chain plus Placard Conformance and Route Advisory acknowledgments — each with the field values frozen at attestation time.
CDL Credentials
CDL number, issuing state, class, endorsements, expiration; HME expiration if held — with provenance tag (OCR-extracted, driver-corrected, or driver-attested).
Audit Chain Proof
SHA-256 hash linking this scan to the immutable ledger; verification command an inspector can run independently to confirm the chain hasn't been altered.
Disclaimers
Honest framing of what AI Output is and isn't — your verification is the legal record, not the OCR extraction.

Illustrative sample — the format and information in every real packet

HAULGUARD AI
Compliance Evidence Packet — Scan 4471-A
Generated 06/18/26 · Mesa Chemical Supply → PHX Terminal · Driver-verified
CHAIN INTEGRITY: VERIFIED · SHA-256
Materials — 3 lines read · 2 regulated
UN1203 Gasoline — Class 3, PG II · 400 gal
UN1789 Hydrochloric acid — Class 8, PG II · 12 drums
Placards Required
FLAMMABLE (Class 3) — 49 CFR § 172.504
CORROSIVE (Class 8) — 49 CFR § 172.504
Segregation § 177.848 — no conflict
Driver Verification
Each material verified against the paper · corrections recorded with provenance
Verify this chain on your own device:
haulguard.ai/verify — head hash printed here

Data from the demo load above. Every real packet prints its own scannable QR; an inspector verifies the chain at haulguard.ai/verify with no account.

Every section grounded in the live Terms of Service, EULA, and Privacy Policy — drafted by outside counsel.

Live Today

Real product. Real artifacts.
No "coming soon".

Every feature below is shipping in production today. Items still on the roadmap aren't on this page on purpose — when they ship, they show up here.

AI hazmat scanner

Bill of Lading and hazmat manifest OCR. Extracts every material with UN number, hazard class, packing group, weight, ERG. Determines required placards under 49 CFR § 172.504 and runs the segregation matrix check from § 177.848.

CDL credential capture

Front + back OCR with HME (Hazmat) expiration parsing. Each field tagged with provenance — OCR-extracted, driver-corrected, or driver-attested — so an inspector can see exactly how every credential value was sourced.

Tamper-evident Audit Ledger

Every scan, attestation, credential capture, and admin action lands in an append-only SHA-256 hash-chained ledger. An auditor or opposing counsel can independently verify integrity with one command. 3-year minimum retention enforced by design.

Inspection-ready Evidence Packet

Single PDF combining the placard determination, driver attestations, CDL credentials, and audit chain proof. Generated for every scan. Downloadable, emailable, and shareable as a tamper-resistant URL with QR code for first responders.

See HaulGuard working.

Real screens from the driver app, public verifier, and fleet dashboard — captured on a sample fleet, not mockups. Tap any image for the full screen.

Exhibit · driver app

A completed driver record

Placards, cited reasoning, driver attestations, and audit status in one place. What to notice:

  • ✓AUDIT COMPLETE — every attestation on file before the wheels turn.
  • ✓Each attestation cites its rule — placard conformance to § 172.332, and a signed acknowledgment that route selection under Part 397 stays with the carrier.
  • ✓PDF button — the Evidence Packet a driver hands an inspector, generated from this record.

Tap the image to see the full screen.

Public verifier — 31 of 31 chain links re-hashed in the inspector’s own browser; the head hash matches the one printed on the Evidence Packet. No account, no trusting HaulGuard. Try it live →
Fleet dashboard — which shippers hand your fleet defective paperwork, and the compliance signal an insurer could price against — with the sample size shown next to every rate.
Real screenshot · sample fleet data
Get Started

Try it free.
Scan your first load today.

One free scan with the full audit trail. No credit card required to start. Founding Member pricing locks in for 12 months from your first paid month.

Start free scan See per-load pricing
Hazmat Compliance FAQ

Common questions about hazmat placarding, BOLs, and PHMSA inspections.

When does a load require hazmat placards under 49 CFR? +

Under 49 CFR 172.504, any quantity of Table 1 materials — Class 1.1, 1.2, 1.3 explosives, Class 2.3 inhalation-hazard gases, Class 4.3 dangerous-when-wet materials, certain Class 6.1 PG I poison-by-inhalation, and Class 7 (Radioactive Yellow III) — requires placards. For Table 2 materials, placards are required when the aggregate gross weight reaches 1,001 pounds across all hazmat in the vehicle.

What information is required on a hazmat Bill of Lading? +

49 CFR 172.202 requires the proper shipping name, hazard class or division number, UN/NA identification number, packing group (in Roman numerals), total quantity, and the number and type of packages. The hazmat description must appear in the prescribed sequence and be distinguishable from any non-hazmat entries on the same shipping paper.

Does HaulGuard AI replace a hazmat employer’s training program? +

No. HaulGuard AI is a documentation and verification tool. Carriers remain responsible for hazmat employee training under 49 CFR 172.704, and drivers remain responsible for the accuracy of their shipping papers. HaulGuard supports compliance by generating cited reasoning and a tamper-evident audit trail for each load — it does not substitute for required training, driver qualification, or motor-carrier supervision.

How does HaulGuard AI support PHMSA inspections? +

Each load generates an inspection-ready evidence packet: the cited 49 CFR reasoning behind the placard determination, the BOL data as read and as the driver verified it, the driver’s CDL credentials with hazmat-endorsement status, and a tamper-evident attestation chain. Drivers and fleet managers can produce the full record at roadside or during a post-incident audit, reducing the time and uncertainty of demonstrating compliance.

Which hazmat classes does HaulGuard AI support? +

HaulGuard AI supports placarding determination across all nine DOT hazard classes: Class 1 explosives (with division and compatibility-group reasoning), Class 2 gases, Class 3 flammable liquids, Class 4 flammable solids and dangerous-when-wet, Class 5 oxidizers and organic peroxides, Class 6 toxic and infectious substances, Class 7 radioactive materials, Class 8 corrosives, and Class 9 miscellaneous dangerous goods, including the Dangerous placard logic at 49 CFR 172.504(b).

Does it work without cell service? +

Capture does. At a remote dock or scale house with no signal, photograph the BOL as usual — the pages are stored on your phone and the scan uploads itself when coverage returns. The placard determination itself runs server-side, so results arrive once you’re back in coverage. Your recent scan results and the full ERG 2024 emergency-response guide are cached on-device, so you can read them back with no signal at all.

What if the AI reads something wrong? +

You’re still the one making the call. HaulGuard reads the Bill of Lading and shows you what it found, but you review every field against the paper before you finalize the scan. If something needs fixing, correct it before you continue. Your review and verification become part of the Evidence Packet, along with a record of what changed — your verification, not the OCR, is the legal record.

What if my shipper made a mistake on the BOL? +

HaulGuard flags what it finds — a missing packing group, a shipping-description problem — each cited to the 49 CFR section behind the flag. Correctable fields can be fixed during your verification, and every correction lands in the append-only audit chain. Anything still open is disclosed in the Evidence Packet rather than hidden, so the record shows you caught the problem, and when.

Can a DOT inspector verify my Evidence Packet? +

Yes — on their own phone, with no HaulGuard account. Every packet prints a QR code and URL for the public verifier at haulguard.ai/verify. That page fetches the audit chain’s hashes (no driver data) and re-runs the SHA-256 verification in the inspector’s own browser, proving the record hasn’t been altered since it was written.