Verify before
the load leaves.

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.

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.

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.

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.

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).

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.

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.

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.

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.