Connects to the tools you use
Set up connections through ERP.AI and Proto workflows, with every change logged.
- Trailer Tracking System
- Telematics provider
- Partner dispatch system
- Delivery document service
- Accounting platform
Trailer Tracking System connects registered trailer assets to yard visits and the loads they support. After departure, yard teams save the visit with the identified trailer, its observed yard location, actual arrival and departure timestamps, and the applicable grace period.
Loads in one list
Yard Supervisor approves or rejects the submitted visit after checking the trailer, times and grace period.
Every feature works on the same records. Pick one to see the screen your team works in.
Identify each trailer and the transport partners responsible for its load handoffs.
Vehicles
| Unit number | Name | Asset type | Plate | Status | Organization | |
|---|---|---|---|---|---|---|
| VHC-70680 | Dry van trailer 218 | Trailer | NV 8TR421 | Available | Silver Basin Transport Co. | |
| VHC-84879 | Reefer trailer 64 | Trailer | CA 9LK772 | In Service | Elm River Freight Group | |
| VHC-77561 | Day cab tractor 31 | Trailer | WA 4BC118 | Maintenance | Westhaven Haulage Ltd. | |
| VHC-93919 | Flatbed trailer 107 | Trailer | OR 7PF503 | Out of Service | Cedar Route Logistics | |
| VHC-80237 | Dry van trailer 224 | Trailer | ID 2RM649 | Available | Ridgeway Fleet Services |
Record trailer location and visit times, then review the evidence for detention and closure.
Approval conditions
| Visit number | Trailer asset | Yard | Trailer location | Arrival timestamp | Departure timestamp | |
|---|---|---|---|---|---|---|
| TV-82181 | Flatbed trailer 107 | Reno east yard | Row B, slot 14 | 2026-10-14 06:42 | 2026-10-14 07:18 | |
| TV-35414 | Dry van trailer 224 | Boise trailer yard | Row C, slot 6 | 2026-10-14 08:15 | 2026-10-14 09:02 | |
| TV-64997 | Sleeper tractor 18 | Fresno cold-chain yard | Dock 8 | 2026-10-14 09:33 | 2026-10-14 10:11 | |
| TV-28002 | Reefer trailer 64 | Phoenix south yard | Reefer row, slot 3 | 2026-10-14 11:20 | 2026-10-14 12:06 | |
| TV-36029 | Dry van trailer 218 | Tacoma port yard | Inspection bay 2 | 2026-10-14 13:05 | 2026-10-14 14:22 |
Prepare the load and its stops, then allocate eligible drivers and trucks without reusing active commitments.
Loads
| Record number | Subject | Lane | Planned departure | Planned arrival | Promised delivery at | |
|---|---|---|---|---|---|---|
| LDS-25490 | Reno to Boise retail replenishment | Reno, NV to Boise, ID | 02 Nov | 09 Nov | 13 Nov | |
| LDS-49085 | Fresno to Phoenix produce load | Fresno, CA to Phoenix, AZ | 18 Oct | 23 Oct | 27 Oct | |
| LDS-70210 | Tacoma to Spokane lumber haul | Tacoma, WA to Spokane, WA | 11 Oct | 13 Oct | 22 Oct | |
| LDS-84919 | Sacramento to Salt Lake freight | Oakland, CA to Reno, NV | 22 Oct | 28 Oct | 06 Nov | |
| LDS-88865 | Oakland to Reno appliance load | Portland, OR to Bend, OR | 19 Oct | 26 Oct | 28 Oct |
Follow planned stop windows and reported milestones through the load's journey.
Tracking events
| Event number | Load | Event type | Occurred at | Location | Source | |
|---|---|---|---|---|---|---|
| TE-69131 | Fresno to Phoenix produce load | Departure | 04 Nov | Reno distribution center | Driver App | |
| TE-84595 | Eugene to Medford paper shipment | Arrival | 12 Oct | Boise retail depot | Telematics | |
| TE-73676 | Portland to Bend grocery transfer | Stop Arrival | 04 Nov | Fresno cold storage | Dispatcher | |
| TE-21511 | Eugene to Medford paper shipment | Stop Departure | 20 Oct | Phoenix produce hub | Partner | |
| TE-78338 | Fresno to Phoenix produce load | Delay | 21 Oct | Tacoma lumber yard | Driver App |
Verify delivery confirmation against the correct delivered load and completed delivery stop.
Load stops
| Stop number | Load | Stop type | Sequence | Location | Window start | |
|---|---|---|---|---|---|---|
| LS-17936 | Fresno to Phoenix produce load | Pickup | 80 | Reno distribution center | 27 Oct | |
| LS-65512 | Tacoma to Spokane lumber haul | Delivery | 30 | Boise retail depot | 23 Oct | |
| LS-83609 | Fresno to Phoenix produce load | Service | 60 | Fresno cold storage | 28 Oct | |
| LS-84489 | Fresno to Phoenix produce load | Pickup | 90 | Phoenix produce hub | 14 Oct | |
| LS-12923 | Reno to Boise retail replenishment | Delivery | 60 | Tacoma lumber yard | 23 Oct |
Keep inspection findings, open defects and maintenance due dates available during equipment planning.
Vehicle defects
Review load charges alongside trailer visits, delivery evidence and recorded operational decisions.
Approval waits for the finance reviewer
| Charge number | Load | Charge type | Amount | Currency | Status | |
|---|---|---|---|---|---|---|
| FC-94857 | Eugene to Medford paper shipment | Linehaul | 340 | USD | Draft | |
| FC-30556 | Portland to Bend grocery transfer | Fuel Surcharge | 880 | CAD | Draft | |
| FC-61627 | Sacramento to Salt Lake freight | Accessorial | 130 | MXN | Draft | |
| FC-73410 | Oakland to Reno appliance load | Detention | 820 | EUR | Draft | |
| FC-49922 | Fresno to Phoenix produce load | Layover | 360 | GBP | Draft |
Trailer arrival to verified delivery ships ready to use. One step needs a named approval before the work moves on: Review visit (Yard Supervisor).
Identify the trailer and its operating organization before recording a yard stay.
Prepare the load and stop sequence with the delivery promise visible.
Capture the yard location, actual visit times and agreed grace period.
Check the submitted visit and record the decision before closure.
Reconcile the visit duration with its closure receipt and supporting evidence.
Match the receiving evidence to the delivered load and its completed delivery stop.
Open any load to see its freight charges, the roles that work on it, its process stages and its approvals on one page.
Lane, Requested units, Equipment class and Planned departure.
Each line is linked to this load.
Admin, Yard Operator and Yard Supervisor, each with their own permissions.
Plan load and Assign resources, with the role that acts.
Review visit, with who decides.
Reno, NV to Boise, ID · Planned
| Charge number | Load | Charge type |
|---|---|---|
| FC-94857 | Eugene to Medford paper shipment | Linehaul |
| FC-30556 | Portland to Bend grocery transfer | Fuel Surcharge |
| FC-61627 | Sacramento to Salt Lake freight | Accessorial |
Signed in as Yard Supervisor
| Decision | Approver | |
|---|---|---|
| Review visitCheck the submitted visit and record the decision before closure. | Yard Supervisor | |
| Approve trailer visits | Yard Supervisor | |
| Approve freight charges | Finance Reviewer |
Everyone opens Trailer Tracking System to the work that is theirs. Pick a role to see what it starts with.
Configures organization records, staff identities and the agreed operating access.
Records the identified trailer's yard visit and gathers arrival and departure evidence.
This is the first screen this role sees.
Trailer visits · Yard Operator
Reviews submitted trailer visits and the evidence needed to authorize closure.
This is the first screen this role sees.
Trailer visits · Yard Supervisor
| Visit number | Trailer asset | Yard | Trailer location | Arrival timestamp | Departure timestamp | |
|---|---|---|---|---|---|---|
| TV-82181 | Flatbed trailer 107 | Reno east yard | Row B, slot 14 | 2026-10-14 06:42 | 2026-10-14 07:18 | |
| TV-35414 | Dry van trailer 224 | Boise trailer yard | Row C, slot 6 | 2026-10-14 08:15 | 2026-10-14 09:02 | |
| TV-64997 | Sleeper tractor 18 | Fresno cold-chain yard | Dock 8 | 2026-10-14 09:33 | 2026-10-14 10:11 | |
| TV-28002 | Reefer trailer 64 | Phoenix south yard | Reefer row, slot 3 | 2026-10-14 11:20 | 2026-10-14 12:06 | |
| TV-36029 | Dry van trailer 218 | Tacoma port yard | Inspection bay 2 | 2026-10-14 13:05 | 2026-10-14 14:22 |
Plans loads, coordinates eligible transport resources and maintains stop and tracking information.
This is the first screen this role sees.
Load stops · Dispatcher
| Stop number | Load | Stop type | Sequence | Location | Window start | |
|---|---|---|---|---|---|---|
| LS-17936 | Fresno to Phoenix produce load | Pickup | 80 | Reno distribution center | 27 Oct | |
| LS-65512 | Tacoma to Spokane lumber haul | Delivery | 30 | Boise retail depot | 23 Oct | |
| LS-83609 | Fresno to Phoenix produce load | Service | 60 | Fresno cold storage | 28 Oct | |
| LS-84489 | Fresno to Phoenix produce load | Pickup | 90 | Phoenix produce hub | 14 Oct | |
| LS-12923 | Reno to Boise retail replenishment | Delivery | 60 | Tacoma lumber yard | 23 Oct |
Maintains fleet and driver records and follows defects through repair.
This is the first screen this role sees.
Load assignments · Fleet Coordinator
Reconciles delivery evidence and operational outcomes against their source records.
This is the first screen this role sees.
Load stops · Evidence Reviewer
| Stop number | Load | Stop type | Sequence | Location | Window start | |
|---|---|---|---|---|---|---|
| LS-17936 | Fresno to Phoenix produce load | Pickup | 80 | Reno distribution center | 27 Oct | |
| LS-65512 | Tacoma to Spokane lumber haul | Delivery | 30 | Boise retail depot | 23 Oct | |
| LS-83609 | Fresno to Phoenix produce load | Service | 60 | Fresno cold storage | 28 Oct | |
| LS-84489 | Fresno to Phoenix produce load | Pickup | 90 | Phoenix produce hub | 14 Oct | |
| LS-12923 | Reno to Boise retail replenishment | Delivery | 60 | Tacoma lumber yard | 23 Oct |
Reviews load charges and their supporting visit or delivery evidence.
This is the first screen this role sees.
Freight charges · Finance Reviewer
| Charge number | Load | Charge type | Amount | Currency | Status | |
|---|---|---|---|---|---|---|
| FC-94857 | Eugene to Medford paper shipment | Linehaul | 340 | USD | Draft | |
| FC-30556 | Portland to Bend grocery transfer | Fuel Surcharge | 880 | CAD | Draft | |
| FC-61627 | Sacramento to Salt Lake freight | Accessorial | 130 | MXN | Draft | |
| FC-73410 | Oakland to Reno appliance load | Detention | 820 | EUR | Draft | |
| FC-49922 | Fresno to Phoenix produce load | Layover | 360 | GBP | Draft |
Review trailer stays, delivery outcomes, fleet exceptions and supported freight charges.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Draft | 26 | ||
| Planned | 11 | 42% | |
| Dispatched | 4 | 36% | |
| In Transit | 1 | 25% |
Sample totals per stage
Which recorded stays need action from the yard team, and which trailer and load do they concern?
Which completed stays contribute detention, and what arrival, departure and grace period explain the duration?
Which active trailers are available, in service or awaiting maintenance attention?
How do recorded arrivals compare with the agreed stop windows?
Which delivered loads met their delivery promise, and which need investigation?
Which confirmations remain captured or disputed, and what evidence can the reviewer inspect?
Which assets have open repair work or service dates needing attention?
What amounts remain at each charge status within the same currency?
See how Trailer Tracking System fits your kind of team.
Keep trailer visits and dispatch handoffs connected across yard shifts.
Connect trailer arrival, delivery appointments and detention evidence at distribution yards.
Keep partner handoffs, trailer visits and disputed transport evidence tied to the correct load.
Each stage of trailer arrival to verified delivery names the role that acts and the status it records, so a change is never anonymous.
Each stage, the role that acts and the status it records
Use Proto to prepare yard reviews and investigate connected load evidence.
Set up connections through ERP.AI and Proto workflows, with every change logged.
Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.
Browse all 21 tablesStart with one team and one process, then add the rest once the basics are running.
Choose a yard and a representative dispatch shift. Yard Supervisor defines the visit review, Dispatcher owns load coordination and Finance Reviewer agrees how detention evidence supports charge decisions.
Reconcile trailer unit numbers, plates and operating organizations. Match drivers, trucks and counterparties before linking open loads, their stops and existing assignments. Preserve the visit reference used by the yard team.
Admin sets up the agreed team access. Check the visit approval inbox, current-user load work and stop schedule with the people who will use them. Configure and test the approval and closure actions with the agreed timestamp and grace-period rules. Create each pilot visit after departure with both actual timestamps; keep arrival paperwork for comparison.
Test a reversed visit interval, a repeated closure request and a driver already committed to another load. Include a delivery signature linked to the wrong stop and cancellation of a load with both completed and unfinished work.
Yard Supervisor checks completed visits against receipts. Dispatcher reviews open assignments and stops. Evidence Reviewer resolves disputed delivery evidence, and Finance Reviewer reconciles charge totals by currency. Release the agreed scope after these owners accept the pilot results.
$0per user
The base account and everyday work in the ERP.AI app are free, for every user.
| Usage | Per $1 |
|---|---|
| Record reads (list, filter, get) | 20,000 |
| Search or aggregate queries | 4,000 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| Workflow runs | 2,000 |
| AI agent runs | 2,000 |
| Scheduled jobs or webhooks | 20,000 |
| File uploads (MB) | 2,000 |
| CSV or PDF exports | 100 |
Click Get started, then use Proto to configure Trailer Tracking System for your business. Pilot a yard and its dispatch shift with representative trailer visits, open loads and receiving evidence. Agree the grace period and visit approver before rehearsing closure.
The visit links to the registered trailer asset and its load. After departure, Yard Operator saves the visit with both actual timestamps, the yard and the observed trailer location. Unit numbers, plates and operating organizations help staff identify equipment before recording arrival or departure.
Yard Supervisor reviews the submitted visit, checks the recorded times and grace period, and approves or rejects the case. Configure that responsibility and its decision action during setup, then rehearse the handoff from Yard Operator.
Configure and test the closure action during setup. Its calculation takes whole elapsed minutes between arrival and departure, subtracts the visit's grace period and floors the result at zero. Keep explicit time zone offsets with the timestamps. Check the resulting duration against the closure receipt before using it in a charge discussion.
Finance Reviewer compares the completed visit with the commercial agreement before approving a load charge. Keep the amount and currency with the charge. Review any conflicting visit evidence before relying on the duration.
Assignment uses active, available drivers and active, available trucks. It excludes resources already used by Assigned or Active assignments and skips a load that already has one of those commitments. The trailer asset remains linked through its yard visit.
The confirmation needs the delivered time, receiver and signature reference. Its load must be Delivered, and its linked stop must be a Completed Delivery stop belonging to that same load. The load also needs its operating organization. Blocked checks become disputed cases for follow-up.
Cancellation cancels related Active assignments and stops that are neither Completed nor already Cancelled. A review decision records the load revision. Dispatcher should inspect the remaining commitments and completed work before closing the operating discussion.
Set up those connections with agreed equipment and load mappings, source identifiers and retry behavior. Keep the reporting source with each milestone and test conflicting or repeated messages before scheduling the feed. See integrations for the ownership decisions.
Fleet Coordinator records inspection findings, assigns defect follow-up and maintains the service plan. Review the equipment's operating status with Dispatcher before further assignment decisions. Keep the original finding available through repair and the return-to-work handoff.
Start free, then use Proto to change fields, steps and approvals before your team goes live.