What happens when a driver says they never saw a cyclist, but the cyclist believes they were clearly visible? Questions like this often arise after bicycle crashes because visibility depends on more than whether a person was physically present on the road. Lighting, traffic, parked vehicles, weather, road design, vehicle blind spots, and the movements […]
After a North Carolina rideshare crash, the decisive insurance fact may be a timestamp: when the driver logged on, accepted a request, began providing transportation, completed the trip, or logged off. A receipt may show one part of that sequence, but North Carolina law calls for a wider record in a coverage investigation.
The required record spans the 12 hours before and the 12 hours after the collision, not only the passenger’s visible trip receipt.
Article 10A defines the rideshare activity
Article 10A of Chapter 20 defines a transportation-network company, driver, online platform, and TNC service. Under the statutory definition, the service begins when a driver accepts a ride request and ends at the later of the application transaction being completed or all passengers and their property leaving the vehicle.
That definition creates timestamps that may not be identical: request, acceptance, travel to pickup, passenger entry, trip movement, passenger exit, unloading, application completion, cancellation, and logoff. Preserve the source of each time and the time zone rather than merging them into one approximate trip period.
G.S. 20-280.4 requires a 24-hour exchange window
G.S. 20-280.4(m) states that, during a claims coverage investigation or accident, the TNC driver, company, potentially providing insurers, and other directly involved parties must exchange policy descriptions, exclusions, and limits. They must also exchange precise login, logoff, and TNC-service times for the 12 hours immediately before and the 12 hours immediately after the accident.
The same statute sets different financial-responsibility requirements for a driver who is logged on but not providing TNC service and a driver who is providing the service. The statutory figures are minimum coverage requirements, not a statement of the amount owed in an individual case.
Build the source-by-source timestamp table
- Driver platform activity showing every login, logoff, accepted request, cancellation, pickup, trip start, trip completion, and service period in the statutory window
- Passenger application screens, trip receipt, route, pickup and drop-off pins, messages, calls, safety reports, refunds, and later account changes
- Phone, location, navigation, vehicle, dash-camera, event-data, toll, parking, fuel, dispatch, and payment records with clock settings and time zones
- Crash-report, 911, emergency-dispatch, responder, photograph, video, witness, medical, and employer records that independently establish time
- Each relevant personal, rideshare, commercial, household, owner, rental, and uninsured- or underinsured-motorist policy and the insurer’s written coverage position
A company must retain service records for one year
G.S. 20-280.5(c) requires a transportation-network company to maintain the record of each TNC service provided in North Carolina for one year from the service date. It also requires a driver record for one year after the driver’s relationship with the company ends.
A statutory retention period is not a promise that every potentially relevant app, phone, telemetry, message, investigation, audio, video, or insurer record will remain available for the same time. A preservation request should identify the event, people, accounts, devices, vehicle, data types, time range, and requested suspension of routine deletion.
Resolve conflicts without assuming one record controls
A receipt can conflict with platform logs, the driver’s phone, a crash-report time, a canceled request, delayed application completion, or a passenger exit that occurred before property was unloaded. Preserve the original records and metadata, identify whether times are local or coordinated universal time, and explain system-generated versus manually entered values.
The related guide to reading a North Carolina rideshare trip receipt after a crash explains the passenger-facing document.
Rosensteel Fleishman Car Accident & Injury Lawyers provides information about consulting a Charlotte rideshare-accident lawyer when app-status and insurance records must be reconciled. Coverage, fault, causation, defenses, deadlines, and damages depend on the actual policies and complete evidence.
Sources
Additional Car Accidents Personal Injury Rideshare Accidents Articles
How Prescription Records Affect an Injury Claim and Document Ongoing Treatment
Prescription records can help show whether an injured person followed a consistent course of medical care after an accident. They may identify when medication was prescribed, what symptoms a provider was trying to manage, whether prescriptions changed as recovery progressed, and how long treatment continued. For families in Charlotte, North Carolina, these details can become […]
Low Speed Collision Basics When Injuries Are More Serious Than Expected
A low speed crash can look minor at first, yet the physical and financial consequences are not always obvious in the first hours or days. In Charlotte, North Carolina, someone may leave a parking lot collision, intersection bump, or stop and go traffic crash believing the matter will be simple, only to notice increasing neck […]
Lane Splitting Accident Considerations for Riders in Charlotte North Carolina
In Charlotte, North Carolina, a motorcycle crash involving movement between lanes can quickly raise questions about visibility, road position, and each driver’s actions. Those questions become even more complicated when an injured rider waits to seek medical care, since an insurance company may examine both the circumstances of the collision and the timing of the […]
