返回 Skill 列表
extension
分类: 开发与工程无需 API Key

class-certification-motion

根据联邦民事诉讼规则23或州级等效规则起草集体认证动议,从案件材料中论证数量性、共同性、典型性、充分性、主导性和优越性。在起草集体认证动议、寻求集体处理或在发现阶段或审前阶段准备规则23简报时使用。

person作者: jakexiaohubgithub

Motion for Class Certification

Produces a plaintiff-side FRCP 23 (or state equivalent) class certification motion grounded in case-file evidence and structured for rigorous judicial scrutiny.

Prerequisites

  1. Pleadings — complaint, answer, amended pleadings
  2. Discovery materials — interrogatories, document productions, RFAs, defendant's business records showing scope of conduct
  3. Expert reports — damages models, class-wide proof methodology, statistical analyses
  4. Deposition transcripts — named plaintiff(s), corporate designees, key witnesses
  5. Named plaintiff declaration — representative-role understanding, absence of conflicts
  6. Class counsel qualifications — CV/firm resume, prior class action experience, resources

Quick Start

  1. Review case materials and identify the uniform policy/practice at issue
  2. Draft a precise, administrable class definition tied to the liability theory
  3. Build Rule 23(a) arguments from discovery evidence
  4. Select and brief the applicable Rule 23(b) subsection
  5. Propose notice/administration plan and case management approach
  6. Preempt anticipated defense arguments with record citations

Core Workflow

1. Introduction (1–2 pages)

State defendant's specific misconduct, proposed class definition (temporal/geographic scope), approximate class size, common injury, and why joinder is impracticable.

2. Class Definition

The definition must:

  • Track the liability theory (not merits outcomes)
  • Be administratively manageable via objective criteria
  • Specify dates corresponding to period of misconduct
  • Match geographic scope to defendant's conduct and applicable law
  • Require no individualized inquiry for membership

3. Rule 23(a) Prerequisites

Numerosity — Cite defendant's records, discovery data, or expert estimates. Address geographic dispersion and economic infeasibility of individual suits. For negative-value claims, show individual recovery < litigation costs.

Commonality — Apply Wal-Mart v. Dukes, 564 U.S. 338 (2011): identify common questions generating common answers. Focus on uniform policies, standardized contracts, common course of conduct. Distinguish substantial common questions from peripheral individual ones.

Typicality — Show named plaintiff suffered the same injury type through the same mechanism. Cite specific evidence. Address unique-defense arguments; distinguish damages quantum from liability theory.

Adequacy — Named plaintiff: case knowledge, commitment, no conflicts. Class counsel: prior class actions, results, judicial recognition, resources, co-counsel arrangements.

4. Rule 23(b) Analysis

Select the applicable subsection:

| Subsection | Standard | Key Proof | |---|---|---| | 23(b)(3) | Predominance + superiority | Common evidence per claim element; common damages methodology; superiority over alternatives | | 23(b)(2) | Generally applicable conduct | Uniform injunctive/declaratory relief; address whether monetary claims are incidental | | 23(b)(1)(A) | Inconsistent obligations risk | Separate actions would impose contradictory requirements | | 23(b)(1)(B) | Impaired interests risk | Individual adjudications would practically dispose of absent members' claims |

For 23(b)(3) predominance, analyze element-by-element:

  1. Identify common proof method for each claim element
  2. Show common damages methodology — distinguish amount variation (acceptable) from methodology variation (problematic)
  3. Integrate expert findings on class-wide proof feasibility
  4. Address reliance/causation through presumptions or burden-shifting frameworks

For superiority: economics of individual claims vs. litigation costs, inconsistent-adjudication risk, concentration benefits, existing individual litigation.

5. Notice and Administration Plan

  • Identification method from defendant's records
  • Plain-language notice (lawsuit nature, class definition, opt-out rights, binding effect)
  • Distribution methods (direct mail, email, publication, digital) with justification
  • Cost estimates and allocation
  • Claims administration process

6. Case Management Proposal

Address as applicable: liability/damages bifurcation, bellwether trials, statistical sampling, special master appointment, subclass structure.

7. Anticipatory Defense

| Defense Argument | Response Strategy | |---|---| | Individual issues predominate | Common proof resolves core liability; individual damages manageable post-certification | | Class unmanageable | Propose specific tools: bifurcation, sampling, special master | | Named plaintiff atypical/inadequate | Distinguish damages variation from liability-theory divergence | | Class definition overbroad | Definition tracks liability theory with objective, administrable criteria | | Ascertainability problems | Objective identification from defendant's own records | | Subclass conflicts | Aligned interests on core liability; propose subclasses only if necessary |

8. Conclusion

Restate class definition, specify requested relief (certify class, appoint representative, appoint counsel), reference notice plan and case management procedures, request hearing if warranted.

Pitfalls and Checks

  • Pinpoint citations required — every factual assertion must cite document name, page, paragraph, exhibit number. No document-level references.
  • Jurisdiction-specific standards — circuits vary on predominance, ascertainability, and merits scrutiny. Identify and apply controlling precedent.
  • Certification ≠ summary judgment — present enough merits evidence for certification without fully litigating the merits.
  • FRE 702 / Daubert-Frye — ensure expert methodology survives reliability challenge under the applicable standard.
  • Adverse authority — distinguish unfavorable cases as factually distinguishable, superseded, or inapposite. Never ignore them.
  • Tone — professional, confident, evidence-driven. No hyperbole.
  • Length — 25–50 pages depending on complexity and local rules.