United States: Plaintiffs' Lawyers Try To Spin Spokeo

A peculiar thing happened after the Supreme Court announced its decision in Spokeo, Inc. v. Robins (pdf) on Monday.

Even though the Court ruled in favor of Spokeo—vacating the Ninth Circuit's ruling that the plaintiff had standing to sue and holding that the court of appeals had applied a legal standard too generous to plaintiffs—both sides declared victory. (Full disclosure: I argued on behalf of Spokeo in the Supreme Court.)

Spokeo tweeted:

Jay Edelson,

What's going on?

Spin—the effort to shape public perception that infects virtually every aspect of official Washington—has come to the world of Supreme Court rulings. The theory is that if you call a horse a cow with enough certainty and repetition, some people will say: "Yes, it's a cow." Others will report: "Opinion is divided. Some say the animal is a horse, some say it is a cow."

Here, the plaintiffs' loss is a matter of plain fact: the Ninth Circuit had held that Mr. Robins had standing to sue and the Supreme Court vacated that determination. The plaintiffs are worse off than they were before. And when viewed from a broader perspective, the decision will make life much more difficult for plaintiffs' lawyers who want to bring statutory-damages class actions.

Let's take a step back and examine what really happened in Spokeo. (If you're looking for a concise explanation of the Supreme Court's ruling, read our discussion.)

The Spokeo case is a classic example of the "no-injury class action." Here's how they work: a putative class action is filed on behalf of a very large potential class alleging violation of a federal or state statute that makes statutory damages available for violations. The plaintiff bases his or her standing to sue on the bare claim that the statute was violated—the claimed "injury in fact" is the statutory violation alone, not any "real" harm actually incurred or anticipated by the plaintiff.

Proof of the statutory violation by itself is claimed to establish everything the plaintiff needs to prevail: standing, the defendant's liability, and entitlement to statutory damages. And, the plaintiff inevitably asserts, class certification necessarily should follow because the only issue in the case—whether the statute was violated by the procedures employed by the defendant or the disclosures published by the defendant—is common to the whole class.

Plaintiffs have instituted hundreds of these class action lawsuits under a variety of statutes: the Fair Credit Reporting Act (invoked in Spokeo), the Telephone Consumer Protection Act, the Real Estate Settlement Procedures Act, the Video Privacy Protection Act and the Truth in Lending Act, and many state statutes. The amicus briefs filed in Spokeo by media companies (pdf), technology companies (pdf), and others (pdf), document the large number of these lawsuits and the exorbitant damages claims—often hundreds of millions or billions of dollars. Because many lower courts applied the same "rubber-stamp" standing rule as the Ninth Circuit, these cases often were permitted to proceed—even past the class certification stage, when they usually settled.

The named plaintiff in Spokeo, Mr. Robins, claimed that Spokeo, which operates a people search website, is subject to the Fair Credit Reporting Act and failed to comply with a number of that law's requirements. Claiming to represent a class of every individual about whom information is posted on Spokeo's website (more than 100 million people), the plaintiff sought statutory damages for each violation—which would have exceeded several billion dollars. (And the proposed class did not differentiate between people like Mr. Robins, who asserted that certain facts about him were inaccurate, and people for whom the information is accurate: everyone was in.)

Although Mr. Robins alleged that he had been affected adversely by inaccurate information posted about him, the district court found that the alleged adverse consequences were not sufficiently concrete to qualify as injury in fact under the Supreme Court's precedents. Robins appealed and the Ninth Circuit said it didn't have to address that question because the alleged statutory violations by themselves were sufficient to establish standing, even if Robins suffered no concrete—that is, "real" or actual—harm.

Spokeo asked the Supreme Court to determine whether the Ninth Circuit was correct, presenting the following question in its certiorari petition:

Whether Congress may confer Article III standing upon a plaintiff who suffers no concrete harm, and who therefore could not otherwise invoke the jurisdiction of a federal court, by authorizing a private right of action based on a bare violation of a federal statute.

The Supreme Court squarely answered that question "no." Here is the relevant passage from the Court's opinion:

Congress' role in identifying and elevating intangible harms does not mean that a plaintiff automatically satisfies the injury-in-fact requirement whenever a statute grants a person a statutory right and purports to authorize that person to sue to vindicate that right. Article III standing requires a concrete injury even in the context of a statutory violation.

A "bare" failure to comply with a statutory requirement "divorced from any concrete harm," the Court explained, cannot "satisfy the injury-in-fact requirement of Article III." The Ninth Circuit erred because it ignored the "concreteness" element, which requires that the plaintiff show that his or her alleged concrete harm "actually exist[s]" and that it is "'real,' and not 'abstract.'"

It is difficult to imagine a more complete rejection of the Ninth Circuit's rule, which the plaintiffs and their amici urged the Supreme Court to uphold.

Plaintiffs and their allies are claiming victory anyway

Perhaps they think they can rely on this passage of the Court's opinion: "the violation of a procedural right granted by statute can be sufficient in some circumstances to constitute injury in fact. In other words, a plaintiff in such a case need not allege any additional harm beyond the one Congress has identified." But all the Court is saying is that sometimes the cause of action itself requires proof of concrete harm, and in that case the plaintiff is not obliged to prove additional concrete harm beyond the harm required by statute. The Court wasn't saying that plaintiffs could avoid proof of concrete harm altogether.

The bottom line: the legal theory on which standing had been upheld in dozens of no-injury class actions is no longer valid and plaintiffs will have to find new arguments to justify standing to sue in these cases.

Why didn't the Supreme Court order the Ninth Circuit to dismiss the case? Because the plaintiffs, perhaps recognizing that they would lose on the "bare statutory violation constitutes injury in fact" contention, advanced new arguments to try to justify standing—arguments that had not been advanced in the Ninth Circuit. For example, they claimed that in the FCRA context, making available any false personal information about a consumer inflicts concrete harm; and that Congress had specifically determined that lawsuits in federal court were appropriate in that circumstance and that determination satisfied Article III's requirement.

The plaintiffs' claim of "victory" apparently rests on the fact that the Supreme Court did not opine on these new arguments. But that is wrong as a matter of Supreme Court procedure—the Court almost never addresses issues neither raised in nor addressed by the lower court. (Perhaps the caricatured view of the Supreme Court as reflexively anti-class action led some to believe that the Court would reach out to decide these issues; but that would have been inconsistent with the way the Court typically works.)

Most important, the plaintiffs' declaration of "victory" ignores the inconvertible facts that (a) plaintiffs now must establish standing based on an injury other than the mere existence of a statutory violation—a new obligation that did not exist before; (b) the Spokeo Court's discussion of the standards for determining the existence of the required concrete harm will impose a significant burden on plaintiffs in many cases; and (c) the obligation to establish concrete harm will make it much more difficult for plaintiffs to obtain class certification.

Given these facts, the declaration of victory by the plaintiffs' bar seems awfully hollow. And digging into these new obligations imposed on plaintiffs shows just how hard it will be for plaintiffs to establish standing without the "bare statutory violation" shortcut they have relied on in hundreds of past class actions.

The Obligation to Prove Concrete Harm

Although the Supreme Court did not resolve the new arguments raised by the plaintiffs, it did provide guidance regarding the meaning of the injury-in-fact standard and how it may be satisfied. That guidance indicates that the new burden that plaintiffs must carry—proving concrete harm rather than simply a statutory violation—is a heavy one.

To begin with, the Court emphasized that concrete harm is harm that "actually exist[s]" and that it is "'real,' and not 'abstract.'" It cited prior decisions making clear that harm can be either tangible—such as financial loss—or intangible. That statement simply reaffirms existing precedent: the Court has found the injury-in-fact test satisfied by claimed loss of enjoyment of parks and other government resources and by alleged discriminatory treatment based on race, sex or other prohibited characteristics (even if the discriminatory treatment has no financial consequences).

The Court also observed that its precedents made clear that the plaintiff need not have suffered concrete harm in order to sue: a "risk of real harm" can in some circumstances satisfy the concrete harm requirement. It cited its prior ruling in Clapper v. Amnesty International USA, which stated that a "'threatened injury must be certainly impending to constitute injury in fact,' and that '[a]llegations of possible future injury' are not sufficient."

Some of the post-decision statements by plaintiffs' lawyers indicate plans to argue that the violation of a statute constitutes intangible harm—essentially circumventing Spokeo's holding by asserting that every statutory violation inflicts intangible harm.

That word game is not going to work. The passages of the opinion discussed above make clear that the plaintiff must demonstrate harm (tangible or intangible) beyond the bare violation of a statute. Plaintiffs cannot avoid their obligation to demonstrate existing or impending concrete harm.

Another mischaracterization of Spokeo is the assertion by plaintiffs' lawyers that Spokeo argued that tangible injury (financial or otherwise) is required for injury in fact, and that the Court broke new ground in holding that concrete intangible harm can satisfy Article III. One advocate for the plaintiffs' bar, Paul Bland of Public Citizen, said that "[e]very justice agreed – the decision is unanimous – that consumers can bring claims for statutory damages . . . even if the consumer has not lost money or suffered a personal injury."

No "victory" for the plaintiffs' bar there. Spokeo didn't argue that financial loss or physical injury is required; it recognized in its briefs that some intangible injuries can satisfy Article III—the precedents regarding loss of enjoyment of national parks and race discrimination, for example. And the Court's recognition of its own precedents certainly plowed no new ground.

But Spokeo emphasized that not all claims of intangible injuries suffice.

The Court expressly agreed. It set forth a test for identifying the types of intangible injuries sufficient to permit suit in federal court. The Court said:

"[B]oth history and the judgment of Congress play important roles." Therefore "it is instructive to consider whether an alleged intangible harm has a close relationship to a harm that has traditionally been regarded as providing a basis for a lawsuit in English or American courts." And, Congress's judgment about whether a particular intangible harm satisfies Article III is "instructive and important."

These inquiries, of course, are statute-specific, because the injury-in-fact identified as the basis for standing is tied to two other standing requirements: the injury must be (as the Court explained in Lujan v. Defenders of Wildlife) "fairly traceable to the challenged action of the defendant" and it must be "likely, as opposed to merely speculative, that the injury will be redressed by a favorable decision."

How would the argument that the Spokeo plaintiffs advanced for the first time in the Supreme Court' argument—that conveying any inaccurate information about a person is sufficient to constitute concrete harm—fare under these standards? Poorly.

It plainly flunks the history test: A false statement, standing alone, almost never was sufficient to provide grounds for suit at common law. We explained in our briefs in Spokeo that no action lies for defamation (written or spoken, per se or otherwise) unless the challenged statement harms the plaintiff 's reputation—and the few situations in which harm was presumed from the false statement itself were limited to very specific statements virtually certain to inflict harm, such as an accusation of criminal activity or a claim that the plaintiff suffered from a serious communicable disease. (See the discussion at pages 49-52 of our opening brief (pdf), and pages 18-19 of our reply brief (pdf).)

And there is no evidence that Congress determined that every inaccurate statement inflicts harm sufficient to justify a lawsuit in court. That is because the statutory damages provision of the FCRA does not require proof of a false statement—rather, it applies across-the-board to every statutory violation, whether or not the violation involves a false statement. There accordingly is no congressional determination that is "instructive" about whether conveying false information always inflicts concrete harm. Congress simply did not address that issue. (See the discussion at pages 22-24 of our reply brief.)

To be sure, one of the purposes of the FCRA is to enhance the accuracy of credit information. But that does not mean that Congress intended every FCRA violation that leads to conveying any inaccurate information to be actionable. The Spokeo Court specifically stated that "not all inaccuracies cause harm or present any mate¬rial risk of harm. An example that comes readily to mind is an incorrect zip code."

In sum, plaintiffs will have a very hard time convincing a court that any inaccurate information, standing alone, inflicts concrete harm—and an even harder time prevailing on the theory of a "certainly impending" risk of harm based on inaccurate information.

The Impact on Class Certification

But even if plaintiffs could overcome that hurdle, they still would have to win class certification. And if harmful, or potentially harmful, inaccurate information about an individual is required to confer standing upon that individual,, then an individualized inquiry will be needed to determine whether each class member was the subject of inaccurate information that was sufficiently harmful to meet the constitutional standard. That is why Justice Kagan, at oral argument, asked counsel for the plaintiff the following question:

You said you you need for the information to be inaccurate to have standing here. That is going to mean that the class, as you've defined it, is not going to be certified. And I think that that's the right answer, but I just want to make sure that we're on the we're on the same page here.

As Justice Kagan observed, the significant burden of showing that information is "inaccurate" for each class member will make it much more difficult for a plaintiffs' lawyer to show that common issues predominate, as Federal Rule of Civil Procedure 23 requires. Similar difficulties for class certification are likely to attend cases under the TCPA; for example, a putative class member who never hears her landline phone ring could hardly assert that she had suffered "real" harm.

In short, while it may take some time to play out in the lower courts, Spokeo is a game-changer for defendants who face "no-injury" statutory damages class actions: plaintiffs will have to prove concrete injury, alleging a statutory violation is no longer enough; plaintiffs relying on intangible injury will have to provide that the claimed injury meets the "concreteness" test spelled out in Spokeo; and plaintiffs who do that will face new and significant challenges in obtaining class certification.

Hard to see the victory for the plaintiffs' bar in that.

Originally published May 18, 2016

Visit us at mayerbrown.com

Mayer Brown is a global legal services provider comprising legal practices that are separate entities (the "Mayer Brown Practices"). The Mayer Brown Practices are: Mayer Brown LLP and Mayer Brown Europe – Brussels LLP, both limited liability partnerships established in Illinois USA; Mayer Brown International LLP, a limited liability partnership incorporated in England and Wales (authorized and regulated by the Solicitors Regulation Authority and registered in England and Wales number OC 303359); Mayer Brown, a SELAS established in France; Mayer Brown JSM, a Hong Kong partnership and its associated entities in Asia; and Tauil & Chequer Advogados, a Brazilian law partnership with which Mayer Brown is associated. "Mayer Brown" and the Mayer Brown logo are the trademarks of the Mayer Brown Practices in their respective jurisdictions.

© Copyright 2016. The Mayer Brown Practices. All rights reserved.

This Mayer Brown article provides information and comments on legal issues and developments of interest. The foregoing is not a comprehensive treatment of the subject matter covered and is not intended to provide legal advice. Readers should seek specific legal advice before taking any action with respect to the matters discussed herein.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

Similar Articles
Relevancy Powered by MondaqAI
Carlton Fields
In association with
Related Topics
Similar Articles
Relevancy Powered by MondaqAI
Carlton Fields
Related Articles
Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Registration (you must scroll down to set your data preferences)

Mondaq Ltd requires you to register and provide information that personally identifies you, including your content preferences, for three primary purposes (full details of Mondaq’s use of your personal data can be found in our Privacy and Cookies Notice):

  • To allow you to personalize the Mondaq websites you are visiting to show content ("Content") relevant to your interests.
  • To enable features such as password reminder, news alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our content providers ("Contributors") who contribute Content for free for your use.

Mondaq hopes that our registered users will support us in maintaining our free to view business model by consenting to our use of your personal data as described below.

Mondaq has a "free to view" business model. Our services are paid for by Contributors in exchange for Mondaq providing them with access to information about who accesses their content. Once personal data is transferred to our Contributors they become a data controller of this personal data. They use it to measure the response that their articles are receiving, as a form of market research. They may also use it to provide Mondaq users with information about their products and services.

Details of each Contributor to which your personal data will be transferred is clearly stated within the Content that you access. For full details of how this Contributor will use your personal data, you should review the Contributor’s own Privacy Notice.

Please indicate your preference below:

Yes, I am happy to support Mondaq in maintaining its free to view business model by agreeing to allow Mondaq to share my personal data with Contributors whose Content I access
No, I do not want Mondaq to share my personal data with Contributors

Also please let us know whether you are happy to receive communications promoting products and services offered by Mondaq:

Yes, I am happy to received promotional communications from Mondaq
No, please do not send me promotional communications from Mondaq
Terms & Conditions

Mondaq.com (the Website) is owned and managed by Mondaq Ltd (Mondaq). Mondaq grants you a non-exclusive, revocable licence to access the Website and associated services, such as the Mondaq News Alerts (Services), subject to and in consideration of your compliance with the following terms and conditions of use (Terms). Your use of the Website and/or Services constitutes your agreement to the Terms. Mondaq may terminate your use of the Website and Services if you are in breach of these Terms or if Mondaq decides to terminate the licence granted hereunder for any reason whatsoever.

Use of www.mondaq.com

To Use Mondaq.com you must be: eighteen (18) years old or over; legally capable of entering into binding contracts; and not in any way prohibited by the applicable law to enter into these Terms in the jurisdiction which you are currently located.

You may use the Website as an unregistered user, however, you are required to register as a user if you wish to read the full text of the Content or to receive the Services.

You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these Terms or with the prior written consent of Mondaq. You may not use electronic or other means to extract details or information from the Content. Nor shall you extract information about users or Contributors in order to offer them any services or products.

In your use of the Website and/or Services you shall: comply with all applicable laws, regulations, directives and legislations which apply to your Use of the Website and/or Services in whatever country you are physically located including without limitation any and all consumer law, export control laws and regulations; provide to us true, correct and accurate information and promptly inform us in the event that any information that you have provided to us changes or becomes inaccurate; notify Mondaq immediately of any circumstances where you have reason to believe that any Intellectual Property Rights or any other rights of any third party may have been infringed; co-operate with reasonable security or other checks or requests for information made by Mondaq from time to time; and at all times be fully liable for the breach of any of these Terms by a third party using your login details to access the Website and/or Services

however, you shall not: do anything likely to impair, interfere with or damage or cause harm or distress to any persons, or the network; do anything that will infringe any Intellectual Property Rights or other rights of Mondaq or any third party; or use the Website, Services and/or Content otherwise than in accordance with these Terms; use any trade marks or service marks of Mondaq or the Contributors, or do anything which may be seen to take unfair advantage of the reputation and goodwill of Mondaq or the Contributors, or the Website, Services and/or Content.

Mondaq reserves the right, in its sole discretion, to take any action that it deems necessary and appropriate in the event it considers that there is a breach or threatened breach of the Terms.

Mondaq’s Rights and Obligations

Unless otherwise expressly set out to the contrary, nothing in these Terms shall serve to transfer from Mondaq to you, any Intellectual Property Rights owned by and/or licensed to Mondaq and all rights, title and interest in and to such Intellectual Property Rights will remain exclusively with Mondaq and/or its licensors.

Mondaq shall use its reasonable endeavours to make the Website and Services available to you at all times, but we cannot guarantee an uninterrupted and fault free service.

Mondaq reserves the right to make changes to the services and/or the Website or part thereof, from time to time, and we may add, remove, modify and/or vary any elements of features and functionalities of the Website or the services.

Mondaq also reserves the right from time to time to monitor your Use of the Website and/or services.


The Content is general information only. It is not intended to constitute legal advice or seek to be the complete and comprehensive statement of the law, nor is it intended to address your specific requirements or provide advice on which reliance should be placed. Mondaq and/or its Contributors and other suppliers make no representations about the suitability of the information contained in the Content for any purpose. All Content provided "as is" without warranty of any kind. Mondaq and/or its Contributors and other suppliers hereby exclude and disclaim all representations, warranties or guarantees with regard to the Content, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. To the maximum extent permitted by law, Mondaq expressly excludes all representations, warranties, obligations, and liabilities arising out of or in connection with all Content. In no event shall Mondaq and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use of the Content or performance of Mondaq’s Services.


Mondaq may alter or amend these Terms by amending them on the Website. By continuing to Use the Services and/or the Website after such amendment, you will be deemed to have accepted any amendment to these Terms.

These Terms shall be governed by and construed in accordance with the laws of England and Wales and you irrevocably submit to the exclusive jurisdiction of the courts of England and Wales to settle any dispute which may arise out of or in connection with these Terms. If you live outside the United Kingdom, English law shall apply only to the extent that English law shall not deprive you of any legal protection accorded in accordance with the law of the place where you are habitually resident ("Local Law"). In the event English law deprives you of any legal protection which is accorded to you under Local Law, then these terms shall be governed by Local Law and any dispute or claim arising out of or in connection with these Terms shall be subject to the non-exclusive jurisdiction of the courts where you are habitually resident.

You may print and keep a copy of these Terms, which form the entire agreement between you and Mondaq and supersede any other communications or advertising in respect of the Service and/or the Website.

No delay in exercising or non-exercise by you and/or Mondaq of any of its rights under or in connection with these Terms shall operate as a waiver or release of each of your or Mondaq’s right. Rather, any such waiver or release must be specifically granted in writing signed by the party granting it.

If any part of these Terms is held unenforceable, that part shall be enforced to the maximum extent permissible so as to give effect to the intent of the parties, and the Terms shall continue in full force and effect.

Mondaq shall not incur any liability to you on account of any loss or damage resulting from any delay or failure to perform all or any part of these Terms if such delay or failure is caused, in whole or in part, by events, occurrences, or causes beyond the control of Mondaq. Such events, occurrences or causes will include, without limitation, acts of God, strikes, lockouts, server and network failure, riots, acts of war, earthquakes, fire and explosions.

By clicking Register you state you have read and agree to our Terms and Conditions