Establishing secure connection…Loading editor…Preparing document…

Support Services Extension

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

SUPPORT SERVICES EXTENSION

This Support Services Extension (the "Extension") is entered into effective as of by and between Client Name: (the "Client") and Service Provider Name: (the "Provider").

WHEREAS

WHEREAS, the Client and the Provider entered into a Support Services Agreement dated under Agreement Reference Number: ;

WHEREAS, the parties wish to extend the term and certain support services described in the original Agreement on the terms set forth in this Extension;

NOW, THEREFORE, in consideration of the mutual covenants and agreements set forth below, the parties agree as follows:

SCOPE OF EXTENSION

The services to be provided under this Extension are limited to those described above and any tasks expressly agreed in writing by the parties. Any additional services beyond the scope set forth here shall be subject to a separate written change order and additional fees as agreed by the parties.

PAYMENT TERMS

Invoices shall be payable within days of receipt unless otherwise agreed. Overdue amounts shall accrue a late fee of from the due date until paid. The parties agree that the stated late fee is a reasonable estimate of the damages caused by late payment and not a penalty.

TERM AND TERMINATION

This Extension commences on and shall continue through unless earlier terminated in accordance with this Section.

Either party may terminate this Extension for convenience upon days' written notice. Either party may terminate immediately for material breach by the other party that remains uncured after fifteen (15) days' written notice specifying the breach. Termination shall not relieve the Client of its obligation to pay for services performed and reimbursable expenses incurred through the effective date of termination.

CONFIDENTIALITY

Each party acknowledges that, during performance of the services, it may receive Confidential Information of the other. "Confidential Information" means nonpublic information disclosed in any form that is designated confidential or that reasonably should be understood to be confidential. Each party agrees to (a) hold Confidential Information in confidence using at least the same degree of care it uses to protect its own confidential information, (b) use Confidential Information solely to perform its obligations under this Extension, and (c) not disclose Confidential Information to third parties except to employees, contractors, or professional advisors who have a need to know and who are bound by confidentiality obligations at least as protective as those herein. Confidentiality obligations shall survive termination of this Extension for a period of three (3) years, except for trade secrets which shall be protected for as long as they qualify as trade secrets under applicable law.

GOVERNING LAW

This Extension shall be governed by and construed in accordance with the laws of the State/Province of without regard to its conflict of laws principles. The parties submit to the exclusive jurisdiction of the courts located in that jurisdiction for any disputes arising out of or relating to this Extension.

ENTIRE AGREEMENT; AMENDMENTS

Except as modified by this Extension, all terms and conditions of the original Agreement remain in full force and effect. This Extension, together with the original Agreement and any written amendments hereto, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous understandings and agreements, whether written or oral. No amendment to this Extension shall be valid unless in writing and signed by authorized representatives of both parties.

NOTICES AND CONTACTS

ADDITIONAL PROVISIONS

Independent Contractor. The Provider is an independent contractor and not an employee, partner, or joint venturer of the Client. The Provider shall have no authority to bind the Client except as expressly agreed in writing.

Liability. Except for willful misconduct or gross negligence, neither party shall be liable to the other for consequential, incidental or punitive damages arising out of this Extension. The aggregate liability of either party for any claim arising from this Extension shall be limited to the amounts paid or payable by the Client under this Extension during the twelve (12) months preceding the claim.

Force Majeure. Neither party shall be liable for delays or failures in performance resulting from acts beyond its reasonable control, provided that the affected party gives prompt written notice to the other and uses commercially reasonable efforts to resume performance.

Client:

By:

Date:

Provider:

By:

Date:

Enter text✕

What a Support Services Extension Is and why it matters

Support Services Extension is a written amendment that extends or modifies an existing support services agreement's term, scope, or payment terms without creating a new master agreement. It records agreed changes such as service level adjustments, renewed term dates, additional deliverables, price modifications, and notice periods. Proper execution requires clear identification of the original contract, an explicit statement of the modifications, and signatures from authorized parties. Electronic execution is generally valid under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted, provided the parties demonstrate intent, consent, attribution, and reliable record retention.

Why organizations use a Support Services Extension

A Support Services Extension preserves service continuity, documents mutually agreed changes, and reduces negotiation overhead. It clarifies obligations, updates payment schedules and performance metrics, and provides a narrow, objective record that helps limit disputes.

Why organizations use a Support Services Extension

Who typically prepares and signs an extension

Typical users who prepare or approve Support Services Extensions include these groups responsible for ongoing vendor relationships.

  • IT procurement teams managing vendor SLAs, renewals, and technical change requests on behalf of the business.
  • Vendor account managers coordinating scope updates, deliverable schedules, and billing adjustments tied to service changes.
  • In-house counsel or contract managers who review amendment language and confirm authorization to bind the organization.

Verify each signer has delegated authority and any internal approval workflows are completed before execution.

Typical signatory roles and responsibilities

Vendor Representative

Account manager or contracting officer who confirms scope changes and signs on behalf of the vendor. They should be authorized in writing or under a delegation of signature authority to bind the vendor for the amended obligations and fees.

Client Representative

Procurement director or authorized signatory for the client organization who accepts the changes. Confirm internal approval steps and purchasing thresholds have been satisfied before signing to avoid later invalidation.

Core elements every professional Support Services Extension should include

A complete Support Services Extension makes the relationship adjustments explicit, links to the original agreement, and sets out operational and financial impacts so both parties understand the updated obligations.

Reference

Identify the original agreement by title, effective date, and parties so the extension is unambiguously tied to the correct contract and avoiding later disputes about applicability.

Extended Term

Specify the new start or end dates, renewal mechanics, and any pro rata treatments for partial periods so service continuity and billing align with expectations.

Scope Changes

List added or removed deliverables, service levels, or geographic coverage in sufficient detail to allow objective verification of performance against the amended scope.

Fees & Payment

State the exact pricing, invoicing frequency, payment due dates, and any transition credits or escalation formulas tied to the extension.

Termination & Remedies

Update termination triggers, cure periods, and liquidated damages or credits tied to nonperformance specific to the extended portion of the agreement.

Execution Block

Include signature lines with printed names, titles, dates, and any required witness or notarization fields; specify whether electronic signatures are permitted.

Step-by-step: complete and execute a Support Services Extension

Follow these steps to prepare, review, and execute an extension that is clear, enforceable, and aligned with the original contract.

  • 01
    Draft amendment: Reference original agreement and describe all proposed changes precisely.
  • 02
    Review internally: Have procurement, legal, and finance confirm scope, fees, and authority.
  • 03
    Obtain signatory approval: Collect signatures from authorized representatives and document approval records.
  • 04
    Distribute executed copies: Provide fully executed copies to all parties and update contract repositories.

How to configure an online workflow for the extension

Set up a repeatable digital workflow so extensions are routed, authenticated, and archived with consistent controls and audit data.

Field Configuration
Document Format Use PDF or DOCX; preserve original contract identifiers.
Signature Order Specify signer sequence to enforce approvals in the correct order.
Authentication Use email link, SMS code, or stronger ID verification as required.
Retention Set automatic archival and export to corporate records storage.

Where to send, file, and submit executed extensions

A clear routing plan prevents lost documents and ensures accounting, legal, and operational teams have access to the executed amendment.

  • Vendor Contact: Send executed copies to the vendor's authorized representative for their records and billing setup.
  • Client Procurement: File with procurement to update contract registers and renewal calendars.
  • Finance / AP: Provide billing teams with updated fee schedules and effective dates to adjust invoicing.
  • Legal Repository: Store the signed extension in the centralized contract management system for auditability.

Digital distribution and platform considerations

Choose a platform that supports secure e-signature, audit trails, and the integrations your team relies on for routing and storage.

  • File formats: PDF, DOCX supported.
  • Integrations: Salesforce, NetSuite, Google Workspace supported.
  • Authentication: Email, SMS, or higher-assurance methods.

Typical dates and deadlines to include and track

Record key dates in the extension and update internal calendars to ensure timely performance and billing.

Effective Date:

Date when amended obligations commence.

Notice Period:

Advance notice window for termination or scope changes.

Renewal Window:

Optional automatic renewal date and opt-out cutoff.

Signature Deadline:

Date by which all parties must sign to accept the amendment.

Processing Time:

Allow internal 5–10 business days for approvals and filing.

Key milestones from draft to implementation

Track the sequential milestones below to move the extension from proposal to active amendment without gaps in service or billing.

01

Draft Preparation

Create amendment draft, citing the original agreement and proposed changes.

02

Internal Approval

Obtain sign-off from stakeholders in procurement, legal, and finance.

03

Execution

Collect authorized signatures and finalize the executed document.

04

Implementation

Update systems, invoices, and service schedules to reflect the extension.

Common preparation mistakes to avoid

  • Failing to identify the original contract precisely, which can create ambiguity about what the extension changes.
  • Using vague scope language that leaves deliverables or service levels open to differing interpretations.
  • Allowing signers without proper authority to execute, risking unenforceability or later repudiation claims.
  • Neglecting to update billing systems and renewal calendars, causing missed invoices or unintended auto-renewals.

Consequences and legal risks of an incorrect extension

Breach Liability: Damages for failing to perform amended obligations.
Enforceability Risk: Invalid execution if signer lacks authority.
Tax Reporting: Incorrect fees can trigger reporting or withholding issues.
Confidentiality Exposure: Unclear terms may permit improper data sharing.
Notary Requirement: Missing notarization where required may impair recordation.
ESIGN Exceptions: Certain documents excluded under ESIGN/UETA.

How an extension differs from an amendment or renewal

Compare typical legal and operational differences so you select the right document type for the intended change.

Criteria Extension Amendment Renewal
Primary purpose extend term alter terms continue services
Scope change allowed minor substantive limited
Consideration needed sometimes often required rare
Execution form simple signature formal amendment renewal notice

Real-world examples of using e-signatures for contract changes

These short examples show how organizations manage contract updates and signature workflows without in-person execution.

Optica Ventures

A small investment firm standardized amendments for recurring support agreements to reduce turnaround.

  • Used cloud routing to collect signatures from remote stakeholders.
  • "The interface is simple and easy-to-use for our team; more importantly, it is just as easy for our customers." — Brian Fitzgibbons, COO, Optica Ventures LLC

Tech Data

An enterprise centralized vendor extensions to align billing and deployment.

  • Automated routing ensured approvals before execution.
  • "Tech Data uses airSlate SignNow to improve our internal and external customer service while increasing our speed to revenue." — Bob Dutkowsky, CEO, Tech Data

Essential information to include for legal clarity and security

Parties' Names: Full legal entity names
Effective Date: MM/DD/YYYY format
Scope Summary: Concise, measurable scope
Payment Terms: Amounts and due dates
Signature Details: Printed name, title, date
Reference Clause: Original agreement citation

Comparison: common eSignature pricing and capabilities

Basic pricing and capability indicators for common eSignature vendors. signNow is listed first per table convention; compare features and limits against your compliance and volume needs.

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 Yes, 7-day trial Varies by plan Varies by plan Varies by plan Varies by plan
Bulk Send Yes Yes Yes Yes Yes
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 Support Services Extensions

Answers to common questions about validity, execution, and post-signature handling of support contract extensions.


Need help? Contact support

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