Logistics Tracking System keeps freight loads, ordered stops, transport partners and delivery timing in one operating record. A dispatcher creates a load with a promised delivery time, an owner and a partner.
Loads in one list
Dispatcher approves the checked route for the current load revision.
Every feature works on the same records. Pick one to see the screen your team works in.
Plan each load against its delivery promise, assign an owner and carry pickup through transit.
Approval conditions
| Record number | Subject | Revision | Owner | Counterparty | Status | |
|---|---|---|---|---|---|---|
| LDS-79411 | Retail fixtures, Reno to Phoenix | 370 | Dae Kim | Cedar Harbor Carriers | Draft | |
| LDS-40449 | Paper rolls, Tacoma to Boise | 560 | Farah Nasser | Hearthstone Freight Co. | Draft | |
| LDS-52199 | Food cartons, Fresno to Denver | 50 | Mei Tan | Mesa Bend Hauling | Draft | |
| LDS-10737 | Pump housings, Tulsa to Dallas | 610 | Dae Kim | Rivercrest Transit | Draft | |
| LDS-95887 | Tile pallets, El Paso to Austin | 460 | Nadia Flores | Rivercrest Transit | Draft |
Put stops in order, compare each arrival with its window and retain recipient proof.
Load stops
| Parent | Stop sequence | Address | Window start | Window end | Actual arrival at | |
|---|---|---|---|---|---|---|
| Furniture frames, Eugene to Portland | 10 | Reno distribution center | 23 Oct | 28 Oct | 06 Nov | |
| Medical packaging, Raleigh to Atlanta | 90 | Phoenix retail receiving dock | 22 Oct | 29 Oct | 05 Nov | |
| Paper rolls, Tacoma to Boise | 80 | Tacoma paper mill gate | 19 Oct | 22 Oct | 30 Oct | |
| Medical packaging, Raleigh to Atlanta | 80 | Boise cross-dock | 21 Oct | 27 Oct | 29 Oct | |
| Food cartons, Fresno to Denver | 20 | Fresno cold storage | 23 Oct | 31 Oct | 06 Nov |
Match a load interval with an eligible driver and a vehicle ready for the job.
Load assignments
| Load | Driver | Vehicle | Starts at | Ends at | Status | |
|---|---|---|---|---|---|---|
| Furniture frames, Eugene to Portland | Priya Bhat | Box truck 12, city route | 21 Oct | 28 Oct | Held | |
| Paper rolls, Tacoma to Boise | Jamal Ortega | Tractor 55, step deck | 23 Oct | 28 Oct | Confirmed | |
| Paper rolls, Tacoma to Boise | Priya Bhat | Tractor 31, dry van | 13 Oct | 18 Oct | Dispatched | |
| Pump housings, Tulsa to Dallas | Arun Mehta | Tractor 9, refrigerated | 13 Oct | 15 Oct | Completed | |
| Pump housings, Tulsa to Dallas | Priya Bhat | Tractor 25, flatbed | 18 Oct | 25 Oct | Held |
Keep carrier events tied to the right load, event time and review decision.
Approval conditions
| Parent | Tracking number | Provider event ID | Occurred at | Revision | Status | |
|---|---|---|---|---|---|---|
| Paper rolls, Tacoma to Boise | CM-94673 | MIL-20261015-4102 | 21 Oct | 740 | Submitted | |
| Bottled juice, Modesto to Las Vegas | CM-35251 | MIL-20261015-4138 | 15 Oct | 550 | Submitted | |
| Furniture frames, Eugene to Portland | CM-89760 | MIL-20261015-4174 | 19 Oct | 520 | Submitted | |
| Tile pallets, El Paso to Austin | CM-24244 | MIL-20261015-4211 | 14 Oct | 420 | Submitted | |
| Furniture frames, Eugene to Portland | CM-18454 | MIL-20261015-4260 | 27 Oct | 610 | Submitted |
Tie route decisions, attachments and operation receipts to the load revision they support.
Review decisions
| Parent | Reviewer | Source revision | Decision | Reason | Decided at | |
|---|---|---|---|---|---|---|
| Medical packaging, Raleigh to Atlanta | Mei Tan | 670 | Approve | POD signature matches consignee | 16 Oct | |
| Medical packaging, Raleigh to Atlanta | Ethan Okafor | 530 | Return | Arrival scan timestamp confirmed | 17 Oct | |
| Retail fixtures, Reno to Phoenix | Mei Tan | 830 | Approve | Seal number does not match dispatch | 15 Oct | |
| Paper rolls, Tacoma to Boise | Lucia Ferraro | 130 | Return | Delivery image needs clearer dock view | 19 Oct | |
| Bottled juice, Modesto to Las Vegas | Lucia Ferraro | 170 | Approve | Carrier ETA accepted after traffic delay | 14 Oct |
Review active loads, pending decisions, delivery timing and operational exceptions together.
Loads
| Record number | Subject | Promised delivery at | Actual delivery at | Owner | Counterparty | |
|---|---|---|---|---|---|---|
| LDS-11319 | Retail fixtures, Reno to Phoenix | 20 Oct | 24 Oct | Dae Kim | Blue Marsh Logistics | |
| LDS-38188 | Paper rolls, Tacoma to Boise | 17 Oct | 21 Oct | Arun Mehta | Willow Peak Transport | |
| LDS-32775 | Food cartons, Fresno to Denver | 14 Oct | 16 Oct | Mei Tan | Oak Hollow Trucking | |
| LDS-40979 | Pump housings, Tulsa to Dallas | 26 Oct | 02 Nov | Mei Tan | Mesa Bend Hauling | |
| LDS-26258 | Tile pallets, El Paso to Austin | 16 Oct | 20 Oct | Arun Mehta | Willow Peak Transport |
Load to verified delivery ships ready to use. One step needs a named approval before the work moves on: Review route (Dispatcher).
Set the owner, partner and original delivery promise.
Check stops, assignment and the current load revision.
Record physical pickup before dispatch advances.
Follow the route and partner events against the promise.
Keep recipient proof and actual delivery time together.
Compare receipts with the records they changed.
Open any load to see its carrier milestones, the roles that work on it, its process stages and its approvals on one page.
Promised delivery at, Owner and Counterparty.
Each line is linked to this load.
Dispatcher, Load Owner and Operations Reviewer, each with their own permissions.
Register load and Sequence stops, with the role that acts.
Review route, with who decides.
Cedar Harbor Carriers · Planned
| Parent | Tracking number | Provider event ID |
|---|---|---|
| Paper rolls, Tacoma to Boise | CM-94673 | MIL-20261015-4102 |
| Bottled juice, Modesto to Las Vegas | CM-35251 | MIL-20261015-4138 |
| Furniture frames, Eugene to Portland | CM-89760 | MIL-20261015-4174 |
Signed in as Dispatcher
| Decision | Approver | |
|---|---|---|
| Review routeCheck stops, assignment and the current load revision. | Dispatcher |
Everyone opens Logistics Tracking System to the work that is theirs. Pick a role to see what it starts with.
Plans load routes and assignments, records pickup and delivery, and submits carrier milestones.
This is the first screen this role sees.
Carrier milestones · Dispatcher
| Parent | Tracking number | Provider event ID | Occurred at | Revision | Status | |
|---|---|---|---|---|---|---|
| Paper rolls, Tacoma to Boise | CM-94673 | MIL-20261015-4102 | 21 Oct | 740 | Submitted | |
| Bottled juice, Modesto to Las Vegas | CM-35251 | MIL-20261015-4138 | 15 Oct | 550 | Submitted | |
| Furniture frames, Eugene to Portland | CM-89760 | MIL-20261015-4174 | 19 Oct | 520 | Submitted | |
| Tile pallets, El Paso to Austin | CM-24244 | MIL-20261015-4211 | 14 Oct | 420 | Submitted | |
| Furniture frames, Eugene to Portland | CM-18454 | MIL-20261015-4260 | 27 Oct | 610 | Submitted |
Owns load scope and requests corrections or cancellation with the supporting reason.
This is the first screen this role sees.
Loads · Load Owner
Makes independent decisions on load revisions and checks receipts that need review.
This is the first screen this role sees.
Carrier milestones · Operations Reviewer
| Parent | Tracking number | Provider event ID | Occurred at | Revision | Status | |
|---|---|---|---|---|---|---|
| Paper rolls, Tacoma to Boise | CM-94673 | MIL-20261015-4102 | 21 Oct | 740 | Submitted | |
| Bottled juice, Modesto to Las Vegas | CM-35251 | MIL-20261015-4138 | 15 Oct | 550 | Submitted | |
| Furniture frames, Eugene to Portland | CM-89760 | MIL-20261015-4174 | 19 Oct | 520 | Submitted | |
| Tile pallets, El Paso to Austin | CM-24244 | MIL-20261015-4211 | 14 Oct | 420 | Submitted | |
| Furniture frames, Eugene to Portland | CM-18454 | MIL-20261015-4260 | 27 Oct | 610 | Submitted |
Maintains driver eligibility, vehicle readiness and defect release records used during assignment.
This is the first screen this role sees.
Load assignments · Fleet Coordinator
Reads load, milestone, timing and exception records for operating reports.
This is the first screen this role sees.
Loads · Operations Analyst
Maintains organizations, user membership and partner records for operating access.
Answer delivery timing, fleet commitment, carrier delay and review questions from linked records.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Draft | 24 | ||
| Planned | 6 | 25% | |
| Dispatched | 2 | 33% | |
| In transit | 1 | 50% |
Sample counts per stage
Which delivered loads arrived after their original promised delivery time?
Which owners carry Draft, Planned, in transit or Exception work?
Which Transport Partners appear on late loads, and which load records explain the result?
What delay minutes did partners report, and how do those events compare with final delivery?
Which driver and vehicle intervals are already committed?
At which destinations did actual arrival fall outside the planned window?
Which operations are Failed or needs review, and what effect was expected?
Which load revisions were approved, rejected or returned, by whom and why?
See how Logistics Tracking System fits your kind of team.
Keep partner loads, milestone events and delivery evidence tied to the same movement.
Connect freight commitments to driver eligibility, vehicle readiness and load intervals.
Track ordered delivery windows and recipient proof across a route with several destinations.
Each stage of load 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
Ask Proto to prepare load work, explain exceptions and help the team inspect 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 14 tablesStart with one team and one process, then add the rest once the basics are running.
Choose the operating Organizations, load ownership, partner directory and the people responsible for dispatch, fleet facts and independent review.
Bring in TeamMembers, TransportPartners, Drivers and Vehicles with current eligibility and readiness details.
Agree stop sequencing, delivery windows, promised delivery time, assignment intervals and recipient proof handling.
Follow a Draft load through route approval, pickup, transit, carrier event review and delivery. Test a rejected revision and a failed receipt.
Move a bounded set of loads first, inspect Operations Overview daily and reconcile each exception with the linked records.
$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 Logistics Tracking System for your business. Start with one organization, a partner, a load with ordered stops and a named dispatcher and reviewer.
A load carries its number, subject, status, promised and actual delivery times, owner, organization, partner, freight amount and revision. Stops, assignments, milestones and evidence link to it.
Yes. Each load stop has its own sequence, address, planned window, actual arrival and departure, and proof reference.
A load assignment links the load to a Driver and Vehicle for start and end times. Review eligibility, readiness, class, capacity and other commitments before confirming it.
Dispatcher checks the stops and feasible assignment, approves the route and plans the load. An Operations Reviewer can record a separate approve, reject or return decision against the load revision.
It can retain a tracking number, provider event identifier, reported occurrence time, delay minutes, review status and decision time against its parent load.
Record the recipient proof reference on the relevant stop and actual delivery time on the load. Compare that time with the original promised delivery time.
Load Owner requests a reasoned correction. The team checks the current revision, stops and operation receipts, then checks successor scope before planning it while retaining prior evidence.
Open the operation receipt, compare its expected revision and linked effects, and record a discrepancy when they do not match. A repeated action should be checked against its stable operation key.
Delivery evidence supports the operating handoff. Carrier invoicing and settlement follow the financial process your team connects to it.
Start free, then use Proto to change fields, steps and approvals before your team goes live.