Skip to main content
Judgment enforcement

CCP § 664.6: How to Enforce a California Settlement (and the Mistakes That Forfeit It)

California Code of Civil Procedure § 664.6 offers summary enforcement of a civil settlement — but the statute's requirements are unforgiving. Here's what § 664.6 actually requires, the two cases that decide most disputes (Levy and Mesa), and how to keep the door to summary enforcement open.

By Taylor E. DarcyPublished

A California civil settlement is supposed to end the dispute. It often does. But when it doesn’t — when payments stop, performance lapses, or a release scope gets contested — the question becomes mechanical: how do you enforce it?

The answer most litigants reach for is California Code of Civil Procedure § 664.6, the statute that allows the trial court to enter judgment on the parties’ settlement through a summary motion in the original action. § 664.6 is fast (months, not years), inexpensive (no new filing fees, no full-blown discovery), and it leverages the original judge’s familiarity with the case.

What surprises litigants — and ends more settlement-enforcement attempts than any other issue — is that § 664.6 isonlyavailable when the settlement satisfies the statute’s formal requirements. The California Supreme Court and Courts of Appeal have read those requirements strictly, and the requirements close off summary enforcement in a meaningful percentage of cases where parties assumed it was available.

This is a guide to the requirements of § 664.6, the two cases that drive most disputes about whether the statute applies (Levy v. Superior CourtandMesa RHF Partners), and the practical steps that keep the door to summary enforcement open while the settlement is still being negotiated. When § 664.6 is closed off, the alternative — a separate breach-of-contract action — works, but slower and at greater cost.

What § 664.6 actually says

The statute is short. Stripped of subdivisions, the operative language reads:

If parties to pending litigation stipulate, in a writing signed by the parties outside the presence of the court or orally before the court, for settlement of the case, or part thereof, the court, upon motion, may enter judgment pursuant to the terms of the settlement.

Two pathways. Either the settlement is a writing signed by the parties, or it’s an oral stipulation made before the court on the record. Either way, the result is the same: the trial court — on motion in the original action — may enter judgment incorporating the settlement’s terms. That judgment is then enforceable through California’s standard judgment-enforcement mechanisms (writs of execution, bank levies, abstracts of judgment, charging orders against entity interests, debtor examinations).

The 2020 amendment to § 664.6 codified the rule that signatures by counsel can satisfy the “signed by the parties” requirement when the attorney is signing on behalf of a represented party — but only in the specific way the statute prescribes. That amendment did not eliminate the personal-signature rule for parties. It clarified what counsel-signature means when it’s expressly authorized.

The two issues that drive most § 664.6 disputes are:

  • Was the settlement signed by the parties(or signed by counsel in a way that qualifies under the statute and the case law)?
  • Did the trial court retain jurisdictionto enforce the settlement after the underlying case was dismissed?

The answer to either question is often “no” in cases where the parties believed the answer was “yes.” That’s whereLevyandMesacome in.

Levy v. Superior Court: parties must sign — not just counsel

The California Supreme Court’s decision inLevy v. Superior Court(1995) 10 Cal.4th 578 settled a recurring procedural question: when § 664.6 says a settlement must be “signed by the parties,” does signature by the parties’ counsel qualify?

The Supreme Court’s answer was no. To invoke § 664.6’s summary enforcement procedure, the settlement must be signed bythe parties themselves, not merely by their attorneys. The Court reasoned that settlement is a serious decision implicating the client’s legal rights — distinct from the routine litigation decisions counsel handles on the client’s behalf — and that the personal-signature requirement reflects the Legislature’s judgment about what proof is necessary before summary enforcement is appropriate.

The practical consequences are substantial. A settlement memorialized in a letter from one attorney to the other, signed by counsel only, doesn’t qualify for § 664.6 enforcement underLevy. Neither does an email exchange between counsel that captures all the material terms but lacks party signatures. Neither does a typed agreement signed at the bottom by counsel for both sides, however carefully it documents the parties’ intent.

The 2020 statutory amendment created a narrow expansion: counsel can now sign on behalf of a party for § 664.6 purposes, but only where the statute’s specific requirements about counsel-signature authority are met. The amendment didn’t eliminateLevy; it codified a limited carve-out. The general rule stands: get personal signatures from each party, on the settlement document itself, in the transaction that creates the settlement.

What about entities? When the settling party is a corporation, LLC, or partnership, signature by an authorized officer or member qualifies — that signature is the entity’s personal signature for § 664.6 purposes. The qualifying authority comes from the entity’s governance documents and resolution practice; outside counsel signing on the entity’s behalf without that authority faces the sameLevyproblem as outside counsel signing on an individual’s behalf.

The takeaway: the safest practice is the simplest. Get the actual parties — the named plaintiffs and defendants, individuals signing for themselves and authorized officers signing for entities — to sign the settlement document personally. Skipping that step in favor of a quicker counsel-signed letter often forfeits § 664.6 in cases where the settlement is later contested.

The oral-on-the-record alternative

§ 664.6’s second pathway is oral recitation of the settlement on the court record. Where the parties are present in court — at a settlement conference, mediation supervised by the court, or in a hearing — the settlement can be made on the record by counsel reciting the terms while the parties confirm assent under oath.

This pathway is its own discipline. The recitation needs to capture every material term: who pays whom, how much, on what schedule, with what consequences for default, what the release covers, what the release carves out, what continuing obligations apply. A general statement that “the parties have reached a settlement” followed by a vague summary doesn’t satisfy the statute. The transcript must contain enough specificity that the court can enter judgment on the recited terms without filling in gaps.

Each party must personally affirm the settlement on the record. “Yes, your honor” from the named individual or authorized entity representative — answering questions from the bench or counsel about whether the recited terms reflect the settlement and whether the party agrees — is what makes the oral stipulation enforceable under § 664.6.

For most California settlements, the writing pathway is more practical than the oral-on-the-record pathway. The writing pathway lets the parties take time to draft the agreement carefully, review it with counsel, and sign at leisure. The oral pathway is best reserved for settlements reached in court (judicial settlement conferences in particular), where the immediate transcript captures the deal before either party can reconsider.

Mesa and the jurisdiction-retention requirement

The second case that closes off § 664.6 summary enforcement most often isMesa RHF Partners, L.P. v. City of Los Angeles(2019) 33 Cal.App.5th 913.Mesaaddresses what happens when the underlying case has been dismissed. § 664.6 only works in a “pending” case — or, where the case has been dismissed, in a case where the trial court has retained jurisdiction to enforce the settlement.

Mesareads “retain jurisdiction” strictly. The court doesn’t retain jurisdiction simply because the parties’ settlement agreement says it does. The retention has to be communicated to the trial court — by request —beforethe dismissal is entered. Once dismissal has been entered without that retention request having been made on the record, the court’s jurisdiction to enforce under § 664.6 is gone, even if the settlement document and the dismissal order both purport to retain it.

This catches more settlements than any other procedural issue. A typical pattern: the parties settle, sign a settlement agreement that includes a clause saying the trial court retains jurisdiction under § 664.6, and immediately file a stipulated dismissal. The settlement document looks airtight. The dismissal looks routine. Months or years later, when default occurs, the non-breaching party files a § 664.6 motion — and discovers thatMesarequires more than what the dismissal order says. The retention request had to be made to the court, in the case, before dismissal was entered. After dismissal, the court has no jurisdiction to grant the request retroactively.

The practical fix is to make the retention request explicit and contemporaneous with dismissal. The standard mechanic is a stipulated request submitted alongside the dismissal:

Pursuant to Code of Civil Procedure § 664.6, the parties stipulate and request that the Court retain jurisdiction over the parties to enforce the terms of their settlement until performance in full of those terms.

Submitted as part of the dismissal package — or shortly before, on the case’s docket — and ruled on by the court before the case is closed. Some practitioners file a separate stipulation and proposed order; others build the retention language into the stipulated dismissal itself with a request for the court to enter the order before processing dismissal. Either approach satisfiesMesa’s requirement that the request reach the court before dismissal forecloses jurisdiction.

What about cases dismissed on the court’s own motion or on a one-side dismissal without retention language? Generally, jurisdiction is gone. The settlement remains a binding contract, and breach gives rise to standard contract remedies — but § 664.6 summary enforcement is not among them.

Action step

When you sign a California settlement, do two things together: (1) get personal signatures from every party (underLevy, signatures by counsel alone don’t qualify), and (2) submit a written § 664.6 jurisdiction-retention request to the trial court before — not after — dismissal is entered (underMesa). The cost of doing both at signing is essentially zero. The cost of getting either wrong is the difference between summary enforcement and a new lawsuit.

When § 664.6 is closed off: the breach-of-contract action

A settlement that doesn’t qualify for § 664.6 enforcement is still a binding contract. Breach gives rise to the standard remedies for breach of contract:

  • Damagesfor the value of what wasn’t performed — typically the unpaid settlement amount, plus consequential damages where they’re recoverable.
  • Specific performancein narrow circumstances where damages are an inadequate substitute. Settlements requiring transfer of unique property (real estate, particular IP rights, controlling shares of a closely held entity) are the principal candidates.
  • Rescissionin limited circumstances where the settlement was procured by fraud or material misrepresentation.
  • Attorneys’ feesif the settlement (or an underlying contract whose attorney-fee clause survives the settlement) provides for them. Many settlements include reciprocal fee provisions specifically for enforcement.

The downside is procedural. A breach-of-contract action is a new lawsuit — new filing fees, new service of process, new pleading challenges, new discovery cycle, new motion practice, new trial. A reasonably contested matter runs 12–24 months from filing to judgment. The cost is substantial relative to the underlying settlement value in many cases, and meaningfully greater than the cost of a § 664.6 motion in the original action.

There are two procedural shortcuts worth knowing about.

Stipulated judgments

Some settlements are signed alongside astipulated judgment— a document agreeing that, in lieu of immediate dismissal, judgment will be entered (typically held in escrow with counsel or with the court) on agreed terms, becoming immediately effective on default. The stipulated-judgment structure gives the non-breaching party a direct judgment on default, without needing § 664.6 motion practice or a new breach action. It’s especially useful where settlement performance happens over time (installment payments) or where the breaching party has a meaningful credit risk.

The trade-off: the breaching party gives up the procedural ability to contest the breach. For breaching parties who genuinely intend to perform and want lenient terms, this concession is worthwhile. For breaching parties who want the option to relitigate later, it’s a deal-breaker.

Acceleration on default

Even where a stipulated judgment isn’t practical, settlements with installment payments should specify what happens on default. Acceleration clauses make the entire remaining balance immediately due on missed payment, which avoids the need to enforce against each installment as it comes due. California courts generally enforce acceleration clauses in settlement agreements.

Three patterns where settlements break down

Three patterns recur in California settlement-enforcement practice:

Payment defaults on installment settlements.The settlement is structured as monthly or quarterly payments over a period of time. Early payments arrive on schedule. Then payments stop. The non-breaching party files a § 664.6 motion (if available) or a breach action (if not), seeking the unpaid balance plus contractual interest, attorneys’ fees, and any acceleration available under the agreement. The faster the procedural pathway, the smaller the breaching party’s ability to dissipate assets between breach and judgment.

Performance disputes on non-monetary settlements.The settlement requires non-monetary performance — transfer of property, dismissal of related actions, return of confidential materials, signed releases of related claims, ongoing non-disclosure obligations. Disputes arise about whether performance has actually occurred. Specificity in the settlement language is the principal defense; ambiguity invites litigation about what the parties meant. Where the dispute is genuinely about performance rather than contract interpretation, evidence preservation and witness testimony become central.

Release scope disputes.The settlement includes broad mutual releases, and a new dispute arises that may or may not be covered. Each side reads the release favorably to its own position. In settlement enforcement, the question becomes whether the new claim is barred by the release (or, conversely, whether the release was fraudulently induced as to that claim). Carve-out language drafted carefully at the time of settlement reduces these problems substantially. Boilerplate “all claims, known and unknown” releases without thoughtful carve-outs invite the most disputes.

Mediation confidentiality and § 664.6

One specific drafting trap deserves note. California Evidence Code §§ 1115–1128 protect mediation communications with strong confidentiality. Settlements reached in mediation often contain language attesting that the document is “intended to be enforceable under § 664.6” or similar — a recognition that the strict mediation confidentiality rules can otherwise prevent the settlement document from being used in subsequent enforcement proceedings.

The recommended belt-and-suspenders approach for mediated settlements is (1) include the § 664.6 attestation in the settlement document itself, (2) get personal signatures from every party, and (3) ensure the underlying case has been kept open with retained jurisdiction (or, if the case will be dismissed, file the retention request before dismissal). All three together preserve summary enforcement against the procedural traps that otherwise close it off.

When to involve counsel

Settlement enforcement matters generally warrant counsel. The procedural choice — § 664.6 motion vs. stipulated-judgment enforcement vs. new breach action — has consequences for timing, cost, and remedy that a non-lawyer is unlikely to optimize. The timing is often urgent (the breaching party may be dissipating assets); the procedural traps (Levy,Mesa, mediation confidentiality, stipulated-judgment formalities) are not intuitive.

Settlementdraftingis where counsel involvement returns the most value. The cost differential at the front end — between a settlement structured for § 664.6 enforceability and one that isn’t — is small. The cost differential at the back end — between summary enforcement and a new breach action — is large.

Related practice pages and guides

Speak with counsel

If you have a California settlement that has broken down — or one that may be heading there —request a case evaluationorcontact our office. The evaluation is complimentary.

The case citations and statutory references in this article are stated to the author’s knowledge; California settlement-enforcement law turns on specific facts and current authority, and any decision about a particular dispute should be confirmed against current Westlaw or Lexis sources by counsel reviewing the specific settlement document at issue.

Two paths to start

Tell us what you're working on.

Transactional matters start with a short discovery call. Litigation matters use the case-evaluation form so we can run conflicts before anything confidential is shared.