PRODUCT WALKTHROUGH

See VerifyFreight in action.

From manifest upload to a full 49 CFR compliance report โ€” here's exactly how it works, step by step.

1
Sign In
2
Upload
3
Analysis
4
Results
5
Resolve
6
Compare
7
History
01

Log in with your credentials

Access the VerifyFreight platform securely using your company email and password. Authentication is handled via AWS Cognito JWT โ€” your session and data are fully isolated from other tenants.

๐Ÿ”’ AWS Cognito Auth ๐Ÿข Multi-Tenant Isolation ๐Ÿ”‘ TLS Encrypted
app.verifyfreight.com
02

Upload your manifest

Drag and drop your hazmat shipping manifest directly into the platform. VerifyFreight accepts multiple file formats โ€” no manual data entry required. AWS Textract immediately begins extracting structured hazmat data.

๐Ÿ“„ PDF ๐Ÿ“Š CSV ๐Ÿ–ผ๏ธ JPEG / PNG / TIFF ๐Ÿ“‹ Scanned Documents โšก Max 50MB
app.verifyfreight.com/upload
โœ“VF Upload History Sign out
Upload Manifest
Upload a hazardous materials shipping manifest for 49 CFR compliance analysis.
โ†‘
Drop your manifest here
or click to browse
PDF, CSV, JPEG, PNG, TIFF โ€” max 50MB
Select a file to continue
03

Click "Analyze Manifest" and watch the process

Once uploaded, click Analyze Manifest. The dual-engine pipeline runs automatically โ€” AWS Textract extracts the hazmat fields, the deterministic CFR Rules Engine validates standard requirements, and focused AI reasoning handles complex checks like load compatibility and special provisions.

๐Ÿ” AWS Textract OCR โš™๏ธ CFR Rules Engine ๐Ÿง  AI Reasoning โฑ๏ธ ~60โ€“90 seconds
app.verifyfreight.com/upload
โœ“VF Upload History Sign out
Upload Manifest
Upload a hazardous materials shipping manifest for 49 CFR compliance analysis.
โ†ป
Processing your manifest
This takes about 60โ€“90 seconds
โœ“
Manifest uploaded
โœ“
Reading document
3
Extracting hazmat fields
4
Running CFR analysis
5
Generating report
6
Complete
04

Review your compliance results

After analysis completes, you receive a full compliance report. Each violation is tagged by severity (Critical, Warning, Advisory), the specific CFR section it violates, and whether it was detected by the Rules Engine or AI โ€” giving you full transparency for DOT audits.

๐Ÿ”ด Critical ๐ŸŸ  Warning ๐Ÿ”ต Advisory โš™๏ธ Rules Engine ๐Ÿง  Claude AI
app.verifyfreight.com/results
Download PDF
โ† โœ“VF Upload History Sign out
Non-Compliant tman04.pdf
12 of 12 violations still open 0%
8Critical
3Warning
1Advisory
12Total
49 CFR ยง172.101WarningRules Engine
UN3264 was not found in the local ยง172.101 reference table โ€” requires verification
โ†’ Verify this UN number against the complete DOT Hazardous Materials Table at phmsa.dot.gov.
49 CFR ยง172.101CriticalRules Engine
No hazard class was found in the manifest. Hazard class is required per ยง172.101.
โ†’ Add the hazard class for each material (e.g. Class 3, Class 8). Must match the UN number per ยง172.101.
49 CFR ยง172.202(a)(1)CriticalClaude AI
Proper Shipping Name is required on shipping papers for all hazardous materials shipments.
โ†’ Add the Proper Shipping Name for each entry (e.g. 'Flammable liquid, n.o.s.' for UN1993).
05

Work through violations and resolve them

Each violation has a status dropdown your team can update as they work through corrections. Track progress in real time โ€” from open to acknowledged, shipper contacted, corrected, or fully resolved. Every status change is timestamped and attributed to the user who made it.

Open
โ†’
Acknowledged
โ†’
Shipper Contacted
โ†’
Corrected
โ†’
Resolved
๐Ÿ‘ค User attribution ๐Ÿ• Timestamped ๐Ÿ“ Accepted with note ๐Ÿšจ Escalated
app.verifyfreight.com/results
Download PDF
49 CFR ยง172.101WarningRules Engine
UN3264 was not found in the local ยง172.101 reference table โ€” requires verification
Updated by kerron@verifyfreight.com ยท 5/31/2026, 1:50:49 PM
โœ“ Acknowledged
49 CFR ยง172.101CriticalRules Engine
No hazard class was found in the manifest. Hazard class is required per ยง172.101.
Updated by kerron@verifyfreight.com ยท 5/31/2026, 1:50:47 PM
๐Ÿ“ž Shipper Contacted
49 CFR ยง172.101CriticalRules Engine
No proper shipping name was found in the manifest.
โ†’ Add the proper shipping name for each material exactly as listed in ยง172.101.
Open
Acknowledged
Shipper Contacted
Corrected
Accepted (with note)
Escalated
Resolved
06

Compare old and new โ€” then download your report

Have a corrected manifest ready? Upload it to see exactly which violations were fixed. When all violations are resolved, the progress bar hits 100% and the shipment is cleared for authorization. Download the full compliance report as a PDF for your records and DOT audits.

๐Ÿ“ค Upload corrected manifest โœ… Side-by-side comparison ๐Ÿ“ฅ Download PDF report ๐Ÿšš Authorize shipment
app.verifyfreight.com/results
Download PDF
Non-Compliant tman04.pdf
โœ“ All violations resolved โ€” ready to authorize shipment 100%
Have a corrected manifest?
Upload it to see exactly which violations were fixed.
Select file
8Critical
3Warning
1Advisory
12Total
49 CFR ยง172.101Warning
UN3264 was not found in the local ยง172.101 reference table โ€” requires verification
Updated by kerron@verifyfreight.com ยท 5/31/2026, 1:52:53 PM
โœ“ Resolved
49 CFR ยง172.101Critical
No hazard class was found in the manifest. Hazard class is required per ยง172.101.
Updated by kerron@verifyfreight.com ยท 5/31/2026, 1:52:54 PM
โœ“ Resolved
07

Check your full compliance history

Every analyzed manifest is logged in your searchable history dashboard. See status, result, and resolution progress at a glance. Records are archived for 90 days in development and 3 years in production โ€” everything you need when PHMSA comes calling.

๐Ÿ” Fully searchable ๐Ÿ“… Timestamped records ๐Ÿญ 90 days (dev) / 3 years (prod) ๐Ÿ“‹ PHMSA audit ready
app.verifyfreight.com/history
โœ“VF Upload History Sign out
Compliance History
8 manifests analyzed
+ New analysis
FILEDATESTATUSRESULTRESOLUTION
๐Ÿ“„ tman04.pdf May 31, 2026, 01:48 PM Complete Non-Compliant โœ“ All resolved
๐Ÿ“„ tman02-cor.pdf May 31, 2026, 10:33 AM Complete Non-Compliant 0/11 resolved
๐Ÿ“„ tman02.pdf May 31, 2026, 10:02 AM Complete Non-Compliant โœ“ All resolved
๐Ÿ“„ tman01.pdf May 30, 2026, 12:44 PM Complete Non-Compliant โœ“ All resolved