Establishing secure connection…Loading editor…Preparing document…

Ongoing Support Agreement

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

ONGOING SUPPORT AGREEMENT

This Ongoing Support Agreement ("Agreement") is entered into effective as of by and between Client Name: and Provider Name: .

RECITALS

WHEREAS, Client requires ongoing technical support and related services with respect to Client's systems, applications, and network resources; and

WHEREAS, Provider represents that it possesses the expertise and resources to provide such support services and agrees to provide support under the terms and conditions set forth in this Agreement; and

WHEREAS, the parties desire to set forth the scope, payment, term, confidentiality and other material provisions governing the support relationship.

SCOPE OF WORK

Provider will perform ongoing support services which may include helpdesk support, software updates, security patching, routine maintenance, monitoring, and reasonable troubleshooting ("Support Services"). Deliverables, response targets, and exclusions are further described below and in any attached Statement of Work.

PAYMENT TERMS

As consideration for the Support Services, Client shall pay Provider the fees described below. All fees are payable in U.S. dollars unless otherwise agreed in writing.

Provider shall invoice Client: Monthly Quarterly Upon milestone completion

Late payments shall accrue interest at % per month (or the maximum permitted by law), plus a minimum late payment charge of $ .

TERM AND TERMINATION

This Agreement commences on Start Date: and continues until End Date: , unless earlier terminated in accordance with this Section.

Either party may terminate for convenience upon days' prior written notice. Provider may terminate immediately for Client's material breach that is not cured within days after written notice. Termination for insolvency, bankruptcy, or cessation of business operations is immediate.

Upon termination, Client shall pay Provider for all Services performed and reasonable non-cancellable expenses incurred through the effective date of termination. Provider shall cease performance and return Client materials in accordance with the parties' instructions.

CONFIDENTIALITY

Each party (the "Receiving Party") shall maintain in confidence all non-public information disclosed by the other party (the "Disclosing Party") that is designated confidential or that reasonably should be understood to be confidential given the nature of the information ("Confidential Information"). The Receiving Party will not use Confidential Information for any purpose other than performing its obligations under this Agreement, and will not disclose Confidential Information to any third party except to employees, contractors or advisors who have a need to know and are bound by confidentiality obligations no less protective than those herein.

Confidential Information does not include information that: (a) is or becomes generally available to the public other than by breach of this Agreement; (b) was known to the Receiving Party prior to disclosure; (c) is rightfully received from a third party without restriction; or (d) is independently developed without use of the Disclosing Party's Confidential Information. The obligations of confidentiality survive termination for a period of years, except for trade secrets, which remain protected for so long as they remain trade secrets.

SERVICE LEVELS AND RESPONSE TIMES

Provider will use commercially reasonable efforts to meet response and resolution targets for incidents categorized as Critical, High, Medium and Low. Specific response targets, escalation procedures, and remedies for failure to meet service levels shall be set forth in this Section or an attached Service Level Schedule.

CHANGE REQUESTS

Changes to the Scope of Work or services shall be managed through written Change Requests. Each Change Request shall describe the change, the impact on fees and schedule, and must be signed by authorized representatives of both parties before Provider proceeds with the change.

LIMITATION OF LIABILITY & INDEMNITY

Except for willful misconduct or gross negligence, neither party shall be liable for indirect, incidental, special or consequential damages. Provider's aggregate liability for claims arising out of or relating to this Agreement shall not exceed the fees paid by Client to Provider under this Agreement during the most recent twelve (12) month period. Each party shall indemnify the other against third-party claims arising from its breach of this Agreement, 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 conflict of laws principles.

ENTIRE AGREEMENT

This Agreement, together with any incorporated Statement(s) of Work and Change Requests executed by the parties, constitutes the entire agreement between the parties with respect to the subject matter and supersedes all prior and contemporaneous agreements, proposals and communications, whether written or oral.

NOTICES

All notices under this Agreement must be in writing and addressed to the parties at the addresses set forth below or to such other address as either party may designate in writing.

MISCELLANEOUS

If any provision of this Agreement is held invalid or unenforceable, the remaining provisions shall remain in full force and effect. Neither party may assign this Agreement without the prior written consent of the other, except to a successor in interest by merger or sale of substantially all assets. The parties are independent contractors and nothing in this Agreement creates an employment, agency or joint venture relationship.

Client Name:

By:

Date:

Provider Name:

By:

Date:

Enter text✕

What an Ongoing Support Agreement Covers

Ongoing Support Agreement is a written contract that defines the continued maintenance, assistance, and service obligations between a service provider and a client for a set term or on an ongoing basis. It specifies scope of support, response and escalation procedures, service levels, fee structures, termination rights, and change-management processes. For U.S. transactions, these agreements can be executed electronically under ESIGN and state UETA laws provided the parties demonstrate intent, consent, attribution, and retention. Use clear definitions and measurable service-level metrics to reduce disputes and ensure enforceability.

Why a Clear Support Agreement Matters

An Ongoing Support Agreement clarifies responsibilities, sets measurable service levels, protects both parties from scope creep, and provides a basis for fees and termination. Clear terms reduce disputes, enable consistent delivery, and support regulatory compliance for sensitive industries.

Why a Clear Support Agreement Matters

Who Prepares and Signs These Agreements

Typical users and roles that prepare or approve an Ongoing Support Agreement include internal legal, procurement teams, and service delivery managers.

  • IT and operations managers who define support scope and uptime commitments.
  • Procurement and finance staff responsible for vendor selection and payment terms.
  • Legal counsel reviewing liability, indemnity, data protection, and termination clauses.

External signers include vendor authorized representatives, account managers, and client executives with formal signing authority.

Common Signatory Profiles

Vendor Signatory — VP Operations

As vendor signatory, the VP of Operations typically certifies that support resources and SLAs will be delivered. They confirm staffing levels, escalation paths, and compliance obligations, and may be authorized to approve amendments within defined limits.

Client Signatory — Director of IT

As client signatory, the Director of IT accepts service levels and authorizes payment terms. They represent business needs, validate performance metrics, and coordinate internal change control; they may escalate contract disputes to legal or procurement where required.

Essential Agreement Fields at a Glance

Parties: Legal names and entity types
Support Scope: Detailed tasks and excluded items
Service Levels: Response and resolution time objectives
Fees: Billing schedule and change pricing
Term & Renewal: Initial term, auto-renewals, notice periods
Contact Info: Primary contacts, escalation, emergency numbers

Common Preparation Mistakes to Avoid

  • Vague scope descriptions that allow scope creep and disputes, such as listing duties as 'as needed' without measurable deliverables or limits.
  • Failure to include response and escalation timelines leads to missed SLAs and unclear accountability for urgent incidents requiring 24/7 coverage.
  • Incorrect or missing signatory authority—documents signed by unauthorized staff can be challenged and potentially void the agreement.
  • Not aligning termination and liability clauses with insurance and indemnity coverage can expose parties to unexpected financial risk.

Filling Out an Ongoing Support Agreement — Step by Step

Step-by-step completion process for an Ongoing Support Agreement, from drafting to execution and post-signature onboarding.

  • 01
    Draft: Define scope, responsibilities, exclusions, and deliverables in plain language.
  • 02
    Service Levels: Set response times, uptime targets, and remediation credits.
  • 03
    Fees: Detail fees, invoicing schedule, and change-order pricing rules.
  • 04
    Sign: Confirm authorized signatories and obtain dated signatures.

Configure an Online Workflow for Completion

Configure an online workflow for drafting, review, e-signing, and archival to streamline execution and maintain audit trails.

Field Configuration
Template name and version number Auto-fill common clauses and metadata
Signer routing order and role assignment Set sequential or parallel signers with reminders
Signer authentication and verification method Choose email, SMS code, or knowledge-based authentication
Archive retention and export format Save PDF/A, store audit trail, and backup

Where Completed Agreements Are Routed

Typical submission paths for completed agreements: internal contract repository, client/vendor records, procurement systems, and cloud storage linked to audit trails.

  • Internal Repository: Upload executed PDF to contract management or shared drive.
  • Vendor Records: Send countersigned copy to vendor's legal or account team.
  • Procurement System: Attach to purchase order and update vendor profile.
  • Cloud Backup: Store long-term copy in encrypted cloud storage with audit.

Key Components to Include in the Agreement

Core components that make an Ongoing Support Agreement enforceable and practical for operational delivery and legal clarity across service organizations.

Scope

Define covered systems, services, and explicit exclusions. Include deliverables, supported environments, assumptions, and any dependencies on third-party vendors to avoid ambiguity and limit disputes over responsibility.

Service Levels

Set measurable KPIs including response times, resolution targets, uptime percentages, patch windows, and credit remedies. Specify measurement windows, reporting cadence, and exceptions for force majeure or planned maintenance.

Fees

List base fees, hourly or per-incident rates, retainer models, billing cycles, expense reimbursement, change-order pricing, and thresholds for renegotiation tied to scope changes or volume.

Term

Specify initial term, renewal mechanics, auto-renew notice periods, and early termination penalties. Include transition assistance obligations and handover timelines to mitigate operational disruption.

Change Control

Describe change request submission, evaluation timelines, approval authorities, impact assessment on fees and schedule, and emergency change handling separate from routine change processes.

Termination

Outline breach cures, notice procedures, data return or destruction obligations, settlement of outstanding fees, and any survival of confidentiality or indemnity clauses after termination.

Key Dates and Notice Periods to Track

Common deadlines, renewal notices, and claim windows often embedded in Ongoing Support Agreements.

Initial Effective Date:

Date agreement begins; format MM/DD/YYYY.

Renewal Notice Period:

Typically 30 to 90 days before auto-renewal.

Billing Cycle Dates:

Monthly, quarterly, or annual invoicing date specified.

Service Credit Window:

Claims submitted within 30 days of incident.

Termination Notice:

Contractual notice period for non-renewal or termination.

Consequences of an Incorrect or Missing Agreement

Contract Voidance: Unauthorized signatures may void agreement.
Financial Penalties: Missed notice periods can incur fees.
Service Disruption: Undefined SLAs risk prolonged outages.
Regulatory Penalties: HIPAA or PCI failures carry fines.
Reputational Damage: Customer trust loss and churn.
Litigation Costs: Disputes increase legal expenses.

Practical Tips for Accurate and Efficient Agreements

Practical tips to improve clarity, reduce risk, and streamline execution of Ongoing Support Agreements across organizations.

Define measurable service-level metrics and remedies
Include exact measurement methods, reporting intervals, and acceptable thresholds. Tie specific remedies or credits to missed targets and describe the calculation method so both parties can independently verify compliance without dispute.
Use clear change control and amendment processes
Require written change requests, defined review windows, and approval authorities. Specify fee recalculation formulas and effective dates for approved changes; include emergency change procedures for critical fixes.
Confirm signer authority and document versions
Maintain version control and ensure signers have documented authority. Record signer title, delegation limits, and attach authorization letters where necessary to reduce challenges to enforceability and speed post-signature actions.
Preserve complete audit trails and backups
Capture timestamps, IP addresses, email confirmations, and field-level edits. Store signed PDFs and separate audit logs in tamper-evident, encrypted storage to meet ESIGN, UETA, and industry-specific retention requirements.

Distribution and Technical Requirements

Technical considerations when choosing tools to distribute, sign, and archive Ongoing Support Agreements across organizations and systems.

  • File Formats: PDF, DOCX, and fillable forms
  • Integrations: CRM, ERP, and cloud storage
  • Authentication: Email, SMS code, or SSO

Comparing eSignature Provider Pricing and Capabilities

A concise comparison of base pricing and key capabilities across common e-signature providers relevant to executing Ongoing Support Agreements.

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 Varies Varies Varies
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Frequently Asked Questions and Troubleshooting

Frequently asked questions addressing execution, signature validity, and common issues with Ongoing Support Agreements below.


Need help? Contact support

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