Car-accident records are rarely held in one file. The police agency may hold the crash report and body-camera material; a 911 center may hold calls and dispatch data; a tow company may hold intake photographs; an insurer may hold claim communications; a repair shop may hold estimates and scans; and a device or application provider may hold electronic data. A custodian map identifies who may hold what before a request is drafted.

A custodian map should connect each requested record to the person or entity that creates or keeps it, the relevant account or incident identifiers, the date range, the available format, the request method, and the response without assuming that one company controls every related record.

Separate the creator, owner, system operator, and custodian

  • Person or device that created the record
  • Entity that owns the account, vehicle, property, device, or business system
  • Vendor that operates or hosts the system
  • Department or person responsible for maintaining and producing records
  • Successor, parent, contractor, third-party administrator, or archive provider identified only when a reliable source supports the role

Build the map by record family

  • Public-safety records: 911 audio, computer-aided dispatch, officer video, photographs, diagrams, notes, citations, and crash-report files
  • Vehicle records: title, registration, inspection, tow, storage, salvage, repair, diagnostic, event-data, camera, navigation, and telematics information
  • Insurance records: policy documents, claim number, acknowledgment, correspondence, recorded material, estimates, payments, and coverage communications
  • Medical and financial records: provider, health plan, pharmacy, employer, wage, benefit, bill, payment, and reimbursement sources
  • Scene and witness records: property cameras, business incident file, traffic-control data, photographs, messages, and contact information

Use stable identifiers

  • Crash-report or incident number, call number, officer, agency, date, time, location, and involved person
  • Vehicle identification number, plate, owner, driver, tow ticket, repair order, claim number, and policy number
  • Provider account, patient or member identifier, date of service, employer, pay period, and benefit claim number
  • Device, account, application, telephone number, email address, username, vehicle, route, trip, or file identifier
  • Name variation, company legal name, trade name, merger, or transfer recorded without merging separate entities

An identifier can connect records without proving that every connected event is accurate. Preserve the source that supplied the identifier, any discrepancy, and the time period during which it applied.

Record format and retention facts without assuming them

  • Native file, database export, report, image, PDF, audio, video, transcript, screenshot, paper record, or physical item
  • Metadata, audit history, field definitions, code tables, timezone information, attachments, and linked objects that may be needed to understand the record
  • Known or claimed retention period, automatic overwrite, deletion event, litigation hold, archive, or unavailable status attributed to the source
  • Public-record request, individual access request, voluntary request, insurer portal, provider request, discovery request, subpoena, or other route identified separately

Turn the map into a request plan

The related guide to document requests and electronic evidence in a North Carolina car-accident lawsuit explains formal litigation tools. A custodian map comes first. It should identify the correct legal entity, system, date range, record fields, and likely objections before anyone chooses a request method.

  • Request only the relevant record family, date range, people, vehicle, account, event, and metadata
  • Name the desired native format and associated field definitions when electronic data is involved
  • Track recipient, delivery, date, confirmation, response, objection, partial production, missing item, follow-up, and supplement
  • Do not access a private account, device, vehicle, property, or system without permission or legal authority

North Carolina Rule of Civil Procedure 34 addresses requests to parties for documents, electronically stored information, tangible things, and property inspection in a civil action. Rule 45 addresses subpoenas, including provisions involving documents, electronically stored information, objections, and protections. These litigation procedures are different from voluntary or public-record requests.

Preserve authenticity and original data form

North Carolina Rule of Evidence 901 addresses authentication and offers examples involving witness knowledge, distinctive characteristics, public records, and a process or system. Rule 1001 defines writings and recordings to include electronic data compilations and addresses originals and duplicates in that setting.

  • Preserve native files, original messages, envelopes, headers, download details, file names, and hashes where available
  • Maintain a collection log recording who obtained each item, when, how, and from whom
  • Keep a read-only source set and perform joins, sorting, redaction, and annotation in a separate working copy
  • Treat a missing response as unresolved rather than evidence that the record never existed

A North Carolina car-accident matter involving records held by several custodians may require a prompt and fact-specific preservation plan. This article provides a mapping method, not a representation that every listed record exists or a conclusion about admissibility, fault, coverage, or recovery.