Real Property is a Real Problem for Class Actions -Onyx Props. LLC v. Bd. Cty. Comm'ners of Elbert Cty

Property-rights class actions are difficult to bring, because property tends to be unique, and class actions do not work well with unique claims. But that doesn't stop plaintiffs from trying to certify classes asserting property based claims.

This week's case--Onyx Props. LLC v. Bd. Cty. Comm'ners of Elbert Cty., 2013 U.S. Dist. LEXIS 7151 (D. Colo. Jan. 17, 2013).--arises out of one such effort. The specific details are convoluted, but basically amount to the following: two developments in Elbert County, Colorado were, for various reasons, rezoned from an "A-Agriculture" designation to an "A-1" designation. This was apparently important to at least one set of property owners who ran a composting business--acceptable under one designation but not the other. When Elbert County told them to cease composting, they challenged its ruling in state court, and won; the court found that the rezoning was fatally flawed because it was based on the wrong map.

Not content with their victory in state court, the plaintiffs filed a §1983 class action, alleging that the defendant had violated their constitutional rights (and other property owners') by enacting and then enforcing invalid zoning regulations against them.  

The trial court in the District of Colorado denied their request for class certification on a number of grounds, but the most significant was that 

the property rights at issue differ appreciably between the proposed class members and, as such, the analysis as to whether the alleged illegal activities of the [Elbert County] BOCC violated the property owners' substantive due process rights requires individualized inquiry.

As a result, the plaintiffs could not establish commonality.  But the court went further, pointing out that the unique nature of the plaintiffs' property rights also precluded certification of either a damages class under Rule 23(b)(3) or an injunctive-relief class under 23(b)(2).  

Among other problems, any damages class would have trouble showing superiority, since in a property-based case

each class member has an interest in controlling his or her claim given the individualized nature of that claim.

Similarly, the plaintiffs' request for injunctive relief was not appropriate for class treatment because 

the BOCC's reliance on the regulations/map at issue to consider past determinations would require an individualized assessment of the applicability and the appropriate relief, as opposed to future injunctive relief to Elbert County citizens and members of the public

In short, the more the plaintiffs relied on their due process rights to their real property, the harder it was to fit their lawsuit into any classwide relief.  

For defense lawyers, the takeaway here is simple: the unique nature of property rights means that property-based class actions are almost always a bad idea.  The key is showing the court the specific ways in which real property differs in a given area.

Technological Change & Commonality - Hartman v United Bank Card Inc

As marketing guru Seth Godin has put it frequently, we live in an attention economy.  Most of us are busy people, and getting unwanted interruptions can be a huge hassle. That is one reason why class actions against blast-faxers and robo-callers have such appeal; they seem like the ideal way to punish people who won't take the time to individually market to us. But just because these interruptions can be truly annoying does not mean they make good class actions.

Case in point: Hartman v. United Bank Card Inc., 2012 U.S. Dist. LEXIS 144759 (W.D. Wash. Oct. 4, 2012). Ed Hartman owned a drum store and percussion studio known as The Drum Store. He had a business line, and he was dismayed to find several unsolicited voicemails on it from United Bank Card, which was offering low rates and new equipment for accepting credit card payments. So he sued. His lawyers subpoenaed ConnecTel, an automatic dialing service, and got hold of a spreadsheet detailing all of the numbers that UBC had automatically dialed.

They sought certification of a class including:

All Washington residents who received one or more commercial solicitations from UBC directly or through its agents, including but not limited to IPS, through the use of an automatic dialing and announcing device.

UBC opposed the class on both commonality and typicality grounds. Its primary argument was that there was no way of telling from the list of phone numbers who might actually have received a call.

Although the ConnecTel spreadsheet purportedly identifies each call made, ConnecTel's records do not show whether a message was left, or (if a message was left) which message was used. If ConnecTel's platform detected that a live person was answering the call, [*39] then the platform played a message that would simply apologize and terminate the call. Defendants assert that such a message does not meet the statutory definition of "commercial solicitation" and therefore would not violate RCW 80.36.400.

Defendants also assert that, with the advent and rapid spread of technology that renders telephone numbers portable, it is impossible to know based on the ConnecTel spreadsheet alone whether telephone numbers with Washington State prefixes were actually located within Washington State at the time of IPS's calls.

(Emphasis added.)  What did the defendant mean by "technology that renders telephone numbers portable?" As the court explained:

Due to the prevalence of new technology in the telecommunications industry which creates portable telephone numbers, such as call forwarding, VoIP (voice over internet protocol) telephones, Google Voice, Skype, or Magic Jack, IPS cannot know with certainty where the business owners it called were physically located at the time it made the calls.

Plaintiff's counsel responded (as plaintiff's counsel have since the days of yore) by arguing that these were "common defenses for Defendants to prove." The court, however, recognized a large difference between the days of yore and now: namely, the Supreme Court's decision in Dukes.

These defenses are not "common" in that they can be resolved on a class-wide basis "in one stroke." See Dukes, 131 S.Ct. at 2551. Rather, these are defenses that will require individualized hearings with respect to each telephone call. As a result, the court will need to resolve Defendants' liability with respect to each potential class member on an individualized basis.

The court also held that Mr. Hartmann had not demonstrated typicality (it was not clear if the rest of the class had faced actual voicemails), nor had he demonstrated a need for undivided injunctive relief under Rule 23(b)(2), or predominance under Rule 23(b)(3).

The takeaway for defendants in this case? When considering whether an issue is truly common, don't forget about the variations that technological change may impose. We live in a rapidly-changing world, that often means that allegedly "common" courses of conduct are not nearly as common as they first appear.
 

More on Fail-Safe Classes and Structural Flaws- Northside Chiropractic Inc. v. Yellowbook, Inc.

Northside Chiropractic doctor Michael Dubick made the mistake of--after a cold call from salesmen--buying advertising space in Yellowbook. He negotiated for a certain kind of advertisement, but the published ad looked nothing like what he had asked for, and lacked even basic information about his business (like his name). So he sued, and added class allegations to his complaint. Yellowbook also listed his advertisement under "Massages - Non-Therapeutic," a possible crack about chiropractors at best, and solicitation of a whole different kind of client at worst.

So Dr. Dubick filed a class action against Yellowbook, and moved for certification. (Northside Chiropractic Inc. v. Yellowbook, Inc., 2012 U.S. Dist. LEXIS 122827 (N.D. Ill. Aug. 29, 2012).) Dubick's proposed class was a textbook example of a fail-safe class, including all those who:

(a) after being beguiled and misled by Yellowbook sales personnel with false promises and material misrepresentations;

(b) were fraudulently induced to make purchases of Yellowbook print display advertising, with placement of advertising in one or more Yellowbook directories distributed within the State of Illinois;

(c) signed sales agreements or contracts containing terms substantially similar to those signed by the named Plaintiffs;

(d) made complaints or claims concerning Yellowbook's failure to properly publish and provide the requested advertising services that conformed to advertising requirements that were agreed upon by such persons and Yellowbook; and

(e) were denied full refunds, or appropriate compensation for the damages sustained as a result of Yellowbook's failures and misconduct.

(Emphases added.)  Yellowbook quite rightly argued that the class was not ascertainable, and the court agreed (adding a good discussion of the policy justifications for an ascertainability requirement). But it also went on to explain why even an amended class definition would not save the class:

  • The plaintiff did not prove numerosity. Dr. Dubick pointed to evidence that Yellowbook received more than 10,000 complaints. But, as the court pointed out, there were no numbers showing how many complaints related to his specific claims that he had been promised a Early Decision Incentive Award that turned out to be valueless.
  • The plaintiff did not prove commonality. Another set of claims Dr. Dubick advanced involved Return-On-Investment calculations that Yellowbook's sales reps used to persuade potential buyers. Dr. Dubick heard these calculations in his sales pitch, but, as the court pointed out, he could not prove that others heard or relied on them.
  • The plaintiff did not prove typicality. Since the class definition was overbroad, including anyone "misled or beguiled," it would include all kinds of alleged misrepresentations, not just those that Dr. Dubick had heard.
  • The court expressed some misgivings about adequacy of counsel (most notably that they had "plainly misinterpret[ed] Walmart v. Dukes," but held that these "concerns do not rise to the level that would disqualify counsel as inadequate."

What can defense counsel take from this opinion? Lots. But most importantly, it's an excellent reminder of a point I tried to make in the Strafford CLE on ascertainability several weeks ago. If there are flaws in the class definition, they often indicate larger flaws with the class proposal.

 

Class Action Summer Camp - Commonality & Predominance

 Commonality (Rule 23(a)(2)) and predominance (one half of Rule 23(b)(3)) are often considered the heart of the class action certification inquiry. Rightly so, for they both strike at the real question a judge must ask: do the class members have enough in common to justify binding them all together in a single case? Through the 1990s and 2000s, predominance was considered the more important inquiry. In the 2010s, it appears that commonality is gaining ground.

Ten Cases to Bring You Up to Speed:


Further Reading:


Questions:

  • * Why require a common answer? Why not just a common question?
  • * Is there any way to certify a multi-state class action for trial?
  • * What role does predominance play in a post-Dukes world?
  • * How do you reconcile Gates v. Rohm & Haas Co. with Sullivan v. DB Investments, Inc.?

 

Is the New Group Action Bill Cause for Concern?

 Last week, Senator Al Franken (D-Minn) proposed a bill that would partially reverse the Supreme Court's opinion in Wal-Mart Stores, Inc. v. Dukes.

According to Senator Franken's press release, the Equal Opportunity Employment Restoration Act (good title) would add a section 4201 to 28 U.S.C.:

Section 4201(a) creates a new judicial procedure – called “group actions” – that workers can use when bringing employment discrimination cases. The requirements for establishing a group action are the same as the pre-Dukes requirements for maintaining a class action under Rule 23 of the Federal Rules of Civil Procedure—namely, clarifying that the merits of the case need not be proven to certify the group action.

Section 4201(b) provides that group actions can be used regardless of whether the group is challenging an objective employment practice, a subjective employment practice, or a mixed employment practice (such as the use of a written test to qualify for an interview). It also provides that employers’ written anti-discrimination policies can be considered as a defense to certification only insofar as the employer demonstrates that the policy actually has been implemented in practice.

Section 4201(c) says that the group actions authorized by this section are subject to the same procedural requirements as class actions authorized by Rule 23. These include notice and opt-out requirements. This section also preserves the application of the Class Action Fairness Act and the availability of appeals.

Section 4201(d) says that courts can use statistical analyses and any other procedures they deem necessary to provide justice to prevailing plaintiffs.

The bill has a number of cosponsors, but is unlikely to pass a heavily Republican House of Representatives. Nonetheless, it's worth considering what the effects of the bill would be if it were passed as is.

And it's hard to tell what those effects are, because the bill as proposed seems pretty confused about Rule 23 practice. (This is not surprising. It was apparently drafted in conjunction with civil rights leaders rather than Rule 23 experts, so it makes sense that it might not be all things to all people.) The largest sources of confusion:

  • It appears unclear what the law is surrounding "merits inquiries." Class actions, even Title VII class actions, have traditionally allowed inquiries into the merits to the extent they overlap with the rigorous analysis required by Rule 23.  And, in fact, most judicial circuits except the Ninth had already reached the conclusion that the Supreme Court did in Dukes.
  • It claims that Rule 23 requirements will apply, but seeks to remove the latest clarifications to the commonality requirement. It's not clear how this will work out in practice. One of the largest potential problems is that class actions face is that, if there are not truly common issues, class trial gets extremely messy. This was the experience that informed the Dukes opinion on commonality; it seems kind of silly to pull back from it unless the legislators don't intend for there to actually be trials of Title VII actions.
  • It would make labor and employment cases even more complicated. There are already "collective actions" under the Fair Labor Standards Act, and controversy over how they interact with Rule 23.

None of these issues, should they arise, are reasons for panic. They're more just, well, inelegant. Rule 23 works as well as it does because it applies equally across various different kinds of lawsuits, and because, over time, courts have figured out how it actually works in real cases. Taking a outlier case like Dukes and building a bill around it is a great way to create lots of unforeseen consequences in litigation.

So it appears that the primary benefit of this bill is rhetorical: it allows Democratic legislators to claim that they are standing up for civil rights, while not really standing a chance of amending Rule 23 in any significant way. Instead, they can claim that they tried to address the primary talking points of Dukes critics, and were stymied.

So Senator Franken's proposal is a competent political tactic, but would make for a lousy solution to civil rights problems.

The New Normal in Class Action Defense - Khalif L. v. City of Union City

Today's case is interesting in no small part because it shows just how far class-action arguments have come in the last 18 months. In the latter half of 2010, most defendants faced with a class action would look primarily at adequacy (are the named plaintiffs good representatives?), typicality (do the named plaintiffs have the same injury and proof as the class?), and predominance (are there more individual issues than common issues?). Now, however, given recent trends in case law--particularly the increased focus on a "rigorous analysis"--more defendants are looking at numerosity [] (can the plaintiffs show that there are enough class members?) and commonality (will the class action yield common answers?) as well.

Take, for example, the recent case of Khalif L. v. City of Union City, 2012 U.S. Dist. LEXIS 64567 (N.D. Cal. 2012). In this case, the named plaintiff sued the Union City Police Department, alleging that it had unlawfully discriminated against its African-American population by denying young blacks who had been victimized by Latino gangs any police assistance.

Under the best of circumstances, this would be a difficult case to prove on a classwide basis. (How, for example, does one really prove non-responsiveness on a common basis? Unless the police systematically never responded to calls from African-Americans, there would always be individualized issues.) When the plaintiffs moved for class certification, the defendants opposed them on both numerosity and commonality grounds, and did so successfully.

For numerosity, the plaintiffs had alleged that, based on 2000 census data, coupled with several affidavits alleging non-responsiveness by the police department, the court could conclude that there were enough African-American high school students in the area to constitute a class.

Defendant, however, asserts that plaintiffs' reliance on the 2000 census data is unduly speculative, and furthermore, that plaintiffs' supporting declarations are insufficient to satisfy numerosity requirements, since the testimony therein exposes a paucity of contact between certain putative class members and the UCPD (and thus, lack of membership in the class).

Defendant's objections are well taken. Plaintiffs have failed to connect the census information they primarily rely upon -- and that establishes the presence of 301 Black or African-American students enrolled in grades 9 through 12 in Union City in 2000 -- to their own class definition or claims.

(Emphasis added.)  Similarly, to establish commonality, the plaintiffs asserted that the common issue was whether the Union City Police Department had violated the civil rights of the class members. The defendants responded with an argument that is becoming more common after Dukes: anyone can pose a "common" question, but will it yield common answers?

What plaintiffs here must posit are not questions that within them presuppose a finite legal conclusion that will apply to all class members (e.g., whether the UCPD acts to violate plaintiffs equal protection rights), but instead questions of law or fact that will generate a common answer among members of the class that will aid in determining questions of liability (e.g, allegations that all plaintiffs were subjected to the same particularized UCPD response, or conduct by the same UCPD officer, as a result of similar underlying incidents/reports). This plaintiffs fail to do.

The takeaway from this case is pretty simple. In the wake of cases like Dukes, courts are beginning to recognize that certifying a class means certifying it for a classwide trial. Under those circumstances, even issues like numerosity and commonality are not foregone conclusions for the plaintiff. This is the new normal in class action defense.

 

Klonoff on Class Action Decline - The Good, the Bad, and the Ugly

Robert Klonoff, Dean of the Lewis & Clark Law School, has produced a new article, The Decline of Class Actions (forthcoming from the Washington University Law Review), that provides a much-appreciated overview of recent developments in class action law from a plaintiff's perspective. (Disclosure: Dean Klonoff provided a very nice blurb for the Class Action Playbook.) Regular readers of this blog know that I am actually a big fan of plaintiffs' perspectives: I think understanding them is crucial to a conscientious and seals defense of class action litigation. And while there is much to like in Dean Klonoff's analysis, there is also a fair amount that is lost to the same old pro-plaintiff analysis that many courts have begun to reject.

Unlike a number of his scholarly colleagues, Dean Klonoff doesn't say that the class action is dead, just that courts have made it a lot harder to get a class certified, and that he considers that a problem. He traces that problem to a number of the "new" requirements that courts have imposed on class-action plaintiffs in the last decade. What are those new requirements? Well, they'll look familiar to readers of Rule 23.

Rigorous analysis. Dean Klonoff worries that courts now require too much evidence from plaintiffs at the certification stage. Some of his concerns have some actual foundation (a number of practitioners, both plaintiff and defense, have noted that the increased focus on rigorous analysis has shifted costs toward the beginning of the case for both sides, a result necessarily in tension with the efficiency arguments for class certification). But others betray an ignorance of how lawyers actually litigate cases. For example, he expresses concern that:

While courts have imposed strict new evidentiary burdens on plaintiffs, they have increasingly permitted defendants to seek denial of class certification without submitting to discovery. For instance, in Pilgrim v. Universal Health Card, LLC, the Sixth Circuit upheld the district court’s dismissal of class allegations in a nationwide class action, reasoning that “we cannot see how discovery or for that matter more time would have helped [plaintiffs].” Other courts have taken this approach as well. Case law requiring plaintiffs to put forward exacting evidentiary proof in support of class certification is difficult to square with case law permitting defendants to move to strike class allegations without allowing plaintiffs even minimal discovery.

In fact, it is easy to square these two requirements. The plaintiff bears the burden of providing the court with an adequate basis for certifying a class. LIke with any burden, that means that ties go to the other party (in this case, the defendant). If the plaintiff has pled a class action that can't be certified because of an insurmountable legal defect, there is no reason to engage in discovery that cannot cure that defect. This is the exact same reason that we require a plaintiff both to prove her case by a preponderance of the evidence, but also allow the defendant to file a motion to dismiss.

More importantly, Dean Klonoff does not address the actual new requirement imposed by Rule 23(c)(1)(B), which requires a detailed order from courts certifying a class. Without actual evidence from plaintiffs, courts will find it hard to meet this new requirement.

Interestingly, Dean Klonoff does think that courts should resolve Daubert questions before certification, because they are about the admissibility of evidence, rather than proof of the merits.

Ascertainability. Dean Klonoff also worries about courts' increased focus on the viability of class definitions.

Indeed, the trend of more exacting scrutiny of class definitions has been recognized by one of the nation’s leading class action defense attorneys, John Beisner. In a recent article, Beisner noted that “more and more decisions are turning on the requirement of an ascertainable class definition.” He thus urged class action defense counsel to look for ways to challenge the class definition.

(Internal footnotes omitted.) According to Klonoff, a "more measured" approach would be to allow the plaintiffs to amend their class definition whenever it is challenged. And, in many cases, that is exactly what a court will do. But sometimes amending a class definition is simply futile: if there is no common issue uniting the class, then any definition will be either overbroad or impermissibly merits-based.

Numerosity. Dean Klonoff has identified an important trend here. Prompted by a need for a more rigorous analysis, courts have expanded their analysis of numerosity. In particular, they have begun to question the assumptions plaintiffs make, and to look at the effect that geographic dispersion may have.

Although the case law is conflicting, plaintiffs are nonetheless at risk of losing on class certification if their numerosity argument is based on inference or on appeal to common sense. The strict approach adopted by some courts represents yet another troublesome trend. Indeed, the large number of successful challenges to numerosity—which was once the least demanding requirement of Rule 23(a)—is one of the most dramatic recent developments.

(Emphasis added.)  Both plaintiffs and defense can benefit from a greater understanding of this development.

Commonality. Not surprisingly, given his overall thesis, Dean Klonoff believes that the Supreme Court erred in its holding in Dukes. As he puts it:

The majority decision in Dukes cannot be squared with the text, structure, or history of Rule 23(a)(2). Nothing in the text of Rule 23(a)(2), or in the Advisory Committee Notes thereto, requires that the common question be central to the outcome. Instead of looking at the traditional methods of interpreting Rule 23(a)(2), the majority relied heavily on a law review article by Professor Nagareda.

Dean Klonoff also questions whether Nagareda was really writing about commonality, even though Nagareda makes makes it clear that he is referring to common questions in Rule 23 a number of times (both Rule 23(a)(2) and 23(b)(3) use the same term; it makes sense they would mean the same thing). This begs the question: Why would you want to certify a class where the common question was not central to the outcome of the case?  This, unfortunately, is not a question he answers. (Dean Klonoff does raise another interesting question, which is whether the use of the term "common question" in Rule 23 is the same as in Rules 20 and 42.)

Adequacy. After pointing out that he actually supports a more stringent adequacy requirement in general, Dean Klonoff argues that adequacy should not encompass claim-splitting.

There is, however, a disturbing trend in “adequacy” jurisprudence. That case law focuses not on the ability of class representatives and counsel to vigorously represent the class, but on counsel’s selection of the causes of action to assert. The argument is that, by not bringing all potentially viable claims, the representatives and counsel have (1) impermissibly “split” claims, thereby prohibiting class members (pursuant to res judicata) from later bringing those omitted claims, or (2) subjected class members to the risk that collateral estoppel could essentially nullify their remaining (unfiled) claims.

(Internal footnote omitted.)  Dean Klonoff's solution is simply to have courts state that collateral estoppel shall not apply to claims that could have been raised, but were not for strategic reasons. This is a disturbing suggestion on several levels, not least of which is that it undermines the balance that justifies class aggregation, that of the right to individual trials on the one hand, and the need for global resolution--for plaintiff or defendant--on the other.

Other Issues. Dean Klonoff also worries that plaintiffs cannot use Rule 23(b)(2) strategically to certify money damages classes that would not qualify under Rule 23(b)(3), and that courts have clamped down on fraud and multi-state class actions (the former because reliance is very difficult to prove on a classwide basis, the latter because plaintiffs have not offered any viable methods of certifying a nationwide class). He believes that these constitute "per se" rules against certification.

Klonoff doesn't have much practical advice for lawyers, instead he advocates forum-shopping to find more receptive circuits. (He recommends the Second, Third, and Ninth.) Instead, he largely critiques the holdings, and asks courts to hold differently going forward.

So the good news is that Dean Klonoff has published an actual work of doctrinal scholarship that can help lawyers, something we desperately need more of. The bad news is, it's clearly plaintiff-biased; but that's not really bad news. Dean Klonoff is a smart man who knows class-action law well; reading his analysis of the latest class certification cases will help any conscientious defense lawyer hone his arguments. The real bad news (call it the "ugly") is that these are apparently the best pro-certifictaion arguments. Rather than basing them on the case law as it stands, Klonoff instead questions the legitimacy of recent holdings:

They suggest a suspicion about class actions generally, premised on the assumption that the class action is a blunt instrument to coerce settlement and secure large attorneys’ fee awards.

In fact, as several class-action plaintiffs made clear at the DePaul Law Review Symposium, these are not the only arguments available to plaintiffs. Plaintiffs who actually meet the requirements of Rule 23--by avoiding individualized issues, providing evidence that each of the requirements are met, and engaging in comprehensive legal analysis where appropriate in multistate class actions--are on exceptionally strong footing at certification. When one's arguments all start out by assuming a premise like "courts should not be suspicious," then the battle is won or lost before any argument gets made. Either the judge is suspicious or she isn't, either she agrees that the text of Rule 23 is secondary to deterrence and efficiency, or she does not. At that point, all the arguments of this kind that exist are unlikely to change her mind from where she started.

(Hat tip to Professor Lahav at the Mass Tort Litigation Blog for finding the article.)

TAGS - 

Spherical Cows, Can Openers, and Classwide Injury

There's an old joke about a physicist asked to help increase milk production at a dairy farm. He begins by assuming a spherical cow.

There's another old joke about a group of academics stranded on a desert island with a can of food. As they try to figure out how to get the food out of the can and into their mouths, the economist argues they should assume a can opener.

Why open a blog post with two lame jokes? It's not to demonstrate that academics shouldn't do comedy; some physicists and economists make good comedians. It's to point out that many academics, in their attempts to come up with accessible explanations of the world around them, wind up assuming away too much.

And that's the problem plaguing Professor Sergio Campos's latest paper on developing proof of classwide injury in class action litigation.  Instead of grappling with the realities of the law as it stands, and therefore offering practical advice on what constitutes classwide proof, Professor Campos tries to assume into existence a world that doesn't exist.

Professor Campos's argument is that the requirement that a class-action plaintiff demonstrate a common injury that can be proven with classwide evidence stems from three "fallacies" about class actions.

The first fallacy is that class actions are "all at once" procedures which require a court to resolve all issues in one fell swoop. ...

The second fallacy is that the class action is an "extraordinary remedy" that, like a preliminary injunction, requires the plaintiffs to show a likelihood of success on the merits before a court can certify a class. ...

The third fallacy is that, in the absence of proof of classwide injury, individual trials as to each plaintiff's injury are required to accurately determine individual injury and prevent uninjured plaintiffs from recovering.

How is it that, in Campos's view, so many courts could have bought into these fallacies? Well, first of all, he's assuming fallacies where none exist. Almost no courts require that a class action resolve all issues in a single swoop. What they do--in the wake of Dukes--is define a common issue as:

of such a nature that it is capable of classwide resolution—which means that determination of its truth or falsity will resolve an issue that is central to the validity of each one of the claims in one stroke.

(Emphasis added.) Similarly, no court requires that plaintiffs show a likelihood of success on the merits before certifying a class. (In fact, despite the emphasis on rigorous inquiry, that part of the ruling in Eisen is still valid.) And--despite the Third Circuit's ruling in Sullivan v. DB Investments--the Supreme Court's ruling in Amchem Products v. Windsor (as well as numerous rulings rejecting overbroad classes) made clear that that if some class members were injured and others were not, a class action is not appropriate.

And how did Professor Campos get these fallacies so wrong? That comes from the fact that he is trying to explain why courts--in contravention to his own theory--treat the class action like a representation device rather than a trust device.  According to Professor Campos:

However, the class action is neither a "joinder" device nor a "representational" device. As I have argued elsewhere, the class action is a "trust" device, which becomes apparent once one examines why class actions are preferable in small claims litigation like the antitrust, securities fraud, civil RICO, and employment discrimination cases I have discussed so far."

Campos's take on the class action as trust is an interesting one, and it would go some way to explaining a few quirks of class action doctrine, like why Rule 23 is so ready to hand control of a case over to the class attorney rather than the representative plaintiff. (There are alternative explanations, such as that some courts have misinterpreted the adequacy requirement.) But to deny that the class action is a representative device ignores--among other things--the text of Rule 23(a):

(a) Prerequisites. One or more members of a class may sue or be sued as representative parties on behalf of all members only if:
(1) the class is so numerous that joinder of all members is impracticable;
(2) there are questions of law or fact common to the class;
(3) the claims or defenses of the representative parties are typical of the claims or defenses of the class; and
(4) the representative parties will fairly and adequately protect the interests of the class.

(Emphases added.)  And this is Professor Campos's problem. He's bought into the "trust" and "deterrence" arguments so far that he doesn't just ignore the remainder of class action doctrine, he's convinced courts must be wrong when they employ it. Deterrence and trusts are Professor Campos's spherical cow and can opener. They explain class actions to him, but they only do so by ignoring the text of the rule and the weight of precedent.

So, why should a defense lawyer bother reading this article? Because, like it or not, these arguments do come up. Professor Campos is not stupid; and it's worth it to see where smart people go wrong in these arguments.

Cohesiveness and Commonality - MD v Perry

 In the wake of Wal-Mart Stores, Inc. v. Dukes, plaintiffs and trial courts are still trying to determine exactly how to apply the clarified commonality standard of Rule 23(a)(2), and the standard for injunctive relief under Rule 23(b)(2). The good news for defendants, as demonstrated in the new case M.D. v. Perry, 2012 U.S. App. LEXIS 6061 (5th Cir. Mar. 23, 2012), the appellate courts are largely following the Supreme Court's lead in Dukes. (My apologies: Google Scholar doesn't have the opinion yet, and the Fifth Circuit website appears to be having difficulties.)

The plaintiffs challenged the state's long-term foster care program, known as the Permanent Managing Conservatorship ("PMC"). They alleged that Texas's mismanagement of the PMC had created a variety of problems for the 12,000 children under its care. They sought injunctive relief under Rule 23(b)(2).

The lower court acknowledged that different children would have been treated differently by the system, but certified the class anyway. It identified the "common question" uniting the class as the legality of the foster-child regime as administered in Texas. It reasoned that the Fifth Circuit had held that the commonality standard was not a demanding one, and that the plaintiffs' proposed common questions could apply to all class members, even if they yielded different answers for different class members.

The Fifth Circuit disagreed. First, it pointed out that that Dukes has changed its standard for commonality.

Thus, the commonality test is no longer met when the proposed class merely establishes that "there is 'at least one issue whose resolution will affect all or a significant number of the putative class members.'" Forbush, 994 F.2d at 1106 (emphasis added) (citation omitted). Rather, Rule 23(a)(2) requires that all of the class member's claims depend on a common issue of law or fact whose resolution "will resolve an issue that is central to the validity of each one of the [class member's] claims in one stroke."

(Emphasis in original.) And then it pointed out that, in this case, the alleged "common issues" had been pitched at too general a level to yield any common answers that would actually advance the litigation.

Accordingly, given the "amorphousness" of the proposed class's proffered common issues of fact and law, the district court should be particularly precise when explaining how the resolution of those claims "will resolve an issue that is central to the validity of each of the [individual class member's claims] in one stroke." Wal-Mart, 131 S. Ct. at 2551. The district court's present certification order failed to do so; thus, we conclude that it failed to perform the "rigorous analysis" that is required in order to find that the proposed class satisfied Rule 23(a)(2)'s commonality requirement.

(Emphasis added.)  But the Fifth Circuit did not stop there. After pointing out that a request for injunctive relief must be "specific," it also held that, because the plaintiffs had asked--indirectly--for individualized injunctive relief, that it was clear that the class lacked the cohesiveness to justify certification under Rule 23(b)(2).

"A proposed class cannot avoid Rule 23(b)(2)'s prohibition on claims for individualized relief by petitioning the district court to order the defendant to craft individualized "injunctive-type" relief for certain class members. See Jamie S., 668 F.3d at 499 (holding that proposed injunctive relief did not satisfy Rule 23(b)(2) when the district court's order "would merely initiate a process through which highly individualized determinations of liability and remedy are made; this kind of relief would be class-wide in name only, and it would certainly not be final"). Accordingly, we find that the requested individual relief implicitly establishes that at least some of the proposed class's underlying claims allege individual injuries that are not uniform across the class; thus, as currently pleaded, the proposed class lacks cohesiveness to proceed as a 23(b)(2) class.

(Emphasis added.)  The Fifth Circuit remanded the case for further consideration. (It reasoned that the plaintiffs might be able to allege a more limited class that could justify certification.)

The applications of this opinion to defense work are clear. First, like the Seventh Circuit in Jamie S., the Fifth Circuit has affirmed that a plaintiff may not simply plead around Rule 23(a)(2) by keeping her claims amorphous. And second, the Fifth Circuit has also affirmed the "cohesiveness" standard implicit in Rule 23(b)(2), and shown its importance in a world with a more rigorously-enforced commonality standard.

More on Commonality - Jamie S. v. Milwaukee Public Schools

Six months after the Supreme Court decided Wal-Mart Stores, Inc. v. Dukes, courts are still working out how best to apply the newly-clarified standard of commonality. This week, the Seventh Circuit offered some further guidance.

In Jamie S. v. Milwaukee Public Schools, the plaintiffs--seven disabled public-school students--challenged Milwaukee's implementation of the Individuals with Disabilities Education Act.  The trial court denied certification, but allowed the plaintiffs to amend their complaint. It then certified the amended class proposal, and proceeded to a bench trial, where it found various violations of the IDEA, and ordered a complex, court-monitored remedial scheme. Both sides appealed: MPS appealed the certification, while the plaintiffs appealed the denial of certification of their first proposed class.

The Seventh Circuit vacated the trial court's certification order. It began by discussing how school districts implement the IDEA:

As relevant here, local districts must identify children with disabilities, determine whether these children require special-education services, and develop individualized education programs ("IEPs") tailored to each student's specific needs. Each step in the process is highly individualized because every child is unique.

(Emphasis added.) As one might expect, the rest of the opinion follows inexorably from that account. The Seventh Circuit vacated the order on three grounds. First, it found that the class was not identifiable from the proposed definition. The trial court had certified a class of

Those students eligible for special education services from the Milwaukee Public School System who are, have been or will be either denied or delayed entry or participation in the processes which result in a properly constituted meeting between the IEP team and the parents or guardians of the student.

As the Seventh Circuit found,

A significant segment of the class (of unknown and unknowable size) comprises disabled students who may have been eligible for special education but were not identified and remain unidentified.

(Emphasis in original.)

The Seventh Circuit also found that the class lacked commonality.

The plaintiffs identify the following common issue: "[A]ll potential class members have suffered as a result of MPS' failure to ensure their Child Find rights under IDEA and Wisconsin law." This completely misunderstands Rule 23(a)(2). Whether MPS failed in its obligations under the IDEA and thereby deprived an eligible disabled child of a free appropriate public education is the bottom-line liability question in any individual plaintiff's IDEA claim. To bring individual IDEA claims together to litigate as a class, the plaintiffs must show that they share some question of law or fact that can be answered all at once and that the single answer to that question will resolve a central issue in all
class members' claims.

(Emphasis in original.) This is, of course, remarkably similar to the language in Dukes. But the Seventh Circuit too it slightly further, providing an example to illustrate why plaintiffs' proposed common issue was not common at all:

To illustrate the commonality problem in the certified class, consider two hypothetical students within the class: one has a disability and would be eligible for special education but has never been identified as being disabled nor gone through the IEP process; another was identified as disabled and received a timely IEP meeting, but the child's parents did not attend the IEP meeting and were not notified of their right to do so. Both scenarios involve violations of the IDEA, but what common question can be answered that would assist the court in determining MPS's liability for each? On the plaintiffs' theory, that question is something like this: Did MPS fulfill its IDEA obligations to each child? But while that generic question is surely a part of both children's claims, it must be answered separately for each child based on individualized questions of fact and law, and the answers are unique to each child's particular situation.

(Emphasis added.)

Finally, the court held that since the plaintiffs had not established any common issue, there could be no common injunctive relief that would apply to all class members. As it held:

"While the compensatory-education remedies will often or always be injunctive in nature, there can be no single injunction that provides final relief to the class as a whole. It is no answer to say that the June 9 remedial order affects the entire class; that order merely establishes a system for eventually providing individualized relief. It does not, on its own, provide "final" relief to any class member."

The application for defense counsel should be clear. In an effort to avoid the dictates of Dukes, plaintiffs continue to label both issues and and relief as "common," even if the proposed common issue is so abstract as to be meaningless in a trial or in granting relief. The Seventh Circuit's "single answer" formulation can help explain to courts just when a common issue is truly common, as opposed to when the only real commonality to the class is their counsel's desire for certification.

Framing the Certification Opposition - Ross v. RBS Citizens NA

Today's case is a perfect illustration of the difference between tactics and strategy, or, more accurately, between litigation strategy and litigation grand strategy. As you may remember, a tactic is a plan to accomplish a specific short-term goal within a larger conflict. (A defendant may have the strategy of defeating certification to minimize litigation risk; one tactic will be to file a motion to strike class allegations.) A strategy (win this case by defeating certification) should also fit into a grand strategy (keep the defendant safe from meritless lawsuits by making sure courts enforce Rule 23 properly) that can include a number of larger moves, including planning for appeals and even lobbying for legislative change.

Last Thursday, the Seventh Circuit decided an appeal in Ross v. RBS Citizens, N.A. that represents a tactical (and even strategic) loss for the specific defendant, but was still a grand strategic win for defendants.

Ross was a wage-and-hour case, asserting claims under the Fair Labor Standards Act and the Illinois Minimum Wage Law.) The plaintiffs alleged that RBS had denied them overtime pay. The lower court certified the class, and RBS appealed.

Interestingly, RBS appealed solely on the grounds that the Court had not followed Rule 23(c)(1)(B), which requires a court to issue

An order that certifies a class action must define the class and the class claims, issues, or defenses, and must appoint class counsel under Rule 23(g).

In this case, RBS argued, the court had not adequately defined the class. (A side issue that came up during the appeal was whether the lower court had properly found commonality, since the Supreme Court arguably changed the standard in its Dukes opinion.)

To "define" a thing or concept is "to state precisely or determinately [its boundaries]; to specify" or "[t]o frame or give a precise description" of a thing. Oxford English Dictionary (2d ed. 1989). According to the Rule, those things to be defined in a certification order include the "class and the class claims, issues, or defenses. . . ." Fed. R. Civ. P. 23(c)(1)(B) (emphasis added). The above elements occur in a conjunctive, undifferentiated list, indicating that the requirement to "define" the "class claims, issues or defenses" is identical to the requirement to define the "class" itself within a given certification order. Id. Furthermore, the use of the definite article "the" before "class claims, issues, or defenses" connotes comprehensiveness and specificity, rather than illustrative or partial treatment, in defining those aspects of class action certification.

(Second emphasis added, quoting Wachtel v. Guardian Life Ins. Co. (3d Cir. 2006).)  Based on that reasoning, the Seventh Circuit held

that the appropriate substantive inquiry for Rule 23(c)(1)(B) is "whether the precise parameters defining the class and a complete list of the claims, issues, or defenses to be treated on a class basis are readily discernible from the text either of the certification order itself or of an incorporated memorandum opinion."

In this case, the Seventh Circuit found that the lower court had in fact met that burden. While it admitted "there might be some room for the district court to have drafted a clearer certification order," it found the order clear enough. (An important side note is that it made this finding in part by relying on the old common-law maxim of expressio unius est exclusion alterius: the lower court's list of issues to be tried on a class basis was complete and exclusive; everything else was an individual issue.) But the opinion offers an important tool for defendants at the same time. Frequently, lower courts certify cases because they have not thought through how the claims will actually be tried, and may therefore elide important individualized defenses to claims. But Rule 23(c)(1)(B) requires them to address each of these issues in turn, a requirement that should cut down on incorrect certifications.

So the end result of the individual case is that the defendants here lost. But, at the same time, the Seventh Circuit, joining the First and the Third, gave defense counsel an important tool to make sure that the lower court is considering all of the issues before it. What's the lesson defense counsel can take away from this? Tactically, it makes sense to remind courts that they must come up with an order that contains a clear statement of how they will treat all of the classwide claims, issues, and defenses. On a larger scale, it always makes sense to keep the court to the text of Rule 23; in the long run, that will continue to cut down on flawed certification orders.

Rothman v. GNC - Why Pure Statutory Violations Don't Make Good Classes

Like many health-minded individuals, Norma Rothman has shopped at GNC stores.  And, like many others, she has bought items there with her credit card.  And, like many consumers everywhere, she didn't like it when the cashier allegedly asked her for her ZIP code when she made her purchase.  Unlike many consumers, Ms. Rothman tried to turn this momentary dissatisfaction into a class action, alleging that GNC had violated the Song-Beverly Credit Card Act and California's infamous § 17200.  (Song-Beverly class actions have become very popular in California since its Supreme Court ruled that requesting a ZIP code can violate the Act.)

How unlike other consumers was Ms. Rothman?  Very.  When a trial court for the Central District of California denied her motion for class certification, it found that her class was overboard, lacked numerosity and commonality, and that, since she may have been the only person harmed in the manner she alleged, she was neither a typical nor adequate class representative.  (For those of you keeping score, that means she did not demonstrate any of the Rule 23(a)(4) requirements.)

The case was argued by a colleague of mine, Susie Germaise from McGuire's Los Angeles office, joined by Brad Funari and Laura Lange in Pittsburgh, so I'm not going to linger on commentary.  Instead, I will simply offer my congratulations for an outstanding win, and thank them for making the briefing available for others to read.  (Motion for class certification here, opposition here, reply brief here.)

Have a happy (and nutritious) Thanksgiving, everyone.  And come back Friday for another post.

The Maturing Motion to Strike Class Allegations

Last week, the Sixth Circuit affirmed a trial court's decision striking class allegations where a proposed nationwide class would necessarily invoke the laws of fifty different jurisdictions. (Russell Jackson has an excellent writeup of the opinion here.) There is no question the opinion is a useful one for defendants. And, since it's the first appellate opinion on a motion to strike in decades, it may be time for an overview of where the motion to strike class allegations stands today.

In the past year, a large number of motions to strike have been filed. (I count at least 25 reported opinions on early challenges to the certifiability of classes.) How have those motions turned out?
Ten of those opinions denied the motion to strike outright as premature, without further analysis.

  • Clerkin v. Mylife.com, Inc., 2011 U.S. Dist. LEXIS 96735 (N.D. Cal. 2011) ("Defendants fail to identify any authority permitting the use of a motion to dismiss for failure to state a claim to contest the suitability of class certification.").
  • Eliason v. Gentek Building Prods., Inc., 2011 U.S. Dist. LEXIS 94032, *7 (N.D. Ohio Aug. 23, 2011) ("While raising possibly valid concerns, Defendants' arguments on class certification are premature. Whether the commonality requirement has been demonstrated cannot be determined until discovery has taken place and choice of law provisions applied.").
  • Garcia v Lane Bryant, Inc., 2011 U.S. Dist. LEXIS 125484 (E.D. Cal. Oct. 31, 2011). (Grants motion to dismiss, denies MTS because "Although Defendants' motion is unopposed, dismissal of Plaintiffs' class allegations at this stage of the proceeding is premature. Although class allegations may be wholly insufficient[,] compliance with Rule 23 is not to be tested by a motion to dismiss for failure to state a claim.") (internal quotations omitted).
  • Ginardi v. Frontier Gas Servs, LLC, 2011 U.S. Dist. LEXIS 89504, *11-12 (E.D. Ark. Aug. 10, 2011) ("Plaintiffs are correct that it is premature to strike the class action allegation.").
  • Kas v. Mercedes-Benz USA, LLC, 2011 U.S. Dist. LEXIS 127581 (C.D. Cal. Oct. 31, 2011) ("Nevertheless, we will defer final decision pending a more robust briefing at the class certification stage.").
  • Martin v. Ford Motor Co., 765 F. Supp. 2d 673 (E.D. Pa. 2011) ("Since the Motion to Strike filed by Defendant is premature, the merits of this argument will not be addressed at this stage of the case.").
  • P.V. v. School Dist. of Philadelphia, 2011 U.S. Dist. LEXIS 125370 (E.D. Pa. Oct. 31, 2011) ("unless the parties have completed discovery and at least one party has moved for class certification, a court very rarely has the information necessary to conduct the 'rigorous analysis' inherent in the class certification decision.").
  • Rivellio v. Penn State Fed. Credit Union, 2011 U.S. Dist. LEXIS 99668 (M.D. Pa. Sep. 6, 2011) ("The Court is not convinced that this case is one of the "rare few where the complaint itself demonstrates that the requirements for maintaining a class action cannot be met."").
  • Rogers v. Capital One Servs., LLC, 2011 U.S. Dist. LEXIS 17064 (D. Conn. Feb. 19, 2011) ("a defendant may move to strike class allegations prior to class certification proceedings "if the inquiry would not mirror the class certification inquiry and if resolution of the motion is clear."").
  • Vlachos v. Tobyhanna Army Depot Fed. Credit Union, 2011 U.S. Dist. LEXIS 69725 (M.D. Pa. Jun. 29, 2011) ("The Court will not address the merits of the argument because the motion to strike is premature at this stage, as the plaintiff has not yet moved for class certification.").

Three denied motions to strike on their merits, usually because the plaintiff had made sufficient allegations to support a class action.

  • Alegations of commonality - NBL Flooring, Inc. v. Trumball Ins. Co., 2011 U.S. Dist. LEXIS 110518 (E.D. Pa. Sep. 27, 2011) ("These allegations speak to a blanket course of conduct that may apply to all insureds.").
  • Denies because of plausible allegations - Perrin v. Papa John's Int'l, Inc., 2011 U.S. Dist. LEXIS 22957, *18-19 (E.D. Mo. Mar. 8, 2011) (""Plaintiff may or may not succeed in proving his claims with respect to other drivers, but at this stage of the case he has set forth sufficient facts to support a plausible allegation of an under-reimbursement [*19] large enough to support a claim that Defendants did not reasonably approximate the delivery drivers' expenses."")
  • Plaintiff had standing - Ralston v. Mortg. Inv. Group, Inc., 2011 U.S. Dist. LEXIS 102945 (N.D. Cal. Sep. 12, 2011) ("The fact that some class members purchased their loans from originators other than MIG does not deprive Ralston of standing to assert claims on their behalf").

Two denied motions to strike as moot, since the courts granted concurrent motions that disposed of the case.

  • Eldee-K Rental Props., LLC v. DirecTV, Inc., 2011 U.S. Dist. LEXIS 132981 (N.D. Cal. Nov. 17, 2011). Court granted concurrent motion to dismiss.
  • Ass'n of N.J. Chiropractors v Aetna, Inc., 2011 U.S. Dist. LEXIS 67718 (D.N.J. Jun. 20, 2011). Denies as Court granted concurrent motion to compel arbitration.


And finally, the remainder of the courts have granted motions to strike. And they have done so for various reasons. Among them, they have ruled that

The class was not ascertainable.

  • Bradley v. Mason, 2011 U.S. Dist. LEXIS 64877 (N.D. Ohio Jun. 20, 2011) ("First, the existence of the class must be pleaded and the limits of the class must be defined with some specificity.").
  • Bauer v. Dean Morris, L.L.P., 2011 U.S. Dist. LEXIS 100399 (E.D. La. Sep. 7, 2011) - struck class allegations where merits-based class definition
  • Schilling v. Kenton County, 2011 U.S. Dist. LEXIS 8050 (E.D. Ky. Jan. 27, 2011) ("Plaintiffs' proposed class definition is fatally flawed because the Court cannot determine its individual members without reviewing the evidence relative to each KCDC inmates' incarceration, which would amount to a merits-based inquiry of each individual's claim.").

Variations in state law precluded certifiable class.

  • Pilgrim v. Universal Health Card, LLC, 2011 U.S. App. LEXIS 22715, *4 (6th Cir. 2011) ("the district court held, because each class member's claim would be governed by the law of the State in which he made the challenged purchase, and the differences between the consumer-protection laws of the many affected States would cast a long shadow over any common issues of fact plaintiffs might establish. That judgment is sound and far from an abuse of discretion …"). 
  • Plaisance v. Bayer Corp., 275 F.R.D. 270 (S.D. Ill. 2011) [] ("In the instant case, defendants have identified numerous facial deficiencies in the class allegations; no amount of time or discovery can cure these deficiencies.").

From the pleadings, the class lacked commonality

  • *Schilling v. Kenton County, 2011 U.S. Dist. LEXIS 8050 (E.D. Ky. Jan. 27, 2011) ("to resolve the legal issue presented the Court must delve into the specific facts of each inmate's incarceration and the medical needs relative to that inmate.")

From the pleadings, the class lacked typicality

  • Schilling v. Kenton County, 2011 U.S. Dist. LEXIS 8050 (E.D. Ky. Jan. 27, 2011) ("The Sixth Circuit has held that where the plaintiffs' claims depends on each individual's unique interactions with the defendant, the typicality requirement is lacking. That is certainly the case here.") (internal citation omitted).
  • Wright v. Family Dollar, Inc., 2010 U.S. Dist. LEXIS 126643 (N.D. Ill. Nov. 30, 2010) ("These defenses, unique as to plaintiff and any other manager in the putative class, prevent plaintiff from establishing typicality and therefore from showing that she will be able to maintain a class action.").

From the pleadings, the class lacked adequacy.

  • Wright v. Family Dollar, Inc., 2010 U.S. Dist. LEXIS 126643 (N.D. Ill. Nov. 30, 2010) ("it is clear from the complaint that the putative class is permeated by conflicts of interest").

From the pleadings, the class lacked predominance.

  • Bauer v. Dean Morris, L.L.P., 2011 U.S. Dist. LEXIS 100399 (E.D. La. Sep. 7, 2011) - (struck class allegations where individual issues concerning liability, affirmative defenses, and damages apparent from pleadings).
  • Bevrotte v. Caesars Ent. Corp, 2011 U.S. Dist. LEXIS 114463 (E.D. La. Oct. 4, 2011) (individual issues of causation and damages would predominate; class not superior to individual litigation).

So, what can defense counsel take from this? First, the trend on motions to strike is becoming more favorable. More courts are willing to entertain these motions on their merits. (You may notice the majority of the denials come from only a few jurisdictions.) And the first appellate court to decide this issue has (correctly, I would argue) found that if the issue is a purely legal one or can be decided from the pleadings, then there is no reason to rule on it sooner rather than later.

Second, those courts that are granting motions to strike are granting them on various grounds. This is also good news, as it provides defendants with precedent for further motions to strike.

And finally, at least if one credits the opinions in Pilgirm and Plaisance, most plaintiffs don't seem to have any strong counter-arguments to a well-argued motion to strike. The best they can argue is that the motion is premature, and discovery is necessary for a rigorous analysis. And, in certain cases, that will be true. But in many more--like when plaintiffs propose nationwide classes that require applying the laws of fifty different states--there will be no discovery that will change the analysis a court must engage in.

 

Motions Practice, Commonality, and Time - Lightfoot v DC

 Sometimes, a case will come along that illustrates clearly a number of the different strategic choices that lawyers have to make when defending class actions. In Lightfoot v. District of Columbia, 2011 U.S. Dist. LEXIS 1983 (D.D.C. Jan. 10, 2011), a group of former District employees sued the District of Columbia, "challenging the policies and procedures that the District applied to terminate, suspend, and modify disability compensation benefits." (It appears they were largely represented by students at George Washington University, as well as lawyers from a prominent DC firm working pro bono.) Over the course of a decade of litigation (involving a number of dispositive motions, a certification hearing, and at least one trip to the DC Circuit Court of Appeals), the District of Columbia was able to whittle the case down to a single issue: whether the District had terminated disability benefits without proper notice.

Seven years before the current opinion, the trial court had certified a class of former District employees. It then ordered the parties to compile a list of the class members. The composition of the list (which at times included as many as 5,000 and as few as 500 members) became a large source of disagreement over the intervening five years, sparking discovery fights and at least one change in the class definition to exclude members who would be precluded from recovering by a recently-passed statute.

In 2007, the defendants moved to decertify the class. While the court denied the motion, it did order the parties to come up with a final class list, a process it admitted later "was a tortured one and consumed substantial time and resources of the parties and this Court." Once the list was completed, the plaintiffs filed a motion for summary judgment, which finally provided a clear picture of how they intended to prove their case. At that point, the defendants moved again to decertify the class, arguing that it was not bound together by common issues.

This time, the court agreed with the defendants. While it conceded that commonality was supposed to be a simple inquiry, it said that, in this case the inquiry had been complicated by plaintiffs' "amorphous" common issues. As the court put it:

Plaintiffs ... seek to conflate a wide variety of practices and impute them to the class as a whole by collecting them under a single, unilluminating umbrella of "systemic" failures. That is, lurking behind the rather vague and conclusory statement that Defendants had a "policy and practice of failing to provide members of the Plaintiff class Due Process" lies a wide variety of more discrete and particularized practices that could conceivably serve as the foundation for municipal liability.

...

This is because Plaintiffs have [the commonality inquiry] backwards. The question is not whether a constellation of disparate but equally suspect practices may be distilled from the varying experiences of the class; rather, Plaintiffs must first identify the "policy or custom" they contend violates the dictates of procedural due process and then establish that the "policy or custom" is common to the class.

(Emphasis added, internal citations omitted) There's certainly room to ask whether the district court could have reached some of these conclusions earlier. (And, at least for purposes of commonality, the Supreme Court's Dukes opinion might guide it going forward.) But the more important lesson here is that, if a defendant believes a class was wrongly certified, it makes sense to continue to challenge the certification ruling. Facts become clearer, laws and understandings of facts change.

So what can defendants learn from this case? There are actually three:

First, time is often on the side of the defense. The longer a class action takes, the longer a court has to acclimate itself to the various issues that make the case unworkable; also the more likely that external events (like the passage of a statute) will interfere with plaintiffs' original plan. But playing for time can come with heavy costs. It can involve complying with costly discovery, and engaging in extensive (and expensive) motions practice. Most defendants, particularly in the past few years, would prefer to resolve cases quickly than to wait around for something to happen that might help their case.

Second, motions practice is extremely helpful for class-action defendants. While plaintiffs will often argue that continued motions are designed to stall and harass, Lightfoot shows the real reason they're valuable to defendants: they continually expose the manageability problems in a class proposal that plaintiffs would prefer to gloss over until they've achieved a classwide settlement.

Finally, especially in the wake of Dukes, it is always worth challenging commonality. In the past, few class actions had progressed far enough for courts to see why commonality was an important requirement. But in the past few years, cases like this, Brown v. RJ Reynolds Co., and Dukes have painted vivid examples of the problems that occur when courts do not pay attention to commonality early in.

The Dukes Opinion - Commonality and Monetary Relief

Today, the Supreme Court issued its much-anticipated opinion in Wal-Mart v. Dukes.

For those who like to skip ahead to the end to figure out whether their side won, the Court ruled in favor of Wal-Mart. That said, the real winner was the late Professor Richard Nagareda, whose articles on commonality clearly influenced Justice Scalia's majority opinion.

In ruling for Wal-Mart, the Court issued two holdings: it held (5-4) that the plaintiffs had not met their burden on proving commonality, and (unanimously) that the plaintiffs could not certify a class for money damages under Rule 23(b)(2).

Now, what does the decision itself mean? Obviously, lawyers will be poring over the opinion in the coming months to tell us just that. But here are some highlights from the opinion.

Commonality means not common questions, but common answers.

Their claims must depend upon a common contention—for example, the assertion of discriminatory bias on the part of the same supervisor. That common contention, moreover, must be of such a nature that it is capable of classwide resolution—which means that determination of its truth or falsity will resolve an issue that is central to the validity of each one of the claims in one stroke.

The "rigorous inquiry" required for class certification is a factual inquiry.

Rule 23 does not set forth a mere pleading standard. A party seeking class certification must affirmatively demonstrate his compliance with the Rule—that is, he must be prepared to prove that there are in fact sufficiently numerous parties, common questions of law or fact, etc.

Plaintiffs must bring individualized monetary claims under Rule 23(b)(3).

[W]e think it clear that individ- ualized monetary claims belong in Rule 23(b)(3). The procedural protections attending the (b)(3) class— predominance, superiority, mandatory notice, and the right to opt out—are missing from (b)(2) not because the Rule considers them unnecessary, but because it considers them unnecessary to a (b)(2) class.

Statistical proof will not cure all problems with a proposed class.

The Court of Appeals believed that it was possible to replace such proceedings with Trial by Formula. A sample set of the class members would be selected, as to whom liability for sex discrimination and the backpay owing as a result would be determined in depositions supervised by a master. The percentage of claims determined to be valid would then be applied to the entire remaining class, and the number of (presumptively) valid claims thus derived would be multiplied by the average backpay award in the sample set to arrive at the entire class recovery—without further individualized proceedings. We disapprove that novel project. Because the Rules Enabling Act forbids interpreting Rule 23 to abridge, enlarge or modify any substantive right, a class cannot be certified on the premise that Wal-Mart will not be entitled to litigate its statutory defenses to individual claims.

(Internal citations omitted.)

And what does this mean for class-action litigation?

It means we're likely to see more robust challenges to commonality at the certification stage. It also means that we're likely to see fewer class actions pitched as seeking "injunctive relief" when what the plaintiffs (and their lawyers) really want is money damages. Combined with the Court's other class-action decisions this term, it seems clear that the limits of the class action are more sharply defined, which defense attorneys can use to protect their clients from spurious class actions.
 

Bonus Case - Brown v. RJ Reynolds

Late last year, the Eleventh Circuit ruled on the preclusive effect of a state-certified class action in federal court.  The Federalist Society very kindly asked me to comment on it for their online journal Engage.  It turned out to be a really interesting project, because what started out as an opinion about preclusion turned out to be more about the nature of commonality.  Here's a quick preview of the argument:

While at first glance Brown addresses the preclusive effect of the Engle class action, the real question the Eleventh Circuit wrestled with was the scope of Rule 23(b)(3)’s predominance inquiry. Neither the Middle District of Florida nor the Eleventh Circuit refused on principle to apply the findings of the Florida jury; instead, they found themselves unable to apply those findings because they lacked enough facts to understand what issues the jury had actually (or necessarily) decided.

You can head on over to the Engage website to read the rest.

 

Classic Cases - General Telephone Company of the Southwest v. Falcon

 In July 1969, General Telephone Company of the Southwest hired Mariano Falcon, a Mexican-American, as part of minority recruitment effort. Falcon maintained a good employment record until, "[i]n October 1972 he applied for the job of field inspector; his application was denied even though the promotion was granted several white employees with less seniority." Dissatisfied with being passed over, Falcon filed a charge with the Equal Employment Opportunity Commission, which promptly granted him a right-to-sue letter.

Falcon filed his lawsuit as a class action, alleging discrimination not just in General Telephone's promotion practices (sensible, since he had been passed over for promotion), but also in its hiring practices. After General Telephone responded to his interrogatories, Falcon moved to certify a class of all employees or potential employees. (This was an "across the board" challenge to Falcon's employment practices, a tactic that the Fifth Circuit allowed at the time.)

The trial court certified the class without conducting a hearing. It then conducted a trial of the liability issues, which resulted in a finding of that General Telephone had discriminated against Mexican-Americans in its hiring--but not its promotion--decisions. Both sides appealed the ruling; General Telephone because the hiring claim had been certified, and Falcon because his hadn't been.

The Supreme Court granted certiorari "to decide whether the class action was properly maintained on behalf of both employees who were denied promotion and applicants who were denied employment." In an 8-1 opinion , (Chief Justice Burger concurred in part and dissented in part), it held that the answer was "no."

Justice Stevens began his opinion by noting that

The class-action device was designed as an exception to the usual rule that litigation is conducted by and on behalf of the individual named parties only. Class relief is peculiarly appropriate when the issues involved are common to the class as a whole and when they turn on questions of law applicable in the same manner to each member of the class. For in such cases, the class-action device saves the resources of both the courts and the parties by permitting an issue potentially affecting every [class member] to be litigated in an economical fashion under Rule 23.

(Internal quotations omitted.)

Justice Stevens's opinion primarily addressed the problem that Falcon's claim was not the cause of action certified for class treatment. As a result, he was an atypical class representative.

We have repeatedly held that a class representative must be part of the class and possess the same interest and suffer the same injury as the class members.

(Internal quotations omitted.)  In fact, Justice Stevens held

Conceptually, there is a wide gap between (a) an individual's claim that he has been denied a promotion on discriminatory grounds, and his otherwise unsupported allegation that the company has a policy of discrimination, and (b) the existence of a class of persons who have suffered the same injury as that individual, such that the individual's claim and the class claims will share common questions of law or fact and that the individual's claim will be typical of the class claims.

The Court also found that the trial itself showed class treatment wasn't appropriate.

Instead of raising common questions of law or fact, respondent's evidentiary approaches to the individual and class claims were entirely different. He attempted to sustain his individual claim by proving intentional discrimination. He tried to prove the class claims through statistical evidence of disparate impact. Ironically, the District Court rejected the class claim of promotion discrimination, which conceptually might have borne a closer typicality and commonality relationship with respondent's individual claim, but sustained the class claim of hiring discrimination. As the District Court's bifurcated findings on liability demonstrate, the individual and class claims might as well have been tried separately.

Falcon is particularly important right now given that the Supreme Court is deciding Wal-Mart v. Dukes. The composition of the Court has changed, so this case does not provide a guide to how the current Court will rule on Dukes. But both parties relied on Falcon in their briefing, so it is particularly important to remind ourselves how the Court has ruled in previous employment class actions. Just because the plaintiff has alleged discrimination does not mean that he has alleged a claim that can be established with classwide proof.

Wal-Mart v Dukes - Postgame

Yesterday was the long-anticipated oral argument in Wal-Mart v. Dukes.  I've attached a copy here.  Overall, the Justices were clearly prepared for the argument, although they--like almost everyone else--had trouble keeping all of the facts straight.  A few highlights:

  • Justices Ginsburg, Kagan, and Sotomayor took an early lead in questioning Ted Boutrous (who argued for Wal-Mart).  
  • Boutrous was clearly having a good day.  He had command of almost all of the facts, and was able to subtly correct various Justices at different points when they got lost in the weeds.
  • Justices Kennedy and Scalia each had problems with the coherence of plaintiffs' underlying theory.  As Justice Kennedy put it: "your complaint faces in two directions. Number one, you said this is a culture where Arkansas knows, the headquarters knows, everything that's going on. Then in the next breath, you say, well, now these supervisors have too much discretion. It seems to me there's an inconsistency there"
  • Awarding "back pay" under Rule 23(b)(2) seemed to cause most Justices heartburn.  Justice Ginsburg called it "a very serious problem in this case."  
  • Several Justices, including Sotomayor and Scalia, had trouble accepting the legitimacy of the proposed statistical proof.

So where does that leave the case?  The "more question" rule doesn't provide much guidance in this case.  But it does appear that the Justices were wrestling with the questions of how to prove commonality and whether 23(b)(2) certification is appropriate.  If I had to predict, I'd say that Wal-Mart's probably in better shape than the plaintiffs at this point.  Of course, we'll find out in June.

 

A Little More on Wal-Mart v. Dukes

If you'll forgive the second piece of self-promotion in a week: the Washington Legal Foundation (which keeps the always-interesting Legal Pulse blog) has just published a Legal Opinion Letter evaluating several of the arguments in favor of overturning the 9th Circuit's Dukes v. Wal-Mart decision, written by yours truly.  

I'll be participating in a briefing for the WLF on this issue in a few weeks (specific details when I get them), and another one a few days later for the American Constitution Society.   

Using the All Writs Act to Block Copycat Class Actions

Earlier this week, the Seventh Circuit, in an opinion by Judge Richard Posner, granted an injunction to Sears under the All Writs Act to block a class action that had been filed in federal court in California. The opinion, Thorogood v. Sears, Roebuck & Co., is noteworthy for a couple of reasons. First, it extends relief under the All Writs Act to defendants facing copycat class actions in other jurisdictions. Second, it does so in response to a plaintiff's attempt to leverage a settlement using the threat of class-action discovery.

Steven Thorogood, the nominal plaintiff here, filed a class action against Sears after he bought a Kenmore stainless-steel dryer, which, as it turned out, was not 100% stainless steel. Instead,

part of the front of the drum—a part the user would see only if he craned his head inside the drum—is made of a ceramic-coated “mild” steel, which is not stainless steel because it doesn’t contain chromium. Thorogood alleged that the “mild” steel in the drum rusted, and stained his clothes.

His lawyer, Clinton Krislov (who just ran for Illinois comptroller) convinced an Illinois federal trial court to certify a consumer-fraud class, but the Seventh Circuit reversed it on a Rule 23(f) appeal, finding that there were no common issues justifying certification. It later affirmed the denial of attorneys' fees after Sears made an offer of judgment to Thorogood personally. 

Undeterred, Krislov filed a copycat class action in California federal court (Murray). The California court originally ruled that it was barred by collateral estoppel, but after a few amendments to the complaint, it reversed its ruling and allowed discovery to begin. At that point, Krislov's co-counsel sent a letter to Sears telling it:

that discovery is proceeding and “will involve Plaintiff’s counsel delving into the full extent of Defendants’ alleged wrongdoing” in order to justify not only equitable relief but also punitive damages—which are potentially very large given the size of the class and the possible preclusive use of any judgments favorable to the plaintiffs in suits brought in other states. The letter continues: “as we progress through the various stages of this litigation, the cost of settlement will necessarily increase . . . . At this point, we may want to consider whether an appropriate olive branch for resolution can be mutually created on a class wide basis commensurate with the status of the case. If interested, please pick up the telephone and call me. In the meantime, Plaintiff will continue to diligently and timely prosecute this case to an appropriate result.” In other words, unless Sears settles now (implicitly for modest relief for the class and an agreement with class counsel to recommend to the judge generous fees for Krislov and Boling), it will incur the considerable cost of responding to class counsel’s distended project of “delving” and assume the risk of a very large adverse judgment.

(Emphasis added.)  Faced with the prospect of plaintiffs' counsel commencing invasive and expensive discovery to leverage a settlement, Sears requested an injunction from the Seventh Circuit. The court, in an opinion by Judge Richard Posner, granted the request. After noting the in terrorem effect of plaintiff's discovery threat, he observed that:

quite apart from the green light that such a ruling would give to extortionate class action practice, a denial of relief would make no sense in a case like this, in which the class (Thorogood’s) was certified, albeit later decertified at our direction. Class counsel had and took the opportunity to litigate the certification issue fully—so that to say that a ruling against certification could not be the basis of an injunction would be inconsistent with the doctrine of collateral estoppel itself. There is no denying that a final ruling against certification has collateral estoppel effect. And the basis of the injunction sought in this case is simply the need for enforcing collateral estoppel more effectively than by forcing the defendant to plead it as a defense in case after case.

This is not the first time the Seventh Circuit has granted relief to a class-action defendant under the All Writs Act. But this opinion is noteworthy for the strong language Judge Posner uses in criticizing plaintiff's conduct, and the plain language he uses in describing the dilemma Sears faced.  It's also noteworthy for its explicit suggestion that a class-action defendant may seek an injunction before it has to assert collateral estoppel in a new case.  

(Also noteworthy, at least for this blog, is that the court cited the Class Acton Playbook in its discussion of plaintiff's strategic use of discovery.)

What Makes a Common Question Common?

All too often, courts and class-action litigants take the question of commonality for granted.  But, when framed properly, the question of commonality can provide a court with the tools necessary to engage in a truly rigorous analysis of a proposed class.

In his recent essay "Common Answers for Class Certification," noted professor Richard Nagareda takes the Ninth Circuit's recent Dukes decision and uses it as a platform to discuss what commonality really means in the context of a class action. In doing so, he provides an excellent analysis of how defense counsel can frame the question of commonality for courts deciding certification. As he puts it:

This Essay spotlights the crucial conceptual error in Dukes: its premise that the raising of common “questions” suffices for class certification. Properly understood, class certification does not turn upon the mere raising of common questions by way of expert submissions or any other form of evidence. Class certification instead turns on the capacity of a unitary proceeding to yield common answers.

Nagareda also points out that courts taking the alternative approach--looking only at whether the question is common, not whether they advance the litigation with common answers--are not wilfully misreading Rule 23.

The Dukes court acts on an understandable impulse—one whereby the format for adjudication inevitably would synchronize with the aggregate character of the allegations on the merits, at least when those allegations rise to the level of presenting a triable case.

Ultimately, Nagareda locates the issue in the fact that most courts are more used to determining issues on the merits than deciding class certification.

The fundamental problem with Dukes consists of the court’s confusion between the class certification determination and the most familiar type of pre-trial ruling that regulates the respective roles of the court and the fact finder at trial: summary judgment. On the Ninth Circuit’s account, the two are intertwined, such that the court regards itself as duty-bound not to withhold class certification when the plaintiffs have put forward a triable case as to the existence of a company-wide policy of discrimination on Wal-Mart’s part. Yet it is only if such a policy of nationwide scope exists that Wal-Mart has acted “on grounds that apply generally to the class,” so as to make appropriate relief “respecting the class as a whole” within the meaning of Rule 23(b)(2)—the basis for the Dukes certification.

In other words, a common question is not common unless the answer applies to the entire class no matter how it is decided.

What can defense lawyers take from Nagareda's analysis? It's always worth reminding the court of how a class trial would actually proceed. Walking the court through how it would have to decide questions on the merits can highlight where supposedly common questions aren't actually common at all.

Classic Cases - Sprague v. General Motors Corp.

The final "classic case" for now, Sprague v. General Motors Corp. involved an alleged violation of the Employee Retirement Income Security Act of 1974 (ERISA). The plaintiffs had sued GM claiming that it had not provided them with the fully "paid up" lifetime healthcare benefits it had promised when it convinced them to take early retirement. The trial court certified a class of 50,000 early retirees, and declined to certify a class of 34,000 general retirees. GM appealed the certification of the early retiree class, and the plaintiffs appealed the denial of certification of the general retiree class. The Sixth Circuit reversed the certification, and affirmed the denial of certification--a complete victory for the defendant. In doing so, it made several important holdings about commonality and typicality:

Commonality. As the court pointed out, a common issue had to have some level of specificity. (An issue discussed here before.) Otherwise, every mass lawsuit would meet the commonality requirement, simply because the question "are class members residents of the Milky Way Galaxy?" would be a common issue.

It is not every common question that will suffice, however; at a sufficiently abstract level of generalization, almost any set of claims can be said to display commonality. What we are looking for is a common issue the resolution of which will advance the litigation.

In other words, a common issue must be a common material issue.

Reliance.  The court also held that, because GM made different statements to different retirees, their ERISA claims were not suitable for class treatment.

GM's statements to the early retirees were not uniform. Among other things, the statements varied (1) based on the person making the representation, (2) based on the particular special early retirement pro- gram that applied, (3) from facility to facility, and (4) from time to time. Given the wide variety of representations made, there must have been variations in the early retirees' subjective understandings of the representations and in their reliance on them. Some retirees might have interpreted GM's statements to mean that their benefits were vested. Others might have understood that their benefits were subject to change. Some early retirees might have relied on GM's statements about health care benefits, while for others the statements might have made no difference at all in the decision to retire early.

Like the Fifth Circuit in Castano, the court here came up with a succinct description of the largest problem with classes that require a finding of reliance.

Typicality.  The most quoted part of the Sprague opinion involved typicality. The court held that plaintiffs had not met the typicality requirement because proving their claims would not prove the claims of the other class members. As the court put it:

In pursuing their own claims, the named plaintiffs could not advance the interests of the entire early retiree class. Each claim, after all, depended on each individual's particular interactions with GM-and these, as we have said, varied from person to person. A named plaintiff who proved his own claim would not necessarily have proved anybody else's claim. The premise of the typicality requirement is simply stated: as goes the claim of the named plaintiff, so go the claims of the class. That premise is not valid here.

(Internal citations omitted.)

The primary lesson defendants can derive from Sprague is a simple one: when possible, frame issues to show the court how resolving them will not advance the litigation for the whole class. After all, the point of allowing a class action to proceed is that proving the plaintiff's case will prove the class's case as well. If that underlying premise is false, then a class action is not appropriate.

Never Assume Commonality - Gaston v. Exelon Corp.

Commonality is rarely the subject of much discussion in class certification. The plaintiff often treats it as a perfunctory hurdle, subsumed into the more difficult questions of predominance (under Rule 23(b)(3)) or cohesiveness (under Rule 23(b)(2)).  But, much like numerosity, commonality is a requirement that may reward careful scrutiny when a defendant opposes class certification.

In Gaston v. Exelon Corp., 247 F.R.D. 75 (E.D. Pa. 2007), a group of African-American employees sued their employer for engaging in various policies (including its promotion and compensation decisions) that they claimed violated Title VII. They sought to represent a class of employees

who have been or may be subjected to Exelon's challenged policies and practices that deny Black exempt employees equal opportunity …

Exelon filed a motion to strike class allegations, which the court granted in part, ruling that no 23(b)(2) class was possible. When the plaintiffs later moved to certify a Rule 23(b)(3) class, the court actually found a number of problems with plaintiffs' class proposal. The class definition was not ascertainable. The named plaintiffs were subject to unique defenses, making them inadequate and atypical representatives. But the fundamental problem the court found was that the proposed common issues were not common.

In fact, the court took a Goldilocks-like approach to commonality (that is, if Goldilocks hadn't liked the baby bear's stuff either). It found that the proposed common issues were either too broad, too narrow or just plain irrelevant. What do I mean by too broad? As the court put it:

[P]laintiffs' first proposed question is “whether PECO's performance evaluation policy or practices negatively impact Class members.” Id. Were a question of this sort suitable to demonstrate commonality, that requirement would become a puff of smoke. Plaintiffs could simply propose the ques- tion “has employer discriminated against class mem- bers” and always meet the commonality requirement. Obviously, something more is necessary.

As for too narrow:

Other supposedly common questions that plaintiffs identify apply only to a small fraction of the proposed class. The question “whether Class members are less likely to be promoted into intermediate- or high-level salary grades than are otherwise-similar White employees,” for example, only applies to class members who were eligible for a promotion into those grades.

And finally, the court found that the remaining common questions had no bearing on the case itself.

Other questions, such as “whether Class members are less likely to be in high-level salary grades,” are simply irrelevant to a Title VII suit. As we discussed above, it is not sufficient for plaintiffs merely to identify a disparity in the representation of black employees in higher salary grades. They must also identify a pattern or practice of employment decisions during the class period that has resulted in this disparity.

What does this analysis mean for defendants? Despite the traditional view that commonality is a low hurdle for the plaintiff to clear, it is still worth challenging when the only common questions have nothing to do with the heart of the case.

Blog Author

Andrew J. Trask

photo of Andrew J. Trask Andrew Trask has defended more than 100 class actions, involving all stages of the litigation process. While his work hasMore...

Twitter Feed

@classstrategist McGuireWoods' Most Recent Twitter Posts