Glossary

An immutable record of actions with timestamp, actor, and outcome.

Document issued by a shipper listing goods, origin/destination, and terms. Used to match delivery and invoice.

A manual status phone call or message used to ask "where's the truck?"

Post-interaction rating from drivers or partners.

Share of notifications successfully delivered (carrier accepted, portal ID captured, or 2xx API response).

An operator-owned software stack that teams configure and staff to plan, execute, and bill loads. High ownership burden; high visibility.

Loads with a complete, matched document set (BOL, POD, accessorials) divided by delivered loads.

Average number of days to collect cash after invoicing.

Pre-/post-trip inspection record documenting vehicle condition and defects.

Elapsed time a truck spends at a stop, gate-in to gate-out.

The predicted arrival time for a stop based on current position, route, traffic, dwell history, and constraints.

Share of arrivals that occur within a defined window of the last published ETA.

Time from a new signal (GPS ping, driver event, facility update) to an observable ETA/status change in the system.

Share of tickets closed without a second interaction with the driver/customer.

A vendor-neutral operating model that runs day-to-day fleet operations end-to-end with event-driven automation and a 24/7 driver desk. Presents a single view of loads, trucks, documents, and cash. Not a DIY TMS and not traditional outsourcing.

The versioned specification defining modules, conformance language (MUST/SHOULD/MAY), KPIs, and evidence rules for FSO implementations.

A virtual boundary around a facility or area used to trigger arrival/departure events.

Regulatory limits on driver on-duty and driving time. Used for planning and violation alerts.

A property of operations that prevents duplicates when retried.

Middle value in a sorted dataset. Preferred for skewed time metrics.

A pre-arrival notification sent to a designated contact when a truck is approaching a stop.

Value at or below which 90% of observations fall. Used for SLA commitments.

Time since last valid location update while the vehicle is moving.

Signed evidence that freight was delivered. Often includes BOL stamp/signature and time.

Elapsed time from POD stored/matched to invoice sent.

Share of active drivers who receive support in their preferred language.

Share of delivered loads invoiced by 23:59 local on the delivery date.

A formal target for a measurable outcome (e.g., "answer time P90 ≤ 60 s"). SLAs use distributions (P90) or medians, not means.

Third-party runs core operations. Lower internal burden; visibility varies by provider and contract.