Administrative Feasibility in TCPA Class Certification

Whether a TCPA plaintiff has to show an administratively feasible way to identify class members before a class gets certified depends on where the case is filed. The federal courts of appeals split on it. In a wrong-number or reverse-append case, that one question often decides whether thousands of claims move forward together or break apart into individual suits nobody will bother to file. A company named in a TCPA class action usually has more ways to attack the class list than the complaint lets on.

What does “administratively feasible” mean in a class action?

It means a court can tell who belongs in the class without running a separate investigation for each person. Federal Rule of Civil Procedure 23 doesn’t use the phrase, but some courts read the idea into it as part of ascertainability, the requirement that a class be defined so its members can actually be identified.

The Third Circuit set the standard in Carrera v. Bayer Corp., 727 F.3d 300 (3d Cir. 2013). The court wrote that “the method of determining whether someone is in the class must be” administratively feasible, and that a plaintiff “does not satisfy the ascertainability requirement if individualized fact-finding or mini-trials will be required to prove class membership.” Carrera also requires the plaintiff to show the identification method is “reliable and administratively feasible” and to let the defendant test the proof of who is in and who is out.

That cuts straight to how most TCPA classes get built. The plaintiff rarely has a clean list of the people who were called. The list comes from running the defendant’s call records through outside databases, a process the industry calls a reverse append: you take a phone number and look up who the number belonged to on the date of the call. If that method can’t sort real class members from everyone else without a person-by-person inquiry, a feasibility court won’t certify.

Which circuits require administrative feasibility, and which don’t?

They disagree, and the disagreement is the whole ballgame on this issue.

The Third Circuit requires it. In Carrera, where the only question on appeal was “whether the class members are ascertainable,” the court refused to certify a class of diet-supplement buyers who had no receipts and could be identified only by their own say-so.

The Ninth Circuit went the other way. In Briseno v. ConAgra Foods, Inc., 844 F.3d 1121 (9th Cir. 2017), the court held that a “separate administrative feasibility prerequisite to class certification is not compatible with the language of Rule 23.” Its reasoning was textual: Rule 23 lists what a class has to show, and a freestanding feasibility test isn’t on the list. The court also pointed to Rule 23(b)(3), which already tells a court to weigh “the likely difficulties in managing a class action,” and said a separate feasibility requirement “would render that manageability criterion largely superfluous.” The bottom line, in the court’s words: “the language of Rule 23 does not impose a freestanding administrative feasibility prerequisite to class certification.” The Sixth and Seventh Circuits had already reached the same place, and so had the Eighth.

California sits in the Ninth Circuit, so a TCPA defendant sued here can’t demand a standalone feasibility showing the way a defendant in Philadelphia can. That sounds like bad news for the defense. It mostly isn’t, for a reason the next section gets to.

Circuit (key case) Separate administrative-feasibility requirement? What it means for a TCPA defendant
Third Circuit (Carrera v. Bayer) Yes, as part of ascertainability The reverse-append method and any affidavit-based list can be attacked head-on at certification
First Circuit (Sandoe; In re Asacol) Folded into Rule 23, so challenged self-identification won’t carry a class The identification problem runs through both ascertainability and predominance
Ninth, Seventh, Sixth, Eighth Circuits (Briseno v. ConAgra) No standalone test The same problem still bites, but through predominance and superiority under Rule 23(b)(3)

How does the split change a TCPA wrong-number class?

Less than the labels suggest. In Sandoe v. Boston Scientific Corp., 333 F.R.D. 4 (D. Mass. 2019), a plaintiff sought to certify a class of people who got prerecorded calls meant for someone else, and his expert used a reverse append to build the class list. The court denied certification.

On identification, the court asked “whether the identification of potential class members is” administratively feasible, a consideration it treated as implicit in Rule 23, and it found the plaintiff hadn’t met that bar. The defense expert showed that the reverse-append method “does not even identify plaintiff as a class member” without an individual look at his own phone records. The court held the plaintiff “failed to demonstrate that the members of the proposed classes are ascertainable and that common issues predominate under Rule 23(b)(3).”

Across the split, one detail carries the most weight. The court didn’t actually rest on feasibility. It wrote that it “need not definitively resolve that issue” and denied certification on predominance instead. Why? Because consent is a defense to a TCPA call, and the defendant “has a unique potential consent defense against every proposed class member.” Sorting the wrong numbers from the intended recipients, and then testing consent for each one, would swamp any common question. That is a Rule 23(b)(3) problem, and it exists in every circuit, feasibility or not.

So the smart defense of a reverse-append class doesn’t ride on whether your circuit uses the feasibility label. It rides on predominance. In a feasibility circuit you get both arguments. In the Ninth Circuit you get one, and it’s the stronger one anyway. Betting the whole defense on a label that four circuits have thrown out is a mistake.

Can plaintiffs fix the problem with class-member affidavits?

They try, and it’s the pressure point. When the data can’t cleanly identify who was called, plaintiffs propose letting putative members swear they belong in the class. Courts that take identification seriously don’t accept that when the defendant has a real defense to test.

Carrera rejected affidavits as a way around an unreliable method. Sandoe did too. The plaintiff there offered a self-attestation process in which each member would swear he used the number and registered it on the Do Not Call Registry. The court held that where testimony is “genuinely challenged and relevant to an element of a party’s affirmative case,” a class can’t be certified without giving the defendant a chance to litigate its defenses, and that a trial of thousands of cross-examined affiants “has been expressly rejected in this Circuit as a means for identifying class members.”

For a business, consent is what turns a self-identification scheme into an individualized mess. If your records show even a plausible consent story for the numbers a plaintiff wants in the class, you’ve earned the right to challenge each affidavit, and that right is usually fatal to the class. This is why your consent records and your call data are the defense long before any legal theory is.

What should your company do when it’s named in a TCPA class action?

The class fight is won or lost on records that exist at the moment the complaint lands, so the first moves are about preservation, not argument. At $500 per call, or up to $1,500 if a court finds the violation willful or knowing under 47 U.S.C. § 227(b)(3), a class of even a few thousand calls is worth fighting on the class list.

  1. Put a litigation hold on the dialer and platform logs, the call and text records, and the consent records for every number in the alleged class, before anything rolls off on a retention schedule.
  2. Pull the account and subscriber data that ties each number to a real person and date, since the gap between the number called and the person who answered is where reverse-append classes fall apart.
  3. Gather the Do Not Call scrub records and the version dates used for each campaign.
  4. Collect the vendor and lead-source contracts, the call scripts, and any recorded or prerecorded message files, because the consent story and the identification method both live in these.
  5. Talk to a lawyer before responding to the demand letter, contacting the named plaintiff, or discussing settlement numbers.

One more point on forum. A nationwide TCPA class filed in the Third Circuit carries an extra, standalone hurdle that the same class filed in California doesn’t. Where a defendant has a say in where the case is litigated, that difference is worth real money. The firm’s work defending TCPA class actions in California covers how these certification fights play out in state and federal court here.

Questions businesses ask about TCPA class certification

What is a reverse append in a TCPA case?

It’s the method a plaintiff’s expert uses to turn a list of dialed numbers into a list of people. The expert runs each number through commercial databases to find who it belonged to on the call date. In wrong-number cases the method has to do more: it has to show the person who answered wasn’t the customer who consented. That extra step is where the method tends to break, because a single number can be tied to several names over time.

Does California require administrative feasibility for a TCPA class?

No. The Ninth Circuit held in Briseno that Rule 23 contains no separate administrative-feasibility requirement, and California federal courts follow it. That doesn’t mean a shaky class list survives here. Courts handle the same concern through the predominance and superiority tests under Rule 23(b)(3), which are often harder to beat anyway.

If the plaintiff can’t identify the class, is the case over?

Not the whole case, but often the class part of it. A denial of class certification leaves the named plaintiff with an individual claim, which is usually worth little on its own. Rule 23 also lets a court revisit a certification decision before final judgment, so a denial isn’t always the last word. Still, knocking out the class changes the settlement math the day it happens.

Why does consent matter so much at the class stage?

Because consent is an individual question. If the defendant can point to a real consent record for the numbers a plaintiff names, the court has to decide consent person by person, and that individualized inquiry can overwhelm the common questions a class action depends on. Even in circuits that reject a separate feasibility test, a genuine consent defense is often enough to defeat predominance under Rule 23(b)(3).

If your company is the one named in a TCPA class action

If your company has been sued or received a demand letter over calls or texts, the consent records and call data you preserve now will drive whether a class ever gets certified. Rosenberger + Kawabata represents businesses defending TCPA lawsuits and class actions through its business litigation practice, including claims that turn on how a plaintiff proposes to identify the class. Contact Rosenberger + Kawabata online for a confidential consultation, or call (310) 894-6921.

Sources

The rule is Federal Rule of Civil Procedure 23, and the statute is the Telephone Consumer Protection Act at 47 U.S.C. § 227.

The court decisions are Carrera v. Bayer Corp., 727 F.3d 300 (3d Cir. 2013); Briseno v. ConAgra Foods, Inc., 844 F.3d 1121 (9th Cir. 2017); and Sandoe v. Boston Scientific Corp., 333 F.R.D. 4 (D. Mass. 2019).

This post is general information about the Telephone Consumer Protection Act and related laws as of August 10, 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.

← Back to Blog

Let’s Talk.