California Demurrer — Contract Claims

A contract count that alleges "the parties entered into an agreement" without identifying which provision was breached, what its terms were, or how the defendant's conduct departed from them is the most common contract-demurrer target in California. The doctrinal anchor is Otworth: a written contract may be pled by attachment, by verbatim recital, or by legal effect — but legal effect requires sufficient precision that the court can determine whether the alleged conduct constitutes a breach. The recurring failure mode is the litigator who treats "alleging a contract" as a one-paragraph throat-clearing exercise rather than as a load-bearing pleading move.

If you're the moving party: Quote the complaint's contract allegations directly in the demurrer and identify what is missing — the term breached, the obligation owed, the language said to govern. Frame the motion as "the complaint asks the court and the defendant to imagine the agreement." Where the contract is alleged to be written but not attached, the missing exhibit is itself a Heritage Pacific problem worth flagging.

If you're the opposing party: Amend by attachment if you have the document, or by verbatim recital if you have the language. If you must plead by legal effect, identify the specific provision (with section number, defined-term reference, or paraphrase tight enough to identify the operative language) and walk through how the alleged conduct violates it. "The defendant breached the agreement" is a label; "the defendant failed to deliver the promised quantity by the date specified in Section 3.2" is a pleading.

Primary source: Otworth v. Southern Pacific Transportation Co. (1985) 166 Cal.App.3d 452, 458-459; Heritage Pacific Financial, LLC v. Monroy (2013) 215 Cal.App.4th 972, 993.

Code of Civil Procedure § 430.10(g) is the only specific demurrer ground in California that names a contract pleading defect by code section. A complaint that gestures at "a contract" or "an agreement" without alleging whether the contract is oral, written, or implied by conduct draws a textbook (g) demurrer. The recurring failure mode is treating the form question as administrative — the cost is that form drives the SOL (§ 337 vs. § 339), drives the statute of frauds, and drives the parol-evidence rule, so leaving it out hands the defendant three demurrer angles instead of one.

If you're the moving party: Cite § 430.10(g) by code section as a separate ground in the demurrer's grounds-paragraph format (CRC 3.1320(a)). Do not bury the (g) attack inside an (e) argument — the rule has its own standalone weight, and a separately-pleaded (g) ground signals the court that the defendant has run the form analysis. Where the form question telegraphs a downstream SOL or statute-of-frauds defect, preview that defect in the (g) argument so the court sees the connected issue.

If you're the opposing party: Amend with the form allegation in the very next paragraph after the introduction of the contract. "The Agreement is a written contract" or "The agreement is an oral contract executed in [month/year]" is a one-line fix. If form is genuinely uncertain at the pleading stage (some implied-by-conduct cases), plead in the alternative — but disclose the alternative explicitly rather than leaving the form question floating.

Primary source: Code Civ. Proc. § 430.10(g); Otworth v. Southern Pacific Transportation Co. (1985) 166 Cal.App.3d 452, 458-459.

Civil Code § 1624 requires a writing signed by the party to be charged for specified categories of contract: agreements not to be performed within one year, agreements for the sale of real property or an interest therein, agreements to answer for the debt of another, agreements not to be performed within the lifetime of the promisor, and others. The recurring failure mode is the multi-year oral arrangement, no writing pleaded, no exception (part performance, equitable estoppel, full performance) addressed — the bar runs out of the complaint's own face. The trap is that plaintiffs often plead the surrounding facts (multi-year duration, real-property nexus, suretyship structure) without recognizing that those same facts trigger § 1624.

If you're the moving party: Identify the § 1624 category (one-year, real-property interest, suretyship, lifetime), pin the term length to the pleaded dates, and show that no exception appears in the complaint. Where the complaint hints at part performance, attack the Sterling v. Taylor identifiability requirement — part performance must be unequivocally referable to the alleged contract, not merely consistent with it.

If you're the opposing party: Plead the writing if one exists, however informal — California courts accept email exchanges, signed memoranda, and other writings short of a formal contract. If no writing exists, plead the exception in facts, not labels: identify the specific acts of part performance and tie them unequivocally to the alleged contract; identify the inducement and detrimental reliance for equitable estoppel; identify the side that has fully performed for the full-performance exception. Generic "plaintiff relied on the agreement" allegations will not move the court off § 1624.

Primary source: Civ. Code § 1624; Sterling v. Taylor (2007) 40 Cal.4th 757, 766.

The implied covenant of good faith and fair dealing is read into every California contract, but it cannot impose substantive duties or limits beyond what the parties bargained for. The recurring failure mode is the implied-covenant count that pleads the same factual basis as the breach-of-contract count (duplicative) or that pleads conduct contradicting an express right the contract gives the defendant — termination at will, sole discretion, unilateral pricing change. Guz, Carma Developers, and Racine & Laramie all stand for the same proposition: the covenant protects the parties' reasonable expectations in performing what they agreed to, not a hypothetically better bargain.

If you're the moving party: Identify the express contract right that the implied-covenant count would defeat — termination clause, sole-discretion provision, at-will language, unilateral-modification right. Quote the provision and frame the implied-covenant count as an attempt to write around it. For the duplicative variant, lay out side-by-side the same factual paragraphs supporting both counts and ask the court to dismiss the implied-covenant count under Careau & Co. v. Security Pacific as unnecessary.

If you're the opposing party: Plead the implied-covenant count only where the alleged conduct is separable from the breach allegation — the defendant complied with the literal terms but exercised a discretionary right in a way that defeats the contract's purpose. Cite Carma Developers for the principle that the covenant constrains discretionary conduct even where the contract is silent on the standard governing that discretion, and tie your facts to that frame.

Primary source: Guz v. Bechtel National, Inc. (2000) 24 Cal.4th 317, 349-350; Carma Developers (Cal.), Inc. v. Marathon Development California, Inc. (1992) 2 Cal.4th 342, 374; Careau & Co. v. Security Pacific Business Credit, Inc. (1990) 222 Cal.App.3d 1371, 1395.

Outside the insurance context, Foley v. Interactive Data Corp. bars tort recovery for breach of the implied covenant of good faith and fair dealing — even where the breach is alleged to be willful, malicious, or in bad faith. The narrow Robinson Helicopter exception permits a fraud-tort recovery alongside contract damages where the defendant's affirmative misrepresentations cause harm independent of the contract. The recurring failure mode is the plaintiff who pleads "bad faith breach" as a tort count to bootstrap punitive damages or fee-shifting onto an ordinary contract dispute.

If you're the moving party: Quote the tort count and identify the conduct alleged. If the conduct is breach of contract dressed as a tort (willful failure to perform, malicious refusal, bad-faith repudiation), Foley bars it as a matter of law. If the plaintiff invokes Robinson Helicopter, identify the affirmative misrepresentation alleged and test it against the Robinson requirements: (a) it must be a misrepresentation independent of the contract, (b) it must cause harm beyond the contract damages, and (c) the harm must be the kind tort law protects against. Generic "bad faith" allegations do not satisfy Robinson.

If you're the opposing party: Robinson Helicopter is the survival path. Plead specific affirmative misrepresentations — not merely failures to perform — and tie them to harm that is not just disappointed contract expectations (out-of-pocket loss caused by reliance, exposure to third-party liability, reputational damage independent of the contract). The narrower the tort theory, the more likely it survives.

Primary source: Foley v. Interactive Data Corp. (1988) 47 Cal.3d 654, 683-700; Cates Construction, Inc. v. Talbot Partners (1999) 21 Cal.4th 28, 43-44; Robinson Helicopter Co., Inc. v. Dana Corp. (2004) 34 Cal.4th 979, 991.

A claim for quantum meruit, unjust enrichment, or quasi-contract cannot proceed where an express contract covers the same subject matter. The equitable remedy fills a gap that no enforceable agreement occupies; once the parties' enforceable contract addresses the subject, equity is unavailable. The recurring failure mode is the plaintiff who pleads quasi-contract counts in the alternative — "if no contract is found, then quantum meruit" — but pleads them on the same facts as the express-contract count without genuinely contesting the contract's existence.

If you're the moving party: Quote the complaint's own contract allegations and use them against the quasi-contract count. The plaintiff's express-contract allegations are admissions for purposes of demurrer; if those allegations make out an enforceable contract on the same subject as the quasi-contract count, Hedging Concepts bars the equity claim. Where the plaintiff genuinely pleads in the alternative (e.g., contests existence), focus the demurrer on the express-contract count instead and let the quasi-contract count proceed as a fallback.

If you're the opposing party: Plead alternative theories cleanly — frame the contract count as one possible characterization and the quasi-contract count as the alternative if the contract is found unenforceable, void, or outside the scope. The clearer the alternative pleading, the more likely both counts survive. If the contract is concededly enforceable, drop the quasi-contract count rather than draw a Hedging Concepts sustain.

Primary source: Hedging Concepts, Inc. v. First Alliance Mortgage Co. (1996) 41 Cal.App.4th 1410, 1419-1420; California Medical Assn., Inc. v. Aetna U.S. Healthcare of California, Inc. (2001) 94 Cal.App.4th 151, 172.

A non-party suing on a contract must satisfy Goonewardene's three-prong test: (1) the third party would in fact benefit from the contract; (2) a motivating purpose of the contracting parties was to benefit the third party; and (3) permitting the third party to enforce the contract is consistent with the objectives and reasonable expectations of the contracting parties. The middle prong is the demurrer target — incidental benefit is not enough. The recurring failure mode is the plaintiff who pleads "the contract was intended to benefit plaintiff" as a legal conclusion without anchoring it in specific contract language or in evidence of the parties' intent at formation.

If you're the moving party: Run the three-prong test in the demurrer and identify which prong fails. The motivating-purpose prong is usually the cleanest attack — if the contract does not name the plaintiff and does not on its terms identify a class of beneficiaries that includes the plaintiff, ask the court to find the alleged benefit incidental as a matter of law. Where the complaint relies on extrinsic evidence (pre-contract communications, course of performance), attack the absence of the supporting facts in the pleading.

If you're the opposing party: Anchor the motivating-purpose allegation in specific contract language or in the parties' communications at formation. The strongest pleadings cite the contract section, defined term, or recital that names the third party or identifies the beneficiary class; the next-strongest pleadings allege specific pre-contract communications evidencing intent to benefit. Generic "the contract was intended to benefit plaintiff" allegations are vulnerable.

Primary source: Goonewardene v. ADP, LLC (2019) 6 Cal.5th 817, 830; Hess v. Ford Motor Co. (2002) 27 Cal.4th 516, 524.

Civil Code § 3390 requires a specific-performance count to allege all of: (1) sufficiently certain contract terms; (2) adequate consideration; (3) the plaintiff's performance, tender of performance, or readiness, willingness, and ability to perform; (4) the defendant's failure to perform; and (5) the inadequacy of the legal remedy of damages. The recurring failure mode is the plaintiff who pleads the contract and the breach but fails to allege continuing readiness to perform — element (3). The trap is doctrinal: specific performance is an equitable remedy that flows from the plaintiff's clean hands, and a complaint that asks the court to compel the defendant's performance without affirmatively alleging the plaintiff's own continued capacity to perform contradicts the equitable premise.

If you're the moving party: Run the § 3390 checklist and identify the missing element. The "ready, willing, and able" allegation is the most commonly omitted; the "inadequacy of damages" allegation is the second. For real-property contracts, the inadequacy element is typically presumed (each parcel is unique), but the pleading still must allege it. For commercial contracts where damages would in fact be adequate, attack inadequacy directly.

If you're the opposing party: Plead all five elements explicitly, with facts. "Plaintiff is and at all times has been ready, willing, and able to perform plaintiff's obligations under the agreement" is the verbatim allegation. For inadequacy of damages, plead the specific reason — uniqueness, ongoing business relationship, intangible value — that makes the legal remedy insufficient.

Primary source: Civ. Code § 3390; Real Estate Analytics, LLC v. Vallas (2008) 160 Cal.App.4th 463, 472; Tamarind Lithography Workshop, Inc. v. Sanders (1983) 143 Cal.App.3d 571, 575.

Whether the implied-covenant count pleads a separable theory — or is duplicative of the breach-of-contract count under Careau & Co.

Under Careau & Co. (1990), courts sustain a demurrer to an implied-covenant count as duplicative when it rests on the same operative facts and seeks the same damages as the breach-of-contract count. A count that alleges “defendant breached the covenant by failing to [same conduct as breach count]” is a relabeled version of the contract count, not a separate claim.

If you're the moving party: Show side-by-side that the covenant count's operative facts and requested damages mirror the contract count. Careau is explicit: the implied covenant applies to the literal performance of contractual terms; it does not give the plaintiff a second bite at facts already pled as breach. Where the only alleged breach is a failure to perform a contractual duty, the implied-covenant count adds nothing.

If you're the opposing party: The implied covenant survives when the defendant complied with the literal contractual terms but exercised a discretionary right in a way that defeated the reasonable purpose of the agreement. Cite Carma Developers v. Marathon Development for the discretionary-rights framework. Plead the specific discretionary right defendant exercised (a contractual option, a termination clause, a renewal provision) and how its exercise defeated plaintiff's reasonable expectation while technically complying with the letter of the contract.

Primary sources: Careau & Co. v. Security Pacific Business Credit, Inc. (1990) 222 Cal.App.3d 1371, 1394–1395; Carma Developers v. Marathon Development California, Inc. (1992) 2 Cal.4th 342, 373.

Corpus signal: strong — Fraizer v. Niakan FP (LA Superior, Mosk Dept 413, May 5, 2026) sustained implied-covenant count on Careau grounds while overruling 10 of 11 other counts in the same ruling.