Load-linked detention tracking

Detention Tracking Without Another Spreadsheet

Track appointment, arrival, release, threshold, evidence, and escalation events in one load-linked workflow instead of a detached sheet.

By WhichAI. Published 2026-07-12. Updated 2026-07-12.

Methodology: Editorial synthesis of workflow design patterns and implementation constraints. Public control references provide context, not proof of a deployment or legal advice. Where a versioned evidence pack appears, its evidence class, method, and limitations govern what the artifact can support. Read the full method. Report a correction.

Built for

Dispatch, 3PL operations, carrier relations, accessorial, and freight billing teams

The decision

Choose authoritative event sources and review rules before replacing the detention spreadsheet with an operational case workflow.

Answer first

A detention tracker should link each threshold and charge candidate to the load, appointment, actual event evidence, governing terms, and human exception owner.

Self-serve workflow planner

Start with this article's task

For Dispatch, 3PL operations, carrier relations, accessorial, and freight billing teams. Start a brief for this task: Choose authoritative event sources and review rules before replacing the detention spreadsheet with an operational case workflow.

Start this brief

The capacity leak

What the team is doing before anyone calls it a systems problem

Headcount pressure rarely starts with one giant task. It starts when ordinary work is split across inboxes, tabs, handoffs, and undocumented judgment calls. These are the signals to map first.

SIGNAL 01

Arrival and release times are copied from driver messages, tracking feeds, facility notes, and TMS events into a sheet.

SIGNAL 02

Appointment changes and geofence events can conflict without a visible source hierarchy.

SIGNAL 03

Operations notices threshold crossings late and then requests documents or facility confirmation.

SIGNAL 04

The spreadsheet is separated from accessorial review, billing approval, and carrier communication state.

The implementation

The system should prepare the decision, not pretend the decision disappeared

A complete implementation connects the intake, context, transformation, review, and record. The output of one stage becomes the controlled input to the next. A human owns the exceptions and the final consequence.

Stage	Current drag	System responsibility	Human responsibility	Evidence kept
1. Appointment baseline	Scheduled times are copied without preserving revisions.	Record the authoritative appointment, timezone, revision history, facility, and source.	Resolve conflicting schedules and appointment exceptions.	Appointment source, timezone, revision, received time, and reviewer.
2. Event timeline	Arrival and release evidence is reconciled after the load moves.	Collect permitted TMS, tracking, facility, document, and driver events into a source-labeled timeline.	Resolve conflicts and reject unreliable events.	Raw event, source, timestamp, timezone, confidence, and correction.
3. Threshold monitor	Staff calculate free time and elapsed time in spreadsheets.	Apply the approved term and clock rule to verified events, then open a candidate case at the threshold.	Approve governing terms and unusual clock pauses or exclusions.	Rule version, input events, calculation, threshold time, and exception.
4. Evidence action	Supporting documents are requested after the threshold or delivery.	Prompt the responsible party for the evidence required by the current charge and customer rules.	Handle facility disputes, missing events, and alternate evidence.	Evidence request, original response, documents, owner, and status.
5. Operational handoff	Detention notes do not reliably reach customer updates or billing review.	Route an approved operational status and candidate charge packet to the right queues.	Approve communications, responsibility, and any billing treatment.	Status message, charge packet, approver, recipients, and resolution.

What the human keeps

The goal is not zero humans. It is zero avoidable preparation around the judgment only a responsible owner should make.

Own appointment source hierarchy, timezone handling, free-time rules, and accepted event evidence.
Resolve conflicting times, facility disputes, exclusions, and responsibility questions.
Approve customer communication and any accessorial charge or exception.

Controls before volume

A workflow is not ready because the happy path worked once. It is ready when access, review, fallback, and evidence are explicit.

Store raw source events and normalized timestamps with explicit timezone and correction history.
Version detention rules and link each calculation to the governing commercial term.
Do not convert a predicted arrival, geofence estimate, or unsourced note into an actual event.
Require review for event conflicts, exclusions, responsibility, and charge preparation.

Control references

National Institute of Standards and Technology: AI Risk Management Framework Federal Trade Commission: Data Security Guidance

The scorecard

Measure capacity, not activity

A system can produce more messages and still make the operation worse. Measure movement through the workflow, the quality of review, and the load that still reaches a person.

Event completeness

Share of eligible loads with reviewed appointment, arrival, release, and source records.

Threshold alert timing

Time between the calculated detention threshold and owner acknowledgment.

Timeline correction rate

Share of cases where staff materially change an event, timezone, or governing rule.

Evidence-ready cases

Share of candidate detention cases with required evidence before billing review.

What a fake implementation looks like here

These patterns create an AI demo while leaving the labor, risk, and accountability in the same place.

Treating projected tracking events as actual arrival or release times.
Ignoring timezone, appointment revision, or facility-specific clock rules.
Calculating detention from an unverified commercial term.
Creating a new tracker that does not hand evidence and state into billing and communication workflows.

Two ways to act

Use the path that matches the decision

Task-specific workflow brief

Plan this recurring task.

Start with this task draft, then complete the three-question brief:

Build a detention tracking workflow with appointment revisions, source-labeled arrival and release events, timezone controls, threshold rules, evidence requests, and human charge approval.

Choose a paid plan after reviewing your brief. WhichAI creates a plan and does not set up tools or accounts.

Start the brief

WhichAI Solutions

The workflow is becoming a company problem.

Use WhichAI Solutions when detention tracking crosses telematics, TMS, facilities, carriers, customers, and billing rules with material dispute or leakage risk.

Bring one bottleneck. We map the work under it, separate consequential judgment from mechanical drag, and decide whether the next move is a hire, a tool, or a rebuild.

See company solutions

Questions

What operators ask before they build

Can geofence data be the source of truth?

It can be one source. Define when it is accepted, preserve the raw event, compare conflicts, and route uncertain or disputed timelines to a person.

What replaces the spreadsheet?

Use a load-linked case with appointment history, source-labeled events, versioned rules, threshold calculations, evidence, owners, and downstream status.

Should the workflow automatically bill detention?

No. It should prepare the event and evidence packet. Responsibility, exceptions, commercial interpretation, and billing approval remain human decisions.

Primary references

Controls should come from the specific operating environment

These are broad public control references, not article-specific evidence, vendor endorsements, or legal advice. Validate the current rules, contracts, system configuration, and organization-specific risk before deployment.

National Institute of Standards and Technology

AI Risk Management Framework

A voluntary framework for mapping, measuring, managing, and governing AI risk.

Accessed 2026-07-14

Federal Trade Commission

Data Security Guidance

Business guidance on reasonable data security practices and reducing unnecessary risk.