Module 2: Pleadings, Motions & Joinder

Rule 8(a)(2) requires only a short and plain statement of the claim showing entitlement to relief. But Twombly and Iqbal refined this into the plausibility standard: the complaint must include enough factual content to state a claim that’s plausible on its face, not merely conceivable — bare legal conclusions and formulaic recitations of the elements aren’t enough.

The two cases behind the standard have real, different facts worth knowing. Bell Atlantic Corp. v. Twombly, 550 U.S. 544 (2007), involved an antitrust conspiracy claim alleging that major telecom companies had unlawfully agreed not to compete with each other; the complaint’s only real support was that the companies had, in fact, behaved in parallel ways. The Supreme Court held that parallel conduct alone is equally consistent with ordinary, lawful independent business decisions, so a complaint needs enough factual content to nudge the claim from merely conceivable to actually plausible. Ashcroft v. Iqbal, 556 U.S. 662 (2009), extended the same standard beyond antitrust to every federal civil case, and applied it even more strictly: a Muslim man detained after September 11 sued the former Attorney General and FBI Director personally, alleging they had adopted a discriminatory detention policy, but the Court held the complaint’s allegations that they “knew of, condoned, and willfully and maliciously agreed to subject” him to harsh conditions were exactly the kind of bare, conclusory assertions the plausibility standard was designed to screen out, regardless of how serious the underlying allegations were.

Example. “Defendant breached the contract” alone is a bare conclusion. “Defendant agreed in writing to deliver 500 units by June 1, delivered only 200, and refused to deliver the rest despite repeated requests” supplies the factual content that makes the breach claim plausible.

A defendant can respond with a Rule 12(b)(6) motion to dismiss for failure to state a claim, among other Rule 12 motions. Critically, lack of personal jurisdiction, improper venue, insufficient process, and insufficient service of process must all be consolidated into the defendant’s first Rule 12 motion (or the answer, if no motion is filed) — omitting an available one waives it. Lack of subject matter jurisdiction, by contrast, can never be waived and may be raised at any time, even for the first time on appeal.

Insurance Corp. of Ireland v. Compagnie des Bauxites de Guinee, 456 U.S. 694 (1982), explains exactly why personal jurisdiction and subject matter jurisdiction are treated so differently on the waiver question. A group of foreign insurance companies repeatedly refused to comply with discovery aimed at establishing whether the court had personal jurisdiction over them; as a sanction, the district court held that their jurisdictional objection was deemed conceded, and the insurers argued on appeal that personal jurisdiction is a constitutional due process right that can never simply be presumed away. The Supreme Court disagreed, explaining that personal jurisdiction, unlike subject matter jurisdiction, exists to protect an individual defendant’s own liberty interest — and a purely personal right, unlike the structural limits on a federal court’s constitutional and statutory power, can be waived by the party it protects, whether through an explicit failure to raise it in time or through litigation misconduct like discovery noncompliance. The case is the doctrinal foundation for why Rule 12’s waiver trap makes sense: subject matter jurisdiction limits the court itself, so no party can waive it, while personal jurisdiction protects the defendant, so the defendant can.

Example. A defendant moves to dismiss for failure to state a claim but never mentions insufficient service of process, even though it was available. That defense is now waived — it can’t be raised later in the answer, unlike the ever-available subject matter jurisdiction defense.

Rule 15 governs amending pleadings. The relation-back doctrine can save an otherwise time-barred amendment: if the amendment arises from the same conduct, transaction, or occurrence as the original pleading, it’s treated as filed on the original pleading’s date, even if the statute of limitations has since run.

Krupski v. Costa Crociere S.p.A., 560 U.S. 538 (2010), addresses the harder version of relation back: amending not just a new legal theory, but the identity of a party. A cruise passenger injured aboard ship sued the wrong corporate entity — the ticket’s fine print actually identified a different, related company as the proper defendant, something the passenger’s attorney only realized after the statute of limitations had run. The defendant argued relation back shouldn’t apply because the passenger knew (or should have known) the correct company’s identity from the start, calling it a deliberate choice rather than a genuine mistake. The Supreme Court disagreed, holding that Rule 15(c)’s relation-back inquiry focuses on what the new defendant knew or should have known about the plaintiff’s mistake — not on how careful or diligent the plaintiff itself had been in identifying the right party. If the proper defendant knew it was the intended target all along (as the related corporate entity here likely did), relation back can save the amendment even where the plaintiff’s own error looks more like carelessness than an honest mix-up.

Example. A plaintiff sues over a car accident and, after the statute of limitations runs, amends the complaint to add a new theory of negligence about the same crash. Because it’s the same underlying occurrence, the amendment relates back and isn’t time-barred.

Rule 18 lets a party join essentially any claims it has against an opposing party, related or not. Rule 20 permissive joinder of parties requires claims arising from the same transaction or occurrence (or a related series) with a common question. Rule 19 asks whether an absent party is necessary — whether complete relief is possible without them, or their own interest would be impaired or create a risk of inconsistent obligations.

Mosley v. General Motors Corp., 497 F.2d 1330 (8th Cir. 1974), reads Rule 20’s “same transaction, occurrence, or series of transactions or occurrences” requirement broadly rather than narrowly. Ten different employees, each alleging racial and sex discrimination by the same employer through different supervisors and different specific incidents, joined together as co-plaintiffs in a single lawsuit; the employer argued their claims were really ten separate, individual disputes that happened to share only a common defendant and a common legal theory, not a genuine common transaction. The Eighth Circuit disagreed, holding that a company-wide policy or practice of discrimination can itself supply the necessary transactional link between otherwise distinct individual incidents, and that Rule 20’s “series of transactions or occurrences” language should be construed liberally to promote trial convenience and avoid a multiplicity of separate lawsuits. The case remains a leading authority for allowing joinder in employment discrimination and civil rights cases where an underlying common policy, rather than one single shared event, ties the individual plaintiffs’ claims together.

Example. Two pedestrians hit by the same car in the same accident can be permissively joined as co-plaintiffs under Rule 20 — same occurrence, common questions about the driver’s negligence.

A compulsory counterclaim (Rule 13(a)) arises from the same transaction or occurrence as the opposing party’s claim and must be raised now or is generally lost. A permissive counterclaim (Rule 13(b)) doesn’t, and isn’t waived by omission. A crossclaim runs between co-parties, like one co-defendant against another. Impleader (Rule 14) lets a defending party bring in a third party who may owe indemnity or contribution.

Courts don’t apply a single rigid test to decide whether a counterclaim really arises from the “same transaction or occurrence.” The most widely used approach, the logical relationship test, traces back to Moore v. New York Cotton Exchange, 270 U.S. 593 (1926) — decided decades before the modern Federal Rules even existed, under an earlier equity rule with nearly identical language. A cotton exchange sued a competitor for wrongfully obtaining and republishing its price quotations; the competitor counterclaimed that the exchange itself had unlawfully violated antitrust law by cutting off the competitor’s access to those quotations in the first place. Even though the two claims rested on very different legal theories (unfair competition versus antitrust), the Supreme Court held they arose from the same transaction because they were logically related — resolving one necessarily required examining much of the same underlying conduct and evidence as the other. That logical-relationship approach, rather than demanding the claims share every specific fact, is still the dominant test federal courts use today to decide whether a counterclaim is compulsory.

Example. Sued for a defective product, a retailer impleads the manufacturer who actually made the defective part, seeking indemnity if the retailer is found liable — resolving the whole chain of responsibility in one case.

Rule 23(a) requires numerosity, commonality, typicality, and adequacy of representation. A Rule 23(b)(3) damages class additionally requires predominance (common questions outweigh individual ones) and superiority (a class action is the best available method).

Wal-Mart Stores, Inc. v. Dukes, 564 U.S. 338 (2011), sharply tightened what commonality actually requires. A proposed nationwide class of roughly 1.5 million current and former female Wal-Mart employees alleged the company’s policy of giving individual store managers broad, subjective discretion over pay and promotion decisions had resulted in company-wide sex discrimination. The Supreme Court rejected class certification, holding that commonality requires more than simply raising some common question — it requires the class’s claims to depend on a common contention capable of a single, class-wide answer that will resolve an issue central to every member’s claim in one stroke. Because store managers exercised genuinely individualized, decentralized discretion rather than following one uniform, centrally imposed policy, the reasons behind any given pay or promotion decision would vary from store to store and manager to manager, meaning there was no single common answer that could resolve the discrimination question for the class as a whole. The case remains the leading authority making commonality a real, substantive hurdle rather than the practically automatic requirement it had often been treated as before.

Example. Thousands of consumers who bought the same defective product, each with a nearly identical claim about the same defect, are a strong candidate for class certification — numerous, with common questions clearly predominating.