Shipper tracking mandates: what location data carriers must share

Where do tracking requirements come from?#

Tracking requirements for carriers come from the documents that govern each load, not from a single federal rule. The ELD mandate requires electronic hours-of-service records, but it does not require carriers to stream location to shippers or brokers. That obligation, where it exists, is a commercial term.

Because the obligation is contractual, its details vary widely. One shipper accepts check calls at pickup and delivery, while another expects live updates through a named platform and applies chargebacks or scorecard penalties for gaps. These are the usual sources to read.

Read these documents as a set. A rate confirmation can incorporate a broker policy that requires a named tracking app, and the app's onboarding screen can add data terms that none of the carrier's managers ever saw. The obligation a carrier actually carries is the sum of all of them.

• 1Shipper routing guides and carrier compliance manuals.
• 2Broker-carrier agreements, including any broker policies they incorporate by reference.
• 3Rate confirmations and load tenders for individual shipments.
• 4Customer scorecards that weigh on-time performance and tracking compliance.
• 5Onboarding terms of the visibility platform the shipper or broker uses.

What location data do carriers typically share?#

Carriers typically share location through one of four channels, and each puts the history in different hands. Knowing the channel tells you who will hold a copy of your movements after the load is delivered.

Integrations through the fleet's ELD or telematics provider are usually the most precise and the most hands-off. They are also the easiest to leave running too long, because nothing on the driver's side reminds anyone that the feed is live.

Many carriers run two channels at once, for example an integration for one broker and check calls for a shipper that does not use a platform. Write down which channel each customer uses, because the answer decides where your location history ends up and whose terms govern it.

How long should location sharing last?#

Location sharing should last for the load and no longer. A sound clause names a start trigger, such as dispatch to the pickup appointment, and an end trigger, such as proof of delivery, and it obliges the recipient to stop collecting once the end trigger fires.

Problems usually come from open-ended language. A broker agreement that allows tracking whenever the carrier is hauling for the broker can be read to cover deadhead miles, other customers' loads or off-duty time. Ask for wording tied to the specific load, and confirm that the platform actually shuts off the feed at delivery.

Owner-operators and company drivers using personal phones deserve extra care. An app that keeps reporting after a shift ends is collecting personal location, not freight status.

What carriers keep the right to use#

Carriers keep the right to use their own operating records, but the documents around tracking can narrow that right. The carrier's dispatch history, ELD records and exception notes are its own, while customer names, lanes and rates often fall under confidentiality clauses in broker-carrier agreements.

The platform terms deserve the closest reading. Visibility platform terms may grant the provider rights to use collected data for benchmarking or product development, and a carrier that clicked through onboarding may have agreed without negotiating. Those rights do not usually transfer ownership of your dispatch records, but your movements may live on in someone else's dataset.

Before signing any of these documents, the person who negotiates customer terms should know what the dispatch and safety teams already share. Many disputes start when sales accepts a tracking requirement that operations cannot meet without a phone app the drivers dislike.

Driver privacy and the personal phone problem#

Driver privacy is the issue most likely to surface after the fact. When tracking runs through a driver's personal phone, the carrier is effectively asking an employee or contractor to share personal device location with a third party.

Several kinds of rules may apply. State privacy laws can cover employee and contractor data, some states require written notice before employers monitor employees electronically, and owner-operator leases often set out what the carrier may collect. Counsel should review how your notices describe tracking for customers, not only tracking for safety.

Simple controls help: prefer integrations through company devices, limit app permissions to the load window, and tell drivers in writing which customers receive their location and for how long.

Illustrative: a reefer carrier tightens its tracking terms#

Illustrative: a fictional refrigerated carrier hauls for several food shippers and a handful of large brokers. Each broker requires a different tracking app, and drivers complain that two of the apps keep reporting after delivery.

The COO lists every tracking obligation by customer, the channel used and the end trigger in each contract. The carrier moves broker tracking to integrations through its telematics provider wherever customers accept that, removes phone apps, and adds a load-specific start and stop clause to its standard rate confirmation addendum.

The result is one register of who receives location, for which loads and under which platform terms. The carrier also confirms that its own dispatch and temperature exception history never left its systems, which keeps that record set clean for later use.

How SourceX treats tracking and location records#

SourceX treats raw location streams as high privacy burden under the SourceX Enterprise Data Value Framework, which reduces their net value. Dispatch decisions, exception notes and resolution outcomes usually carry more AI utility, with location coarsened or removed during Preparation.

In the SourceX five-step transaction, the Rights step checks broker and platform terms before anything is scoped. The SourceX Evidence Packet then records which records came from the carrier's own systems and which customer restrictions were applied.