Defeating a statute of frauds motion: enforcing oral and partly-performed contracts

You sued on a contract. The defendant has moved to dismiss because nothing was reduced to a signed writing covering the deal you say was made. The [statute](/insights/glossary/statute) of frauds is one of the oldest defenses in Anglo-American law, and on its face it can seem unbeatable: no writing, no contract, case dismissed. In practice, the statute is riddled with exceptions, and the modern doctrine of partial performance, promissory estoppel, and merchant exceptions defeats far more statute-of-frauds motions than the statute itself supports.

This guide walks through how courts actually decide statute-of-frauds motions, the doctrinal escape hatches that survive the statute's text, and the structural moves that turn a seemingly fatal defense into a procedural skirmish. The Supreme Court's docket has been thin on the modern statute of frauds because most of the action plays out in state courts and under the Uniform Commercial Code, but the principal exceptions are universally recognized and well documented in the federal courts of appeals.

What the statute of frauds actually requires

Every state has a statute of frauds derived from the 1677 English original. The categories of contracts that must be in writing vary in detail but commonly include:

Contracts for the sale of an interest in land.
Contracts that cannot be performed within one year.
Contracts to answer for the debt of another (suretyship).
Contracts in consideration of marriage.
Contracts for the sale of goods at or above a threshold price (UCC 2-201 sets the federal default at $500; some states have raised the threshold).
Contracts of executors or administrators to pay estate debts from their own funds.

When a statute of frauds applies, it requires:

A writing.
Signed by the party to be charged (or that party's authorized agent).
Sufficient to evidence the essential terms of the contract.

The third requirement is where most statute-of-frauds defenses fail. Modern courts have read the writing requirement leniently. Letters, emails, internal memos, invoices, purchase orders, and even text messages can satisfy the statute when they reflect the essential terms. The signature requirement is satisfied by any mark made with intent to authenticate, including a typed name in an email signature block.

The signed-writing requirement is loose

Defendants often write statute-of-frauds motions as if the writing requirement demanded a formal contract document signed in ink on a single page. That is not the law. Courts have been remarkably accommodating about what counts as a writing and how multiple documents can be combined to satisfy the statute.

The leading authority on combining multiple writings is Crabtree v. Elizabeth Arden Sales Corp., 305 N.Y. 48, 55-56 (1953), which held that the statute is satisfied when one or more signed writings refer to or relate to one or more unsigned writings that together evidence the essential terms of the agreement. Most states have followed the Crabtree approach, and the federal courts apply it in diversity cases governed by Crabtree-state law.

What can be combined:

A signed offer letter and a signed acceptance.
A signed retainer agreement and unsigned scope-of-work attachments.
A series of emails between the parties where at least some are signed.
An invoice and a check.
A purchase order and a confirming letter.
Internal memos prepared by the party to be charged that document the deal terms.

The response brief should marshal every document in the parties' communications and arrange them to show that the essential terms appear, in writing, somewhere in the record. The defendant who insists on a single signed contract is asking for more than the statute requires.

The electronic age has further relaxed the signature requirement. The federal E-SIGN Act (15 U.S.C. § 7001) and the Uniform Electronic Transactions Act (adopted in nearly every state) provide that electronic signatures and electronic records satisfy any writing requirement, including the statute of frauds. A typed name at the bottom of an email is a signature. A clicked "I agree" button is a signature. A text message thread can be a writing.

Partial performance defeats the statute

The single most important exception to the statute of frauds is partial performance. The doctrine has different formulations in different states and different contexts, but the core idea is that when one party has performed in a way that confirms the existence of the alleged contract, the statute does not bar enforcement.

For contracts involving real property, partial performance typically requires some combination of:

Payment of the purchase price (in whole or in part).
Taking possession of the property.
Making substantial improvements to the property in reliance on the contract.

Two of these three are usually enough. The classic case is the buyer who pays a deposit, moves onto the land, and builds a house, only to have the seller invoke the statute when the time comes to convey title. Courts almost universally enforce the contract in that posture because refusing to do so would work a fraud on the buyer.

For contracts for the sale of goods under UCC 2-201, the partial performance exception is statutory: the contract is enforceable "with respect to goods for which payment has been made and accepted or which have been received and accepted." UCC 2-201(3)(c). When the buyer has paid for and received some portion of the goods, the contract is enforceable to that extent even without a writing.

The response brief should identify, with specificity, the acts of performance the plaintiff has undertaken and explain how those acts confirm the alleged contract. The court should be able to see that the performance is not consistent with any explanation other than the contract the plaintiff alleges.

Promissory estoppel under Restatement § 139

When the statute of frauds would otherwise bar enforcement, Restatement (Second) of Contracts § 139 provides an equitable escape hatch: a promise that the promisor should reasonably expect to induce action or forbearance is enforceable, notwithstanding the statute, if injustice can be avoided only by enforcement.

Section 139 lists factors the court considers:

The availability and adequacy of other remedies, particularly cancellation and restitution.
The definite and substantial character of the action or forbearance in relation to the remedy sought.
The extent to which the action or forbearance corroborates evidence of the making and terms of the promise.
The reasonableness of the action or forbearance.
The extent to which the action or forbearance was foreseeable by the promisor.

The Ninth Circuit's decision in McIntosh v. Murphy, 469 P.2d 177 (Haw. 1970), is a foundational application of § 139 in the employment context. The plaintiff moved across the country in reliance on an oral promise of a year-long employment contract that fell within the one-year provision of the statute of frauds. The court enforced the promise on promissory-estoppel grounds because the move was substantial, foreseeable, and corroborated the existence of the contract.

Federal courts apply § 139 broadly. A plaintiff who can plead substantial reliance on an oral promise often defeats a statute-of-frauds motion even where none of the other exceptions applies. The response brief should identify the specific reliance acts and explain how each maps onto the § 139 factors.

The merchant exception under UCC 2-201(2)

For contracts between merchants for the sale of goods, the UCC provides a powerful exception that defeats many statute-of-frauds defenses without any need for partial performance or estoppel theories.

UCC 2-201(2) provides that "between merchants if within a reasonable time a writing in confirmation of the contract and sufficient against the sender is received and the party receiving it has reason to know its contents, it satisfies the requirements of subsection (1) against such party unless written notice of objection to its contents is given within 10 days after it is received."

Translation: when one merchant sends another merchant a written confirmation of an oral deal, the recipient is bound unless it objects in writing within ten days. The Seventh Circuit's decision in Monetti, S.P.A. v. Anchor Hocking Corp., 931 F.2d 1178, 1183-84 (7th Cir. 1991), applied this exception to find a confirming writing sufficient where the recipient had failed to object within the statutory window.

The response brief facing a statute-of-frauds motion in a goods case between merchants should look for:

Any written confirmation sent by the plaintiff to the defendant after the alleged oral agreement.
Any indication that the defendant received the confirmation and did not object within ten days.
Any subsequent course of dealing consistent with the confirmed terms.

The merchant exception is unusual in that it shifts the writing requirement to the recipient by operation of silence. Defendants who failed to object in writing within ten days have effectively waived the statute of frauds.

The specially-manufactured-goods exception

UCC 2-201(3)(a) excepts from the writing requirement contracts for goods "specially manufactured for the buyer and not suitable for sale to others in the ordinary course of the seller's business" where the seller has made a substantial start on manufacture or commitments for procurement.

The exception is narrow but practical. When the goods are unique, custom, or branded for the specific buyer such that they cannot reasonably be sold to anyone else, and the seller has begun production, the contract is enforceable without a writing. The reasoning is that no rational seller would begin custom manufacture without an actual contract.

The response brief should plead the unique character of the goods, the seller's substantial start on manufacture, and the absence of any reasonable alternative buyer.

Admissions defeat the statute

UCC 2-201(3)(b) provides that the writing requirement does not apply "if the party against whom enforcement is sought admits in his pleading, testimony or otherwise in court that a contract for sale was made." A similar doctrine has been adopted by common law in many states for non-UCC contracts.

The admissions exception has teeth. A defendant who admits the existence of a contract in deposition testimony, in answers to interrogatories, in a verified pleading, or in court argument waives the statute of frauds for the contract terms admitted. Defense lawyers know this and try to thread the needle by admitting "discussions" but denying any concluded agreement. The response brief should comb the defendant's pleadings, discovery responses, and prior statements for admissions that can be used to defeat the statute.

Judicial estoppel and prior representations

Where the defendant has taken a contrary position in a prior proceeding, judicial estoppel may bar invocation of the statute of frauds. A defendant who represented in a prior case (or to a regulatory agency, lender, or tax authority) that a contract existed cannot turn around and deny the contract in litigation. The doctrine is equitable and discretionary, but it can be decisive when the prior representation is well documented.

How to plead around a statute-of-frauds motion

A statute-of-frauds defense is an affirmative defense, and it is rarely appropriate for resolution on a 12(b)(6) motion unless the complaint affirmatively pleads facts that bring the contract within the statute and forecloses every exception. A well-drafted complaint can usually leave enough room to defeat a pleading-stage motion.

The complaint should:

Allege the existence of the contract and its essential terms.
Identify any writings that confirm or evidence the contract (without necessarily attaching them).
Plead any acts of partial performance.
Plead any reliance facts that would support a promissory estoppel theory.
Avoid affirmative admissions that the contract falls within a statute-of-frauds category (where the answer is genuinely contested).

When the defendant moves to dismiss, the response brief should explain that the statute of frauds is an affirmative defense, that the defendant bears the burden of establishing both that the contract falls within the statute and that no exception applies, and that the question is unsuitable for resolution on the pleadings. See Jones v. Bock, 549 U.S. 199, 215 (2007) (affirmative defenses may be raised by motion to dismiss only when their applicability is clear from the face of the complaint).

How to brief the response

A clean statute-of-frauds response brief follows a predictable structure.

Introduction

Open with the relevant exception. "The Defendant invokes the statute of frauds, but the complaint pleads substantial partial performance by the Plaintiff, including payment of the deposit and three years of occupancy. Under the partial-performance doctrine, those acts are sufficient to take the contract out of the statute." Get the operative exception on the page in the first paragraph.

Background

Walk through the contract and the performance facts. Identify every writing in the parties' communications. Identify every act of performance. Identify every reliance act. The judge needs the factual hooks before evaluating the exceptions.

Legal standard

Cite the statute of frauds applicable in the forum (UCC 2-201 for goods, the state common-law statute for everything else). Cite Jones v. Bock for the proposition that affirmative defenses are usually not appropriate for 12(b)(6) resolution. Cite Crabtree for the multiple-writings doctrine if applicable. Cite the leading state authority on partial performance.

Argument

Take the exceptions in order of strength. Start with the strongest exception and work down. For each exception:

State the elements.
Identify the complaint allegations or attached documents that satisfy the elements.
Cite the controlling authority.

Do not concede that the contract falls within the statute unless the complaint affirmatively pleads it. Many statute-of-frauds motions can be defeated at the threshold by showing that the contract is not actually a contract subject to the statute.

Conclusion

Ask the court to deny the motion. In the alternative, ask for leave to amend to add facts supporting any exception the court finds insufficiently pleaded.

What the response must do

A statute-of-frauds response succeeds when it: identifies the specific statute the defendant invokes, marshals every writing in the record to satisfy the Crabtree multiple-writings doctrine, pleads partial performance with specificity, invokes Restatement § 139 promissory estoppel where reliance is substantial, deploys the UCC 2-201(2) merchant exception in goods cases, and frames the motion as inappropriate for resolution on the pleadings under Jones v. Bock. It fails when the response treats the writing requirement as absolute, ignores the merchant exception, or accepts the defendant's framing that no writing means no contract.

The statute of frauds was designed to prevent perjured claims of imaginary contracts, not to invalidate real agreements that were never reduced to a single signed document. A plaintiff who confronts a statute-of-frauds motion with the right framework usually finds that the modern exceptions reach further than the statute itself.