A covenant not to execute is a contract in which the winner of a lawsuit promises not to collect the judgment from a specific losing party. The judgment stays on the books and the debt technically remains owed, but the creditor gives up the right to garnish wages, seize accounts, or place liens on that person’s property. These agreements appear most often in liability insurance disputes, where a plaintiff and an insured defendant use the covenant to shift the financial burden onto an insurer that refused to defend or settle. They also show up in multi-defendant cases when a plaintiff wants to settle with one defendant without releasing the others.
How the Promise Actually Works
The judgment does not go away. It remains a valid court record, and the named debtor still owes the money on paper. What changes is the creditor’s ability to enforce. No garnishment, no levy, no liens against the person covered by the covenant. Think of it as a permanent pause on collection against one specific debtor.
Because the judgment survives, it can still be enforced against anyone else who is liable but not covered by the agreement. A plaintiff with three defendants can sign a covenant with one and continue pursuing the other two for the full amount. The covenant shields one party. It does not wipe the slate.
The Insurance Dispute That Drives Most of These Deals
The typical scenario runs like this. A plaintiff sues a defendant who carries liability insurance. The insurer refuses to defend, denies coverage, or rejects a reasonable offer to settle within policy limits. The defendant is now personally exposed to a judgment that could take savings, a home, and everything else.
Plaintiff and defendant then negotiate their way out of the standoff. The defendant agrees to a consent judgment for a set amount of damages. The plaintiff signs a covenant not to execute against the defendant personally. And the defendant assigns to the plaintiff the right to sue the insurer for bad faith. The plaintiff then goes after the insurance company directly, holding both the judgment and the assigned claim.
The defendant avoids personal financial ruin. The plaintiff gets a path to recovery that doesn’t depend on the defendant’s assets. The insurer answers for its refusal to handle the claim. In some jurisdictions this package is called a Coblentz agreement, after the Florida case that shaped the framework.
Use in Multi-Defendant Cases
Insurance is not the only setting. When several defendants are on the hook, a covenant not to execute lets a plaintiff settle with one without giving up the case against the rest. A straight release would typically extinguish the settling defendant’s liability, which in some jurisdictions reduces or eliminates what the plaintiff can recover from the remaining defendants. A covenant not to execute avoids that consequence because the underlying liability stays intact. The plaintiff collects partial compensation now and keeps the full case alive against the holdouts.
How It Differs From a Release and a Covenant Not to Sue
Three tools sound similar and produce very different results.
A release kills the underlying claim. Once signed, the obligation is gone, and depending on the jurisdiction the creditor may lose the ability to pursue anyone else tied to the same claim.
A covenant not to sue is a promise not to file a lawsuit over a particular claim. It usually comes into play before any litigation or judgment. The right to sue may still exist in theory, but the party has contracted not to exercise it.
A covenant not to execute applies after a judgment exists or is about to be entered. Liability remains, the judgment remains, and the obligation to pay remains on paper. The creditor simply promises not to enforce it against a named debtor.
The distinction matters enormously in insurance cases. Under the majority approach, courts treat a covenant not to execute as a contract rather than a release. Because the insured’s liability is not extinguished, the insurer’s duty to indemnify survives. A release would eliminate that obligation and potentially free the insurer as well.
What a Covenant Not to Execute Typically Contains
A well-drafted agreement leaves little room for later argument. Expect it to cover:
- The parties. Who is promising not to execute, and against whom enforcement is being waived. In the insurance setting, that is the plaintiff as judgment creditor and the insured defendant as judgment debtor.
- The judgment. Case number, court, and amount. If a consent judgment is part of the deal, its terms are described.
- Scope of non-enforcement. Whether the covenant covers all of the debtor’s assets or only certain property, and whether it applies permanently or for a limited period.
- Conditions precedent. Any requirements that must be satisfied before the covenant takes effect, such as entry of the consent judgment by the court.1Federal Deposit Insurance Corporation. Settlement Agreement, Assignment and Covenant Not to Execute
- Assignment of rights. If the defendant is handing over bad faith or breach-of-contract claims against the insurer, the assignment is documented in detail.
- Consideration. What each party gives and receives, whether that is money, the assignment, or the consent judgment itself.
How Insurers Fight These Agreements
Insurers rarely accept the package without a fight. When a plaintiff arrives holding a consent judgment, a covenant not to execute, and an assignment of bad faith rights, expect the insurer to attack on several fronts.
Collusion
The most common argument is that the consent judgment was not the product of genuine adversarial negotiation. Because the covenant removes the defendant’s personal financial risk, the insurer contends the defendant had no reason to contest liability or push back on damages. Courts respond by looking at whether the parties dealt at arm’s length and whether the judgment amount bears a reasonable relationship to actual damages.
The “Legally Obligated to Pay” Argument
Most liability policies require that the insured be legally obligated to pay damages before the insurer must indemnify. Insurers argue that a defendant protected by a covenant is not truly obligated, because the plaintiff has promised never to collect.
Most courts reject this reasoning. Under the majority view, the covenant is a separate contract that does not eliminate the underlying tort liability. The insured remains legally obligated to pay even if the plaintiff has voluntarily agreed not to enforce. The duty to indemnify survives.
The Minority Approach
A minority of jurisdictions side with insurers. Courts following the minority rule treat the covenant as functionally equivalent to a release: if the insured will never pay a dollar out of pocket, the judgment is a fiction designed to reach the insurer’s money. Some of these courts have warned that enforcing the arrangement would invite collusion between plaintiffs and defendants at the insurer’s expense.
Reasonableness of the Amount
Even in jurisdictions that generally enforce these agreements, the consent judgment amount must be reasonable. The plaintiff typically bears the burden of showing the figure reflects a fair assessment of the insured’s potential liability at the time of the deal. A number wildly out of proportion to actual damages will draw scrutiny and may be reduced or set aside. Courts evaluate reasonableness on what was known at the time of settlement, not with hindsight.
Breach of the Duty to Cooperate
Most liability policies require the insured to cooperate with the insurer in defending a claim. An insured who consents to judgment without the insurer’s knowledge or approval may be found to have breached that duty. In jurisdictions that require the insurer to prove actual prejudice, this defense is harder to win. Elsewhere, the breach alone may be enough to void coverage.
What Happens After the Covenant Is Signed
The real fight starts after signing. The plaintiff, now holding the assigned bad faith claim, sues the insurer directly. The consent judgment fixes the damages. The question in that second lawsuit is whether the insurer must pay or whether the arrangement can be set aside.
If the court finds the agreement was reasonable and made in good faith, the insurer may owe not only the judgment amount but also additional damages under the bad faith claim. Depending on the jurisdiction, those damages can include emotional distress, attorney fees, and punitive damages that far exceed the original policy limits. That exposure is why insurers push so hard to invalidate the deal.
For the defendant, the covenant means no one comes knocking to collect. The judgment still appears on the public record and can affect credit or later proceedings. And the protection lasts only as long as the covenant’s terms allow. If the agreement is time-limited or conditional, the defendant needs to keep those conditions satisfied.