Ridgway v. Ford Dealer Computer Services, Inc.

Citation114 F.3d 94
Decision Date28 May 1997
Docket NumberNo. 96-1271,96-1271
Parties137 Lab.Cas. P 58,527, 47 Fed. R. Evid. Serv. 159 Robert RIDGWAY, Plaintiff-Appellee, v. FORD DEALER COMPUTER SERVICES, INC., Defendant-Appellant.
CourtUnited States Courts of Appeals. United States Court of Appeals (6th Circuit)

ARGUED: F. Mark Hugger, Ann Arbor, MI, for Appellee. John C. Allen, Houston, TX, for Appellant. ON BRIEF: F. Mark Hugger, Ann Arbor, MI, for Appellee. John C. Allen, Houston, TX, for Appellant.

Before: GUY, MOORE, and COLE, Circuit Judges.

OPINION

MOORE, Circuit Judge.

In this action for wrongful termination, Defendant-Appellant Ford Dealer Computer Services, Inc. ("FDCS") appeals from the judgment entered against it in favor of Plaintiff-Appellee Robert Ridgway following a jury verdict in Ridgway's favor. We affirm.

I. BACKGROUND

Robert Ridgway began working for Ford Motor Company in 1970. After holding a variety of positions at Ford, he became involved in the Dealer Computer Services division ("DCS"). In January 1992, Ford sold DCS to Ford Dealer Computer Services, which just had been incorporated. The sales agreement contained a provision that FDCS would provide a severance benefit to DCS employees terminated without cause within one year of the sale. Four months after the sale was consummated, FDCS fired Ridgway. When FDCS failed to pay Ridgway the severance package provided for in the agreement it entered into with Ford, Ridgway filed suit against Ford Motor Company and FDCS in Michigan state court, alleging four state-law causes of action. The defendants then removed the action to federal district court. Shortly after removal, Ridgway settled with Ford, leaving FDCS as the only remaining defendant. 1

Prior to trial, FDCS moved for summary judgment on the ground that Ridgway was neither a party nor a third-party beneficiary to its contract with Ford. Ridgway then voluntarily dismissed all his claims except for a single breach-of-contract claim against FDCS. The district court denied FDCS's motion for summary judgment, concluding that Ridgway was a third-party beneficiary to the contract between FDCS and Ford. The primary issue remaining for trial, then, was whether FDCS had cause to terminate Ridgway. The jury answered this question in the negative and awarded severance benefits to Ridgway. FDCS then filed this timely appeal, contending that the district court erred in concluding that Ridgway was a third-party beneficiary, that the court erroneously instructed the jury on the burden of proof, and that the court erred by not granting either FDCS's motion for judgment as a matter of law or its motion for a new trial.

II. THIRD-PARTY BENEFICIARY STATUS

FDCS contends that Ridgway did not plead a third-party beneficiary theory in his complaint and that even if such a theory were pleaded, the district court erred in determining that Ridgway was a third-party beneficiary of the contract between FDCS and Ford. Ridgway's complaint provides:

Defendants Ford and UCS[ 2] entered into a contractual relationship with Plaintiff which promised Plaintiff that during the first year following the transfer of DCS from Ford to UCS, his employment would not be terminated except for cause or in the alternative that should Plaintiff's employment be terminated during the first year absent just cause, Plaintiff would be compensated at his base salary for one year.

J.A. at 47-48 (Compl.p 37). Although this claim is not artfully worded, it adequately sets forth the third-party beneficiary theory and provided notice to FDCS of the nature of the claim. See Conley v. Gibson, 355 U.S. 41, 47-48, 78 S.Ct. 99, 102-103, 2 L.Ed.2d 80 (1957) (stating that under the liberal pleading requirements in the Federal Rules of Civil Procedure, the complaint must simply "adequately set forth a claim and [give the defendant] fair notice of its basis").

We likewise reject FDCS's argument that Ridgway was not a third-party beneficiary of the contract between FDCS and Ford. Michigan's third-party beneficiary statute provides in relevant part:

Sec. 1405. Any person for whose benefit a promise is made by way of contract, as hereinafter defined, has the same right to enforce said promise that he would have had if the said promise had been made directly to him as the promisee.

(1) A promise shall be construed to have been made for the benefit of a person whenever the promisor of said promise had undertaken to give or to do or refrain from doing something directly to or for said person.

M.C.L. § 600.1405. To determine the claiming party's status, an objective test that focuses on the contract itself is used. Paul v. Bogle, 193 Mich.App. 479, 484 N.W.2d 728, 735 (1992). "Where the contract is intended to primarily benefit its signatories, the mere fact that a third person would be incidentally benefitted does not entitle that person to its protection." Id.

FDCS contends that the contract provision at issue in this case primarily was intended to benefit Ford and FDCS and that any benefit flowing to Ridgway was only incidental. This argument fails in light of the plain language of the contract. The relevant section of the sales agreement provides: "In the event that within one year of the Closing Date (i) a DCS Regular Employee employed by FDCS is involuntarily terminated from employment with FDCS ... FDCS shall provide to such DCS Employee a severance benefit...." J.A. at 188. Ridgway correctly notes that the primary--if not the sole--purpose of this promise is to benefit the Ford DCS employees involuntarily transferred to FDCS. And while the primary purpose of the sales agreement as a whole may not have been to benefit Ford DCS employees, the relevant question is whether the "promise ... [was] made for the benefit of a person." M.C.L. § 600.1405 (emphasis added). In this case, it undoubtedly was.

III. BURDEN OF PROOF

FDCS contends that the district court erred by instructing the jury that FDCS had the burden to prove that Ridgway was not terminated for cause. It is well established in Michigan that in wrongful discharge cases based upon an employment contract, after the plaintiff proves the existence of a contract and his performance under the contract until the time of discharge, the burden shifts to the defendant to prove that there was "just cause" for the termination. See Turner v. Allstate Ins. Co., 902 F.2d 1208, 1210-11 (6th Cir.1990) (citing numerous Michigan cases). FDCS argues that this rule does not apply to the present dispute because it is undisputed that Ridgway was an employee at-will. Thus, appellant would have us recognize a difference for burden-of-proof purposes between cases dealing with contracts that promise not to terminate an employee except for just cause and cases dealing with contracts that promise not to deny a certain class of benefits to a former employee except for when that employee was terminated for just cause. FDCS has offered no reason why this difference is important, and we can find none. We thus conclude that the district court correctly placed the burden of proving just cause on FDCS.

IV. MOTION FOR JUDGMENT AS A MATTER OF LAW

After Ridgway rested his case, FDCS moved for judgment as a matter of law. The district court deferred ruling on the motion until after the close of the trial and then ultimately denied it. In reviewing a district court's ruling on a motion for judgment as a matter of law, "this circuit has long held that the state law standard controls in a diversity case." Engebretsen v. Fairchild Aircraft Corp., 21 F.3d 721, 726 (6th Cir.1994). 3 Under Michigan law, a judgment as a matter of law "may not be granted unless reasonable minds could not differ as to the conclusions to be drawn from the evidence." Toth v. Yoder Co., 749 F.2d 1190, 1194 (6th Cir.1984) (citing cases).

Appellant contends that the district court should have granted his motion for judgment as a matter of law because Ridgway failed to introduce the relevant contract into evidence during his case-in-chief. FDCS points to a Michigan Court of Appeals decision that provides: "When an action is based on a written contract, it is necessary to plead and produce the contract." Burrill v. Michigan, 90 Mich.App. 408, 282 N.W.2d 337, 339 (1979) (citing Michigan GCR § 113.4 (1963)). In essence, FDCS interprets Burrill as creating an additional element in contract claims based upon written contracts. Burrill, however, does nothing more than paraphrase a Michigan Court Rule governing pleadings filed in Michigan court. The pleading rule cited in Burrill provides in pertinent part: "Whenever a claim or defense is founded upon a written instrument ..., a copy of such instrument or the pertinent parts thereof shall be attached to the pleading as an exhibit...." Stocker v. Clark Ref. Corp., 41 Mich.App. 161, 199 N.W.2d 862, 864-65 (1972) (quoting Michigan GCR § 113.4 (1963)). 4 Because there is no indication that the rule cited in Burrill is anything more than a pleading requirement, and FDCS does not contend that Ridgway's complaint violated this requirement or that the district court in this case should have followed Michigan's pleading rules 5, FDCS's reliance on Burrill is misplaced.

Nonetheless, FDCS is correct that in the typical contract case based upon a written contract, the plaintiff must introduce the contract itself into evidence. Under the "best evidence" rule, "[t]o prove the content of a writing, recording, or photograph, the original writing, recording, or photograph is required, except as otherwise provided in these rules or by Act of Congress." FED.R.EVID. 1002. In this case, it is undisputed that only oral evidence regarding the contract and a summary of the relevant contract provision were admitted into evidence during Ridgway's case in-chief. The summary was contained in a letter sent to all DCS employees informing them of the imminent agreement between Ford and FDCS and of the various benefits the employees would continue to receive after the...

To continue reading

Request your trial
24 cases
  • Harris v. Wal-Mart Stores, Inc., Civil No. 1:13–cv–2218–JTF–egb.
    • United States
    • United States District Courts. 6th Circuit. Western District of Tennessee
    • September 15, 2014
    ...adequately sets forth a claim against the Defendants under the Equal Protection Clause. Ridgway v. Ford Dealer Computer Servs., Inc., 114 F.3d 94, 96 (6th Cir.1997). Defendants reply that the Supreme Court in Iqbal held that factual allegations are necessary in an equal protection claim to ......
  • Harris v. Wal-Mart Stores, Inc.
    • United States
    • United States District Courts. 6th Circuit. Western District of Tennessee
    • September 15, 2014
    ...adequately sets forth a claim against the Defendants under the Equal Protection Clause. Ridgway v. Ford Dealer Computer Servs., Inc., 114 F.3d 94, 96 (6th Cir.1997). Defendants reply that the Supreme Court in Iqbal held that factual allegations are necessary in an equal protection claim to ......
  • Tate Farm Fire & Cas. Co. v. Allied & Assocs.
    • United States
    • United States District Courts. 6th Circuit. United States District Court (Eastern District of Michigan)
    • March 19, 2012
    ...The Federal Rules of Civil Procedure govern the pleading requirements in federal court. Ridgway v. Ford Dealer Computer Servs., Inc., 114 F.3d 94, 98 n. 5 (6th Cir.1997) (“Of course, an argument that the federal district court should have followed Michigan's pleading requirements would have......
  • Tann v. Chase Home Fin. LLC, Case Number 10-14696
    • United States
    • United States District Courts. 6th Circuit. United States District Court (Eastern District of Michigan)
    • August 26, 2011
    ...inasmuch as federal rules govern the pleading requirements in federal court. 28 U.S.C. § 2702(b); Ridgway v. Ford Dealer Computer Servs., Inc., 114 F.3d 94, 98 n.5 (6th Cir. 1997) (quoting 5 Charles Alan Wright & Arthur R. Miller, Federal Practice and Procedure § 1204 (2d ed. 1990)); Long v......
  • Request a trial to view additional results

VLEX uses login cookies to provide you with a better browsing experience. If you click on 'Accept' or continue browsing this site we consider that you accept our cookie policy. ACCEPT