Federal Circuit Limits Prosecution Laches in Google v. Sonos

Prosecution laches is one of those legal doctrines that sounds like a sleepy Latin spelland, honestly, it kind of is.
When it shows up in a patent case, it’s basically the court saying: “You don’t get to hit the snooze button for years,
then wake up and surprise everyone with new claims.”

That’s why Google LLC v. Sonos, Inc. turned heads. A district court tossed out Sonos’s jury win by declaring two
patents unenforceable for prosecution lachesdespite the patents being from the modern, post-1995 patent-term world
(where delaying prosecution usually doesn’t extend a patent’s life). Then the Federal Circuit stepped in and, in a very
polite appellate way, told the district court: “Slow down. If you’re going to use laches, you need proof of prejudicenot vibes.”

This article breaks down what happened, what the Federal Circuit actually limited, and what patent owners,
prosecutors, and product teams should do nowbesides stress-eating pretzels during claim review meetings.

What Is Prosecution Laches (and Why Does It Exist)?

Prosecution laches is an equitable defense that can make an issued patent unenforceable
when the patent issued only after an unreasonable, unexplained delay in prosecution that amounts to an
“egregious misuse” of the patent system. It’s rare, and it’s supposed to be reserved for extreme situationsthink
“submarine patent” scenarios where the public builds an industry while an applicant keeps an application alive and
then surfaces later with claims aimed right at successful products.

Modern courts typically describe prosecution laches as having two main ingredients:
(1) unreasonable and inexcusable delay under the totality of circumstances, and
(2) prejudice attributable to that delay. The prejudice piece is often framed as “intervening rights”
evidence that the accused infringer (or others) invested in, worked on, or used the claimed technology during the period of delay.

In other words, prosecution laches isn’t supposed to punish normal patent strategy. It’s supposed to stop a kind of
procedural time-travel: holding back claims until the market commits, then popping up to demand a toll.

The Google v. Sonos Backstory: “Zone Scenes,” Continuations, and a Jury Verdict

The patents at the center of the prosecution-laches fight were Sonos’s “Zone Scene” patentsU.S. Patent
10,469,966 and 10,848,885. These patents relate to organizing speakers (zone players)
into predefined groups (“zone scenes”) so users can quickly set up multi-room audiolike “Morning” music in the kitchen
and “Evening” music on the patio, with some rooms potentially overlapping between scenes.

Here’s the timeline that mattered:

• September 2006: Sonos filed a provisional application.
• September 2007: Sonos filed a nonprovisional application and requested nonpublication.
• July 2013: The application became public when it issued as a patent (meaning the specification was out in the world).
• April 2019: Sonos filed the applications that later became the asserted Zone Scene patents.
• 2020: Litigation between Google and Sonos ignited in federal court.
• 2023: A jury awarded Sonos about $32.5 million on infringement findings tied to the Zone Scene patents.

After trial, though, the district court did what trial courts sometimes do when they’ve had a long week:
it reached for a big red “UNDO” button. It held the Zone Scene patents unenforceable for prosecution laches,
reasoning that Sonos waited about 13 years from the early priority filing to pursue the overlapping-zone-scene claims,
and that Google had invested in products during that period.

If you’re a patent prosecutor, you probably felt a chill. The decision looked like it might turn standard continuation practice
into a legal liabilityespecially in high-tech where product cycles move fast and claim strategy evolves as competitors’ designs evolve.

The District Court’s Theory: Delay + Investment = Laches

The district court treated the long delay in presenting certain claim scope as enough to raise prosecution laches concerns.
It also believed Google was prejudiced because Google supposedly invested in products using the accused functionality
before Sonos pursued the later claims.

This framing mattered because many patent families are built exactly this way:
a foundational disclosure is filed early; applications continue; claims are refined over time as technology and markets become clearer.
The difference between “legitimate refinement” and “equitable abuse” is supposed to be where courts apply laches with a scalpel
not with a lawnmower.

The Federal Circuit’s Limit: No Prejudice, No Prosecution Laches

On August 28, 2025, the Federal Circuit reversed the prosecution-laches holding (the decision was labeled nonprecedential),
focusing hard on one element: prejudice.

The court did not need to decide every controversy about delay, continuations, or modern patent terms because it found
Google’s showing of prejudice legally insufficient. In plain English: you can’t win prosecution laches by pointing at a calendar and saying,
“Trust me, we invested.”

1) Prejudice must be proven with evidence, not asserted in briefing

The Federal Circuit emphasized that the accused infringer bears the burden to show prejudice attributable to the delay.
Google argued it began investing in relevant products “by at least 2015,” but the court faulted Google for not supporting that assertion
with evidence (like testimony or documentation) in the record. That matters because prosecution laches is not a casual doctrinecourts treat it as an
equitable sledgehammer, so the proof needs to be real, not rhetorical.

Practical takeaway: if you want prosecution laches, you need a well-built recordproduct development timelines,
decision memos, engineering testimony, financial commitments, and the “we did X because we believed Y was safe” story.
Without that, laches becomes a bedtime story with no receipts.

2) Publication matters: you can’t be “surprised” by what was already disclosed

The Federal Circuit also highlighted a second, independent reason prejudice failed: the relevant specification became public in
2013 when a related patent issued. And the court concluded that the published disclosure adequately described the overlapping zone scene concept.

That undermines a key laches narrative: that Sonos delayed in claiming and kept the public in the dark.
The Federal Circuit’s reasoning is essentially: once the core idea is publicly disclosed in a published patent document,
a competitor who later builds products using that disclosed feature has a much harder time proving it was prejudiced by
the patentee’s later claim pursuitbecause the competitor was on notice that the patentee had described the feature.

This doesn’t mean publication eliminates prosecution laches forever. It means that, in a case like this, where the court found the
overlapping concept was already disclosed before Google’s claimed investments, the prejudice story collapses. You can’t say you were blindsided by
something you could have read years earlierespecially in an industry where freedom-to-operate analysis is supposed to be a thing people do
before the product launch party.

3) What the Federal Circuit didn’t fully resolve

By “limiting the discussion” to prejudice, the Federal Circuit avoided making a sweeping statement like
“prosecution laches is basically dead for post-1995 patents.” So the doctrine remains alivebut the decision makes clear
that courts should not apply it casually, and defendants must show concrete prejudice tied to the delay.

Translation: prosecution laches is still on the menu, but it’s now priced like a tasting menu you only order on special occasionswhen you have the
evidence to justify it.

Related Issues the Decision Tackled: Written Description and Obviousness

Google v. Sonos wasn’t a one-issue appeal. Alongside prosecution laches, the Federal Circuit addressed two other major rulings that shaped the case.

Written description: the “overlapping zone scenes” were adequately disclosed

The district court had also found Sonos’s Zone Scene patents invalid for lack of written description (tied to a “new matter” theory and priority date issues).
The Federal Circuit reversed that as well, pointing to specification language describing different scenes (“Morning,” “Evening”) and groupings thatread together
supported the idea of overlap (where the same room/speaker can belong to more than one predefined scene).

Why it matters: written description problems are often where continuation strategies go to die. If you broaden claims later,
you must be able to point back to the original disclosure and say, “See? We had this.” The Federal Circuit concluded that, on the record presented,
Google failed to establish a genuine dispute of material fact that Sonos lacked that disclosure support.

Direct Control patent: obviousness affirmed

The appeal also involved Sonos’s “Direct Control” patent (U.S. Patent 10,779,033). The district court had granted summary judgment
that certain asserted claims were obvious based on a version of Google’s YouTube Remote (YTR2) in view of a related Google patent
(U.S. Patent 9,490,998). The Federal Circuit affirmed that obviousness ruling, rejecting Sonos’s arguments that genuine factual disputes
precluded summary judgment on key limitations like a “remote playback queue” and aspects of the “device picker” concept.

That split outcome is important: the decision was very good news for Sonos on laches and written description, but it still left Sonos with a loss on the
Direct Control patent. In appellate terms, it was a “you get your fries back, but the milkshake is still spilled” kind of day.

What This Means for Patent Owners and Prosecution Strategy

If you manage patent portfolios, the headline “Federal Circuit limits prosecution laches” should feel like a pressure valve releasing.
But it’s not a free pass to treat continuation practice like an endless buffet.

Continuations aren’t automatically laches baitbut your record should make sense

The decision supports a practical principle: normal continuation practice, especially where the invention is already disclosed in a published specification,
should not be condemned absent real, proven prejudice. Still, long gaps between an early priority filing and later-asserted claims can invite scrutiny,
especially if claim strategy looks like it was designed to ambush a mature market.

Disclose broadly early (and keep your “claims roadmap” updated)

The best continuation strategy has two layers:
(1) robust disclosure that supports future claim evolution, and
(2) a documented strategy for how claim sets relate to product features and competitive landscapes.

If someone later points at your timeline and screams “submarine!,” your best defense is a file history that looks like deliberate prosecution management,
not a spy thriller.

Nonpublication is lawfuljust remember what it changes

Nonpublication requests can be perfectly appropriate. But they alter how “surprise” arguments play out later.
One reason Google struggled on prejudice here was that the disclosure became public in 2013, undercutting a claim of being caught unaware during later product investment.
Different factslike a longer period where competitors truly had no public noticecan change the analysis.

What This Means for Product Teams, FTO, and Patent Defendants

If you build products in crowded tech spaces, Google v. Sonos reinforces a truth people love to ignore until litigation arrives:
freedom-to-operate isn’t just about current claimsit’s about published disclosures and what those disclosures might support later.

Read specifications, not just claims

The Federal Circuit’s prejudice analysis highlights why “we checked the claims and we were fine” is sometimes a flimsy comfort blanket.
If a published specification describes a feature your team wants, there is at least some risk that future continuation claims could target itassuming the family stays alive.

This doesn’t mean you can’t innovate. It means your risk review should include:

• whether the patent family is still active (continuations possible),
• whether the disclosure supports broader claim scope than currently issued claims, and
• whether design alternatives exist before you cement the architecture.

If you want prosecution laches, build the prejudice case like it’s a product launch

The Federal Circuit didn’t say “never.” It said “prove it.”
A viable prosecution-laches defense needs evidence showing that the delay caused real-world harm tied to reliance or intervening rights.
Examples that can matter (depending on facts) include:

• documented investments and commitments made during the delay period,
• testimony explaining why the company believed the tech was unclaimed and safe,
• evidence that key evidence became unavailable because of the delay (evidentiary prejudice), and
• a clear causal link between delay and harm (not just “we launched stuff”).

Prosecution laches is not a shortcut. It’s more like a boss fight: you need preparation, a strategy, and a lot of screenshots. (Not the fun kind.)

Practical Checklist: How to Act on Google v. Sonos

For patent owners

• Keep disclosures strong enough to support foreseeable claim evolution.
• Use continuations intentionally; avoid patterns that look like claim ambush.
• Document prosecution strategy so “delay” has a reasonable explanation.
• When adding claims later, be able to point to earlier disclosure clearly.

For product teams and defendants

• In FTO reviews, analyze published specifications and continuation risk.
• Track patent-family status and continuation activity in your risk dashboards.
• If raising prosecution laches, build an evidence-backed prejudice timeline.
• Don’t assume “no claim today” means “no claim tomorrow.”

Conclusion

The Federal Circuit’s decision in Google v. Sonos puts meaningful guardrails around prosecution lachesespecially when the argument is built on
standard continuation behavior plus a thin claim of “we invested.” The core message is straightforward:
no proven prejudice attributable to delay, no prosecution laches.

Patent owners can breathe a little easier that continuation practice isn’t automatically a legal trapdoor. Defendants, meanwhile, get a roadmap for what
will (and won’t) work: if you want laches, bring evidence, establish causation, and show the court the real-world harm the delay created.

And for everyone building products in fast-moving tech markets: treat published specifications as meaningful notice. Because sometimes the biggest surprise
in patent law isn’t the claimit’s that somebody actually read the spec.

Not legal advice; just a practical analysis of a very awake appellate court.

Bonus: Real-World Experiences Around “Prosecution Laches Panic” (Approx. )

Even if you’ve never litigated a case, you can spot the “prosecution laches moment” from a mile away because it triggers a very specific corporate ritual:
the emergency meeting where everyone suddenly becomes intensely interested in dates.

It usually starts innocently. Someone in-house forwards an alert with a subject line like “Federal Circuit / prosecution laches / please read.” Then the calendar
archaeology begins. Patent counsel is pulling file histories. Product counsel is pulling launch timelines. Engineers are pulling old Jira tickets like they’re
unearthing ancient tablets. Somebody asks, “When did we first implement this feature?” and the room goes quiet because the honest answer is,
“Depending on what you mean by ‘implement,’ it’s complicated.”

The emotional whiplash is real because continuation practice is normal. Many teams have lived the same pattern:
you file a strong foundational application early, then keep a continuation alive because the product roadmap keeps moving. You don’t always know in 2006 which
2019 feature will become commercially critical. That’s not bad faithit’s how innovation works. But when prosecution laches enters the chat, the narrative can be
reframed as if continuing an application is secretly the patent equivalent of hiding under the bed with a stopwatch.

This is where Google v. Sonos hits home for a lot of teams. The case highlights the difference between the story you tell yourself internally
(“we prosecuted responsibly and claimed what our disclosure supports”) and the story an opponent tries to tell a judge
(“they waited forever and then targeted a successful product”). The practical experience is that you can’t rely on being “reasonable” in your own mind
you need the paper trail that shows the reasonableness.

For prosecution teams, that often means building a living “claims roadmap”a simple internal document that ties major claim concepts to disclosure support
and explains why certain claim sets were pursued when they were. It doesn’t have to read like a novel. It just has to make the timeline look like strategy
rather than suspense. When the portfolio later becomes a litigation exhibit, that clarity can be the difference between “standard continuation practice” and
“why did you wait thirteen years?”

For product teams, the experience is usually the opposite lesson: you learn that “we didn’t see a claim” isn’t the same as “we were safe.”
Mature organizations start tracking not only issued claims but also patent-family vitalitybecause a published specification can be the seedbed for future
claims. That changes how feature launches are evaluated. It can also change how teams document decisions. If you ever need to prove prejudice for laches,
you’ll want contemporaneous records showing what you knew, what you relied on, and why delay matterednot a reconstructed story built from faded emails
and heroic guessing.

In short, the “experience” of prosecution laches in the real world is less about courtroom drama and more about operational discipline.
Google v. Sonos doesn’t eliminate the doctrine, but it nudges everyone toward better habits: patent owners should prosecute with a timeline they can explain,
and product teams should treat published disclosures as real notice. The best outcome is when nobody has to learn that lesson at 2:00 a.m. the night before
a deposition.