Establishing secure connection…Loading editor…Preparing document…

IT Services Agreement Amendment

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

IT Services Agreement Amendment

Amendment Identification

Amendment Number:    Original Agreement Date:    Amendment Effective Date:

Parties

WHEREAS

WHEREAS, the Client and the Service Provider entered into an IT Services Agreement dated (the Agreement);

WHEREAS, the parties desire to amend certain provisions of the Agreement to reflect changes in services, fees, and the term as set forth in this Amendment; and

WHEREAS, except as expressly modified by this Amendment, all terms and conditions of the Agreement remain in full force and effect.

Amendments

The Agreement is hereby amended as follows. Checked items below identify the sections to be modified; full amended text shall be set forth in the Scope of Work or Payment Terms sections below where applicable.

Scope of Work

Describe the specific services, deliverables, milestones, and acceptance criteria being added, modified, or removed under this Amendment. If work is recurring, include frequency and estimated hours.

Payment Terms

Unless otherwise specified herein, all invoices will be payable in accordance with the Agreement. The parties hereby set forth the specific compensation terms for the amended services.

Term and Termination

The term of this Amendment shall be as follows, subject to earlier termination in accordance with the Agreement as amended.

Amendment Start Date:    Amendment End Date:

Termination for Cause: Either party may terminate this Amendment for material breach of the amended provisions if the breaching party fails to cure within the notice period specified above. Termination shall be without prejudice to remedies available at law or in equity.

Confidentiality

All information exchanged in connection with the amended services that is identified as confidential or that a reasonable person would understand to be confidential shall be handled in accordance with the confidentiality and non-disclosure provisions of the Agreement. The parties reaffirm and incorporate those obligations by reference; any modification to confidentiality obligations must be expressly set forth in this Amendment.

Governing Law

This Amendment shall be governed by and construed in accordance with the laws of the State of , without regard to conflicts of law principles.

Representations; No Other Amendments

Each party represents and warrants that it has full power and authority to enter into this Amendment and that the person signing below is authorized to execute this Amendment on its behalf. Except as expressly set forth in this Amendment, the Agreement remains unmodified and in full force and effect.

Entire Agreement

This Amendment and the Agreement constitute the entire agreement between the parties with respect to the subject matter hereof and supersede all prior proposals, agreements, and understandings, whether written or oral, relating to such subject matter.

Notices

Additional Provisions

Client Printed Name:

By:

Date:

Service Provider Printed Name:

By:

Date:

Enter text✕

What an IT Services Agreement Amendment Is and When It Applies

An IT Services Agreement Amendment is a written modification to an existing IT services contract that changes scope, pricing, term, deliverables, service levels, or other material terms. It is executed by the original contracting parties and becomes part of the contract once signed by authorized representatives. Amendments avoid reissuing a full contract when limited changes are needed and should reference the original agreement by date and section. Proper execution, version control, and record retention help preserve enforceability and reduce disputes.

Why Use a Formal Amendment Instead of a New Agreement

A targeted amendment preserves the original contract history, reduces negotiation time, and limits administrative work while keeping existing terms intact where unchanged.

Why Use a Formal Amendment Instead of a New Agreement

Who Commonly Prepares and Signs IT Services Agreement Amendments

Typical preparers include in-house legal, procurement teams, vendor account managers, and project managers responsible for contract changes.

  • Client legal or procurement teams — review scope, approvals, and budget before signing.
  • Vendor account or contract managers — draft amendment language matching service delivery changes.
  • C-level or authorized officers — sign for value or term modifications that exceed delegation limits.

Ensure the person signing on each side has delegated authority; record signatory name, title, and date for auditability.

Core Elements to Include in a Professional Amendment

A well-drafted amendment is concise but precise, referencing the original agreement, specifying changed clauses, and including execution details and governing law.

Reference

Identify the original agreement by title and effective date to make the amendment’s relationship explicit and avoid ambiguity.

Purpose

State the business reason for the change, e.g., expanded scope, added services, or corrected pricing, so parties share the same intent.

Amended Terms

Quote or paraphrase the exact provisions being changed and insert new language; use section numbers that map to the original contract.

Effective Date

Specify when the amendment takes effect and whether it applies retroactively or prospectively to services performed.

Signatures

Provide signature blocks with printed name, title, company, and date for each authorized signatory; indicate whether electronic signatures are accepted.

Integration

Confirm that all other original terms remain in force unless expressly modified and state whether the amendment supersedes prior inconsistent documents.

Step-by-Step: How to Complete and Execute an IT Services Agreement Amendment

Follow a controlled sequence to draft, approve, sign, and store the amendment to maintain a clear audit trail and avoid enforceability gaps.

  • 01
    1. Draft: Prepare amendment language referencing original agreement and clearly stating changes.
  • 02
    2. Review: Obtain internal legal, procurement, and finance approvals before sending to the counterparty.
  • 03
    3. Sign: Have authorized signatories execute the amendment—electronic signatures are acceptable under ESIGN/UETA when permitted.
  • 04
    4. Record: Attach the amendment to the original contract and update contract management records and version control.

Suggested Digital Workflow Settings for Managing Amendments

Configure a simple e-signing workflow to reduce friction while preserving authentication and audit data.

Field Configuration
Document Naming Include original agreement ID and amendment number for easy retrieval
Signer Order Use sequential or parallel signing depending on internal approval needs
Authentication Enable email code or SMS for signer attribution; KBA for higher risk
Retention Store signed copy with audit trail and set retention policy per compliance rules

Technical Considerations for eSigning an Amendment

Confirm the eSignature platform supports legal admissibility, audit trails, and the authentication level your organization requires.

  • File Formats: Use PDF or PDF/A to preserve layout and signatures
  • Authentication: Choose email, SMS, or stronger methods for signer verification
  • Audit Trail: Capture IP, timestamp, and signer actions for evidentiary value

Ensure integrations with contract repository, CRM, or document management systems to automate attachment of the amendment to the original contract record.

Typical eSigning Flow for an Amendment

A clear signer flow reduces errors and supports legal validity when using electronic signatures under ESIGN and state law.

  • Upload: Upload amendment and map signature/date fields
  • Assign: Add signer emails and set signing order
  • Authenticate: Apply email or SMS verification
  • Complete: Capture signed PDF and detailed audit log

Essential Information to Collect and Protect

Party Names: Legal entity names
Signatory Titles: Officer or authorized signer
Effective Date: MM/DD/YYYY format
Amendment ID: Sequential identifier
Consideration: Monetary amount or credit
Attachment List: Exhibits and referenced docs

Common Mistakes to Avoid When Preparing an Amendment

  • Failing to reference the original agreement precisely, which can create ambiguity about which terms are modified.
  • Using vague language for changed terms, such as 'reasonable efforts' for pricing or deliverables, which invites disputes.
  • Allowing an unauthorized person to sign, risking a challenge to enforceability and potential repudiation.
  • Not preserving version control or failing to attach the signed amendment to the original contract in the repository.

Legal and Practical Risks of Incorrect Amendments

Breach Risk: Invalid amendment may not be enforceable
Tax Consequences: Incorrect consideration reporting can trigger IRS penalties
I-9 Risk: Employment-related changes can affect I-9 compliance
Liability Exposure: Unclear scope shifts may expand vendor liability
Operational Delay: Incomplete approvals delay project delivery
Recordkeeping: Poor retention risks regulatory noncompliance

eSignature Vendor Comparison for Executing Amendments

Typical vendor differences include starting price, trial availability, bulk send, audit trail, HIPAA support, and envelope or usage caps.

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 free trial Yes, trial available Yes, trial available Yes, trial available Yes, trial available
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 env/user/year Varies by plan Varies by plan Varies by plan

How to Update or Revise an Existing Amendment

Use a controlled revision process to avoid multiple, conflicting amendments and maintain a clear change log.

01

Identify:

Locate original amendment and determine the exact clauses needing revision
02

Draft:

Draft a second amendment referencing the prior amendment number and changes
03

Approve:

Route revised amendment through the same approval channels as the original
04

Execute:

Have authorized signatories sign and date the revision
05

Attach:

Attach revised amendment to the contract folder and update metadata
06

Communicate:

Notify stakeholders of the revision and updated effective dates

Example Scenarios for Common Amendment Types

Real-world examples show practical amendment uses and expected documentation.

Scope Increase Case

A vendor adds managed services for cloud backups to an existing support contract

  • Change adds monthly fee and SLA targets
  • The amendment quotes the original section, inserts new deliverables, and sets an effective date for services to begin next billing cycle.

Pricing Adjustment Case

A client negotiates a volume discount after year one of a multi-year deal

  • The amendment reduces per-unit rates and adjusts invoicing terms
  • Execution included signature blocks, effective date for new pricing, and a clause preserving unchanged warranty terms.

Frequently Asked Questions About IT Services Agreement Amendments

Answers to common execution, enforceability, and eSignature questions when modifying IT services contracts.


Need help? Contact support

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