Spokeo left FCRA’s accuracy duty intact and made concrete harm the first question in a private suit

On May 16, 2016, the Supreme Court said a bare procedural violation of the FCRA does not by itself give a plaintiff standing. In our reading, it changed who could sue, not what the statute requires, and raised the value of evidence about each error.

Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.

Two-minute summaryThe dek and the first sentence of each section, quoted from the article

On May 16, 2016, the Supreme Court said a bare procedural violation of the FCRA does not by itself give a plaintiff standing. In our reading, it changed who could sue, not what the statute requires, and raised the value of evidence about each error.

  1. The week The case arose under the Fair Credit Reporting Act of 1970.
  2. The holding: concreteness as its own test Particularized means the injury affects the plaintiff in a personal and individual way. [1] Concrete means the injury actually exists; the Court said it meant real, not abstract. [1] The Ninth Circuit had found particularization and treated the question as answered.
  3. What did not change: the duties and public enforcement The opinion summarized several FCRA requirements on consumer reporting agencies.
  4. The litigation exposure: statutory damages meet a threshold For a willful violation, the FCRA lets a consumer recover actual damages or statutory damages of not less than $100 and not more than $1,000. [3] It adds punitive damages as the court allows, and costs and attorney’s fees. [3] Statutory damages do not require proof of a dollar loss.
  5. The evidence: which errors matter, and how to show it The Court’s zip code example made the content of an error a legal fact. [1] An organization that can show what the erroneous field was, and why it could not affect a decision, holds a stronger standing argument than one that can only say its procedures were followed.
  6. How the decision reached different organizations A bank uses consumer reports in credit decisions and, as a creditor, reports account information to consumer reporting agencies.
  7. Objections to our reading, taken in order Formally, yes.
  8. Checks a compliance or data leader could run These checks build the two-layer record Spokeo made valuable.
  9. With hindsight On remand, in an opinion filed August 15, 2017, the Ninth Circuit held that the plaintiff had alleged injuries sufficiently concrete for Article III standing. [5] It adopted a two-step test.

The week

On Monday, May 16, 2016, the Supreme Court decided Spokeo, Inc. v. Robins, No. 13-1339. [1] [2] The Court vacated a Ninth Circuit judgment and remanded the case. [2] The docket lists the Justices who joined the opinion of the Court, a concurring opinion and a dissenting opinion. [2]

The case arose under the Fair Credit Reporting Act of 1970. The Court described the Act’s requirement that consumer reporting agencies follow reasonable procedures to assure maximum possible accuracy of consumer reports. [1] It also described the Act’s remedy for willful noncompliance. [1] A person who willfully fails to comply is liable for actual damages or statutory damages of $100 to $1,000 per violation, plus costs, fees and possibly punitive damages. [1]

Spokeo operated what the Court called a people search engine. It searched a wide spectrum of databases and provided information about individuals, such as address, phone number, marital status, approximate age, occupation, hobbies, finances, shopping habits and musical preferences. [1] For purposes of its opinion, the Court assumed that Spokeo was a consumer reporting agency. [1]

A consumer found that his Spokeo profile was inaccurate. According to his complaint, it said he was married, had children, was in his fifties, had a job, was relatively affluent and held a graduate degree. He said all of it was wrong. [1] He filed a class action alleging that Spokeo willfully failed to comply with FCRA requirements. [1]

The District Court dismissed the complaint for lack of standing, finding he had not properly pleaded an injury in fact. The Ninth Circuit reversed. [1] It reasoned that he alleged a violation of his own statutory rights, and that his interests in the handling of his credit information were individualized rather than collective. [1]

The Supreme Court said that analysis was incomplete. An injury in fact must be both concrete and particularized, and the Ninth Circuit’s two observations concerned only particularization. [1] The Court said a concrete injury must actually exist, and that concrete is not necessarily synonymous with tangible. [1]

The Court said that history and the judgment of Congress both play important roles in deciding whether an intangible harm is concrete. [1] It said Article III standing requires a concrete injury even in the context of a statutory violation, so a plaintiff could not allege a bare procedural violation, divorced from any concrete harm. [1] It also said the risk of real harm can satisfy the requirement of concreteness. [1]

The Court gave examples. A consumer reporting agency might fail to give a required notice to a user of its information, while the information is entirely accurate. [1] And not all inaccuracies cause harm or present a material risk of harm. The Court said an incorrect zip code, without more, could hardly work any concrete harm. [1]

The Court said it took no position on whether the Ninth Circuit’s ultimate conclusion was correct. It sent the case back for that court to consider whether the particular violations alleged entailed a degree of risk sufficient to meet the concreteness requirement. [1]

Among the friends of the court, the opinion lists briefs urging reversal from a group of states led by Alabama, the American Bankers Association, the Consumer Data Industry Association, Experian, Trans Union and others. [1] Briefs urging affirmance came from a group of states led by Massachusetts, consumer and privacy organizations, and others; the United States argued as amicus urging affirmance. [1]

Spokeo reads as a standing case, a federal courts question for litigators. In our view it belongs in a data quality library too. The decision did not change a word of what the Fair Credit Reporting Act requires. It changed what a private plaintiff must show before a federal court will hear a claim that those requirements were broken. [1]

Our argument is that Spokeo moved the litigation question from whether a procedure was violated to whether a particular error or omission caused, or risked, real harm. In our reading, that made the content of each error, and the evidence of what was done with it, the center of the dispute. For banks and others that use or supply consumer data, the practical effect is that accuracy evidence answers both the compliance question and the litigation question. [1]

Its lesson for technology leaders is about records: what an organization can prove about each piece of data it handles. That is a question for data architecture as much as for legal strategy, because the proof has to be designed into systems before anyone asks for it.

We take the decision in four parts:

  1. The holding: concreteness as a separate requirement, and the role of history, Congress and risk.
  2. What did not change: the FCRA’s duties and its public enforcement, which do not depend on a private plaintiff’s standing.
  3. The litigation exposure: statutory damages, class actions and the threshold Spokeo set for them.
  4. The evidence: which errors matter, and how an organization shows what an error did or could have done.

The parts are separate. The first is the legal rule, the second is the regulatory duty it left alone, the third is the private risk it reshaped, and the fourth is the record that decides cases under it. After them we look at how the decision reached different organizations, take the objections in order, and end with checks a compliance or data leader could run. This is not legal advice; standing questions turn on facts and on each circuit’s law, and organizations should check with counsel.

The holding: concreteness as its own test

Two requirements, not one

The Court restated the three elements of standing: an injury in fact, fairly traceable to the defendant’s conduct, and likely to be redressed by a favorable decision. [1] It said injury in fact is the first and foremost, and requires an invasion of a legally protected interest that is concrete and particularized, and actual or imminent. [1]

Particularized means the injury affects the plaintiff in a personal and individual way. [1] Concrete means the injury actually exists; the Court said it meant real, not abstract. [1] The Ninth Circuit had found particularization and treated the question as answered. The Supreme Court said that elided the independent concreteness requirement. [1]

Intangible harm can count

The Court said intangible injuries can be concrete, citing free speech and free exercise cases. [1] To decide whether an intangible harm qualifies, it said courts should ask whether it has a close relationship to a harm traditionally regarded as a basis for a lawsuit in English or American courts. [1]

It said Congress’s judgment is also instructive and important, because Congress is well positioned to identify intangible harms meeting Article III’s minimum. [1] Congress may elevate to legally cognizable status concrete injuries that were previously inadequate in law. [1]

But a statute is not enough by itself

The Court then set the limit. Congress’s role does not mean a plaintiff automatically satisfies the injury requirement whenever a statute grants a right and authorizes suit. [1] Article III standing requires a concrete injury even in the context of a statutory violation. [1] A bare procedural violation, divorced from any concrete harm, does not satisfy it. [1]

Risk can be enough

The Court said this did not mean the risk of real harm could never satisfy concreteness. It pointed to libel and slander per se, where the common law permitted recovery even when harm was hard to prove or measure. [1] It said the violation of a procedural right granted by statute can be sufficient in some circumstances, so that a plaintiff need not allege any additional harm beyond the one Congress identified. [1]

Widely shared harm is still particular

The Court added a point that matters for data incidents and class actions. It said the fact that many people suffer an injury does not by itself make it a nonjusticiable generalized grievance. [1] Its example was a mass tort, where injuries are widely shared but each person suffers a particularized harm. [1]

In our reading, that footnote means Spokeo does not bar large classes by size alone. Size was not the problem. The problem was whether each member’s injury was concrete. A data error that hits a million records can still produce a million concrete injuries, if each error is material and is used or disclosed.

The two sources of guidance

The Court’s method has two inputs that pull in different directions. History asks whether a harm resembles one the common law recognized, such as defamation. [1] Congress’s judgment asks what harms the legislature chose to protect against, which the Court said is instructive and important. [1]

For the FCRA, the two inputs fit together well where false information is communicated to others, because that resembles defamation and is what Congress sought to curb. [1] They fit less well where the failure is a missing notice and the information is true. The Court’s examples traced that pattern. [1]

Applied to the FCRA

Applied to this statute, the Court said two things. Congress plainly sought to curb the dissemination of false information by adopting procedures designed to decrease that risk. [1] But the plaintiff could not satisfy Article III by alleging a bare procedural violation, because a violation of an FCRA procedure may result in no harm. [1]

The Court’s two examples define the range. An agency could fail to give a required notice while its information was accurate. And an inaccuracy might be trivial, as with a wrong zip code. [1] In a footnote, the Court said it expressed no view on other types of false information that might merit similar treatment, and left that for the Ninth Circuit. [1]

What the Court did not decide

The Court did not decide whether the plaintiff had standing. It said it took no position on the Ninth Circuit’s ultimate conclusion. [1] It also did not decide whether Spokeo was a consumer reporting agency; it assumed so for purposes of the opinion. [1] In our reading, the decision set a method and left its application to lower courts, which is why its effect depended on how they used it.

What did not change: the duties and public enforcement

The duties

The opinion summarized several FCRA requirements on consumer reporting agencies. They include following reasonable procedures to assure maximum possible accuracy, notifying providers and users of information of their responsibilities, limiting reports for employment purposes, and posting toll-free numbers for consumers to request reports. [1] Spokeo did not alter any of them.

That point is easy to lose in the litigation commentary. A consumer reporting agency’s duty to follow reasonable accuracy procedures exists whether or not any consumer could sue over a particular lapse. The same is true for the other actors the statute reaches, including users and furnishers of information, under provisions the case did not address.

What reasonable procedures look like

The accuracy duty the Court described is a duty to follow reasonable procedures to assure maximum possible accuracy. [1] It is a process standard. It asks whether the organization designed and ran sensible controls, not whether every record was right.

In data operations terms, those controls are familiar. They include validating data at intake, matching records to the right person, monitoring error rates by source, investigating disputes and feeding corrections back to the source. Each produces a record. Together they are the evidence a regulator would ask for, and, after Spokeo, part of the evidence a court would weigh on harm.

The two uses of the evidence differ. A regulator asks whether the system was reasonable. A court on a standing question asks what a particular error did. In our reading, an organization that keeps both system-level and record-level evidence can answer either question without building a new file under pressure.

Public enforcement

The FCRA also provides for administrative enforcement. The statute authorizes the Federal Trade Commission to enforce compliance against consumer reporting agencies and other persons subject to the Act. [4] The exceptions are where enforcement is committed to another agency listed in the statute, and the Act’s coordination with the Consumer Financial Protection Act. [4] It provides for civil penalties in actions for knowing violations that constitute a pattern or practice. [4]

The statute also gives states a role. A state’s chief law enforcement officer may sue to enjoin violations and may sue on behalf of the state’s residents to recover damages for which a person would be liable to them under the Act. [4]

In our reading, the standing doctrine in Spokeo concerns who may invoke a federal court’s jurisdiction as a private plaintiff. Government enforcement rests on a different footing. The case did not address it, and we do not suggest it affected agencies’ authority. The practical conclusion for compliance is that a narrower path for private suits leaves the public path where it was. [1] [4]

Who enforces against whom

The statute divides public enforcement. The FTC’s authority covers consumer reporting agencies and others subject to the Act, except where the statute commits enforcement to another agency. [4] The statute gives the FTC its investigative and enforcement powers under the FTC Act for this purpose, and treats a violation as an unfair or deceptive act or practice. [4]

For a regulated bank, the practical consequence is that its own supervisor may be the enforcer for FCRA duties, under the allocations the statute lists. For a nonbank data company, the FTC or the CFPB may be. In our reading, none of those paths requires a consumer with Article III standing, so Spokeo leaves them untouched. [4]

Why this matters for program design

A compliance program built to defeat private class actions would focus on the harm question. A program built to satisfy the statute and its public enforcers would focus on the procedures. Spokeo gave organizations a reason to be tempted by the first approach. The statute gave them no permission to drop the second.

The safest design treats them as one. Accurate data and documented procedures defeat both kinds of claim. Errors that are caught and corrected quickly reduce harm, and therefore reduce the facts a private plaintiff would need.

The litigation exposure: statutory damages meet a threshold

Why statutory damages mattered

For a willful violation, the FCRA lets a consumer recover actual damages or statutory damages of not less than $100 and not more than $1,000. [3] It adds punitive damages as the court allows, and costs and attorney’s fees. [3] Statutory damages do not require proof of a dollar loss. That is what made class actions over procedural violations attractive: each class member’s claim did not depend on showing individual loss.

The opinion did not change those remedies. It required each plaintiff invoking federal jurisdiction to show a concrete injury. [1] A footnote said a class action adds nothing to the standing question, because named plaintiffs must show they were personally injured. [1]

A threshold, not a defense on the merits

Standing is decided before the merits. In our reading, Spokeo gave defendants a way to contest a case at the pleading stage by asking whether the alleged violation caused or risked concrete harm. The opinion said that where a case is at the pleading stage, the plaintiff must clearly allege facts demonstrating each element of standing. [1]

That placed weight on the complaint’s description of the error. A complaint that alleges only that a procedure was not followed invites a standing challenge. A complaint that alleges a specific, material inaccuracy, communicated to someone, is harder to dismiss. The remand opinion in this very case turned on that difference. [5]

Willfulness is a separate hurdle

Statutory damages under section 1681n require willful noncompliance. [3] Spokeo did not address willfulness. In our reading, the two hurdles are independent: a plaintiff with standing must still show the violation was willful to reach statutory damages. Records that show an organization took its duties seriously bear on willfulness as well as on harm.

From pleading to proof

At the pleading stage, a court reads the complaint. The opinion said the plaintiff must clearly allege facts demonstrating each element of standing. [1] As a case moves forward, the facts about what an error said, who received it and how it was used become matters of proof. In our reading, that is where a defendant’s records begin to decide outcomes, for class certification as well as for individual claims.

Class membership and records

In our reading, Spokeo’s focus on individual injury makes class membership a data question. If a class is defined by people whose inaccurate reports were disseminated, the defendant’s dissemination records may decide who is in it. If the class is defined by people subject to a procedure, those records may show which members suffered only a procedural lapse. [1]

That gives the records a role beyond defense. They let an organization estimate its own exposure honestly, decide whether to settle, and identify consumers who were actually harmed and should be made whole. A remediation program built from the same data serves the consumers the statute protects.

The forum question

Article III governs federal courts. The opinion did not address whether a plaintiff without Article III standing could pursue an FCRA claim in a state court. We do not take a position on that question, which depends on state law. Organizations should ask counsel how their exposure differs by forum.

Notice claims

The Court’s first example was a consumer reporting agency’s failure to give a user the required notice of the user’s responsibilities, where the information was accurate. [1] In our reading, that example covers a family of duties that are about informing parties rather than about the data itself. A missed notice is a real compliance failure, and a regulator can act on it. [4]

For a private plaintiff, the opinion suggested such a failure may result in no harm at all. [1] Organizations should not read that as permission. Notices exist so that users handle data lawfully; a user who never learns its responsibilities is more likely to misuse the data, which produces the kind of harm that does support standing.

What plaintiffs adapted

A threshold rule also shapes how complaints are written. After Spokeo, a plaintiff seeking to stay in federal court had reason to describe the specific inaccuracy, who received it and what followed. The plaintiff’s allegations about his employment prospects are an example the Ninth Circuit relied on. [5] In our reading, that shift makes a defendant’s own records more important, because the complaint now points at facts those records can confirm or refute.

Which claims were most affected

In our reading, the Court’s examples point to two kinds of claim that became harder after Spokeo. The first is a pure notice or disclosure claim, where information was accurate and the only failure was procedural. [1] The second is a claim over an immaterial inaccuracy. [1] Claims over material inaccuracies, disseminated to others, were the kind the Court’s reasoning left open. [1]

In our reading, this sorting changed what a compliance team should fear more. The paperwork failure with accurate data became less likely to produce a federal class action. The substantive error with real consequences became, relatively, the main exposure. From a consumer’s point of view, that ordering is right too.

Settlement value

Any rule that makes it easier to dismiss a class claim early changes negotiating positions. We make no claim about how Spokeo changed settlement values or filing volumes, because we did not find an official source measuring them. The direction of the incentive, from the opinion’s logic, is that defendants with strong evidence about the content and use of an error gained arguments at the threshold.

The evidence: which errors matter, and how to show it

Content

The Court’s zip code example made the content of an error a legal fact. [1] An organization that can show what the erroneous field was, and why it could not affect a decision, holds a stronger standing argument than one that can only say its procedures were followed.

The remand opinion shows the other side. The Ninth Circuit held that inaccuracies about age, marital status, educational background and employment history could be deemed a real harm to employment prospects. [5] It said the allegations related facts substantially more likely to harm the plaintiff’s concrete interests than the Supreme Court’s zip code example. [5]

Communication

The remand opinion also relied on dissemination. It said both the challenged conduct and the injury had already occurred, because the report was published and the intangible injury had occurred. [5] It expressly did not consider whether a materially inaccurate report that was prepared but never published would cause concrete harm. [5]

In our reading, dissemination records therefore matter. An organization that can show who received a report, when and for what purpose can answer the question the courts were asking. One that cannot reconstruct who saw what is defending blind.

Use

Harm also depends on use. An inaccurate field in a report used to deny credit, set a price or decline employment presents a different risk from the same field in a report never used in a decision. Decision logs that record which data drove an outcome let an organization show the connection, or its absence.

Flattering errors

An error that makes a consumer look better can seem harmless. The remand opinion recorded a different view. It noted the CFPB’s argument that even flattering inaccuracies can hurt employment prospects, by making an employer doubt the applicant’s truthfulness or judge the applicant overqualified. [5]

The court said that determining whether a given inaccuracy would help or harm an individual is not always easily done. [5] In our reading, a data quality program should not triage errors by whether they flatter the consumer. It should triage by whether the field is the kind a decision maker relies on.

Mixed and matched records

Some material errors are wrong people rather than wrong values: one consumer’s data attached to another’s file. Matching logic decides which records belong together. An organization that can show its matching rules, their tests and their exception handling has evidence that speaks both to reasonable procedures and to how an error arose.

Correction

Correction shortens the period in which an error can cause harm. A dispute process that fixes errors quickly and records the fix narrows the window a plaintiff can point to. It also serves the statute’s purpose directly, which the Court described as curbing the dissemination of false information. [1]

A harm assessment, step by step

An organization can assess each confirmed error in a consistent way. First, identify the field and the wrong value. Second, classify the field by whether decision makers rely on it. Third, list who received the record while it was wrong. Fourth, find any decisions that used it. Fifth, record when and how it was corrected, and whether recipients were told.

That sequence mirrors the questions the Supreme Court and the remand court asked about content, dissemination and consequence. [1] [5] Done routinely, it produces a file for each error that serves remediation, regulators and, if needed, litigation. Done only after a lawsuit, it relies on logs that may no longer exist.

Retention

Evidence only helps if it still exists when it is needed. Logs of dissemination and use can be rotated out for storage reasons. An organization should set retention for these records with counsel, long enough to cover the period in which claims or examinations could reach them, and apply legal holds when a dispute begins.

Disputes as an early warning

Consumer disputes are a direct signal that a field is wrong. They also show which errors consumers notice, which are likely to include errors that affected them. In our reading, an organization that analyzes disputes by field and by source learns where its material errors come from. That analysis is the same one that tells it which errors would support a claim of concrete harm, and which procedures need fixing first.

Procedure records

None of this replaces evidence of procedures. The FCRA’s accuracy standard is about reasonable procedures, and the public enforcement path tests them. [1] [4] The point is that after Spokeo the record needs two layers: proof that procedures existed, and proof of what each error did. Data quality teams produce the second layer, which was once a litigation afterthought.

How the decision reached different organizations

A bank or credit union

A bank uses consumer reports in credit decisions and, as a creditor, reports account information to consumer reporting agencies. The Spokeo case concerned a reporting agency’s accuracy duty, not a bank’s duties. [1] In our reading, its standing analysis would apply to any FCRA claim a consumer brings in federal court, including claims against users and furnishers, though the content of each duty differs.

For a bank, the practical response is the same evidence discipline. Record what data was received, what was used in each decision, what was reported out, and how disputes were resolved. That record supports compliance with the statute and answers a standing challenge.

A health system or public agency as employer

Employers that obtain background reports are users of consumer reports for employment purposes, a use the opinion listed among the FCRA’s regulated purposes. [1] The opinion’s example of a notice failure with accurate information speaks directly to employment-screening paperwork. [1]

In our reading, Spokeo made purely procedural claims over screening forms harder to bring in federal court, without changing the requirements for those forms. An employer that relaxed its forms on that basis would be trading a litigation argument for a compliance violation, and the public enforcement path would still apply. [4]

A data broker or people-search service

Spokeo itself was the example. Its profiles drew on a wide spectrum of databases and covered personal details unrelated to credit. [1] The remand opinion found that errors about age, marriage, education and employment could harm employment prospects when published. [5] For a broker, the lesson was that the breadth of fields it sells is also the breadth of fields that can carry a material error.

A state agency that publishes or sells records

State agencies that sell or license records to data compilers are suppliers in the chain that produced Spokeo’s profiles. The decision did not address their duties. In our reading, the accuracy of public records feeds every report built from them, so an agency’s correction process reaches people it never deals with directly.

A lender using alternative data

Lenders that draw on data beyond traditional credit files face Spokeo’s questions in sharper form. The more fields a decision uses, the more fields can carry an error that affects the outcome. The Court’s distinction between trivial and material errors gives such lenders a way to rank fields by consequence, and to spend verification effort where errors would matter. [1]

A state attorney general’s office

State attorneys general appear in the case on both sides as amici. [1] The statute gives a state’s chief law enforcement officer authority to sue to enjoin violations and to recover damages on behalf of residents. [4] The decision did not address that state role, and we do not read it as changing it.

A broker-dealer or insurer

Insurers and broker-dealers also obtain consumer reports, for underwriting or account opening. The FCRA’s purposes listed in the opinion include insurance. [1] The same two-layer record applies: procedures, and evidence of what each error did.

Objections to our reading, taken in order

1. Spokeo was about standing, not compliance

Formally, yes. But a compliance leader decides where to spend money, and Spokeo changed which failures were more likely to produce federal class litigation. The decision also made the content and dissemination of errors legally relevant, which is a data quality question. [1] [5]

2. The remand shows nothing changed

On remand, the Ninth Circuit held that the plaintiff had alleged injuries sufficiently concrete for Article III standing. [5] That shows material, published inaccuracies still support suit, which is our point. It does not show that procedural claims with accurate data were unaffected; the Supreme Court’s own examples said they were. [1]

3. Organizations should optimize for litigation risk

Optimizing only for private litigation ignores the statute and its public enforcers, which Spokeo did not touch. [4] It also ignores the consumers the statute protects. The overlap between the two goals, accurate data and fast correction, is large enough to make a single program sensible.

4. The harm test is too vague to use

The Ninth Circuit said the Supreme Court gave little guidance beyond the zip code example about which inaccuracies are harmless. [5] That vagueness is a reason to keep evidence on content, dissemination and use, because the outcome depends on facts a court will weigh case by case. [5]

5. Later decisions superseded Spokeo

The Court decided TransUnion LLC v. Ramirez, another case from the Ninth Circuit, in 2021. [7] The Ninth Circuit’s remand decision in Spokeo applied Spokeo’s framework rather than replacing it. [5] We describe the 2021 case only through its docket, under Hindsight, and make no claim about whether it changed that framework.

6. Risk of harm lets any plaintiff speculate

The Court said the risk of real harm can satisfy concreteness, and some feared that would swallow the rule. [1] On remand the Ninth Circuit rejected the argument that the harm alleged was too speculative, but it did so because the report had been published and the injury had occurred. [5] The risk route still required a material error, which is a limit.

7. Spokeo shields careless data companies

A data company with sloppy procedures and errors that happen to be trivial may escape private suits. But the decision left public enforcement intact, and material errors that are published remain actionable, as the remand shows. [4] [5] The protection is for trivial errors, not careless systems.

Checks a compliance or data leader could run

These checks build the two-layer record Spokeo made valuable. Each works without predicting litigation.

Classify fields by consequence

For each field you supply or use in consumer decisions, record whether an error in it could plausibly affect a credit, insurance, employment or pricing outcome. The Court distinguished trivial errors from material ones; your data dictionary can too. [1]

Log dissemination

Keep a record of each report or data transmission: recipient, date and permissible purpose. The remand decision turned partly on publication. [5]

Log use

For automated decisions, store which data elements drove the outcome. That record answers the question whether an error was used, and supports adverse action notices.

Time corrections

Measure the time from a consumer’s dispute to correction, and from correction to notice to recipients where required. Faster correction shortens exposure and serves the statute’s purpose. [1]

Keep procedure evidence current

Document accuracy procedures, testing and exceptions, because public enforcement tests procedures directly. [4] A standing defense does not answer a regulator.

Test matching

Sample files where two consumers share a name or similar identifiers and confirm the records were kept apart. Record the test and its results. Mismatched records produce the material, disseminated errors that the remand court treated as concrete harm. [5]

Trace one error end to end

Pick a recently corrected error and reconstruct its life: when it entered, where it came from, who received it, what decisions used it and when it was fixed. If any step cannot be shown from records, that gap is the first thing to close.

Do not triage by flattery

Rank errors by whether the field drives decisions, not by whether the error helps or hurts the consumer. The remand court recorded the CFPB’s argument that flattering errors can harm. [5]

Set retention for the evidence

Agree with counsel how long to keep dissemination logs, decision logs and dispute records, and make sure routine log rotation does not delete them sooner.

Brief leadership on two exposures

Report private litigation exposure and public enforcement exposure separately. Spokeo affected the first and not the second, and a single risk rating hides that difference. [1] [4]

Review form compliance anyway

Audit notices and disclosures, including employment-screening forms, against the statute’s requirements. Spokeo made some procedural claims harder to bring; it did not make noncompliant forms lawful. [1]

With hindsight

On remand, in an opinion filed August 15, 2017, the Ninth Circuit held that the plaintiff had alleged injuries sufficiently concrete for Article III standing. [5] It adopted a two-step test. First, whether the statutory provisions were established to protect the plaintiff’s concrete interests, as opposed to purely procedural rights. Second, whether the specific violations alleged actually harm, or present a material risk of harm to, those interests. [5]

On the first step, the court said the FCRA provisions at issue were crafted to protect consumers’ concrete interests in accurate credit reporting about themselves. [5] On the second, it held that alleged inaccuracies about age, marital status, educational background and employment history could be deemed a real harm to employment prospects. [5]

The court rejected the argument that the harm was too speculative. It said both the conduct and the intangible injury had already occurred, because the inaccurate report was published. [5] It noted that the Supreme Court gave little guidance on which kinds of misinformation are harmless beyond the zip code example. [5] The Consumer Financial Protection Bureau appeared as amicus curiae in the remand appeal. [5] The court recorded the Bureau’s argument that even flattering inaccuracies can hurt employment prospects, by leading an employer to doubt an applicant’s truthfulness or judge the applicant overqualified. [5]

Spokeo petitioned the Supreme Court again, filing on December 4, 2017 after an extension of time. [6] Trans Union, the Chamber of Commerce, the Consumer Data Industry Association and others filed amicus briefs at that stage. [6] The docket for No. 17-806 records that the petition was denied on January 22, 2018. [6] The remand decision therefore stood.

The Court later decided TransUnion LLC v. Ramirez, No. 20-297, which came from the Ninth Circuit. Its docket records argument on March 30, 2021, with the United States participating as amicus curiae, and a judgment on June 25, 2021 that reversed the Ninth Circuit and remanded. [7] The docket shows two dissents, each joined by other Justices. [7]

We describe that case only through its docket, which records that the judgment issued on July 27, 2021. [7] We make no claim here about its reasoning or about how it applied Spokeo.

The remedies the opinion described remain in the statute’s text. We checked the 2023 edition of the United States Code on November 16, 2026. In it, section 1681n still provides for actual damages or statutory damages of $100 to $1,000 for willful noncompliance, with punitive damages and fees. [3] Section 1681s still provides for administrative enforcement by the FTC and other agencies, and for actions by states. [4]

What held up is the framework. The remand court asked whether the violations alleged caused or risked concrete harm, and answered by looking at the content and publication of specific errors. [5] What did not settle was the boundary between trivial and material error. The Ninth Circuit itself said the Supreme Court gave little guidance on it. [5] For data and compliance teams, that uncertainty is the reason to keep the evidence the framework rewards.

The broader lesson since 2016 is about where data quality belongs in an organization. Spokeo turned the content of individual errors into a legal fact, and the remand decision showed courts examining those facts field by field. [1] [5] A data team that can answer, for any record, what it said, who saw it and what it changed, is doing compliance work.

Spotted an error? Tell us and we will check it and correct the article where needed.

  • FCRA
  • Spokeo
  • standing
  • consumer reporting
  • data quality
  • class actions