When Does an Amended Complaint Relate Back in Federal Court?

March 15, 2011

Yesterday, the Seventh Circuit applied the United States Supreme Court’s decision in Krupski v. Costa Crociere S.p.A., 130 S. Ct. 2485 (2010), to a motion to amend a complaint that was filed after the applicable statute of limitations had run in Joseph v. Elan Motorsports Technologies Corp., Case No. 10-1420. The Court held that there are only 2 inquiries that a district court may make when deciding whether an amended complaint relates back to the date of the original one: 1) whether the defendant who is sought to be added by the amendment knew or should have known that the plaintiff, had it not been for a mistake, would have sued him instead or in addition to suing the named defendant; and 2) whether, even if so, the delay in the plaintiff’s discovering his mistake impaired the new defendant’s ability to defend himself.

In this case, the plaintiff signed an employment contract with Elan Motorsports Technologies, Inc. (“Elan Inc.”). He later filed a breach of contract claim under that contract against Elan Motorsports Technologies Racing Corp. (“Elan Corp.”), which is a separate corporation from Elan Inc. though affiliated with it. After the statute of limitations had expired, the plaintiff realized that he had sued the wrong corporate entity and sought leave to amend the complaint to change the defendant to Elan Inc. with relation back to the date of the original complaint. The district court (relying on 7th Circuit precedent) ruled that the proposed amended complaint did not relate back because “it is the plaintiff’s responsibility to determine the proper party to sue and to do so before the statute of limitations expires. The judge thought that since the amended complaint did not (in his view) relate back to the date of the original filing, permitting the amendment would be futile. And since the plaintiff acknowledged that Elan Corp. — the only defendant named in the original complaint — was not liable to him, the judge concluded that there was no controversy between the parties, and so he dismissed the suit, just as he would have done had it been abandoned by the plaintiff, or settled.

On appeal, the Court found that the district court’s actions were in error in a few ways. First, it concluded that the district court’s dismissal for lack of a controversy was an error.

Rule 15(c) is about relation back of amendments; it is not about whether to permit an amendment, which is the subject of Rules 15(a) and (b). Rule 15(a)(2), which governs amendments to pleadings before trial (and there hasn’t been a trial in this case, despite its age), allowed Wardrop to amend his complaint with the district court’s leave; the rule adds that “the court should freely give leave when justice so requires.” Amending the complaint to substitute the alleged contract breaker for the innocent affiliate was entirely proper; whether the amendment would relate back to the date when the original complaint was filed and thus defeat the defense of statute of limitations was a separate question. The judge should have allowed the amendment and then, believing that the amended complaint did not relate back, should have rendered judgment on the merits for both defendants — for Elan Corp., the original defendant, because it had not broken any contract with Wardrop, and for Elan Inc., added as a defendant by the amendment, because the statute of limitations for a suit against it based on the contract had expired.

The Court then acknowledged that the district court’s more serious error “was a forced error” because of the Supreme Court’s decision in Krupski changed the test for when a complaint relates back.

We had thought the focus should be on what the plaintiff knew or should have known, and by that criterion Wardrop indeed had failed to make the case for relation back because he had intended to sue Elan Corp. even though the other party to his contract was Elan Inc. From early in the case, moreover, filings by Elan Corp. — including a corporate disclosure statement that showed it was a separate corporation from Elan Inc. (it was Elan Inc.’s parent …) — should have alerted Wardrop’s lawyer to his mistake. It took him almost six years to discover it. His delay was inexcusable.

But the Supreme Court’s decision in Krupski, hewing closely to the language of Rule 15(c)(1)(C), has cut the ground out from under the district court’s decision. The only two inquiries that the district court is now permitted to make in deciding whether an amended complaint relates back to the date of the original one are, first, whether the defendant who is sought to be added by the amendment knew or should have known that the plaintiff, had it not been for a mistake, would have sued him instead or in addition to suing the named defendant; and second, whether, even if so, the delay in the plaintiff’s discovering his mistake impaired the new defendant’s ability to defend himself. …

The fact that the plaintiff was careless in failing to discover his mistake is relevant to a defendant’s claim of prejudice; the longer the delay in amending the complaint was, the likelier the new defendant is to have been placed at a disadvantage in the litigation. But carelessness is no longer a ground independent of prejudice for refusing to allow relation back.

Based on the facts of the case, the Court determined that the amendment should relate back.

Prejudice manufactured by a defendant is not a ground for refusing relation back. It’s like failing to mitigate damages. As soon as the employee we mentioned read Wardrop’s complaint, he knew, and therefore Elan Inc. knew, that Wardrop had sued the wrong entity. Elan Inc. sat on its haunches for almost six years while the litigation ground forward, and it would still be squatting on its haunches had Wardrop not finally woken up in 2009 and moved to substitute it as defendant. No prejudice accrued to Elan Inc. in the brief interval between the filing of Wardrop’s original complaint and the receipt of the complaint by the employee who had administered Wardrop’s contract. Elan Inc., if it had promptly disabused Wardrop of his mistake and he had amended his complaint forthwith, would have suffered no harm from delay in the amending of the complaint because there wouldn’t have been any delay. It brought on itself any harm it has suffered from delay, and can’t be allowed to gain an advantage from doing that.

The main takeaway from this case is the point mentioned earlier: an amended complaint relates back if 1) the defendant who is sought to be added by the amendment knew or should have known that the plaintiff, had it not been for a mistake, would have sued him instead or in addition to suing the named defendant; and 2) the delay in the plaintiff’s discovering his mistake prejudiced the new defendant’s ability to defend himself. The new defendant is not prejudiced if it has simply “sat on its haunches” and allowed the case to go forward against the wrong defendant.

Lessons:

  1. A district court should not dismiss a case for a lack of controversy merely because it has concluded that the plaintiff sued the wrong defendant and that an amended complaint does not relate back after the statute of limitations has run.
  2. An amended complaint relates back if 1) the defendant who is sought to be added by the amendment knew or should have known that the plaintiff, had it not been for a mistake, would have sued him instead or in addition to suing the named defendant; and 2) the delay in the plaintiff’s discovering his mistake prejudiced the new defendant’s ability to defend himself.
  3. A newly added defendant is not prejudiced under the relation-back analysis if it knew of the plaintiff’s mistake and did nothing to correct that mistake.
Brad A. Catlin
Price Waicukauski & Riley, LLC
Learn more about Brad and contact us
Download a copy of this article here
This entry was posted in Amending Pleadings, Procedure and tagged , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>