The three-period insurance model is the pivot point for every Lyft injury case. Miss which period the driver was in at the moment of impact and you'll chase the wrong policy — or none at all.
Lyft accident cases look like straightforward motor vehicle claims until the insurance question comes up. Then they become a coverage puzzle that most intake teams get wrong — either underselling the value to the client or missing the correct defendant entirely. This guide is a practical intake reference for law firm staff handling inbound Lyft accident leads.
Lyft's insurance coverage is structured around three states of the driver app at the moment of the crash. Which period applies determines whether your client is dealing with the driver's personal insurer, a Lyft contingent policy, or Lyft's $1 million corporate liability layer.
| Period | Driver App State | Coverage Available | Who Pays First |
|---|---|---|---|
| Period 1 | App off / driver offline | Driver's personal auto policy only | Driver's insurer |
| Period 2 | App on, waiting for match (no rider accepted) | $50K/$100K BI / $25K PD contingent via Lyft; personal policy may deny | Driver's personal policy (if it applies), then Lyft contingent |
| Period 3 | Ride accepted through drop-off (rider in vehicle or en route to pickup) | $1,000,000 third-party liability; uninsured/underinsured included | Lyft's commercial policy |
Lyft cases have a different information architecture than standard auto cases. These 12 questions cover the period identification, defendant identification, and documentation preservation window.
Lyft accident cases often have multiple potential defendants. Intake should identify each before intake is closed.
In Period 3, the driver's personal policy usually denies coverage because the vehicle was in commercial use. The driver is still a defendant, but the recovery is typically through Lyft's commercial policy, not the driver personally. In Period 1, the driver's personal policy is the only coverage.
In Period 3, Lyft's $1M commercial policy applies. Whether Lyft bears direct negligence liability (negligent driver vetting, negligent retention) or is purely vicariously liable via the policy varies by jurisdiction. Some states have specific TNC liability statutes. Pleading Lyft as a direct defendant — not just as insurer — opens discovery into driver screening and vehicle inspection records.
If another vehicle caused the crash, that driver and their insurer are primary defendants. Lyft's UIM layer ($1M in Period 3) can apply if the third-party driver is underinsured. This is the most valuable case structure — two policy layers.
Lyft drivers can operate vehicles they don't own. If the vehicle is owned by a third party (a family member or fleet operator), the owner may have vicarious liability depending on state permissive use law.
Lyft's app data — GPS logs, trip start/end records, app state timestamps — is not retained indefinitely. Third-party subpoenas issued months later often return "no data retained" responses. Intake teams should flag these preservation items at the first call:
Period 2 is where the most intake errors happen. If the driver was logged into the app and waiting for a ride match but had not yet accepted a request when the crash occurred, the coverage picture is complicated:
For Period 2 cases, the first thing to do is request Lyft's driver app session log via subpoena or a pre-litigation evidence request under your state's TNC act (many states now require TNCs to retain this data). Clients with serious injuries in Period 2 cases frequently get underpaid because intake teams write off the corporate coverage layer too early.
| Mistake | Why It Happens | The Fix |
|---|---|---|
| Treating it as a standard auto claim | Intake rep doesn't recognize the TNC coverage structure | Add a Lyft/Uber checkbox to the intake form that triggers a rideshare-specific script |
| Not asking about app state | Caller doesn't know to mention it | Ask explicitly: "Did the Lyft app show your driver was on the way?" |
| Skipping the UIM analysis | Assumes the $1M Lyft policy is enough | Always gather the client's own auto policy; stack potential is substantial in catastrophic cases |
| Letting the client talk to Lyft's TPA first | Lyft sends claims contact quickly | Advise the caller to say "I have an attorney" even if they haven't signed yet; you can get a letter of representation out within hours |
| Missing the pedestrian/cyclist caller | Third-party callers think they can't claim against Lyft | Any person injured by a Lyft vehicle in Period 3 is a third-party claimant against Lyft's $1M policy |
Our intake agents are trained on the TNC coverage period structure and know to ask the period-identifying questions on the first call. We document the app state determination in the case intake form so your attorneys see it before they open the file. For Lyft cases that come in overnight or on weekends — when most rideshare accidents happen — our 24/7 coverage means the evidence preservation window doesn't close before someone talks to your client.
HQ Intake specializes in rideshare accident intake. Our agents identify the coverage period, preserve the evidence trail, and get the case file to your team ready for demand.
Schedule a CallRideshare accident cases frequently involve overlapping injury practice areas. For attorneys handling motorcycle and vehicle accident cases in the Tampa Bay area, Injury Lawyers of Tampa covers a range of urban vehicle injury matters. When a Lyft accident involves a waterway, port, or vessel-adjacent location, it may also be worth consulting a maritime personal injury attorney to evaluate potential admiralty law considerations.