A release and a covenant not to sue both end a dispute, but they end it in fundamentally different ways. In the covenant not to sue vs. release comparison, the pivotal distinction is what happens to the underlying legal claim: a release extinguishes it, treating the claim as if it never existed, while a covenant not to sue leaves the claim alive and adds a contractual promise not to pursue it. That single difference drives everything else — who else can still be sued, what remedy the protected party gets if the promise is broken, and whether the settling party has bought true finality or only a conditional peace.
What a Release Actually Does
A release is a voluntary surrender of a legal right. Signing one permanently extinguishes the underlying claim or cause of action. The claim doesn’t just become harder to pursue; it ceases to exist. If you later try to sue on a released claim, the court will dismiss the case outright because there is nothing left to litigate.
Every valid release needs consideration, meaning something of value exchanged for the surrender of the claim. In most settlements that consideration is money, but it can also be mutual promises, returned property, or the other side dropping their own claims against you. Without consideration, the release is just a piece of paper.
Releases come in two basic forms. A general release covers all claims between the parties, including ones neither side has discovered yet. A specific or limited release only extinguishes the particular claims spelled out in the document. If you had a slip-and-fall claim and a separate contract dispute with the same party, a specific release could eliminate one while preserving the other.
Unknown Claims and Statutory Protections
The trickiest part of any general release involves claims the signer doesn’t yet know about. Some states have laws providing that a general release does not cover claims the releasing party didn’t know existed at the time of signing, on the theory that you can’t voluntarily give up a right you didn’t know you had. California’s version of this rule is probably the most recognized, and settlement agreements around the country reference it.
To work around these protections, lawyers typically add an express waiver clause in which the releasing party acknowledges that the release is intended to cover unknown claims and voluntarily gives up any statutory protections to the contrary. Courts scrutinize these waivers, so the language needs to be specific and unambiguous. A vague “release of all claims” without addressing unknown claims may not hold up in a state with protective statutes.
Mutual Versus Unilateral
Most settlement releases are mutual: both sides release the other from all claims arising out of the dispute. That’s the norm because it gives both parties clean finality. A unilateral release, where only one side gives up claims, leaves the non-releasing party free to bring future actions. That asymmetry makes sense in limited situations, such as an insurer settling a claim, but in general both sides want the protection that comes from a mutual exchange.
What a Covenant Not to Sue Actually Does
A covenant not to sue is a contract. You promise not to file or continue a lawsuit against a specific party, and in return you receive consideration. The critical difference from a release is that the underlying legal claim stays alive. You have agreed not to act on it against the protected party, but you have not surrendered the right itself.
Think of it this way. A release is like tearing up a winning lottery ticket, so the prize no longer exists for anyone. A covenant not to sue is like locking that ticket in a drawer with a promise not to cash it at one particular office, while every other office still has to honor it.
When Someone Breaks the Promise
If a person signs a covenant not to sue and files a lawsuit anyway, the protected party’s remedy is a breach-of-contract claim. They can counterclaim or file a separate action seeking the damages the broken promise caused, most importantly the legal fees and defense costs of fighting the improperly filed suit. Courts are split on whether those attorney’s fees count as recoverable damages automatically or whether the covenant itself needs to expressly provide for them. The safer practice is to include a fee-shifting clause in the covenant so there’s no ambiguity.
The Circuity-of-Action Shortcut
Some courts skip the breach-of-contract detour entirely. Under the circuity of action doctrine, these courts treat a covenant not to sue as functionally equivalent to a release when the plaintiff sues anyway. The reasoning: if the plaintiff sues, the defendant counterclaims for breach, and the contract damages roughly equal whatever the plaintiff would recover on the original claim, everyone ends up back where they started. Rather than running that pointless circle, the court just dismisses the original suit. This is a practical shortcut, not a change in the covenant’s legal nature. The claim technically still exists, but the court won’t let the parties waste resources proving the obvious.
Why the Difference Matters in Multi-Defendant Cases
This is where choosing the wrong instrument can be genuinely costly.
Under the old common law rule, releasing one party who was jointly responsible for an injury automatically released every other party responsible for the same injury. The logic: a single injury produces a single claim, and once the injured person received compensation and released that claim, it was gone against everyone. If two negligent drivers caused a car accident and the injured person settled with Driver A using a release, Driver B walked free too, even though the plaintiff never intended that result and Driver B never paid a dime.
The covenant not to sue was developed specifically to avoid that harsh outcome. Because a covenant doesn’t destroy the underlying claim, it lets a plaintiff settle with one defendant while keeping the claim alive against the others. Collect from Driver A, promise not to sue Driver A again, and still take Driver B to trial for the remaining damages.
Modern Statutory Reforms
Most states have moved away from the old common law rule through legislation modeled on the Uniform Contribution Among Tortfeasors Act. Under the modern approach, a release given in good faith to one jointly liable party does not discharge the others. Instead, it reduces the total claim against the remaining defendants by the amount the settling party paid. This pro tanto credit prevents the plaintiff from collecting twice for the same injury while still allowing pursuit of the non-settling parties for whatever remains.
Even with these reforms, lawyers in multi-party cases still overwhelmingly prefer covenants not to sue for partial settlements. The reasoning is belt-and-suspenders caution. In a state where the old rule hasn’t been fully abrogated, or where the release language is ambiguous, a covenant not to sue eliminates the risk entirely. There’s no argument that settling with one defendant inadvertently freed the others because the claim was never extinguished in the first place.
When to Use Which
The choice comes down to whether you want finality or flexibility.
A release is the right tool when the dispute is truly over. Both sides have agreed on terms, no other parties are involved, and nobody wants to leave the door open. Insurance settlements, business buyouts, and resolved contract disputes all call for releases because the goal is a clean break with no possibility of future litigation on the same facts.
A covenant not to sue fits situations where the story isn’t finished. The most common scenario is a partial settlement in a multi-defendant lawsuit. A plaintiff who settles with one defendant early, perhaps because that defendant has limited assets, needs the claim to survive against the remaining defendants. A covenant accomplishes exactly that: it monetizes one defendant’s share of liability without jeopardizing the larger case.
Covenants also work well for conditional resolutions. A party might agree not to sue as long as the other side performs on a contract, completes remediation work, or meets certain benchmarks. If performance fails, the right to sue can revive. That kind of conditional peace is impossible with a release, because once the claim is extinguished, it’s gone regardless of what happens next.
From the defense side, the calculus flips. A defendant who wants to buy permanent peace demands a release: once executed, the claim is dead, no future lawsuit on that claim is possible, and the only way to undo it is to convince a court the entire agreement was fraudulent or unconscionable. If the plaintiff insists on a covenant, the settling defendant gets less certainty. When the plaintiff breaches the covenant, the defendant’s remedy is a breach-of-contract action rather than an outright dismissal, and the damages may need to be proven rather than assumed.
How Either Agreement Can Be Challenged
Neither a release nor a covenant not to sue is bulletproof. Like any contract, either can be challenged on traditional contract-law grounds. The burden falls on the party trying to undo the agreement, and courts generally start from a presumption that signed contracts should be enforced. Several defenses come up repeatedly.
- Fraud. If one side lied about or concealed material facts to induce the other to sign, the agreement can be voided. A defendant who hides the true severity of a plaintiff’s injuries to secure a low-value release may find that release set aside.
- Duress or undue influence. An agreement signed under threats, coercion, or improper pressure isn’t truly voluntary. Courts look at whether the signing party had a realistic alternative. If the only option was sign or lose everything, that tips toward duress.
- Mutual mistake. When both parties shared a factual belief that turns out to be wrong, and that belief went to the heart of the agreement, a court can rescind or reform the contract. The classic example involves settling a personal injury claim based on a medical diagnosis that later proves incorrect. If both sides believed the injuries were minor and settled accordingly, but the injuries turned out to be far more serious, the release may not stand.
- Unconscionability. A release that is overwhelmingly one-sided, signed by someone with vastly unequal bargaining power and no meaningful opportunity to negotiate, can be struck down. Courts examine both the process and the substance. A take-it-or-leave-it waiver buried in fine print that strips away nearly all legal rights is the textbook candidate.
- Lack of consideration. A release given in exchange for nothing, or for something the releasing party was already entitled to receive, fails for want of consideration. This comes up in employment releases where the employer offers only benefits the employee had already earned.
A release executed with proper disclosure, reasonable terms, adequate consideration, and genuine voluntariness is extremely difficult to undo. Most challenges fail. Cutting corners on any of these elements creates an opening that a motivated litigant will find.
One Boundary Worth Knowing: Employment Releases
If the release is being signed as part of an employment separation, the general rules above are not the whole story. Federal age discrimination claims have their own mandatory requirements under the Older Workers Benefit Protection Act, and if any of them are missed the release is unenforceable as to those claims. The employee must get at least 21 days to consider an individual agreement (45 days for a group layoff or exit incentive program) and 7 days after signing to revoke, and the parties cannot shorten that revocation period for any reason.1Office of the Law Revision Counsel. 29 USC 626 – Recordkeeping, Investigation, and Enforcement The waiver must specifically name the Age Discrimination in Employment Act, be written in plain language, advise the employee in writing to consult an attorney, and be supported by consideration beyond what the employee is already owed. No ADEA waiver can cover claims that arise after the date the employee signs.2eCFR. 29 CFR 1625.22 – Waivers of Rights and Claims Under the ADEA A severance release that skips any of these steps looks enforceable on paper but collapses the moment an ex-employee files an EEOC charge.
For a single-defendant dispute headed to full resolution, a release is almost always the better choice. For a multi-defendant case where you need to settle with one party without letting the others off the hook, a covenant not to sue is the standard tool, and it remains so even in states where the old joint-tortfeasor rule has been softened. The instrument you pick should match the future you actually want.