An Uber receipt, driver-app event, phone log, GPS point, dash camera, vehicle system, 911 record, traffic camera, and crash report can display different times for the same event. Before comparing conduct, the clocks and event definitions should be reconciled.

A rideshare time map should record each source clock, displayed time, stored time, time zone, offset, drift, event marker, collection method, export format, custodian, and uncertainty before events from different systems are placed on one sequence.

Inventory every time-bearing source

  • Passenger receipt, request, acceptance, arrival, pickup, trip start, route point, stop, drop-off, cancellation, safety report, message, and call
  • Driver app, passenger app, device clock, operating-system log, carrier call or message record, photograph, screenshot, and notification
  • Vehicle infotainment, navigation, event data, camera, motorcycle or other vehicle system, toll, parking, fuel, or access record
  • 911, dispatch, EMS, police, roadway sensor, business video, home camera, witness device, and crash-report entry

G.S. 20-280.5 addresses transportation network company records and identified retention and access subjects. Record the exact statutory version, record type, holder, request, response, and limitation rather than assuming every platform or device record is immediately available.

Record each clock before converting time

  • Displayed value, stored value, UTC or local basis, daylight-saving status, time-zone setting, device setting, server time, and export conversion
  • Known synchronization source, manual setting, offset, drift, reboot, battery loss, software update, edit, upload, download, and processing time
  • Event definition such as “accepted,” “arrived,” “pickup,” “trip started,” “message sent,” “message delivered,” or “video created” kept exact
  • Uncertainty range and reason preserved instead of forcing an exact second

Preserve native records and collection context

North Carolina Rule of Civil Procedure 34 addresses documents, electronically stored information, tangible things, and requested production forms. Preserve native files, metadata, export instructions, screenshots, reports, production ranges, replacements, objections, and collection notes separately.

North Carolina Rule of Evidence 901 addresses authentication or identification. A synchronized chart is a working summary; it does not itself authenticate the source or prove who used a device, what the person saw, or why a collision occurred.

Separate evidence of device activity from distraction conclusions

NHTSA’s distracted-driving resource describes visual, manual, and cognitive distraction. A timestamp can place an app, call, message, or screen event near a collision, but the user, task, attention, context, and causal significance require additional evidence.

  • Person associated with the device or account kept separate from proof of actual use at the relevant moment
  • App-generated event kept separate from a manual action, notification display, passenger action, or automated process
  • Time sequence compared with roadway, vehicle, witness, video, and physical evidence
  • Qualified technical or reconstruction opinion identified by author and foundation rather than supplied by the chart

The related guide to preserving Uber trip and app records after a North Carolina crash explains record identity and collection. This page owns the narrower task of synchronizing their clocks.

Rosensteel Fleishman Car Accident & Injury Lawyers provides general information about Charlotte Uber-accident matters involving disputed digital timelines. Preservation, access, authentication, technical interpretation, and legal conclusions require the complete record.

Sources