Can a covenant bar all future claims?

A covenant can be broad, but courts may limit enforcement if language is ambiguous or if it attempts to waive non-waivable claims like criminal matters or certain regulatory actions. Draft clear scope and exceptions to reduce litigation over interpretation.

Is an e-signed covenant enforceable?

Yes—electronic signatures are generally enforceable under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted, provided intent, consent, attribution, and reliable record retention are present.

When is notarization required?

Notarization rules depend on the document purpose and state law. Some states or transaction types (e.g., deeds) require a notary or witnesses; confirm state requirements before relying on non-notarized execution.

What if a signer lacked authority?

If a signer lacked authority, the covenant may be voidable. Verify corporate signer authority through board resolutions or power-of-attorney documents before finalizing.

Can a covenant be revoked after signing?

Revocation depends on contract terms and consideration. If the covenant is supported by consideration and properly executed, unilateral revocation is typically not allowed; remedies may require mutual agreement or court action.

Should counsel always review the covenant?

Yes. Legal review ensures appropriate scope, preserves reserved rights, and confirms compliance with applicable statutes and public policy that might render certain waivers unenforceable.

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 written promise in which one party agrees not to initiate litigation against another party over defined claims or circumstances. It commonly appears in settlement agreements, release packages, commercial transactions, and construction dispute resolutions where parties prefer a contractual bar to future lawsuits rather than court adjudication. The covenant can be narrow (covering a single claim or claim category) or broad (covering all claims arising from a specific event). Properly drafted, it clarifies scope, duration, consideration, and exceptions to preserve enforceability and reduce post-settlement disputes.

Why parties choose a Covenant Not to Sue

A Covenant Not to Sue reduces litigation risk by replacing threatened or potential claims with negotiated terms, clarifies mutual obligations, and can be structured to permit specific future claims while barring others under clearly defined conditions.

Typical users and signers of this agreement

The Covenant Not to Sue is used by private parties, businesses, and their counsel to resolve disputes without litigation and by third parties (insurers, lenders) to secure predictable risk allocation.

Individual claimants and defendants in consumer, employment, or tort disputes
Businesses and contractors settling commercial or construction claims
Insurers, sureties, and lenders needing contractual protection

When properly executed and documented, it becomes part of the transaction record and may be relied on as the exclusive remedy within its defined scope.

Who typically signs

Claimant / Plaintiff

An individual or entity giving up the right to bring specified claims; signs after consideration is confirmed. Counsel often confirms scope before execution to avoid inadvertent waiver of unrelated claims.

Respondent / Defendant

The party receiving the covenant; signs to acknowledge consideration and mutual terms. May attach exhibits or reserved exceptions describing permitted future claims.

Core elements to include in a professional Covenant Not to Sue

A clear, enforceable covenant contains defined parties, precise scope of claims barred, consideration, effective date and duration, governing law, dispute resolution provisions, and signature blocks with authority statements.

Parties

Identify full legal names and capacities (individual, corporation, trustee).

Scope

Describe claims covered (by statute, act, time period, or transaction) and any explicit exceptions.

Consideration

State payment, credit, or other consideration that supports the covenant.

Effective Term

Specify when the covenant starts and, if applicable, when it ends.

Governing Law

Name the state law that will interpret the covenant and venue for disputes.

Signatory Authority

Include title lines and representation statements confirming signers have authority.

Step-by-step completion checklist

Follow these steps to prepare, confirm, and execute the Covenant Not to Sue.

01

Draft: Populate parties, scope, exceptions, consideration and dates.
02

Review: Have counsel verify waiver language and reserved rights.
03

Execute: Obtain authorized signatures and notarization if required.
04

Distribute: Provide fully executed copies to all parties and custodians.

Typical online setup for completing the covenant

Configure a digital workflow to collect signatures, supporting documents, and audit records in a consistent order.

Field	Configuration
Signer Order	Sequential or parallel based on negotiation and approvals
Authentication	Email + SMS OTP or stronger KBA for high-risk matters
Attachment	Include settlement schedules, release exhibits, and payment confirmation
Retention	Archive signed PDF with audit trail for the required retention period

How digital execution typically proceeds

Use a secure e-signature flow to verify identity, capture intent, and preserve an evidentiary audit trail.

Upload Document: Sender uploads the covenant and supporting exhibits.
Place Fields: Add signature, initials, dates, and conditional fields as needed.
Send to Signers: Deliver via email link or secure signing portal.
Capture Audit: Platform records timestamps, IP, and authentication events.

Digital signing and technical considerations

Choose a platform that produces a tamper-evident signed file, supports strong signer authentication, and preserves an audit trail.

File Formats: PDF or Word DOCX preferred for archival integrity
Authentication: Email + SMS OTP, KBA, or SSO for elevated assurance
Integrations: Connectors for storage (Box, Google Drive) and systems (NetSuite, Salesforce)

Retain the final signed document and audit record in secure storage with access controls and regular backups to meet legal and compliance needs.

Timing considerations and deadlines to watch

Certain dates affect enforceability and ancillary filings — set clear internal deadlines for execution and delivery of consideration.

Effective Date:

Set MM/DD/YYYY and ensure consideration is delivered by that date

Payment Deadline:

Specify when settlement funds must clear to avoid revocation

Delivery of Releases:

Require signed originals or verified e-signed copies within a set window

Record Retention:

Archive executed documents immediately per retention policy

Statute Impact:

Consider tolling or waiver effects on statutes of limitations

Key milestones from negotiation to final archive

Track milestone stages to ensure enforceability and evidence collection at each step.

01

Negotiation Complete

Terms agreed and draft covenant finalized for signatures

02

Execution

Authorized signers sign; notarization performed if required

03

Consideration Delivered

Settlement funds, credits, or other consideration confirmed

04

Archival

Store signed document and audit trail in secure records

Common mistakes to avoid

Vague scope language that unintentionally waives unrelated claims
Failure to specify consideration or condition precedent for the covenant
Using unsigned or unsigned-by-agent copies without authority confirmation
Neglecting notarization or witness formalities where state law requires them

Risks and legal consequences of an incorrect or incomplete covenant

Enforceability Risk: Ambiguous waivers may be invalidated by a court

Statute Issues: Incorrect effective dates can affect limitation periods

Regulatory Exception: Some government or criminal claims cannot be waived

Tax Consequences: Settlement characterization may trigger reporting and withholding

Authentication Failures: Weak e-sign methods may not satisfy ESIGN/UETA proof

Costs: Remediation, further litigation, or rescission can raise exposure

eSignature provider comparison for executing a Covenant Not to Sue

Common capability and pricing dimensions to consider when choosing an eSignature provider for legal releases and covenants.

	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 / Plan	Yes, 7-day trial	Varies by plan	Varies by plan	Limited free option	Limited free option
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Security and compliance essentials for electronic execution

Encryption: TLS 1.2/1.3 in transit; AES-256 at rest

Standards: SOC 2 Type II; ISO 27001

Regulatory: ESIGN Act (15 U.S.C. §7001) and UETA compliance

Healthcare: HIPAA support with BAA available

Audit Trail: Timestamps, IP, and action logs preserved

Accessibility: WCAG 2.0 Level AA conformity

Real-world ways organizations use a Covenant Not to Sue

Representative examples show how covenants simplify dispute resolution in different settings.

Settlement in a Business Dispute

A vendor and client resolve payment claims through a release

Parties exchange a release for a single lump-sum payment
The covenant limits future claims to those arising after execution and includes a confidentiality exhibit to protect trade secrets.

Construction Claim Resolution

A contractor and owner settle delay claims tied to Project A

Contractor receives a partial payment and lien waiver
The covenant narrows barred claims to listed change orders and preserves rights for future latent defect claims discovered after close-out.

Frequently asked questions about Covenants Not to Sue

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

Need help? Contact support

Can a covenant bar all future claims?
A covenant can be broad, but courts may limit enforcement if language is ambiguous or if it attempts to waive non-waivable claims like criminal matters or certain regulatory actions. Draft clear scope and exceptions to reduce litigation over interpretation.
Is an e-signed covenant enforceable?
Yes—electronic signatures are generally enforceable under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted, provided intent, consent, attribution, and reliable record retention are present.
When is notarization required?
Notarization rules depend on the document purpose and state law. Some states or transaction types (e.g., deeds) require a notary or witnesses; confirm state requirements before relying on non-notarized execution.
What if a signer lacked authority?
If a signer lacked authority, the covenant may be voidable. Verify corporate signer authority through board resolutions or power-of-attorney documents before finalizing.
Can a covenant be revoked after signing?
Revocation depends on contract terms and consideration. If the covenant is supported by consideration and properly executed, unilateral revocation is typically not allowed; remedies may require mutual agreement or court action.
Should counsel always review the covenant?
Yes. Legal review ensures appropriate scope, preserves reserved rights, and confirms compliance with applicable statutes and public policy that might render certain waivers unenforceable.

Explore Templates

Notice of Breach of Lease Utah Landlord Tenant Agreement Utah Paternity Law and Procedure Handbook Utah Marriage Certificate Utah Complaint Form Non-Military Affidavit

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now