Can an extension be signed electronically?

Yes. Electronic signatures satisfy the ESIGN Act (15 U.S.C. ch. 96) and UETA in most jurisdictions when intent, consent, attribution, and record retention are present. Confirm there are no statutory exceptions for the specific transaction before relying solely on e-signatures.

Is notarization required for an extension?

Notarization requirements depend on the document and state law. Many states permit remote online notarization (RON) with identity proofing and recording when authorized; other states require in-person notarization. Check the relevant state notary commission or counsel before assuming RON is acceptable.

What if signer names differ from IDs?

If signer names differ from government IDs, expect identity verification steps or requests to correct records. Mismatched names can trigger backup withholding or enforcement challenges. Require a corrective amendment or certified identification where appropriate before finalizing the extension.

How long must signed extensions be kept?

Retention periods vary by document and regulation. Financial records should be kept at least three years per IRC §6501(a); HIPAA-covered documents six years per 45 CFR §164.530(j). Retain originals for the active term and consult counsel for state-specific requirements.

Are electronic records admissible in court?

Yes. Under the ESIGN Act (15 U.S.C. ch. 96) and UETA, electronic records and signatures are admissible when they demonstrate intent, consent to electronic transactions, attribution to the signer, and reliable record retention. Preserve audit trails and metadata to support admissibility.

Which vendors support HIPAA and RON?

Vendor capabilities vary. signNow offers HIPAA compliance with a BAA and a range of authentication options; RON support differs by provider and state. Confirm with any vendor whether they provide RON, identity proofing, and compliant record retention before relying on remote notarization.

Electronic Signature
Templates
Miscellaneous
User Extensions Agreement

User Extensions Agreement

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

USER EXTENSIONS AGREEMENT

Parties

Provider Name: Provider Address: Provider Entity Type:

Individual Corporation LLC Other:

User Name: User Address: User Entity Type:

Individual Corporation LLC Other:

Recitals

WHEREAS, Provider develops, maintains and licenses software extensions, plugins, or add-on modules used to extend functionality of the User's software environment; and

WHEREAS, User desires to obtain certain extensions from Provider and Provider is willing to provide such extensions under the terms and conditions set forth in this Agreement;

NOW, THEREFORE, in consideration of the mutual covenants and agreements contained herein, the parties agree as follows:

Scope of Work

Provider shall deliver the extensions, associated documentation, and any customizations described below. Provider will perform installation guidance, reasonable configuration assistance, and limited testing as set out in the Scope of Work field.

Scope of Work (Describe deliverables, functionality, acceptance criteria, milestones):

Payment Terms

User shall pay Provider the fees for development, license and delivery of the extensions as specified below. Fees are exclusive of taxes unless otherwise specified.

Total Fee: Payment Schedule: Invoice Due (Net days): Late Fee / Interest: Taxes:

Term and Termination

This Agreement commences on the Start Date and continues until the End Date unless earlier terminated in accordance with this section.

Start Date: End Date:

Termination for Convenience (Notice Period):

Either party may terminate this Agreement for material breach by the other party if such breach remains uncured for the notice period specified above following written notice. Termination shall not relieve User of the obligation to pay for Services and Deliverables performed or delivered prior to the effective date of termination.

Confidentiality

Each party shall keep confidential all non-public information disclosed by the other party that is designated as confidential or that reasonably should be understood to be confidential given the nature of the information and the circumstances of disclosure ("Confidential Information"). Confidential Information shall not include information that is (a) publicly known through no fault of receiving party, (b) rightfully received from a third party without breach, or (c) independently developed without use of or reference to the disclosing party's Confidential Information.

The receiving party shall (i) use Confidential Information only to perform its obligations under this Agreement, (ii) restrict disclosure to personnel with a need to know and who are bound by confidentiality obligations at least as protective as those herein, and (iii) take reasonable measures to prevent unauthorized disclosure.

Intellectual Property and License

Provider retains all right, title and interest in and to the extensions, source code, know-how, tools, and any modifications thereto, except as expressly granted herein. Subject to payment in full and compliance with this Agreement, Provider grants User a non-exclusive, non-transferable license to use the delivered extensions for User's internal business purposes as set forth in the Scope of Work. Any custom development commissioned by User may be subject to separate ownership or license terms as expressly provided in the Scope of Work.

Warranties; Disclaimer

Provider warrants that the extensions will materially conform to the specifications set forth in the Scope of Work for a period of thirty (30) days after delivery. Provider's sole obligation under this warranty shall be to use commercially reasonable efforts to correct non-conforming functionality. EXCEPT AS EXPRESSLY SET FORTH HEREIN, THE EXTENSIONS ARE PROVIDED "AS IS" AND PROVIDER DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT.

Limitation of Liability

Except for liability arising from willful misconduct or a party's breach of confidentiality or intellectual property obligations, neither party shall be liable to the other for indirect, incidental, consequential, special, or punitive damages, and aggregate liability for direct damages shall not exceed the amount actually paid by User to Provider under this Agreement in the twelve (12) months preceding the event giving rise to liability.

Governing Law

This Agreement shall be governed by and construed in accordance with the laws of the state of without regard to its principles of conflict of laws. The parties submit to the exclusive jurisdiction of the courts located in that state for resolution of disputes.

Entire Agreement

This Agreement, including the Scope of Work and any exhibits or addenda signed by the parties, constitutes the entire agreement between Provider and User with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, proposals, or representations, whether written or oral. Any amendment or modification must be in writing and signed by authorized representatives of both parties.

Miscellaneous

Notices shall be in writing and delivered to the addresses set forth above. If any provision of this Agreement is held invalid or unenforceable, the remainder of the Agreement shall remain in full force and effect. The parties are independent contractors and nothing in this Agreement creates an employment, partnership, joint venture, or agency relationship.

Execution

The individuals signing below represent and warrant that they are authorized to bind their respective parties to this Agreement.

Provider Printed Name:

By:

Date:

User Printed Name:

By:

Date:

What the User Extensions Agreement Is

The User Extensions Agreement is a written addendum that documents an authorized extension of time, services, features, or license privileges provided to a user under an existing contract or terms of service. It clarifies scope, effective dates, any additional fees or consideration, and updated obligations for both parties. This agreement can modify termination rights, renewal schedules, or support commitments while preserving the original contract's primary terms. Use it to memorialize negotiated extensions, reduce disputes, and ensure clear enforceability under electronic signature laws when executed by authorized signatories.

Why a User Extensions Agreement Matters

A User Extensions Agreement reduces ambiguity about modified rights, timelines, and fees and creates a clear record of consent. When signed electronically it meets the ESIGN Act (15 U.S.C. ch. 96) and UETA requirements for enforceability in most U.S. jurisdictions.

Who Typically Uses a User Extensions Agreement

Organizations and individuals use the User Extensions Agreement to document extended deadlines, feature access, pricing changes, or temporary license extensions under an existing contract.

Small businesses negotiating short-term license, feature, or support extensions with existing vendors.
Enterprise legal and procurement teams documenting scope and fee adjustments for renewals.
Service providers granting temporary access or extended service levels to clients.

Use the agreement to create an auditable record for future disputes and to clarify who authorized extensions and under what conditions.

Core Elements to Include in a Professional Agreement

A complete agreement defines the extension's scope, duration, consideration, signer authority, notice procedures, and dispute resolution terms to integrate smoothly with the underlying contract.

Scope

Describe exactly what is extended (services, features, licenses, deadlines), any limits or exclusions, and whether the extension modifies or supplements specific clauses of the original contract.

Effective Date

State the start and end dates using MM/DD/YYYY, whether retrospective extensions apply, and how the effective date affects renewal triggers or notice periods in the main agreement.

Consideration Detail

Specify monetary payments, service credits, or non-monetary exchanges; include timing of payments, invoicing procedures, prorated calculations, billing practices, and remedies for missed consideration to avoid ambiguity.

Authority

Identify signatories and confirm they have authority to bind their organization; require printed name, title, and a statement that execution amends the underlying agreement where permitted.

Notices

Update notice addresses and methods, specify whether email or e-delivery satisfies notice requirements, and describe how changes to contact details must be communicated to remain effective.

Dispute Resolution

State the governing law, venue for disputes, any agreed mediation or arbitration procedures, and whether costs or attorney fees are recoverable after enforcement of this extension.

Essential Information to Capture

Parties Identified: Full legal names and entity type

Effective Date: Use MM/DD/YYYY date format

Extension Details: Scope, limits, exclusions listed

Consideration Detail: Amount, credits, timing, invoicing

Signer Details: Printed name, title, date

Governing Law: State selection and venue

Penalties and Risks of an Incorrect Agreement

Unenforceable Terms: Extension may be invalid

Backup Withholding: 24% tax withholding

Late Fees: Additional charges possible

Compliance Breach: HIPAA or FERPA exposure

Litigation Risk: Contract dispute or damages

Recordkeeping Failures: Retention violations

Common Mistakes to Avoid

Failing to state exact effective dates leads to disputes about when obligations begin or end and can void intended extension rights if ambiguous.
Using unclear consideration language such as 'reasonable fee' without specific amounts or calculation methods creates billing disputes and enforcement difficulties.
Not confirming signatory authority or including titles may result in signatures that do not bind the organization and can be rejected in court.
Omitting notice provisions or failing to update contact details can prevent timely communications about defaults, renewals, or early terminations.

Step-by-Step: Completing a User Extensions Agreement

Follow these steps to fill, approve, and execute an extension while preserving the original contract's terms and legal enforceability.

01

Prepare: Gather original contract and proposed extension text
02

Draft: Describe scope, dates, fees, and amendments clearly
03

Review: Legal and stakeholder approval, confirm signer authority
04

Execute: Sign, date, and retain copies; capture audit trail

How to Customize and Complete the Agreement Online

Set up fields, authentication, and routing to match your approval process before sending for signature through an e-signature platform.

Field Name and Configuration Guide	Configuration
Signature Field Settings and Options	Required signers, initials, and date fields
Authentication Method Configuration Details and Options	Email link, SMS code, or KBA
Routing Order and Parallel Options	Specify signing order and parallel routing options
Conditional Field Visibility Rules and Logic	Show fields only when conditions are met

Where to File, Send, or Submit Executed Agreements

Identify the appropriate recipient, internal file location, and any regulatory filing required once parties execute the extension electronically.

Client: Send executed copy to the client's authorized contact
Internal Records: Upload signed PDF to contract repository with tags
Accounting: Provide invoice and updated payment schedule to billing
Regulatory: File with agencies only if statute requires it

Distribution Methods and Platform Requirements

Choose a platform that supports required file formats, signer authentication, and retains an audit trail for enforceability.

File Types: PDF, DOCX, or native uploads
Integrations: Salesforce, NetSuite, Google Workspace
Security: TLS 1.2/1.3 and AES-256

Timelines, Deadlines, and Processing Expectations

Timelines depend on internal approvals, regulatory filing requirements, and whether notarization or witness authentication is necessary before the extension takes effect.

Drafting and Review:

Allow at least 3–5 business days for drafting and legal review

Internal Approvals:

Dependent on signatory availability; typical 1–7 business days

Remote Notarization:

RON may add 1–3 business days and identity proofing

eSignature Completion:

Many signings complete within 24 hours electronically

Record Retention:

Signed copies uploaded to repository immediately after completion

Examples: How Organizations Use an Extensions Addendum

These short case summaries illustrate how organizations used an extensions addendum to manage deadlines, access, or payment terms while maintaining compliance.

Martin Properties — Tim Martin

Martin Properties used an extensions agreement to defer tenant move-in dates and extend lease terms after construction delays.

Needed rapid electronic signatures across mobile and desktop.
They executed the extension electronically, captured audit trails and signer attribution, and updated the contract repository so accounting and property management teams could implement revised billing and occupancy schedules without paper delays.

Fertility Centers — John Butler

Fertility Centers implemented extensions to consent forms and appointment scheduling for treatment plan adjustments during regulatory updates and staffing changes.

Required HIPAA-compliant electronic signatures and audit logs.
They used electronic execution to ensure timely consent updates, maintain patient privacy controls, and keep six years of records per 45 CFR §164.530(j), simplifying audits and regulatory reporting for clinical staff.

eSignature Solution Pricing Comparison

Compare common plan features and starting prices among leading eSignature vendors to evaluate cost and compliance considerations for executing extensions electronically.

	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 offer	Varies by offer	Varies by offer	Varies by offer
Bulk Send	Yes (Business Premium)	Varies by plan	Varies by plan	Varies by plan	Varies by plan
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes (BAA required)	Varies by plan	Varies by plan	Varies by plan	Varies by plan
Envelope Cap	No envelope cap	100 envelopes/user/year	Varies by plan	Varies by plan	Varies by plan

Frequently Asked Questions

Answers to common questions about drafting, signing, and enforcing a User Extensions Agreement electronically, including notarization, retention, and signatory authority.

Need help? Contact support

Can an extension be signed electronically?
Yes. Electronic signatures satisfy the ESIGN Act (15 U.S.C. ch. 96) and UETA in most jurisdictions when intent, consent, attribution, and record retention are present. Confirm there are no statutory exceptions for the specific transaction before relying solely on e-signatures.
Is notarization required for an extension?
Notarization requirements depend on the document and state law. Many states permit remote online notarization (RON) with identity proofing and recording when authorized; other states require in-person notarization. Check the relevant state notary commission or counsel before assuming RON is acceptable.
What if signer names differ from IDs?
If signer names differ from government IDs, expect identity verification steps or requests to correct records. Mismatched names can trigger backup withholding or enforcement challenges. Require a corrective amendment or certified identification where appropriate before finalizing the extension.
How long must signed extensions be kept?
Retention periods vary by document and regulation. Financial records should be kept at least three years per IRC §6501(a); HIPAA-covered documents six years per 45 CFR §164.530(j). Retain originals for the active term and consult counsel for state-specific requirements.
Are electronic records admissible in court?
Yes. Under the ESIGN Act (15 U.S.C. ch. 96) and UETA, electronic records and signatures are admissible when they demonstrate intent, consent to electronic transactions, attribution to the signer, and reliable record retention. Preserve audit trails and metadata to support admissibility.
Which vendors support HIPAA and RON?
Vendor capabilities vary. signNow offers HIPAA compliance with a BAA and a range of authentication options; RON support differs by provider and state. Confirm with any vendor whether they provide RON, identity proofing, and compliant record retention before relying on remote notarization.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now