Is a Covenant Not to Sue legally binding?

Yes, when it includes offer, acceptance, and consideration and meets applicable formalities; enforceability also depends on state contract law and the agreement's clarity.

Can it be signed electronically?

Generally yes under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, provided the electronic signature shows intent, attribution, and retention; certain narrow exceptions may apply.

Do I need a notary or witnesses?

Not always; state rules vary. Some states or specific contexts benefit from notarization or witness lines to strengthen evidentiary value or support related filings.

How do I amend or revoke one?

Amendments should be in writing signed by all parties; unilateral revocation is generally ineffective unless the covenant expressly allows it or parties agree otherwise.

What if payment under the covenant is late?

Late payment can trigger a breach and may reinstate litigation rights if the covenant's remedies specify rescission or reversion of release on nonpayment.

Where should I store executed copies?

Keep signed originals or certified e-copies in a secure contract repository with audit trails; maintain copies with counsel and any insurer involved.

Electronic Signature
Templates
Other
Covenant Not to Sue

Covenant Not to Sue

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

What a Covenant Not to Sue Is and when it matters

A Covenant Not to Sue is a written agreement in which a claimant promises not to commence or continue litigation against a specified party for defined claims or causes of action. It typically identifies the parties, describes the scope of covered claims, states any consideration exchanged, and sets an effective date. These agreements are commonly used to resolve disputes without dismissal, preserve settlement terms, or conditionally release liability while leaving some remedial options intact if the covenant is breached.

Why organizations and individuals use a Covenant Not to Sue

A Covenant Not to Sue provides a clear, enforceable mechanism to avoid litigation while documenting the settlement terms and obligations between parties. It can reduce dispute resolution costs, create predictable exposure limits, and serve as part of a broader risk-transfer or settlement strategy under governing state law.

Who commonly prepares and signs a Covenant Not to Sue

Typical users include plaintiffs or claimants, defendants or releasees, insurers, and counsel advising settlement or release terms.

Individuals with personal injury or consumer claims seeking a structured settlement or partial release.
Companies resolving contract, employment, or commercial disputes without protracted litigation.
Insurance carriers formalizing limited releases or settlement conditions on coverage positions.

Common signer roles

Claimant

An individual or entity asserting a claim who agrees not to sue in exchange for consideration or other terms; usually signs as the releasing party and may attach related claim details or docket numbers.

Releasor

The party receiving the covenant (often a defendant or insurer) who may provide payment, corrective action, or other consideration and will typically sign to acknowledge mutual terms and scope of covered claims.

Essential data elements to include

Parties' legal names: Full legal entity names

Effective date: MM/DD/YYYY format

Scope of claims: Specific claim descriptions

Consideration: Payment or non-monetary terms

Signature blocks: Signer's name and date

Notary/witness: If required by state

Core components of a professional Covenant Not to Sue

A complete covenant balances clarity and enforceability: identify parties, narrow covered claims, record consideration, set duration and exceptions, outline dispute resolution, and provide signature and authentication details.

Parties

Clearly identify every party using full legal names and, where relevant, roles (claimant, defendant, insurer), to avoid ambiguity about who is bound.

Covered claims

Describe claims with sufficient specificity—dates, contracts, or claim numbers—so enforceability and scope are clear without overbroad language.

Consideration

State the payment amount or other consideration and the timing or conditions for performance to establish a bargained-for exchange.

Duration and exceptions

Specify whether the covenant is perpetual, limited by statute of limitations, or subject to carve-outs such as fraud or future breaches.

Authentication

Include signature blocks, dates, and any notary or witness lines required by state law to support evidentiary weight.

Enforcement terms

Address remedies for breach, choice of law, and whether the covenant bars all relief or only certain claims to reduce future disputes.

Step-by-step completion process

Complete the covenant in sequence to reduce revision cycles: identify parties, define claims, record consideration, set exceptions, and finalize signatures and authentication.

01

Draft core terms: Identify parties and covered claims.
02

Specify consideration: State exact payment or actions.
03

Add exceptions: List carve-outs like fraud or future claims.
04

Execute and authenticate: Sign, date, and notarize if required.

How to configure an online signing workflow

Set up a clear digital workflow to capture intent, attribution, and retention—key ESIGN elements—while matching your authentication needs.

Field	Configuration
Upload template	Use PDF or DOCX, set editable fields
Signer order	Specify sequential or parallel signing
Authentication	Choose email, SMS, or KBA
Retention	Enable audit trail and download copies

Where to send, file, and store the executed covenant

After execution, route copies to each signer, retain an authoritative original, and file with counsel or the insurer as required by the settlement terms.

Recipient copies: Provide each party a signed PDF copy with certificate
Internal records: Store in contract repository or case file
Insurer notice: Send to carrier if coverage is involved
Court filing: File only if required or to effect dismissal

Digital signing and file-format considerations

Use a platform that preserves an audit trail, supports common formats, and meets necessary compliance (ESIGN/UETA and any sector-specific rules).

Supported formats: PDF and DOCX are standard
Authentication options: Email, SMS, or stronger KBA
Integrations: CRM and cloud storage links

Timing and deadline considerations to watch

Time elements affect enforceability and strategy: consider the effective date, payment schedule, statute of limitations, revocation windows, and any insurer reporting deadlines.

Effective date:

When obligations begin and payment triggers

Payment timing:

Due dates or installment schedule

Statute of limitations:

Varies by claim type, commonly 2–6 years

Revocation window:

Any short window to rescind limited by contract

Insurer notice:

Report within carrier-specified period

Common mistakes to avoid when preparing the covenant

Using vague release language that unintentionally bars unrelated future claims or remedies and invites litigation over interpretation.
Failing to specify consideration or making an unenforceable promise of 'future consideration' without present exchange.
Omitting necessary authentication such as proper authorized signer details, corporate signature blocks, or required notarization or witness lines.
Neglecting to align governing law and venue provisions with the parties' practical ability to enforce or defend the covenant.

Key risks and potential consequences of errors

Unenforceability: Court may refuse to enforce

Residual liability: Claims may survive if carved out

Payment disputes: Breach claims over consideration

Fraud allegations: Claims of misrepresentation

Regulatory exposure: Industry-specific penalties

Recordkeeping gaps: Loss of audit evidence

eSignature pricing and feature comparison relevant to Covenants Not to Sue

Compare typical entry pricing and core capabilities when selecting an eSignature provider; signNow is listed first per vendor comparison conventions.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Trial	7-day free trial	Varies	Varies	Varies	Varies
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Real-world scenarios using a Covenant Not to Sue

These brief examples show how covenants are applied across disputes and settlement contexts.

Employment Settlement

An employee agrees not to sue for specific termination claims

Employer pays severance and provides a neutral reference
The covenant narrows claims while preserving other statutory rights and conditions for payment.

Property Dispute

Neighboring owners negotiate over boundary issues

One party provides corrective action and a limited payment
The covenant prevents suit on past boundary claims but allows enforcement for new encroachments.

Frequently asked questions about Covenants Not to Sue

Answers to common questions about validity, signatures, notarization, and amendment to help you avoid procedural pitfalls.

Need help? Contact support

Is a Covenant Not to Sue legally binding?
Yes, when it includes offer, acceptance, and consideration and meets applicable formalities; enforceability also depends on state contract law and the agreement's clarity.
Can it be signed electronically?
Generally yes under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, provided the electronic signature shows intent, attribution, and retention; certain narrow exceptions may apply.
Do I need a notary or witnesses?
Not always; state rules vary. Some states or specific contexts benefit from notarization or witness lines to strengthen evidentiary value or support related filings.
How do I amend or revoke one?
Amendments should be in writing signed by all parties; unilateral revocation is generally ineffective unless the covenant expressly allows it or parties agree otherwise.
What if payment under the covenant is late?
Late payment can trigger a breach and may reinstate litigation rights if the covenant's remedies specify rescission or reversion of release on nonpayment.
Where should I store executed copies?
Keep signed originals or certified e-copies in a secure contract repository with audit trails; maintain copies with counsel and any insurer involved.

Explore Templates

Transfer on Death Deed Cohabitation Agreement Wisconsin Beneficiary Form West Virginia Deed West Virginia Power of Attorney Wyoming Single-Member Operating Arrangement

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now