Questions, answered

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.