Why the periods exist
Personal auto policies exclude commercial driving. The app going on starts the disclaimers. California’s TNC framework filled the gap with mandatory tiers. Every claim becomes a timestamp question before it is an injury question.
Downtown makes the timestamp fight concrete. Drivers stage near the Hall of Justice, the convention center, and the Marketplace, then run University Avenue toward UCR or hop on the 91. The same driver can be Period 0 in a parking structure, Period 1 circling Market Street, and Period 2 two minutes later. The crash does not care. The coverage does.
About one in six California drivers is uninsured. If you were the other car — not the passenger — the period still decides whether you are chasing a personal policy, a thin contingent tier, or a million-dollar commercial layer.
Period 0 and Period 1 — thin ice
App off: personal policy responds like any commute crash. The fight often runs the other way. Drivers claim “off” when they were waiting, because Period 1 embarrasses their personal claim. Subpoenaed app records settle it.
Period 1 — app on, circling for a ping: contingent coverage at 50/100/30. Real, but thin against a surgical injury, and it typically answers only after the personal policy formally denies. Badly hurt victims here often need their own UIM to be made whole. A denial letter from the personal carrier is not a dead end. It is the on-ramp to the TNC tier.
Hit between rides on Van Buren or waiting in a downtown lot? That is the Period 1 fact pattern. Screenshot anything you can. Do not take the driver’s word for app status.
Periods 2–3 — the million-dollar window
Acceptance through drop-off: the $1M commercial policy covers the driver’s liability. Passengers also get UM/UIM protection layered on. Hypothetical: a visitor picked up at the convention center is injured when a third driver runs a civic-grid signal on a minimum policy. The passenger may still recover fully — through the TNC’s UM tier. Passengers rarely know this. It is the most valuable fact on this page, and the passenger-rights guide builds on it.
The trip receipt is period-proof for passengers. Struck third parties need the police report plus subpoenaed app data. Screenshot early. Anchored requests go smoother.
How period fights show up on local trips
Court-day downtown: drivers stage near the Hall of Justice and the convention hotels. A crash in that lot while the app is on and idle is Period 1 until a ping says otherwise. A crash two minutes after acceptance on Market Street is Period 2. The passenger’s receipt settles it. The other car’s driver has to subpoena it. Screenshot anyway.
UCR runs on University Avenue look like ordinary arterial crashes until someone asks what the app said. A student passenger has the cleanest proof. A third car hit by the rideshare driver has the hardest. Both still start with the timestamp. Police narratives that say “Uber” are helpful and not enough. The company data is the period.
91 corridor trips toward Orange County add speed and multi-car stacks. Period 3 plus another at-fault driver is a two-policy file. Do not let the administrator settle “their share” in a way that releases the other share. Sequence the releases. That is counsel work.
Delivery-app crashes are a cousin, not a twin. Bring the app name. The method — status first, terms second — stays. (909) 233-7999.
Drivers sometimes toggle the app after a crash. Do not rely on what they say in the street. The company’s logs have a clock. So does your receipt. So does a passenger’s push notification. Collect those three when you can. A Period 0 story that contradicts a Period 2 receipt is not a mystery. It is a coverage fight the data will end.
If you were the other car, your own UM/UIM still matters when Period 1’s thin limits run out. Do not assume “it was an Uber” means million-dollar coverage. That is Periods 2–3. Period 1 is a different ceiling. The whole point of this page is that sentence.
Lyft and Uber use the same California period structure with different administrator names. Do not get lost in the brand. Get the timestamp. Then read that brand’s declarations for the trip date. Forms change. The period logic does not.
If the driver was carrying a passenger and a delivery bag, say so. Mixed-use trips can scramble which product’s coverage answers. The timestamp still comes first. The product name comes second. Guessing first is how Period 3 becomes a Period 1 argument.
Winning the timestamp fight
Report in-app promptly. It creates the company’s own record. Expect each insurer to point at another period. The data is subpoenaable and decisive. When carriers stall in the gaps — and whether these files end up in a courtroom at the Hall of Justice at all — here is how they actually resolve.
A rideshare crash claim starts by nailing the period. One call. Free. (909) 233-7999.
