Establishing secure connection…Loading editor…Preparing document…

Software License Amendment Form

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

SOFTWARE LICENSE AMENDMENT

This Software License Amendment ("Amendment") is made as of the , (the "Effective Date"), by and between Licensor: , a entity, with its principal place of business at ; and Licensee: , a entity, with its principal place of business at .

RECITALS

WHEREAS, Licensor and Licensee are parties to that certain Software License Agreement dated , (the "Agreement");

WHEREAS, the parties desire to amend certain provisions of the Agreement as set forth in this Amendment to reflect changes in the licensed software, scope, fees, and support obligations;

WHEREAS, capitalized terms used but not defined in this Amendment shall have the meanings given to them in the Agreement unless otherwise provided herein.

NOW, THEREFORE, in consideration of the mutual agreements contained herein and other good and valuable consideration, the sufficiency and receipt of which are hereby acknowledged, the parties agree as follows:

1. AMENDMENT TO DEFINITIONS

Section(s) of the Agreement are amended to revise the following definitions. The definition of "Licensed Software" is amended to include the updates and modules described in Exhibit A attached hereto. Any capitalized term defined in Exhibit A shall be deemed incorporated into the Agreement.

2. MODIFICATION TO LICENSE GRANT

Effective as of the Effective Date, Section [insert section number] of the Agreement is deleted in its entirety and replaced with the following:

3. FEES AND PAYMENT

In consideration for the amendments set forth in this Amendment, Licensee shall pay Licensor the amount of USD, payable in accordance with the following terms:

4. TERM; TERMINATION

Except as expressly modified herein, the Term of the Agreement shall remain unchanged, provided that the amendments in this Amendment shall commence on the Effective Date and continue for the remaining term of the Agreement. Termination rights under the Agreement remain in full force; however, a material breach of the amended provisions shall constitute a material breach of the Agreement entitling the non-breaching party to terminate in accordance with the Agreement.

5. SUPPORT AND MAINTENANCE

Licensor shall provide support and maintenance for the amended Licensed Software in accordance with the service levels set forth in Exhibit B attached hereto. Any deviations from standard service levels shall be documented in Exhibit B and, where applicable, adjusted fees shall be reflected in Section 3 above.

6. REPRESENTATIONS AND WARRANTIES

Each party represents and warrants that: (a) it has the full corporate power and authority to enter into this Amendment and to perform its obligations hereunder; (b) execution and delivery of this Amendment have been duly authorized by all necessary corporate actions; and (c) this Amendment, when executed and delivered, will constitute a valid and binding obligation enforceable in accordance with its terms.

7. INDEMNIFICATION

Each party agrees to indemnify, defend and hold harmless the other party from and against any third-party claims, liabilities, losses, damages, costs, and expenses (including reasonable attorneys' fees) arising out of the indemnifying party's breach of this Amendment or the Agreement, except to the extent such liability results from the gross negligence or willful misconduct of the indemnified party.

8. LIMITATION OF LIABILITY

Except as expressly set forth in this Amendment or the Agreement, in no event shall either party be liable to the other for any indirect, incidental, consequential, special, exemplary, or punitive damages, whether in contract, tort or otherwise, even if advised of the possibility of such damages. The parties' aggregate liability under this Amendment shall be limited to direct damages not to exceed the fees paid under this Amendment during the twelve (12) months preceding the claim.

9. CONFIDENTIALITY

All information exchanged pursuant to this Amendment shall be treated as Confidential Information under the Agreement. The parties agree that any disclosure or use of Confidential Information inconsistent with the Agreement shall constitute a material breach.

10. NOTICES

All notices required or permitted under this Amendment shall be in writing and shall be delivered to the addresses below (or such other address as a party designates by written notice):

11. AMENDMENTS; WAIVER; COUNTERPARTS

This Amendment may be amended only by a written instrument signed by authorized representatives of both parties. No failure or delay by either party in exercising any right shall operate as a waiver. This Amendment may be executed in counterparts, each of which shall be deemed an original, and all of which together shall constitute one and the same instrument.

12. GOVERNING LAW; SEVERABILITY; ENTIRE AGREEMENT

This Amendment shall be governed by and construed in accordance with the laws of the jurisdiction specified in the Agreement. If any provision of this Amendment is held to be invalid or unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable, and the remaining provisions shall continue in full force and effect. This Amendment, together with the Agreement and any exhibits expressly incorporated herein, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements and understandings relating thereto.

13. EXHIBITS

The following exhibits are attached and incorporated by reference: Exhibit A — Amended Licensed Software and Definitions; Exhibit B — Support and Service Levels. Any deliverables or schedules referenced in those exhibits shall have the force of this Amendment.

SIGNATURES

Licensor:

By:

Date:

Licensee:

By:

Date:

Enter text✕

What a Software License Amendment Form Is

A Software License Amendment Form is a written modification to an existing software license agreement that documents agreed changes to scope, term, fees, licensed users, support levels, or deliverables. It identifies the original agreement, lists specific clauses being changed, sets an effective date, and attaches any revised exhibits or schedules. Proper execution requires authorized signatories for each party and clear identification of consideration where applicable. When executed correctly the amendment becomes part of the contract and supersedes conflicting prior terms; electronic signing is generally acceptable under ESIGN and UETA frameworks.

Why using a formal amendment matters

A formal Software License Amendment Form reduces ambiguity, documents mutual consent to changes, protects contractual rights, and creates an auditable record. It helps avoid disputes about scope, fees, or renewal terms by making modifications explicit and time-stamped.

Why using a formal amendment matters

Who typically executes and manages amendments

Parties and roles that commonly prepare or sign amendments include corporate legal teams, procurement, product owners, and vendor account managers.

  • Software vendors and contract managers who update license scope or fees.
  • Customer legal, procurement, or IT teams who accept modifications and operational impacts.
  • Third-party resellers or integrators when sublicensing or support changes are required.

Each signer should have documented authority; corporate approvers often supply a signature block listing name, title, and date.

Typical signatory profiles

Licensor — Executive

A senior company representative (VP or authorized signatory) who can bind the vendor for licensing, warranty, and support obligations. Their signature confirms vendor acceptance of modified commercial or technical terms and may trigger new delivery or billing schedules.

Licensee — Officer

A procurement or legal representative authorized to accept contractual changes on behalf of the customer. This signer confirms budgetary approval and acknowledges any new obligations such as increased user counts, payment terms, or escrow provisions.

Key information the form should record

Effective Date: MM/DD/YYYY format
Original Agreement: Title and execution date
Amendment Summary: Clear concise list
Consideration: Dollar amount or exchange
Signatures: Printed name and title
Attachments: Revised exhibits listed

Consequences of incorrect or incomplete amendments

Invalid Amendment: Unenforceable
Unauthorized Signature: Voidable change
Tax Exposure: Reporting issues
Breach Claims: Liability increase
IP Ambiguity: Ownership disputes
Confidentiality Risk: Disclosure errors

Common preparation mistakes to avoid

  • Failing to reference the original agreement precisely, which can create uncertainty about which clauses remain in force.
  • Using vague language like 'adjust fees reasonably' without precise formulas, creating room for later disagreement and dispute.
  • Allowing unsigned or partially signed amendments into operational workflows, leading to billing or support problems.
  • Not confirming signatory authority or corporate approval, which risks a counterparty later challenging amendment validity.

Practical examples of amendment use

These brief scenarios show typical reasons organizations use a Software License Amendment Form to document agreed changes effectively.

Increase in User Seats

A mid-size company needed 50 additional named users to support growth

  • Amendment added seat counts and pricing per seat
  • The amendment referenced the original agreement, set a clear effective date, and established a revised invoice schedule to avoid billing disputes and enable provisioning.

Extended Support SLA

An enterprise requested 24/7 support and faster response times

  • Vendor agreed to higher SLAs with extra fees
  • The amendment defined SLA metrics, attached a support exhibit, and required signatures from authorized vendor and customer representatives to bind the new service level.

Step-by-step: completing a Software License Amendment Form

Follow these steps to prepare, review, and execute an enforceable amendment that integrates cleanly with the original license.

  • 01
    Review Original: Identify clauses to change and cross-reference exhibit numbers.
  • 02
    Draft Changes: Use precise, numbered edits and avoid ambiguous phrases.
  • 03
    Obtain Approvals: Confirm internal authority and budget signoffs.
  • 04
    Execute: Collect dated signatures from authorized representatives.

Sample eSignature vendor comparison for amendment workflows

Comparison of common plan criteria for eSignature providers used to execute and store amendments; signNow is listed first for parity with other vendors.

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

Typical digital workflow settings for an amendment

Set these fields when creating an electronic amendment workflow to ensure secure routing, proper authentication, and repeatable processing.

Field Configuration
Authentication Email plus optional SMS code or KBA for higher assurance
Signature Type Simple e-signature or PKI-based digital signature as required
Reminders Automated reminders at set intervals until signed
Routing Order Specify sequential or parallel signers and approval steps

Technical and platform considerations

Confirm integration, file format support, and authentication options before eSign deployment for amendment workflows.

  • Integrations: Salesforce, NetSuite, Google Workspace
  • File Formats: PDF, DOCX, HTML supported
  • Authentication: Email, SMS, KBA, SSO

Frequently asked questions about amendments and eSignatures

Answers to common questions about validity, authority, notarization, and recordkeeping when using a Software License Amendment Form and electronic signing.


Need help? Contact support

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