A tractor-trailer may display several names and numbers that refer to different entities. The tractor owner, trailer owner, driver’s employer, authorized carrier, lessee, shipper, broker, loading facility, maintenance provider, insurer, and device vendor may not be the same organization. A logo or police-report label is a starting point, not a complete relationship map.

An entity-and-custodian matrix should connect every truck, trailer, driver, carrier, owner, lessee, shipper, broker, maintenance provider, insurer, device, document, and public record to a verified identifier, role, time period, source, custodian, and unresolved relationship.

Capture identifiers from each source

  • Legal name, trade name, former name, address, telephone number, USDOT number, MC or other operating-authority number, state registration, process agent, and insurance-related identifier
  • Tractor and trailer year, make, model, vehicle identification number, plate, state, unit number, markings, title owner, registrant, operator, and physical custodian
  • Driver name, license jurisdiction and class, employer or contracting entity as reported, dispatch source, trip, route, origin, destination, cargo, and time period
  • Source document, photograph, public database, date accessed, effective or event date, record custodian, conflicting source, and status requiring verification

Use public carrier data within its limits

FMCSA explains that the SAFER Company Snapshot provides public identification, size, commodity, inspection, crash, and safety-rating information drawn from government motor-carrier databases. Snapshot fields and counts have their own update periods and definitions. A current public result does not by itself establish the entity’s event-date role, equipment ownership, employment relationship, insurance coverage, fault, or the contents of private records.

  • Search term used, exact result, USDOT number, legal and trade names, status, operation classification, carrier type, cargo, power units, drivers, and displayed dates
  • Profile, registration, authority, insurance, process-agent, state, title, lease, trip, dispatch, bill-of-lading, and other sources kept separately
  • Name or number mismatch, inactive or changed status, shared address, related entity, equipment marking, stale public field, or missing event-date record flagged for follow-up
  • Screenshot or saved result retained with access date and no assumption that later public data recreates the event-date record

Determine how equipment was being used

49 C.F.R. § 376.11 addresses specified leasing of equipment by an authorized carrier and includes written-lease, equipment-receipt, identification, and trip-record provisions. 49 C.F.R. § 376.12 addresses required lease terms, including parties, duration, possession, control, use, compensation, receipts, and costs. Applicability depends on the operation and agreement; the required control provision does not by itself decide every employment or responsibility question.

  • Lease, interchange, rental, owner-operator agreement, dispatch agreement, trip lease, receipt, vehicle list, amendment, termination, and event-date version
  • Party names and identifiers, equipment covered, start and end, possession transfer, receipt date and time, driver source, route, cargo, compensation, control terms, and operating authority
  • Who selected, dispatched, inspected, maintained, fueled, loaded, tracked, insured, stored, repaired, or recovered each unit and the source for that role
  • Contract label compared with actual records and conduct without treating one clause as a complete legal conclusion

Assign every record to a likely custodian

  • Driver qualification and employment or contract records; dispatch, trip, communication, duty-status, fuel, toll, navigation, telematics, and device records
  • Tractor, trailer, tire, brake, inspection, maintenance, repair, recall, warranty, rental, lease, tow, storage, download, and post-crash inspection records
  • Shipping, broker, shipper, consignee, bill-of-lading, cargo, weight, seal, loading, securement, facility, gate, appointment, and surveillance records
  • Policy, endorsement, certificate, filing, notice, claim, reservation, coverage, excess or other layer, and insurer or administrator records

49 C.F.R. § 390.15 requires covered motor carriers to maintain an accident register for a stated period and identifies specified information and report copies. The register is one carrier record; it is not a substitute for the police file, vehicle evidence, private communications, maintenance material, electronic data, medical records, or a complete event investigation.

Track preservation and response separately by custodian

  • Custodian legal name, address, contact, role, record categories, relevant time window, retention information, format, system, access authority, and preservation request
  • Date sent, method, recipient, delivery evidence, acknowledgment, objection, partial response, alternate custodian, unavailable source, and next action
  • Native data, metadata, paper record, physical equipment, video, photograph, public filing, database extract, report, and later summary identified separately
  • Entity conflict or unknown relationship left open until supported by contracts, public records, testimony, business records, equipment records, and event evidence

The related guide to mapping carrier-controlled records after a rear-end truck collision identifies record categories that may be held by a carrier. This page owns the prior entity, identifier, relationship, equipment, and custodian map used to direct those requests.

Rosensteel Fleishman Car Accident & Injury Lawyers provides information about North Carolina truck-accident claims. Entity roles, regulatory applicability, custody, and responsibility should be determined from event-specific records and qualified legal review.

Sources