Negligent Retention of Unfit TNC Drivers

Bottom line. Under California negligent retention law, a hirer may be liable where it knew or should have known that the worker became unfit and that unfitness created a particular risk to others. The TNCs collect, in real time, every piece of data they would need to identify dangerous drivers. When they retain a driver despite documented complaints, low ratings, prior accidents, and explicit rider removal requests, that is a deliberate institutional decision — not an oversight.

---

The doctrine

Negligent retention is captured in CACI 426 and Noble v. Sears, Roebuck & Co. (1973) 33 Cal.App.3d 654. Noble held:

"Where a corporation undertakes an activity involving possible danger to the public under a license or franchise granted by public authorities, these liabilities may not be evaded by delegating performance to an independent contractor." (Id. at pp. 660-661.)

The elements: the defendant hired or retained the worker; the worker became unfit; the defendant knew or should have known of the unfitness; the unfitness harmed the plaintiff; and the defendant's failure to remove the worker was a substantial factor in causing the harm.

---

Why the theory has special force in the TNC context

The TNCs collect, in real time, every piece of data they would need to identify dangerous drivers:

• Every rider report, rating, and complaint is logged in real time.
• GPS location, speed, and acceleration are tracked multiple times per minute. Hard-braking and harsh-acceleration events are flagged automatically.
• Cambridge Mobile Telematics scoring is contracted with at least one major TNC and produces a Driving Insights score history for every driver.
• Motor vehicle records, accident histories, and prior platform deactivations are visible to the TNC.
• Warnings are routinely sent to drivers — the TNC knows when it warned the driver and what the warning said.
• Unilateral deactivation authority sits with the TNC at all times.

When a TNC retains a driver despite documented complaints, low ratings, prior accidents, and explicit rider removal requests, that is a deliberate institutional decision. The defense will frame it as a "bug" in the system. The record will show it is a feature.

---

Hooker reinforces the affirmative-contribution path

The theory draws additional support from Hooker v. Department of Transportation (2002) 27 Cal.4th 198, which held that where a hirer's conduct "affirmatively contributed" to injury, liability is "direct in a much stronger sense" and is not derivative of the contractor's negligence.

The TNC's affirmative decision to continue matching a driver with a documented dangerous record is precisely the type of affirmative contribution that creates direct hirer liability under Hooker. Defense counsel cannot brush this off as a hiring-stage negligence claim subject to Privette.

---

Privette/Camargo does not bar passenger-injury claims

The defense sometimes argues that Privette v. Superior Court (1993) 5 Cal.4th 689 and Camargo v. Tjaarda Dairy (2001) 25 Cal.4th 1235 bar negligent retention claims. They do not.

Privette and Camargo address claims by a contractor's own employees against the hirer. A passenger injured by a TNC driver is not the contractor's employee. She is a member of the public, and a member of the public is precisely the type of third party Restatement (Second) of Torts § 411 was designed to protect.

The same logic applies in third-party non-passenger cases. The injured pedestrian, cyclist, or motorist is not the driver's coworker. Privette does not reach the claim.

---

How to build the unfitness record

To win on negligent retention, develop the record on the driver's pre-incident history. Map directly to the discovery roadmap:

• Category (2) — Driver file and onboarding. Complete platform history.
• Category (3) — Background checks. Checkr screening, motor vehicle records, criminal history, continuous monitoring, DMV Pull Notice enrollment.
• Category (7) — GPS, telematics, and sensors. Raw GPS data, accelerometer, gyroscope, hard-braking and harsh-acceleration events.
• Category (9) — Cambridge Mobile Telematics. CMT contracts, Driving Insights methodology, score history, Advantage Mode.
• Category (11) — Rating system. Star methodology, two-way rating, minimum thresholds, complete driver history.
• Category (13) — Complaints, tags, and feedback. All rider reports by category, removal requests, customer support records. The single most important category for negligent retention.
• Category (14) — Prior accidents and RideCheck activations. All motor vehicle incidents, near misses, internal review outcomes.
• Category (15) — Deactivation and account review. Suspensions, safety reviews, flagging thresholds, automated triggers. Establishes that the TNC had the authority and the data to remove the driver and chose not to.

The defense will try to keep this record narrow. Resist with motions to compel that tie each category to the negligent retention elements.

---

The institutional-decision framing

Negligent retention works best in front of a jury when framed as an institutional decision, not a paperwork failure. The TNCs have:

• The data (complaints, ratings, telematics).
• The authority (unilateral deactivation).
• The incentive (commission on each fare).
• The promise (Community Guidelines, public marketing).

When they fail to remove a known-dangerous driver, the jury can see the decision tree. The TNC chose the fare over the safety call. That framing converts a doctrinal theory into a story.

---

Practitioner playbook

1. Plead negligent retention as a stand-alone count under CACI 426 and Noble v. Sears.
2. Build the unfitness record from Day One discovery. Categories (2), (3), (7), (9), (11), (13), (14), (15) are non-negotiable.
3. Frame the TNC's conduct as affirmative contribution under Hooker. Defeats the Privette argument structurally.
4. Defeat the Privette/Camargo defense by pointing out that the plaintiff is not the contractor's employee.
5. Tell the institutional-decision story. Data + authority + incentive + promise = liability. The jury can see it.
6. Pair with direct negligence and negligent undertaking. All three direct-liability theories survive Prop 22 in full.

---

See also

• Hub: The Seven-Theory Framework
• Direct Negligence Against Uber/Lyft (§ 1714; Kuciemba)
• Negligent Undertaking and the TNC's Safety Promises (CACI 450)
• TNC Discovery Roadmap — 24 Categories
• Proposition 22 Is a Labor Statute, Not a Tort Immunity

---