Logistics and distribution
Dedicated contract carriage agreements: who owns the operating data?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
In a dedicated contract carriage agreement, the carrier usually owns the operating records its own systems create, such as ELD logs, telematics, maintenance and dispatch, while the shipper's orders, customers and delivery requirements stay shipper confidential information. Route histories mix both. Give the shipper visibility through access rights rather than ownership, and write termination returns down.
Key takeaways
- Dedicated carriers generally hold the records their own ELD, telematics, maintenance and dispatch systems create.
- Shipper orders, customer locations and delivery requirements are usually shipper confidential information, even inside carrier systems.
- Telematics access for the shipper works best as scoped visibility, with limits on video, driver data and use after termination.
- Route plans and stop sequences built by the carrier are mixed records, so the agreement should assign them expressly.
- Driver qualification, hours-of-service and camera records stay with the carrier as employer and motor carrier.
Who owns operating data in a dedicated fleet?#
Operating data in a dedicated fleet generally belongs to the carrier when its own systems create it, and to the shipper when it describes the shipper's business. The carrier runs the trucks, employs the drivers and holds the operating authority, so ELD logs, telematics, maintenance histories, dispatch records and driver files sit in carrier systems and carry carrier obligations.
The shipper's information still runs through those systems: order details, store or customer addresses, delivery windows, dock rules and product data. Dedicated agreements usually treat that information as shipper confidential information. The hard cases are records that combine both, such as a route history that shows the carrier's driver performance against the shipper's customer list.
Clause checklist for dedicated agreements#
A dedicated contract carriage agreement should answer data questions in writing, because the relationship often runs across several renewals and records pile up on both sides. Check that the agreement covers each point below, and flag any that the current draft leaves silent.
- Shipper data definition: which order, customer, location and product information counts as shipper confidential information.
- Carrier operating records: an express statement that ELD, telematics, maintenance, dispatch and personnel records are the carrier's.
- Telematics and camera access: what the shipper may see, through which portal, for which loads, and whether video is included.
- KPI reporting: which metrics the carrier must report, at what level of detail, and whether the shipper may share them.
- Route plans and network design: who owns plans, stop sequences and schedules developed during the program.
- AI use: whether either party may use the other's data to train models or build tools.
- Subcontracting: how data obligations flow to any subcontracted carrier or owner-operator.
- Termination: what is returned, destroyed or retained, and what transition help is owed to the next provider.
Telematics access is visibility, not ownership#
Telematics access for a dedicated shipper should be framed as visibility into the carrier's data, not a transfer of it. Shippers commonly want live location, ETAs, temperature readings and delivery confirmation; some also ask for driver scorecards or dash cam clips after incidents.
Scope the access by data type and purpose. Location and ETA for loads in progress is usually reasonable. Raw video, driver-level safety scores and hours-of-service details raise driver privacy and employment issues, and state privacy laws may apply depending on where drivers live and work. A narrow access right with an end date protects both parties.
Check the telematics vendor's terms as well. The carrier's subscription may limit sharing account data with third parties, and a shipper portal may need the vendor's support or a separate license.
Route know-how: the record both sides built#
Route plans and stop sequences are mixed records because the carrier built them from the shipper's delivery requirements. The carrier contributes driver scheduling, equipment planning and practical knowledge of each lane; the shipper contributes customer locations, volumes and delivery windows.
The table shows where each side usually starts and where negotiations tend to land. None of these outcomes is automatic, so write the chosen position into the agreement.
| Record | Carrier position | Shipper position | Common compromise |
|---|---|---|---|
| Route plans and stop sequences | Carrier work product and know-how | Built from shipper data and paid for | Shipper gets a copy; carrier keeps general methods |
| Driver schedules and assignments | Carrier employment records | Needed for service continuity | Carrier keeps; shipper receives service levels |
| Delivery exceptions and refusals | Carrier operating records | Describe the shipper's customers | Shared; customer details remain shipper data |
| Fuel, mileage and equipment use | Carrier cost records | Relevant to pricing and surcharges | Carrier keeps; agreed summaries reported |
| Customer site notes and dock rules | Driver safety knowledge | Shipper customer information | Shipper data, usable for the service only |
Driver records stay with the carrier#
Driver records stay with the carrier because the carrier is the employer and the motor carrier responsible for compliance. Driver qualification files, hours-of-service logs, drug and alcohol testing records and safety camera footage carry regulatory and privacy duties that a shipper agreement cannot transfer.
Give the shipper the outcomes it needs, such as on-time performance and safety event counts, rather than raw driver files. If the shipper insists on more, limit it to named purposes, require confidentiality, and confirm that driver notices and consents support the sharing before anything is sent.
Owner-operators leased onto the carrier add one more layer. Those owner-operators may keep their own settlement and business records outside the carrier's control, so the dedicated agreement should not promise the shipper anything the carrier's lease agreements do not support.
Termination: what comes back and what stays#
At termination, the shipper's confidential information should come back or be destroyed, and the carrier's operating records should stay where regulators expect to find them. The agreement should say which is which, because both sides tend to assume they keep everything.
Carriers usually keep ELD logs, maintenance files and driver records for their legal retention periods, along with records needed for claims and billing disputes. Shipper order files, customer lists and route plans that identify the shipper's customers are returned or destroyed. A transition clause can require the carrier to hand agreed route plans and service data to the next provider in a stated format, which shortens the handover and limits disputes.
Illustrative: a dedicated fleet for a building products distributor#
Illustrative: a fictional dedicated carrier runs tractors and flatbeds for a building products distributor, delivering to job sites from several yards. The carrier's TMS holds every order, stop and delivery exception, its telematics account records location and engine data, and its shop software tracks every unit.
At renewal, the distributor asks for full telematics access, including video, and ownership of all route data. The carrier's CEO and counsel propose live location and ETA access, incident clips on written request, and a copy of route plans at termination, while confirming that ELD, maintenance, dispatch and driver records remain the carrier's. The distributor agrees, and the carrier records the split in its data inventory so later questions about reuse already have a written answer.
How SourceX approaches dedicated fleet records#
SourceX starts from the agreement. In the Rights step of the SourceX five-step transaction, shipper confidential information is excluded unless the shipper consents in writing, driver personnel records are excluded, and the carrier's own operating records, such as maintenance histories and de-identified exception handling, are reviewed against the agreement and the telematics vendor's terms. Nothing is shared during the initial assessment, and the carrier approves each step before any package is licensed.
Packages that clear review are documented in a SourceX Evidence Packet: provenance, licensing rights, permitted use, privacy record and release authorization. A clear data clause in the dedicated agreement makes that review faster, because the split between carrier records and shipper information is already written down.
Frequently asked questions
Can the shipper require us to use its telematics platform?
It can ask, and some agreements require it, especially when the shipper owns the equipment. If the shipper's platform holds the data, the shipper's terms decide access, so negotiate the carrier's right to export its own operating and compliance records, such as ELD logs and maintenance data, at any time.
Does shipper-branded equipment change who owns the data?
Branding alone does not. Ownership of the equipment and of the telematics account matter more. If the shipper owns or leases the trucks and installs devices, it may hold that data, while the carrier still needs its compliance records. Spell out access in both directions in the agreement.
Can the carrier use dedicated program data to win other customers?
General know-how, such as how to staff and run a multi-stop flatbed operation, is usually the carrier's. Using the shipper's volumes, customer names, rates or route maps to pitch competitors would likely breach confidentiality. Keep sales material to aggregated experience that identifies no shipper or customer.
What if a subcontractor runs part of the dedicated fleet?
The subcontractor's records sit in its own systems, so the prime carrier needs a flow-down clause requiring confidentiality, reporting and data return on the shipper's terms. Without one, the prime carrier may promise the shipper protections it cannot enforce against the subcontractor.
Should the agreement address AI use at all?
Yes, because silence invites different assumptions. A balanced clause lets each party use its own records freely, bars model training on the other party's confidential information without consent, and defines de-identified data. That keeps the carrier's maintenance and dispatch history usable while protecting the shipper's customer information.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.