Insurance and record questions after a rideshare crash can depend on what the driver and platform were doing at the collision time. “Driving for a rideshare company” is too broad. The driver may have been logged off, logged on and waiting, responding to an accepted request, traveling to pickup, carrying a passenger, completing a trip, or using another platform.

A rideshare app-status timeline should identify precise logon, request, acceptance, pickup, service, drop-off, cancellation, logoff, and collision times and name the source for each entry.

Fix the collision and participant identities first

  • Collision date, time, time zone, location, investigating agency, report number, vehicles, drivers, owners, passengers, and witnesses
  • Rideshare company, driver account, vehicle shown in the app, actual vehicle, license plate, phone, app version if known, and other active platform
  • Passenger account, request identifier, pickup and destination, fare or receipt, route, driver photograph, vehicle description, and displayed map retained from the original source
  • Difference between the collision time, device time, platform time, report time, screenshot time, and later export time recorded explicitly

Build the app-state timeline from more than screenshots

  • Driver logon and logoff, availability, request offered, request accepted or declined, route to pickup, arrival, passenger pickup, service, drop-off, cancellation, and later activity
  • Trip receipt, in-app message, email, push notification, account history, data export, support ticket, payment record, and platform response
  • Driver phone, passenger phone, another occupant’s phone, vehicle system, camera, location history, carrier record, and witness observation kept as separate sources
  • Missing interval, clock drift, delayed synchronization, edited screenshot, shared account, device replacement, or disputed status flagged rather than filled with an assumption

Use North Carolina’s required time exchange

N.C. Gen. Stat. § 20-280.4 addresses transportation-network-company financial responsibility. Subsection (m) requires identified participants in a coverage investigation or accident to exchange policy descriptions and precise driver logon, logoff, and TNC-service times for the stated period before and after the accident. Preserve the request, response, complete time data, policy material, and any disputed or missing interval.

Request the service and driver records tied to the date

N.C. Gen. Stat. § 20-280.5 addresses TNC safety requirements and requires the company to maintain each North Carolina TNC-service record for one year and identified driver records for one year after the relationship ends. A targeted request should identify the company, driver, vehicle, passenger or request, date, time range, account, and collision.

  • Request native or complete exports where available, not only a cropped screen image
  • Preserve field names, timestamps, time zone, status codes, device or account identifier, export date, and custodian response
  • Ask what data were searched, what period was retained, what fields were omitted, and whether any record was overwritten or unavailable
  • Keep a later customer-service summary separate from underlying platform events

Compare app state with the actual policies

The North Carolina Department of Insurance explains on its rideshare and delivery driving page that personal-auto coverage can exclude public-livery or conveyance use and urges drivers to disclose platform driving and review available coverage. For a collision file, obtain each complete policy, declarations, endorsements, exclusions, reservation or denial, and written coverage position rather than deciding coverage from the app label alone.

Keep activity, coverage, and collision cause separate

  • App or service status may affect a coverage analysis without proving how the collision happened
  • A route or location point may show device activity without proving who held the phone or what the driver perceived
  • A policy limit is not proof that coverage applies, liability exists, injury was caused, or a payment is due
  • Platform, driver, vehicle, passenger, insurer, and other-driver records should be reconciled before a final status is assigned

The related guide to closing a North Carolina rideshare-injury claim across multiple policies addresses the later payment, release, lien, expense, and closing record. This page owns the earlier app-status and service timeline.

Rosensteel Fleishman Car Accident & Injury Lawyers provides general information about North Carolina rideshare-accident claims involving disputed app status. The complete time data, policies, collision evidence, and current law control the analysis.

Sources