When the dispute arrives, the answer is already in the timeline.
Every action in LogAI — whether a dispatcher makes a decision or an agent writes a position event — lands on the same load event timeline with an actor, a timestamp, and a reason. Freight disputes are won or lost on documentation. LogAI generates the documentation automatically.
How the audit trail works
One event spine. Every actor. Complete history.
One timeline. Every action.
Human actions and agent actions write to the same load event spine. A dispatcher updating an appointment and the Check Call Agent writing a position event land in the same timeline, in order, with timestamps. There is no separate log for agent activity — everything is visible in the load detail screen.
Actor, timestamp, and reason on every event
Every load event carries: who acted (dispatcher name or agent name), when (UTC timestamp to the millisecond), and what changed (status transition, document classification, rate update). When a dispute arrives weeks later, the answer is already recorded.
Agents are reviewable
Any event an agent wrote can be inspected: what data the agent read, what decision it made, and what it wrote. If an agent made an incorrect classification, a dispatcher can see exactly what the agent was given and override the result. The agent's reasoning is not a black box.
Agents are reversible in v1
In LogAI v1, no agent sends a rate confirmation, tenders a load, or pays a carrier without human approval. Actions that cannot be easily undone require a human in the loop before they happen — not after. This is a deliberate design choice, not a technical limitation.
Dispute resolution from the timeline
A shipper claims they were never notified of a delay. A carrier says they were never given detention authority. The load event timeline has the answer: the timestamp of the notification, the agent that sent it, and the message content. You do not need to search email threads.
Carrier invoice audit trail
Every rate line in an AP bill is traceable to the rate confirmation that produced it and the load events that verified each accessorial. The audit trail does not summarize — it shows the exact clause, the exact event, and the exact calculation.
Common disputes and where the answer lives
These are real freight disputes. The load event timeline resolves them without email archaeology or carrier finger-pointing.
Shipper claims they weren't notified of a late delivery
Timeline answer: Load event timeline shows: notification timestamp, recipient, channel (email or Phony), and the agent that sent it.
Carrier claims they were never given detention authority
Timeline answer: Rate confirmation event shows the detention clause as agreed. Detention clock event shows when it started and why.
Customer disputes an accessorial charge
Timeline answer: Audit event shows the accessorial type, the load event that triggered it, the agreed rate from the rate confirmation, and the calculation.
Carrier invoice shows a higher rate than agreed
Timeline answer: Audit report event shows the rate confirmation rate, the invoiced rate, the delta, and the dispatcher who approved or disputed the discrepancy.
Missing POD — shipper claims delivery never occurred
Timeline answer: Document events show the signed POD received, classified, and reconciled — with piece count, delivery timestamp, and consignee signature verified.
No agent acts on a load without leaving a trace — and no agent acts on a consequential decision without a human
In LogAI v1, the following actions always require a human to approve before they happen: sending a rate confirmation, tendering a load to a carrier, creating an AP bill, and resolving or closing an exception. Agents can open exceptions, classify documents, write position events, and place check calls — but they do not make commitments on behalf of the brokerage.
This is not about distrust of AI. It is about building a track record. As agents accumulate a history on a specific brokerage's freight patterns, auto-approval thresholds for low-risk actions will be introduced — with the full audit trail preserved throughout.