For years, immunity defenses were usually treated as limited protections. A company could avoid liability in certain situations, but courts were often hesitant to apply immunity too broadly, especially when the company itself was accused of wrongdoing.
A recent Florida decision involving Lyft may signal a shift in how courts approach these cases.
In Haddad v. Lyft Florida, Inc., a woman claimed she was assaulted by her Lyft driver during a ride. She sued Lyft directly, alleging the company made misleading safety representations on its website about background checks, driver monitoring, and rider protections. According to the lawsuit, those statements influenced her decision to use the platform.
What makes the case important is not simply that Lyft won. It is the reasoning the court used to get there. The plaintiff was not only arguing Lyft should be responsible for the driver’s conduct, she also claimed Lyft itself acted improperly by making allegedly misleading statements about safety. Normally, that distinction matters. Courts are often more willing to let cases proceed when a plaintiff alleges direct negligence rather than traditional vicarious liability.
The Fourth District Court of Appeal disagreed.
The court focused heavily on the language of Florida’s rideshare statute, section 627.748(18). Even though the section is titled “Vicarious Liability,” the court explained that the actual wording of the statute controls.
The court interpreted the statute very broadly. According to the opinion, the immunity applies to claims arising from a rideshare company operating its digital platform or being connected to the driver while the driver is logged into the app. That interpretation matters because it means plaintiffs may not be able to avoid immunity simply by changing how the claim is framed. Calling something negligent misrepresentation instead of vicarious liability may not make a difference if the court believes the injury still arose from the rideshare relationship itself.
The court emphasized that this statute does not operate like a normal affirmative defense. In many cases, defenses are sorted out later in litigation after discovery has taken place. Here, the court focused on the statute’s wording that says, “There is no liability.” According to the court, that language creates a default rule of nonliability unless the plaintiff can clearly show one of the statutory exceptions applies.
That changes the timeline of the case significantly, especially from a subrogation standpoint.
In the past, immunity defenses were often treated as issues that would be worked out later in litigation after discovery had already begun. But decisions like Haddad suggest some defendants may now be able to raise immunity immediately at the motion-to-dismiss stage.
From a subrogation perspective, that matters because it changes how claims should be evaluated from the very beginning. Traditionally, a strong liability case might justify early investment into investigation, experts, preservation efforts, or litigation strategy. But if a defendant operates inside a statutory framework that provides broad immunity, the real question may not be whether negligence occurred at all. The question may instead become whether the claim can legally survive long enough to reach discovery. That creates a major shift in how recoverability is evaluated.
Subrogation teams may now need to analyze immunity issues much earlier in the life of the claim, particularly in cases involving rideshare companies, delivery platforms, app-based services, or other technology-driven industries governed by specific statutes.
A claim that appears viable from a negligence standpoint may still face significant recovery obstacles if the defendant can successfully argue the legislature intended broad immunity protections for that industry.
The Haddad decision also highlights a larger trend involving platform-based businesses and statutory liability protections. Companies like Lyft, Uber, and DoorDash do not operate under traditional business models. They operate inside legal frameworks specifically created for their industries, and courts may increasingly enforce those statutes exactly as written.
The Fourth DCA repeatedly emphasized that courts are supposed to apply the language of the statute, not rewrite it based on fairness concerns or policy arguments. That approach could have significant consequences for future subrogation efforts.
As more industries rely on apps, digital platforms, and legislatively created business models, immunity issues will likely become more common in recovery litigation. Subrogation professionals may increasingly encounter situations where liability exists factually, but recovery is limited or eliminated because the statute itself creates a barrier to suit.
That distinction is important.
Historically, immunity often functioned as a narrow defense argument raised later in litigation. Decisions like Haddad suggest immunity may now operate more like a threshold issue capable of stopping a claim before the case meaningfully develops.
For subrogation professionals, that means statutory analysis may become just as important as liability analysis when evaluating recovery potential.
About the author
Anne Kardas is managing partner at Billeci Kardas Law, PLLC. anne@billecikardas.com