The load page

The load page is where you work one load: read its current issue, see where the truck is and what the driver said, and send updates back to your TMS. Everything on it is grouped by job, so this article walks the page top to bottom and says what each part is for. Admins, Tracking Users, and Internal Users can open it; Customer Users see a simpler customer load page instead.

Header

The load number is the title; select it to copy it. Next to it, View Public Load opens the page a customer would see, and Share Public Load copies that link so you can paste it into a tracking request. The line under the title shows the mode, the TMS status, the assignee, and the load's service level, which links to the tier that decides its exception thresholds.

Small icons beside the title are the load's flags: high value, hot, or exception load; a tracking link; a spider-web icon when the carrier has a tracking portal on file, which opens the carrier page; and a phone or message icon when the driver has replied, which opens that conversation.

Current issue and highlights

One badge states the load's condition: Fully Compliant, an issue marked Managed, or an Unmanaged issue. When several exceptions are open, smaller badges list the rest. The Exception reference defines each one.

The highlights row answers the questions a customer asks first: Latest Update, Latest Location with miles to the next stop, Tracking Status, Next Stop, Next Stop ETA with its source, and Detention Accrual Minutes, a live timer once the truck has arrived.

Buttons

The buttons at the top are grouped into columns. Your admin can rename, add, and reorder them, so your columns may differ; these are the defaults.

• Update TMS: Load Update records what you learned and syncs it; Load Status moves the load to its next stage; Tracking Info edits driver, truck, and trailer. Each has its own guide: Load updates, Update a load's status, Driver info updates.

• Docs: Upload POD, and Download POD once one is on file. See POD updates.

• External Contact: Driver SMS Conversation and Driver AI Voice Call, shown when the load has a driver phone, and Carrier Email Conversation. See Send an SMS to the driver and Place an AI voice call.

• Manage Load: Manage Issue to park a handled load until a time you set, Tracking URL to attach a tracking link, and Data Approval for values the AI extracted from this load's conversations.

• Categorize Load: Exception flags the load as hot, high value, or an exception; Ignore removes it from the boards with a reason. See Mark a load as an exception.

Turvo teams see Turvo Status Update in place of the separate update and status buttons. Some companies add a View in TMS deep link, dispatch buttons, or MacroPoint tracking controls.

Load details

The left panel has five tabs. Carrier shows the driver and equipment, including whether the driver's number has opted in or out of SMS, the carrier's contacts, tracking portal login, and instructions, and a count of the carrier's total and non-compliant loads. Ref # lists every reference number on the load. Customer shows the customer, industry, and instructions, with a button to see their active loads. Team lists the reps and account managers on the load with copyable emails. Docs shows POD status, Manage Issue details, sync timestamps, and any ignore reason.

Map and stops

The Tracking Map numbers the stops and shows the truck at its latest location. The Stops table lists each stop with its type, reference, status, address, appointment window in local time, and actual arrival and departure. The pencil on a row opens the stop update form; Stop updates explains recording arrivals and departures in order.

History tabs

The tabs at the bottom are the load's memory, and knowing which one to open saves most "who changed this" questions.

• All Updates (open by default) and Priority Updates: the location and event timeline, with city, miles to next stop, ETA, when it happened, when it was entered, and the source.

• Update History: every update your team or automation sent to the TMS, with the user, the TMS response code and message, and the status. Start here when an update did not land.

• Issue History: each exception, when it was identified, who owned it, and how it ended.

• Assignment History: who owned the load and when it moved.

• Action History: what people did on the load, by type and time.

• Outreach Automation History: every automated SMS, email, and voice call, with direction, contact, message, and approval outcome.

Who can open it, and when

The page is company-scoped; a load from another company will not open. Loads older than the tracking window are read from the boards' history instead, and very old loads show a notice that they cannot be viewed. A load created in the last few minutes shows a banner asking you to wait for the TMS sync to finish before updating it.