Establishing secure connection…Loading editor…Preparing document…

License Release Agreement

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

LICENSE RELEASE AGREEMENT

This License Release Agreement (the "Agreement") is made and entered into on , by and between Licensor Name: and Licensee Name: .

RECITALS

WHEREAS, Licensor is the owner or authorized controlling party of certain intellectual property, works, or rights described as: (the "Licensed Materials");

WHEREAS, Licensee has previously held or asserted a license, claim, or use right in respect of the Licensed Materials, and the parties wish to document the release, surrender, or modification of those rights under the terms set forth below;

WHEREAS, in consideration of the mutual covenants and other good and valuable consideration set forth herein, the parties agree to release and settle their respective rights and obligations as provided in this Agreement.

SCOPE OF RELEASE / SCOPE OF WORK

1. Release. Subject to the terms and conditions of this Agreement, Licensor hereby irrevocably releases, relinquishes, and forever discharges Licensee from all claims, demands, causes of action, liabilities, and obligations arising out of or related to Licensee's past use of or claim to the Licensed Materials to the extent described in this Agreement. This release applies only to the rights expressly identified herein and does not operate as a grant of new rights except as expressly provided.

2. Scope of Work / Deliverables (if applicable). The parties acknowledge the following obligations, deliverables, or actions to be performed in connection with this release:

PAYMENT TERMS

As consideration for the release and any license modifications set forth herein, Licensee shall pay Licensor the amounts and according to the schedule described below. All payments shall be in lawful money and made to the payee designated by Licensor.

TERM AND TERMINATION

This Agreement shall commence on and shall continue in effect until , unless earlier terminated as provided below.

Either party may terminate this Agreement for material breach by the other party if the breaching party fails to cure such breach within days after receipt of written notice. Termination does not relieve either party of obligations accrued prior to termination.

CONFIDENTIALITY

Each party acknowledges that it may receive Confidential Information from the other party. "Confidential Information" means non-public information disclosed in connection with this Agreement, including but not limited to financial terms, business plans, technical data, source materials, and any information labeled or reasonably understood to be confidential.

Each receiving party shall (a) hold Confidential Information in strict confidence and protect it with at least the same degree of care it uses to protect its own confidential information but in no event less than reasonable care; (b) use Confidential Information solely to perform its obligations under this Agreement; and (c) not disclose Confidential Information to any third party except to those employees, agents, counsel, or professional advisors who have a need to know and who are bound by confidentiality obligations at least as protective as those herein. Confidential Information shall not include information that is or becomes generally available to the public other than through a breach of this Agreement, was lawfully known to the receiving party prior to disclosure, or was independently developed without use of the disclosing party's Confidential Information.

REPRESENTATIONS, WARRANTIES AND COVENANTS

Licensor represents and warrants that it has the full right, power, and authority to enter into this Agreement and to grant the release and any limited licenses described herein and that, to Licensor's knowledge, the Licensed Materials do not infringe third party rights except as expressly disclosed in writing to Licensee prior to the Effective Date.

Licensee represents that it will abide by the terms of this Agreement and will not assert claims inconsistent with the release granted herein. Each party covenants to execute and deliver such further instruments and take such further actions reasonably necessary to effectuate the terms and intent of this Agreement.

INDEMNIFICATION

Each party shall indemnify, defend, and hold harmless the other party from and against any and all third-party claims, liabilities, losses, costs and expenses (including reasonable attorneys' fees) arising out of the indemnifying party's breach of representations, warranties, or obligations under this Agreement, except to the extent such claims result from the other party's gross negligence or willful misconduct.

GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of the State of without regard to its conflicts of law principles. The parties submit to the exclusive jurisdiction of the state and federal courts located in that state for any dispute arising under this Agreement.

ENTIRE AGREEMENT; AMENDMENT

This Agreement constitutes the entire understanding and agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, negotiations, and understandings, whether written or oral. Any amendment or modification to this Agreement must be in writing and signed by authorized representatives of both parties.

GENERAL PROVISIONS

If any provision of this Agreement is held invalid or unenforceable, the remainder of this Agreement will remain in full force and effect. No waiver of any breach shall constitute a waiver of any other breach. The parties acknowledge that monetary damages would be an inadequate remedy for any breach of the confidentiality or release provisions and that the non-breaching party shall be entitled to seek equitable relief in addition to other remedies.

LICENSOR

Printed Name:

By:

Date:

Title:

LICENSEE

Printed Name:

By:

Date:

Title:

Enter text✕

What a License Release Agreement Is and When it’s Used

A License Release Agreement is a legal document where one party (the licensor) relinquishes claims, rights, or obligations under an existing license and the other party (the licensee) accepts that release. Typical uses include ending software licenses, releasing intellectual property claims, or removing encumbrances on licensed technology. The agreement describes the scope of rights released, any consideration paid, effective date, and surviving obligations such as confidentiality or indemnity. Parties commonly use releases to avoid litigation, finalize settlements, or permit new licensing arrangements free of prior restraints.

Why a Clear Release Matters for Risk and Enforcement

A precise License Release Agreement limits future disputes by defining released rights, residual obligations, and remedies, and by specifying governing law and effective date.

Why a Clear Release Matters for Risk and Enforcement

Typical parties and situations that rely on a License Release Agreement

Confirm each signer’s authority and include required attachments to avoid later challenges to the release’s scope or validity.

  • Technology licensors and licensees resolving software disputes or replacing legacy licenses with new agreements.
  • Creative rights holders and publishers clearing prior claims before a new distribution or assignment.
  • Commercial parties completing a settlement where one side receives a release in exchange for payment or performance.

Who can sign a License Release Agreement

Corporate Officer

A duly authorized officer (CEO, CFO, General Counsel) may sign on behalf of a corporation. The signer should confirm board or delegated authority in corporate records and include printed name and title beneath the signature to evidence signing authority.

Authorized Individual

An individual licensee or licensor may sign in their personal capacity. If signing for an entity, include a capacity statement (for example, 'John Doe, CFO') and verify any required corporate or partnership approvals.

Core clauses every professional License Release Agreement should include

A well-drafted release combines precise definitions with clear operational provisions. Each clause controls scope, duration, and remedies; omissions create ambiguity and litigation risk.

Parties and Recitals

Identify licensor and licensee by full legal name, describe the original license being released, and state the background facts that justify the release.

Scope of Release

Spell out exactly which rights, claims, obligations, or territories are released. Use inclusive language and avoid vague terms such as 'all matters' without definition.

Consideration

Specify payments, credits, or other consideration. If nominal, state that consideration exists to meet contract formation rules under state law.

Effective Date

Provide a clear effective date in MM/DD/YYYY format and state whether performance before that date is covered by the release.

Surviving Obligations

List obligations that survive the release (confidentiality, indemnity, escrow, or royalties) and their duration.

Governing Law & Remedies

Name the governing state law and dispute resolution path, and limit or clarify available remedies such as injunctive relief or liquidated damages.

Security and compliance items to note when exchanging releases

Encryption: TLS 1.2/1.3, AES-256 at rest
Audit Trail: Complete timestamps and IP log
HIPAA: BAA required for PHI
21 CFR Part 11: Supported where required
SOC 2 / ISO: SOC 2 Type II, ISO 27001
ESIGN / UETA: Compliant for U.S. transactions

Step-by-step: completing a License Release Agreement

Follow a consistent sequence: identify parties, define the release, list consideration, set the effective date, include signatures and any notarization, and distribute executed copies to all parties.

  • 01
    1. Identify Parties: Enter full legal names and roles for each party.
  • 02
    2. Define Release: Describe released rights, limitations, and exclusions.
  • 03
    3. Record Consideration: State payment terms, if any, and method of transfer.
  • 04
    4. Sign and Date: Collect signatures, dates, and any notarizations or witness attestations.

Typical online workflow settings for an electronic release

Configure the document for clear roles, authentication, and retention before sending for signature to reduce rework and ensure legal compliance.

Field Configuration
Upload Document Use a final PDF or DOCX; include exhibits as attachments.
Signature Fields Place signature, date, and capacity fields for each signer.
Signer Authentication Choose email link, SMS code, or stronger KBA where required.
Retention Settings Enable audit trail and set retention period per policy.

End-to-end process: from draft to executed release

An efficient process reduces risk: prepare, verify identities, obtain signatures, and store executed copies with an audit trail.

  • Prepare the Draft: Assemble facts, exhibits, and authority documentation.
  • Assign Roles: Designate who signs, initials, and witnesses.
  • Sign Electronically: Use an ESIGN/UETA-compliant platform for signatures.
  • Store Execution Copies: Archive signed PDF with audit trail and metadata.

Technical considerations for electronic completion and submission

Document export formats, access controls, and retention settings should match your legal and records-management policies before finalizing execution.

  • Authentication Options: Email link, SMS code, KBA, or SSO depending on risk
  • Audit and Tamper Evidence: Detailed logs, timestamps, and tamper-evident PDF outputs
  • Integrations: Connectors for storage and workflow such as Salesforce, NetSuite, or Box

Consequences of errors or incomplete releases

Ambiguous Scope: May lead to continued litigation
Improper Signatory: Release could be voided
Missing Consideration: Contract formation may be challenged
Lack of Notarization: Affects recordability or enforceability
Tax Consequences: Unreported consideration risks IRS penalties
Data Exposure: Violates privacy rules if PHI is mishandled

Common drafting and execution pitfalls to avoid

  • Using vague language that fails to identify the exact licensed assets or claim categories released.
  • Omitting signer capacity lines when an entity signs, creating doubt about authority to bind the organization.
  • Forgetting to attach or reference the original license or addenda that specify what is being released.
  • Failing to select governing law and dispute resolution, which increases uncertainty about enforcement venue and remedies.

Typical dates and deadlines to track in a release workflow

Key dates include the effective date, payment deadlines for consideration, deadlines for objections or revocations (if any), and record retention start and end dates.

Effective Date:

The MM/DD/YYYY when the release becomes operative

Payment Deadline:

Date by which any consideration must be transferred

Revocation Window:

If provided, state the number of days to revoke

Record Retention Start:

Often the effective date or execution date

Retention End:

As required by document retention policy or law

Key milestones from negotiation to archived release

A sequential milestone view helps teams coordinate negotiation, signature collection, and archival tasks without delaying related transactions.

01

Draft Finalization

Complete negotiations and attach exhibits prior to signature routing

02

Authority Verification

Confirm signatory capacity and approvals before sending

03

Execution and Notarization

Collect signatures and any required notarizations or witness attestations

04

Archive and Distribute

Store executed copies and distribute to stakeholders with audit evidence

Comparing common eSignature options for executing a License Release Agreement

This table summarizes core pricing and feature differences among signNow and several widely known competitors to help evaluate platform suitability for executing releases.

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 by vendor Varies by vendor Varies by vendor Varies by vendor
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No
Envelope Cap No cap 100 envelopes/user/year Varies Varies Varies

Frequently asked questions about License Release Agreements

Answers to common practical and legal questions about drafting, signing, and enforcing a License Release Agreement.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users