Access to the load — not access to your transportation system.
Send the driver a secure load-specific link by SMS or email. They open it in the browser, approve required tracking, and follow the live execution plan through final delivery — no app install, driver account, or separate tracking service required.
One secure browser session from dispatch through final evidence.
CarrierTool does not require a driver to install a mobile application or maintain a CarrierTool account. The load itself creates the secure execution context. The driver follows the approved sequence, receives changes, completes required actions, and provides evidence through the browser already on the device.
Access to the load, not access to the TMS.
The execution link is scoped to the particular load and its lifecycle. The assigned driver receives the instructions and capabilities required to execute that freight without exposing the tenant's broader operating system.
No Install. No Driver Account.
A secure load-specific link is sent by SMS or email. The driver opens CarrierTool in the phone or tablet browser and receives only the execution context required for that load.
Enforced Stop Sequence
The driver follows the approved load plan in sequence. Required arrival, check-in, check-out, completion, and evidence actions control progression instead of leaving execution to an open-ended checklist.
Adaptive Location Tracking
After the driver grants location permission, CarrierTool collects operational location telemetry during the active load. Tracking can become more frequent near planned stops to support precise geofence events and execution visibility.
Actual vs. Driver-Reported Events
Geofence arrivals and departures provide an independent operational timestamp alongside driver-claimed arrival, departure, and completion events.
Live Route Changes
If operations applies a new optimized sequence or manually changes the remaining route, the active driver session receives the revised plan and prompts the driver to review it. Dispatch can include a note explaining the change.
Stop-Specific Evidence
Each stop can require different proof: BOL or POD, reefer temperature, pallet condition, delivery photos, display/setup photos, signatures, quantities, receipts, or exception evidence.
FreightIQ™ At Submission
Evidence is evaluated by FreightIQ when the driver submits the action. The requirement can be verified or kept actionable immediately instead of waiting for a later document-review process.
Immutable Verified Evidence
After FreightIQ verification or authorized dispatch confirmation, accepted evidence becomes part of the immutable execution record. Failed evidence can be superseded by replacement evidence without silently erasing the original chain.
Evidence isn't collected and reviewed later. It's evaluated while the freight is moving.
Every required driver action can be evaluated by FreightIQ™ at submission. CarrierTool retains the load, stop, requirement, time, location, driver-session, AI decision, and authorized human-resolution context needed to understand the execution record.
Customer and load rules define what must be completed.
The driver submits evidence inside the active stop workflow.
FreightIQ evaluates the evidence immediately against the requirement.
Exceptions stay actionable and authorized human decisions remain attributable.
Accepted evidence becomes immutable with its execution history.