Fail-Safe Class Definitions and Ascertainability in TCPA Cases
Many TCPA complaints define the class as everyone who got a call or text without prior express consent. That’s a fail-safe definition: a person is in the class only if the defendant is liable to them. The Ninth Circuit has said courts may not certify a class built that way. Pointing it out rarely ends a case on its own, because Rule 23 lets a court change the class definition before judgment. But the redrafted definition usually exposes the real problem, which is that consent has to be proved person by person.
What is a fail-safe class?
It’s a class whose membership depends on winning. In Olean Wholesale Grocery Cooperative, Inc. v. Bumble Bee Foods LLC (9th Cir. 2022) 31 F.4th 651, the en banc court said a court may not create a fail-safe class, one “that is defined to include only those individuals who were injured by the allegedly unlawful conduct.”
The problem is easy to see in a TCPA case. If the class is people called without consent, and the business proves a person did consent, that person was never in the class and isn’t bound by the judgment. Class members can win but can’t lose, which defeats the point of a class judgment. A definition like that also hides the hardest question in the case inside the word “without.”
What do fail-safe TCPA definitions look like?
They usually borrow the statute’s elements. Common examples are people who received autodialed calls without prior express consent, and people who got texts after they revoked consent. Do Not Call classes limited to people with no established business relationship with the defendant have the same flaw, since a court can’t tell who belongs in any of these classes without first deciding whether the defendant is liable to them.
A properly drawn definition uses objective facts the parties can check from records: the numbers dialed, the platform used, the campaign or date range, and whether a number appeared on the Registry. Plaintiffs know this, so a well-drafted complaint often uses objective criteria from the start. The fail-safe argument is strongest against complaints that copied the statute into the class definition.
| Definition problem | Example | Defense argument | Likely court response |
|---|---|---|---|
| Fail-safe | Everyone called without prior express consent | Membership depends on liability | May let the plaintiff redefine the class |
| Overbroad | Every number the platform texted in four years | Includes many people who consented or weren’t harmed | May narrow the class or deny certification |
| Hard to identify | Every person who used a number, not the subscriber | Records don’t show who received each text | Addressed through manageability, not a separate test |
| Objective but individualized | Every number with no consent record on file | Consent comes from many sources, not one database | Predominance fight under Rule 23(b)(3) |
What goes wrong with Do Not Call class definitions?
They often leave out what the statute requires. A private Do Not Call claim isn’t available to everyone on the Registry who got one call. Under 47 U.S.C. § 227(c)(5), the right to sue belongs to a person who “has received more than one telephone call within any 12-month period by or on behalf of the same entity” in violation of the FCC’s rules. A class of every Registry number the company called once or more doesn’t track that element, and it’s worth pointing out at the pleading stage.
The fix plaintiffs usually reach for is a definition built on call counts and Registry dates, and that’s harder to draft than it looks. The class period, the Registry listing date for each number, the 31-day scrub window, and any customer relationship or written agreement all shape who can actually recover. When a definition ignores those facts, the class ends up full of people the statute doesn’t protect, and when it includes them, the plaintiff has usually written a fail-safe class by another name. Either way, a defendant that understands its own calling records can show the court where the definition breaks down, and the post on prior express invitation or permission covers one of the defenses that splits these classes apart.
What happens when a court finds a fail-safe definition?
Usually a rewrite, not a dismissal. Rule 23 lets the court adjust the class as the case goes on. Under Rule 23(c)(1)(C), “An order that grants or denies class certification may be altered or amended before final judgment.” That gives a court room to treat a fail-safe definition as a drafting problem and let the plaintiff fix it, rather than deny certification outright.
That doesn’t make the argument a waste of time. When the plaintiff has to drop the consent language and define the class by objective facts, the new definition often sweeps in customers who did consent. That sets up the overbreadth argument. The Olean opinion said a court must consider “whether the possible presence of uninjured class members means that the class definition is fatally overbroad,” and the post on uninjured class members after TransUnion covers the standing side of the same problem. Raising the defect early, through a motion to strike class allegations, is discussed in the post on motions to strike TCPA class allegations.
Does the Ninth Circuit require an administratively feasible way to find class members?
No. In Briseno v. ConAgra Foods, Inc. (9th Cir. 2017) 844 F.3d 1121, the court held that “the language of Rule 23 does not impose a freestanding administrative feasibility prerequisite to class certification.” Some other circuits have taken a stricter approach, but a business defending a TCPA case in California federal court shouldn’t build its opposition around a separate ascertainability test.
The same concerns still matter under Rule 23’s other requirements. The Briseno court pointed out that Rule 23(b)(3) requires a court to consider “the likely difficulties in managing a class action.” In a TCPA case, that’s where problems like identifying who actually used a reassigned or shared number, or matching phone numbers to people, belong. A defendant should frame those issues as manageability and predominance problems, backed by evidence about its own records.
How should a defendant use these arguments?
As part of the consent defense, not instead of it. The definition fight works best when the business can show, with its own records, that consent came from several sources: web forms, point-of-sale sign-ups, keyword texts, and calls to customer service. That variety is what makes a class built on objective criteria overbroad, and it’s what makes consent an individual question. The post on consent defenses at class certification explains how that evidence is presented.
The timing matters too. Records that show where each number came from are often held by vendors and platforms, and they’re harder to get the longer a case runs. For businesses facing a putative class, California TCPA defense usually starts with mapping each consent source to the numbers in the plaintiff’s proposed class.
Records that shape the class definition fight
- Preserve call and text logs, dialer and platform data, and every consent record, under a litigation hold, organized by source so each sign-up method can be shown separately.
- Pull opt-out and internal do-not-call logs with dates, since revocation classes depend on them.
- Pull the National Do Not Call Registry scrub records and the Registry version dates used for each campaign.
- Collect vendor and lead-source contracts and call scripts, plus any prerecorded or AI-voice files, which show how numbers entered the system.
- Talk to a lawyer before answering the complaint or discussing settlement, since the first response is the natural place to raise the class definition.
Questions about TCPA class definitions
Will a court dismiss a TCPA class action because the class is fail-safe?
Rarely by itself. Rule 23 lets the court change a class definition before final judgment, so a fail-safe definition is usually something the plaintiff gets a chance to fix. The argument still has value, because the redrawn class often includes people who consented, and that makes the overbreadth and predominance arguments stronger.
Is a class of numbers with no consent record on file fail-safe?
Probably not, because it uses an objective fact: whether a record exists in the defendant’s system. But it can be overbroad if customers consented in ways that never made it into that system, such as at a store counter or on a call. Evidence of those other consent channels is what turns an objective definition into an individualized question.
Does Briseno mean ascertainability doesn’t matter?
It means there’s no separate administrative feasibility requirement in the Ninth Circuit. The underlying concerns move to Rule 23’s listed requirements, most often manageability and predominance. A defendant should still show the court, with evidence, why identifying class members and their consent would require individual inquiries.
Can a defendant raise the class definition before the certification motion?
Yes. A motion to strike class allegations, or a motion to dismiss them, can challenge a definition that’s fail-safe on its face. Courts are often reluctant to decide class issues that early, so the argument works best when the defect is clear from the complaint itself and doesn’t depend on discovery.
When a complaint defines the class by the statute
If your company has been named in a TCPA class action whose class definition borrows the statute’s elements, the consent records and how they were collected usually decide what kind of class, if any, a court will allow. Rosenberger + Kawabata represents businesses defending TCPA lawsuits and class actions through its business litigation practice, including claims involving putative classes of text and call recipients. Contact Rosenberger + Kawabata online for a confidential consultation, or call (310) 894-6921.
Sources
The class action rule is Federal Rule of Civil Procedure 23.
The court decisions are Olean Wholesale Grocery Cooperative, Inc. v. Bumble Bee Foods LLC (9th Cir. 2022) 31 F.4th 651 and Briseno v. ConAgra Foods, Inc. (9th Cir. 2017) 844 F.3d 1121.
This post is general information about the Telephone Consumer Protection Act and related laws as of April 12, 2026. It is not legal advice, and reading it does not create an attorney-client relationship. Courts and the FCC change the rules in this area often, and the outcome of any claim depends on its facts. Past results do not guarantee future outcomes.