Uber and Lyft cases in Atlanta look like ordinary car-accident cases until you start unpacking the insurance. Three or four policies can be in play at once, and which one pays depends entirely on what the driver's app was showing at the moment of impact. The wrong assumption about coverage at the start of the case can cost real money at the end of it. The right assumption is grounded in the rideshare company's actual policy structure and Georgia's statutory rules for transportation network companies.
What follows is the framework we use at Pereira & Associates to evaluate Uber and Lyft cases in metro Atlanta. None of it is exotic. All of it gets missed by adjusters who would rather route the case to whichever policy pays the least.
The driver's app status is the threshold question
Both Uber and Lyft structure their insurance coverage in tiers, and the tier that applies depends on what the rideshare app was showing at the moment of the collision. There are four states, and the coverage available to an injured passenger, pedestrian, cyclist, or other driver changes dramatically as you move from one to the next.
The four app states
- App offline — driver is not working. The rideshare company has zero coverage. The driver's personal auto policy is the only source of insurance.
- App on, no ride accepted — driver is logged in and waiting for a ride request. Limited contingent coverage applies (typically $50,000 / $100,000 / $25,000 in liability) only if the driver's personal policy denies the claim.
- Ride accepted, en route to pickup — the rideshare company's $1,000,000 commercial liability policy is in primary coverage from the moment the driver accepts the ping until the moment the rider is dropped off.
- Ride in progress (rider in the vehicle) — same $1,000,000 policy applies. Plus the rider has access to $1,000,000 in uninsured/underinsured motorist (UM/UIM) coverage if the at-fault party turns out to be uninsured or underinsured.
The difference between state two and state three is the difference between $50,000 in coverage and $1,000,000 in coverage. That single fact decides whether a case is worth ten thousand dollars or several hundred thousand dollars before any other analysis.
Why proving the driver's status is harder than it sounds
The rideshare company's app records exactly what state the driver was in at every moment. That record is conclusive evidence — when you can get it. The problem is that the record is in the rideshare company's possession, not the driver's, and obtaining it requires either the driver's voluntary cooperation or a properly served subpoena to Uber Technologies, Inc. or Lyft, Inc.
We have seen cases where the driver tells the responding officer they were 'just driving home from a ride' — implying app-off — when the trip data later shows they had a passenger en route to a destination at the moment of impact. The officer's report reflects what the driver said. The trip data reflects what was true. Reconciling those two is part of the work in every rideshare case.
This is the single biggest reason rideshare cases benefit from prompt counsel. The data exists. It is recoverable. But the rideshare company is not in a hurry to hand it over to the injured party, and the driver may have reasons of their own — including avoiding personal liability if app-off — to remember the moment differently than it actually unfolded.
Georgia's statutory framework for rideshare insurance
Georgia codifies these coverage tiers at O.C.G.A. § 33-1-24, the state's transportation network company insurance statute. The statute requires Uber and Lyft (and any other TNC operating in Georgia) to maintain the layered coverage outlined above. The statute also addresses what happens when there is a dispute over which tier applies — and it tilts in favor of the injured party in close calls, which matters when the driver's status is contested.
Beyond the TNC statute itself, the underlying personal-injury rules of Georgia all apply: the two-year statute of limitations under O.C.G.A. § 9-3-33, the modified comparative negligence rule under O.C.G.A. § 51-12-33 (with the 50% bar on plaintiff fault), and the apportionment rules among multiple defendants. None of these are suspended just because Uber or Lyft is in the picture.
Common scenarios and how the coverage shakes out
Scenario 1: You were the rideshare passenger
If you were a passenger in the Uber or Lyft and the rideshare driver was at fault, the rideshare company's $1,000,000 commercial liability policy is the primary source of recovery. If the at-fault party was someone else (another vehicle hit the rideshare you were in), that other driver's liability insurance is the primary source — and if their coverage is inadequate, the rideshare company's $1,000,000 UM/UIM policy is the backstop. As a passenger, your own personal auto insurance also potentially applies through MedPay, health insurance, or any UM coverage you carry.
Scenario 2: You were in another car hit by a rideshare driver
If a rideshare driver hit you and the driver had a rider in the car (or was en route to one), the $1,000,000 commercial policy applies. If the driver was logged in but had no ride accepted, you may be limited to the smaller contingent coverage — typically only after the driver's personal auto insurer has denied. If the driver was app-off, only the personal policy applies, and Georgia's minimum-coverage drivers carry just $25,000 per person.
Scenario 3: You were a pedestrian or cyclist
Same coverage analysis as scenario 2. The rideshare driver's app status at the moment they struck you decides the coverage tier. Pedestrians and cyclists do not have the rideshare company's UM coverage as a backstop the way passengers do — only your own UM/UIM coverage on your own auto policy applies, if you carry one.
Scenario 4: The rideshare driver themselves was injured
Rideshare drivers are independent contractors, not employees, so workers' compensation generally does not apply. The driver's recovery against an at-fault third party comes from that third party's liability insurance and (if available) the driver's own UM coverage. Some rideshare-driver-specific commercial policies are now available; whether the driver carried one matters.
Evidence that disappears in days
Rideshare cases have a narrower evidence-preservation window than ordinary auto cases for one specific reason: the trip record. Uber and Lyft retain trip data for years internally, but obtaining it requires a formal request — and depending on how the request is made, the company may produce only the bare-minimum records or may produce the full data set including GPS pings, app status changes, ride acceptance and completion timestamps, and any in-app messages between driver and rider. The detail in those records often determines the case.
Evidence to preserve immediately
- Photos of the rideshare driver's app screen if it is visible on the phone (screenshot of the trip in progress is gold)
- The trip receipt the rider receives by email or in-app — which contains the trip ID, route, and timestamps
- Police-report identifiers and any officer body-cam footage available through public-records request
- Witness names and contact information — especially other rideshare drivers in the area who may have seen the crash
- Any in-vehicle dashcam or rear-facing camera footage from the rideshare vehicle
- Texts or messages between rider and driver that reference the trip
Why these cases benefit from a tax-aware lens
This is where the firm's tax-and-injury combination changes the analysis. Uber and Lyft cases often produce mid-six-figure to seven-figure settlement potential when a serious injury is involved and the $1,000,000 commercial policy is in play. Settlements at that scale come with tax-treatment and structuring decisions that most personal injury firms handle from rough estimates rather than from analytical training.
Compensatory damages for physical injury are excluded from federal income tax under IRC § 104(a)(2). The interest and punitive components are taxable. Lost-wage portions of settlements without underlying physical injury are taxable. Structured settlements created at the time of resolution are tax-free under IRC § 130 — but only if structured at the time of resolution; converting after the check clears does not preserve the exclusion.
William Pereira spent his earlier career doing this kind of analysis at PricewaterhouseCoopers and holds an LLM in Taxation. On serious rideshare cases, that lens is applied to the settlement structuring from day one rather than handed off to an outside CPA after the fact.
What to do in the first 48 hours after an Atlanta Uber or Lyft accident
- Get medical attention even if you feel okay — soft-tissue and concussion injuries often surface on day 2 or 3, not at the scene
- Photograph the rideshare driver's app screen, license, registration, and vehicle from multiple angles
- Save the trip receipt — Uber emails it; Lyft shows it in the in-app trip history
- Get the responding officer's name, badge number, and report number
- Collect contact information for any witnesses, including other rideshare drivers in the area
- Do not give a recorded statement to either the rideshare company's adjuster or the at-fault driver's adjuster
- Do not sign any medical authorization for either insurer until an attorney has reviewed it
- Note exactly what you remember about the rideshare driver's behavior and the app status before the impact
The honest read
Atlanta Uber and Lyft cases are layered but not mysterious. The coverage architecture is public. The trip data exists. The Georgia statute is clear. What separates a well-handled rideshare case from a mishandled one is whether the lawyer involved has actually mapped the coverage to the facts before negotiating with the carriers — and whether the evidence preservation happened in days rather than weeks.
If you were injured in an Uber, Lyft, or comparable rideshare in metro Atlanta, the consultation is free. We will tell you which coverage tier applies based on what we know, what evidence is salvageable, and whether the case is one we believe is worth pursuing. The honest assessment is part of the standard.