Georgia Legal Guide: How Does an Uber or Lyft Driver’s App Status Affect Your Accident Claim?
Key Points
- Under Georgia’s rideshare statute, O.C.G.A. § 33-1-24, insurance coverage can change depending on the driver’s app status.
- An offline driver generally relies on personal auto insurance, while a driver waiting for a request, driving to a pickup, or on an active trip may trigger different levels of rideshare coverage.
- Trip logs, ride acceptance and drop-off timestamps, and GPS data can establish the driver’s app status after a crash.
- Identifying every applicable source of coverage matters when injuries and damages are serious and exceed the limits of the first available policy.
If you were hurt in a wreck involving an Uber or Lyft driver, the driver’s app status at the time of the crash can affect which insurance coverage applies. Whether the driver was logged into the app, had accepted a ride, or was already transporting a passenger may determine which policy covers your injuries and how much coverage is available.
Why Does an Uber or Lyft Driver’s App Status Matter to My Accident Claim?
Under Georgia’s rideshare statute, O.C.G.A. § 33-1-24, required insurance coverage varies depending on the driver’s rideshare activity at the time of the crash.
Georgia also allows a driver’s personal auto insurer to exclude coverage, including uninsured motorist (UM) and medical payments coverage, while the driver is providing rideshare services (O.C.G.A. § 33-1-24(g)(2)). As a result, whether the driver was on a personal trip, waiting for a request, heading to a pickup, or transporting a passenger can determine which insurer and policy limits apply.
What Are the Different Uber and Lyft App Statuses That Can Affect Insurance Coverage?
There are four basic app statuses. The driver may be logged out and using the car personally; logged in and waiting for a request; driving to pick up an accepted passenger; or transporting a passenger until drop-off.
Insurers may call the waiting phase “Period 1” or “Period A” and the accepted-ride-through-drop-off phase as “Periods 2 and 3” or “Period B.” In Georgia, the accepted-ride period requires higher insurance coverage, while the logged-in-but-unmatched period requires lower coverage.
What Insurance Applies If the Uber or Lyft Driver Was Logged Out of the App?
If the driver was logged out and driving for personal reasons, the driver’s personal auto policy is generally the primary coverage. Because someone drives for Uber or Lyft does not mean rideshare insurance covers every crash.
If the app was off, the driver’s personal policy could carry Georgia’s minimum liability limits of at least $25,000 per person and $50,000 per accident under (O.C.G.A. § 40-9-37; see also O.C.G.A. § 33-7-11(a)(1)(A)). Additional coverage may be available through the injured person’s UM coverage.
Whether a driver was truly logged out is not always clear. The app may have remained active in the background, the driver may have logged out after impact, or the driver may have been between trips without ending the session. When app status affects available coverage, electronic records should be reviewed rather than relying only on the driver’s memory.
What Insurance Applies If the Driver Was Logged In but Waiting for a Ride Request?
A driver who is logged in but has not accepted a ride is in a separate insurance period. Georgia’s rideshare requirements provide minimum bodily injury limits of $50,000 per person and $100,000 per accident during this waiting period, plus property damage coverage. These limits are significantly lower than the $1 million in coverage commonly associated with Uber and Lyft.
Georgia allows the statutory rideshare coverage to be maintained by the driver, the rideshare company, or both. If the coverage the driver was maintaining to satisfy those requirements has lapsed or ceased to exist, the rideshare company must provide the coverage, and it becomes primary beginning with the first dollar of the claim (O.C.G.A. § 33-1-24(f)).
Uber and Lyft are subject to Georgia’s minimum requirements, but they may use different insurers, policies, and endorsements. Available coverage should be confirmed by reviewing the policy, declarations, and endorsements in effect on the date of the crash.
What Changes Once an Uber or Lyft Driver Accepts a Ride Request?
Under Georgia law, the higher-coverage period begins when the driver accepts a ride request and continues until the driver completes the transaction or the ride is complete – whichever is later, even before the passenger enters the vehicle. During that period, the rideshare policy must provide at least $1 million for death, personal injury, and property damage per occurrence (O.C.G.A. § 33-1-24(a)(5)(B), (b)(3)).
A driver who causes a crash while waiting for a request may have much lower required coverage than the same driver after accepting a ride. The injuries may be identical, but the available insurance can change based on the driver’s app status.
Comparing the ride-acceptance time with the time of impact can help determine which coverage applies. Platform records can provide important evidence of when the driver accepted the ride.
What Insurance Applies When an Uber or Lyft Passenger Is Already in the Vehicle?
Once a passenger has been picked up and the trip is active, the rideshare policy must provide at least $1 million in liability coverage per occurrence under (O.C.G.A. § 33-1-24(a)(5)(B), (b)(3)). Which coverage applies may then depend on who caused the crash.
If the rideshare driver caused the collision, the active-trip rideshare liability policy generally applies. If another driver caused the crash, that driver’s liability policy usually comes first. If that driver was uninsured or underinsured, UM/UIM coverage may also apply. For causes of action accruing on or after July 1, 2023, Georgia’s required rideshare UM/UIM minimums for bodily injury are $100,000 per person and $300,000 per accident; earlier claims had a $1 million per-incident minimum (O.C.G.A. §§ 33-7-11, 33-1-24(b)(3)). Insurance coverage for lost or damaged cargo is available, with a minimum requirement of $25,000.
Rideshare UM coverage may be written as “reduced-by” rather than “added-on,” allowing an offset for payments from the at-fault driver’s liability policy. The injured person’s UM coverage may also apply because Georgia UM coverage can follow the insured person, sometimes allowing multiple policies to be stacked.
What If the Uber or Lyft Driver Disputes Their App Status After the Accident?
A driver may tell the insurer the app was off, the trip had ended, or the ride was canceled before impact. Because the driver’s app status can affect which policy and coverage limits apply, that information should be verified.
A driver may not remember the sequence of events or know when the app recorded a cancellation or status change. Platform records can provide a more complete timeline and help establish the driver’s status at the time of the crash.
How Can You Prove the Uber or Lyft Driver’s App Status at the Exact Time of the Crash?
The rideshare platform’s records may include important evidence of the driver’s app status. Relevant evidence may include driver activity and trip logs, acceptance and cancellation records, pickup and drop-off timestamps, GPS data, passenger receipts, screenshots, police reports, witness statements, legally obtainable phone records, and the driver’s platform status history.
Because coverage periods can change within seconds, timestamps are especially important. For example, a ride-acceptance log with the time of a 911 call can help establish whether the driver had accepted a ride before the crash. The rideshare policy, declarations page, and UM endorsement from the crash date should also be reviewed because policy terms, including whether UM is add-on or reduced-by, can change the available recovery.
Uber or Lyft holds many of these records and may not provide them automatically. Trip and status data should be preserved early, policy documents should be requested in writing, and disputed records may need to be obtained through formal discovery in litigation.
What Happens If the Driver’s App Status Changes Right Before the Accident?
App status can become especially important when it changes shortly before a crash, such as after a ride is accepted, canceled, or completed, or when the driver logs out.
In these situations, insurers may disagree about which policy was in effect. Platform records, GPS data, 911 or dispatch records, and the police report can help establish when the status changed in relation to the crash.
Georgia law established required insurance minimums for different rideshare periods, but the available coverage also depends on the specific policy language, endorsements, and facts of the case. These documents and records should be reviewed to determine which coverage applies.
Can the Driver’s App Status Affect How Much Insurance Is Available for an Injury Claim?
Yes. App status does not change the value of your injuries, but it can change how much insurance is available to pay a valid claim. Medical bills, future treatment, lost income, reduced earning capacity, pain and suffering, permanent limitations, and other damages can exceed the limits of a personal auto policy.
If the app was off, the claim may depend on the driver’s personal liability limits and any available UM coverage. If the driver had accepted a ride, a $1 million per-occurrence rideshare policy may apply. Georgia UM coverage pays damages you are legally entitled to recover, up to applicable limits (O.C.G.A. § 33-7-11(a)(1)).
When damages are substantial, every applicable policy should be identified before a claim is resolved. Potential coverage may include rideshare liability and UM/UIM coverage, the driver’s personal policy, the injured person’s UM coverage, and qualifying resident-relative coverage, subject to applicable exhaustion requirements.
Example: Andre’s Story
The following scenario is fictional and is provided for educational purposes only.
Assume Andre is logged into Uber and waiting for a request near Ponce City Market in Atlanta. At 7:12 p.m., he accepts a ride and starts toward the pickup. At 7:15 p.m., he runs a red light on North Avenue and strikes Dana’s vehicle, causing serious injuries that require hospitalization and ongoing treatment. No passenger was in Andre’s car yet.
Andre later says he “wasn’t on a trip” because he had not picked up the passenger. Under Georgia law, the higher-coverage period can begin when the driver accepts a ride. Whether the lower waiting-period limits or a $1 million per-occurrence policy applies may depend on the three minutes between acceptance and impact. Uber’s acceptance record, activity log, GPS data, cancellation history, and the 911 call time could help establish the timeline.
Confirming Andre’s app status is only the first step. The applicable rideshare policy, declarations, and UM endorsement should also be reviewed to determine the available limits, UM structure, and interaction with other policies. If Dana’s damages exceed the first available policy, additional sources of coverage may apply.
Trip records, activity logs, GPS data, receipts, and the police report can help establish the driver’s app status at the time of the crash and can be requested and preserved.
Not necessarily. The key question is whether the driver was logged into and operating through the platform under the policy and Georgia law, which can be established through platform records.
Georgia’s higher-coverage period begins when the driver accepts a ride request and continues through completion. A crash while the driver is heading to the pickup may fall within that period (O.C.G.A. § 33-1-24(b)(3)).
The cancellation and crash times can help determine which coverage applies. The cancellation record, status log, and applicable policy language should also be reviewed.
Coverage depends on when the trip ended in the platform records and policy. The drop-off timestamp, post-trip status, and policy definition of when active-trip coverage ends should be reviewed.
The driver’s activity on each app should be reviewed to determine which policies or endorsements may apply.
The driver’s statement is relevant but not conclusive. Electronic records and policy language should also be reviewed. Georgia law does not allow rideshare coverage to depend on a personal insurer first denying the claim (O.C.G.A. § 33-1-24(h)(4)).
Trip, acceptance, cancellation, and GPS records can be requested and preserved. Disputed records and policy documents may also be obtained through formal discovery in litigation.
Myths and Facts About Uber and Lyft Driver’s App Status and Accident Claims
Myth #1: “If someone drives for Uber or Lyft, the rideshare company’s insurance automatically covers every accident they cause.”
Fact: Rideshare coverage depends on the driver’s activity at the time of the crash. If the driver was logged out on a personal trip, the personal auto policy is generally primary.
Myth #2: “If the Uber or Lyft app was turned on, the same insurance coverage applies no matter what the driver was doing.”
Fact: Georgia law distinguishes between waiting for a request and handling an accepted ride. O.C.G.A. § 33-1-24 requires a $1 million per-occurrence minimum during the accepted-ride period, while the waiting period has lower required limits.
Myth #3: “The driver must already have a passenger before rideshare insurance can apply.”
Fact: The higher-coverage period can begin when the driver accepts a ride request. A crash while driving to the pickup may fall within that period.
Myth #4: “If the driver says the app was off, there is no way to prove otherwise.”
Fact: Uber and Lyft maintain electronic records of log-ins, requests, acceptances, cancellations, trip times, and GPS data that can help establish the driver’s app status.
Myth #5: “The driver’s app status does not matter because an accident claim works the same whether the driver was working or not.”
Fact: App status can substantially change the insurance available to pay the claim, particularly when injuries and damages are serious.
