Three Parts of TraceNet That Save You Time on 406/19 Hauling Records

Running Ontario soil, you already know the 406/19 workflow: record created and confirmed accurate before departure, record in the vehicle throughout transport, acknowledgment at the deposit site, copies at both ends, two-year retention. None of it is optional. What changes is how long each step takes when the tool is built around it.

Here are three parts of TraceNet built around that workflow.

Ontario hauling record: driver lookup by plate

The Ontario hauling record has fields for driver first name, last name, phone, company, and plate. Drivers are stored at the project level.

When you start typing a plate, the form filters the project's drivers by plate and suggests matches. Pick one, and the rest of the driver's info fills in and locks. It's saved, so it doesn't get edited by accident. If the info actually needs to change — new phone, new company, a different driver on that same plate — the reset button clears the line and lets you type fresh values. The new data gets saved back to the project's driver roster when you submit.

Why that saves you time: on the first load of a project you enter driver info once. Every subsequent load for the same driver, you enter the plate with autocomplete. That's four fields down to one. On an active site with a regular crew running a lot of hauls, it adds up quick.

Manifest download by QR code

When generating a new transaction, the app will show a QR code. Behind the code is a one-time download link, that returns the manifest PDF. Show that QR code to your driver and with a simple QR scan on his phone, the driver will obtain the transport manifest to comply with the regulations.

Why that saves you time: No app download, no registration, no time loss. Simple... like scanning a QR code.

Moreover, the QR dialog is available from both the desktop and the mobile transaction screens, so it works on whatever device you're on when the ask comes up.

Mobile transaction form: same driver flow, same PDF

The mobile transaction form has the same driver flow as the desktop form: plate typed, matches filtered, existing driver auto-filled and locked, reset to enter fresh info. Whatever your field tech or super does on a phone/tablet at the site, your office sees the same structured driver record on the transaction instantly.

The common thread

Compliance is already happening. You can't move a load without the record. What TraceNet does is shave seconds to minutes off each step of a record that's going to get filled in anyway. A few seconds per load, across a multi-project season, is the real return. We've seen field technicians going from dozens of loads a day to over a 100. Projects shifting from 3 field techs to 1. Massive cost savings can be achieved by accelerating this transport bottleneck.

If you haven't tested the driver autocomplete yet, have a look! If you've never used the QR manifest transfer, try it on the next manifest you generate. And for a walkthrough before your next project, book a demo!

Jean-Sébastien Rolland

General Manager, TraceNet.ca

1-833-922-0999