Can a covenant be limited to specific claims?

Yes. A covenant commonly identifies specific claims or dates; limiting language reduces ambiguity and is preferable to a broad, undefined waiver that courts may interpret against the drafter.

Is notarization required for validity?

Not generally required in all states, but notarization or witnesses can strengthen proof of execution. Check state practice where the parties reside or where enforcement may occur.

Can a party reserve future claims?

Yes. Include explicit reservation language for future or unrelated claims; absence of reservation risks courts treating the covenant as a release of broader rights.

Is an electronic signature acceptable?

Electronic signatures are enforceable under ESIGN (15 U.S.C. §7001) and UETA where adopted; ensure intent, consent, attribution, and retention elements are documented.

What makes a covenant unenforceable?

Common grounds include lack of consideration, fraud, undue influence, lack of signer authority, or unconscionable terms. Clear documentation reduces these risks.

How should I store executed copies?

Retain signed copies in a secure archive with an audit trail and backups; for tax or HIPAA-related matters follow applicable statutory retention periods.

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’s used

A Covenant Not to Sue is a legal agreement in which one party agrees not to initiate litigation against another party for specified claims or circumstances, typically in exchange for consideration or settlement. It narrows or eliminates the right to sue for listed causes of action while leaving unrelated claims intact unless the agreement expressly releases them. These instruments frequently appear in settlement contexts, insurance claims, and commercial compromises and can be executed as standalone documents or as clauses within broader settlement agreements.

Why parties use a Covenant Not to Sue

A Covenant Not to Sue provides certainty by resolving a specific dispute without a full release, preserving limited rights while preventing litigation on defined claims. It reduces litigation cost and risk, clarifies the scope of settlement obligations, and sets objective terms for payment or performance tied to non‑suit promises.

Typical parties and roles that use this document

Many organizations and individuals use Covenants Not to Sue where a narrow waiver of litigation rights is preferable to a broad release.

Insurers and claimants resolving subrogation or coverage disputes
Contracting parties settling a discrete contractual or tort claim
Corporate counsel protecting ongoing business relationships while resolving specific exposures

Who can sign and why their role matters

Authorized Signer

An officer or authorized agent of a company must sign for corporate parties. The signer should have corporate authority or a power of attorney to bind the entity; otherwise, a later challenge could render the covenant unenforceable.

Individual Claimant

A claimant or claimant's guardian must sign personal covenants. If the claimant is represented by counsel, the agreement should confirm that counsel has explained rights waived and that the signature is knowingly given.

Essential elements to include in a professional Covenant Not to Sue

A well-drafted covenant identifies the claims covered, the parties bound, the consideration provided, and any exceptions or reserved rights to ensure clarity and enforceability.

Parties Identified

Full legal names and capacities of each party (individual, corporate entity, trustee) so the agreement binds the intended persons and avoids ambiguity about who is restricted from suing.

Scope of Claims

A specific list or clear description of the claims, dates, incidents, or causes of action covered by the covenant — avoid vague language that could create interpretive disputes later.

Consideration

The payment, promise, or other consideration supporting the covenant. State the amount, timing, and any conditions precedent to performance to show enforceable exchange.

Exceptions and Reservations

Explicitly list claims or causes of action that remain reserved, such as future, unrelated claims or claims for fraud or criminal conduct, to prevent unintended broad releases.

Duration and Term

Specify whether the covenant is permanent, limited by time, or conditional on future events (for example, final payment or expiration of a cure period).

Signature and Authority

Printed name, title, capacity, date, and any required notary or witness blocks to confirm identity and authority under applicable law.

Step-by-step: completing and executing the covenant

Follow a clear sequence to create an enforceable Covenant Not to Sue and reduce the risk of future disputes.

01

Draft the scope: Define specific claims and any exclusions in precise language.
02

Document consideration: State payment or obligations supporting the covenant with exact terms.
03

Confirm authority: Ensure each signer is authorized to bind the named party.
04

Execute and retain: Sign, notarize or witness if required, and store the original securely.

How to set up an online workflow for this document

Configure a digital workflow that places signature, date, and conditional fields in the right order for secure eSigning and recordkeeping.

Field	Configuration
Signature Field	Require signer initials plus full signature
Date Field	Auto-fill timestamp on signature
Authority Attachment	Attach POA or corporate resolution when entity signs
Audit Trail	Enable IP, timestamp, and authentication logging

Where to send and how the executed document is routed

After execution, route copies to all parties and retain a certified record in the central contract repository to support compliance or later enforcement.

Signer Delivery: Email signed copies to all named parties.
Legal Counsel: Send final version to counsel for retention.
Claims File: Place executed covenant in the associated claims or contract file.
Secure Archive: Store the PDF/A or system-generated copy in a secure repository.

Digital signing and recordkeeping considerations

Use an eSignature platform that preserves a detailed audit trail and supports required authentication levels to strengthen enforceability.

Authentication: Email, SMS, or higher-assurance options
Audit Trail: IP, timestamp, and event log
Storage Format: PDF/A or system-native archival

Representative use cases showing common outcomes

These short scenarios illustrate typical uses of a Covenant Not to Sue in settlement and claims contexts.

Insurance Claim Settlement

A policyholder and insurer agree to settle a vehicle claim for a fixed sum, excluding future unrelated claims

The covenant bars suit on the specified collision claim only
The insurer pays on a schedule, the covenant is signed, and the claim file notes the limited waiver to avoid reopening similar disputes.

Construction Dispute

A subcontractor accepts partial payment and signs a covenant not to sue for defects discovered before the date listed, reserving fraud claims

The covenant limits litigation to listed defects
Documentation includes repair schedule and retention of evidence, and the parties record the covenant in the project file to prevent conflicting claims.

Practical drafting and execution tips to reduce later disputes

Follow these drafting practices to increase clarity and preserve enforceability across jurisdictions and dispute contexts.

Be specific about covered claims

Identify claims by type, date range, or incident description to avoid courts interpreting the covenant more narrowly or broadly than intended; specificity reduces ambiguity-based challenges.

Document consideration clearly

State the exact payment terms, conditions, and contingencies to demonstrate an enforceable exchange and to tie obligations to non‑suit promises.

Confirm signer authority

Obtain evidence of corporate authority (resolution or POA) when entities sign; lack of authority is a common lawsuit basis challenging enforcement.

Preserve execution evidence

Use reliable authentication and retain audit trails, notarizations, or witness affidavits when the jurisdiction or context makes them advisable.

Consequences and legal risks of a flawed covenant

Invalidation Risk: Ambiguous terms

Enforcement Challenge: Lack of signer authority

Fraud Exception: Fraudulent concealment

Tax Reporting: Incorrect reporting risk

Perjury Exposure: False attestations

Costs and Delays: Future litigation expense

Frequent mistakes to avoid when preparing the covenant

Using broad, catch-all language that unintentionally releases unrelated claims and alters bargaining positions in future disputes.
Failing to document or attach proof of consideration, leaving the covenant vulnerable to claims it lacked contractual consideration.
Allowing an unauthorized person to sign for an entity without a resolution or power of attorney, creating an enforceability gap.
Neglecting to include execution evidence (notary, witness, or digital audit trail) where local practice or courts expect stronger proof.

Key timing points and common deadlines to track

Timelines vary by settlement terms; tracking these dates helps trigger payments, preserve rights, and meet filing or statute-of-limitations deadlines.

Effective Date:

Date when covenant obligations begin; use MM/DD/YYYY

Signature Deadline:

Date by which all parties must sign to trigger consideration

Payment Schedule:

Dates when consideration must be transmitted or deposited

Preservation Period:

Time to retain supporting evidence and audit logs

Statute Check:

Confirm relevant SOLs before agreeing to long-term covenants

Common eSignature vendor features compared for document execution

An eSignature platform with audit trails and appropriate authentication helps establish intent, attribution, and record retention when executing Covenants Not to Sue.

	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

Frequently asked questions about Covenants Not to Sue

Answers to common execution and enforceability questions when preparing or signing a Covenant Not to Sue.

Need help? Contact support

Can a covenant be limited to specific claims?
Yes. A covenant commonly identifies specific claims or dates; limiting language reduces ambiguity and is preferable to a broad, undefined waiver that courts may interpret against the drafter.
Is notarization required for validity?
Not generally required in all states, but notarization or witnesses can strengthen proof of execution. Check state practice where the parties reside or where enforcement may occur.
Can a party reserve future claims?
Yes. Include explicit reservation language for future or unrelated claims; absence of reservation risks courts treating the covenant as a release of broader rights.
Is an electronic signature acceptable?
Electronic signatures are enforceable under ESIGN (15 U.S.C. §7001) and UETA where adopted; ensure intent, consent, attribution, and retention elements are documented.
What makes a covenant unenforceable?
Common grounds include lack of consideration, fraud, undue influence, lack of signer authority, or unconscionable terms. Clear documentation reduces these risks.
How should I store executed copies?
Retain signed copies in a secure archive with an audit trail and backups; for tax or HIPAA-related matters follow applicable statutory retention periods.

Explore Templates

Texas Criminal Records Transfer Affidavit Form Arbitration Case Submission Form Transfer Automobile Title Cemetery Fund Plan of Liquidation and Dissolution of a Corporation

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now