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.
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.
Typical users and roles that prepare or approve an Ongoing Support Agreement include internal legal, procurement teams, and service delivery managers.
External signers include vendor authorized representatives, account managers, and client executives with formal signing authority.
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.
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.
| 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 |
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.
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.
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.
Specify initial term, renewal mechanics, auto-renew notice periods, and early termination penalties. Include transition assistance obligations and handover timelines to mitigate operational disruption.
Describe change request submission, evaluation timelines, approval authorities, impact assessment on fees and schedule, and emergency change handling separate from routine change processes.
Outline breach cures, notice procedures, data return or destruction obligations, settlement of outstanding fees, and any survival of confidentiality or indemnity clauses after termination.
Date agreement begins; format MM/DD/YYYY.
Typically 30 to 90 days before auto-renewal.
Monthly, quarterly, or annual invoicing date specified.
Claims submitted within 30 days of incident.
Contractual notice period for non-renewal or termination.
Technical considerations when choosing tools to distribute, sign, and archive Ongoing Support Agreements across organizations and systems.
| 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 |