Establishing secure connection…Loading editor…Preparing document…

Support Services Schedule

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

SUPPORT SERVICES SCHEDULE

This Support Services Schedule ("Schedule") is entered into as of Effective Date: by and between Client Name: and Service Provider Name: .

WHEREAS

WHEREAS, Service Provider is engaged in the business of providing technical support, maintenance, and related services and represents that it has the personnel, skills and resources necessary to perform the services described in this Schedule; and

WHEREAS, Client desires to procure and Service Provider desires to furnish support services under the terms and conditions set forth in this Schedule and any master agreement between the parties; and

WHEREAS, the parties intend that this Schedule shall specify service levels, fees, and the administrative procedures governing the provision of support services.

1. SCOPE OF SERVICES

Service Provider shall provide the support services described below. The services shall include support, maintenance, monitoring, troubleshooting, updates, and consulting as specifically itemized in this Schedule.

2. SERVICE LEVELS AND RESPONSE TIMES

Service Provider shall use commercially reasonable efforts to meet the response and resolution time targets set forth below. Response and resolution times are measured from the time a support ticket is acknowledged by Service Provider.

3. PERSONNEL AND SUBCONTRACTING

Service Provider shall assign qualified personnel to perform the services. Service Provider may subcontract portions of the services provided that it remains responsible for subcontractors' compliance with this Schedule.

4. FEES AND PAYMENT TERMS

Client shall pay Service Provider the fees set forth in this Section in consideration of the services performed under this Schedule. All fees are due in accordance with the billing schedule below.

5. TERM AND TERMINATION

This Schedule commences on Start Date: and shall continue until End Date: unless earlier terminated in accordance with this Section.

Either party may terminate this Schedule for convenience upon written notice to the other party not less than days prior to the intended termination date. Either party may terminate immediately for material breach not cured within thirty (30) days after receipt of written notice of such breach.

6. CONFIDENTIALITY

Each party (the "Receiving Party") shall keep confidential and not disclose to any third party Confidential Information of the other party (the "Disclosing Party"). "Confidential Information" means non-public business, technical, and financial information marked or otherwise identified as confidential or which, by its nature, a reasonable person would understand to be confidential. The Receiving Party shall use Confidential Information only for performance under this Schedule and shall restrict disclosure to employees and contractors with a need to know and subject to obligations of confidentiality at least as protective as those contained herein. Confidentiality obligations shall survive termination of this Schedule for a period of three (3) years, except for trade secrets, which shall remain confidential for as long as they qualify as trade secrets.

7. CHANGE ORDERS

Any change to the scope, deliverables, fees, or schedule shall be documented in a written change order signed by authorized representatives of both parties. Service Provider shall not be obligated to perform work outside the scope until such change order is executed.

8. REPORTING AND MEETINGS

Service Provider shall provide periodic reports describing work performed, incidents, open items, and planned activities. The parties shall hold regular status meetings at intervals agreed below.

9. DATA SECURITY AND BREACH NOTIFICATION

Service Provider shall implement and maintain reasonable administrative, physical, and technical safeguards appropriate to the nature of the Confidential Information and personal data processed in the provision of services. Service Provider shall notify Client of any confirmed data security incident affecting Client data without undue delay and in no event later than after detection.

10. LIMITATION OF LIABILITY AND INDEMNITY

Each party's liability for direct damages arising from this Schedule shall be limited to the fees paid or payable under this Schedule in the twelve (12) month period preceding the claim. Neither party shall be liable for special, incidental, consequential, or punitive damages except for liability arising from a party's gross negligence, willful misconduct, or breach of confidentiality obligations. Service Provider shall indemnify Client for third-party claims arising from Service Provider's negligent performance or willful misconduct in connection with the services.

11. GOVERNING LAW

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

12. ENTIRE AGREEMENT

This Schedule, together with any master services agreement between the parties to which this Schedule is attached, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, proposals, and communications, whether oral or written. In the event of any conflict between the terms of this Schedule and the master agreement, the master agreement shall control unless this Schedule expressly states that it modifies specific provisions.

13. MISCELLANEOUS

Notices required under this Schedule shall be in writing and delivered to the addresses set forth in the master agreement or to the contact information provided above. If any provision of this Schedule is held invalid or unenforceable, the remainder of the Schedule shall remain in full force and effect.

Client:

By:

Date:

Service Provider:

By:

Date:

Enter text✕
Prepare your document for signing right on this page
  • 01 Edit the text and complete the fields
  • 02 Click Sign Now and on the next screen add recipients and signature fields in SignNow
  • 03 Start your free trial to sign and send your doc
Sign Now

What the Support Services Schedule Is and how it fits

A Support Services Schedule is a contractual attachment that defines the scope, service levels, response times, hours of support, pricing for support activities, and escalation procedures that apply to a vendor relationship. It is typically appended to a Master Services Agreement or Statement of Work and translates high-level obligations into operational commitments, measurable metrics, and reporting obligations. The Schedule clarifies responsibility for maintenance, updates, and incident handling and creates objective criteria for credits, remedies, and termination related to support performance.

Why a clear Support Services Schedule matters

A well-drafted Support Services Schedule reduces ambiguity about response expectations, limits disputes over service performance, and sets objective triggers for credits or termination. It supports predictable budgeting and compliance with procurement rules.

Why a clear Support Services Schedule matters

Who typically prepares and relies on this Schedule

The Schedule is a cross-functional document: ensure stakeholders from finance, security, and the business unit review before execution.

  • Procurement teams—manage vendor selection, pricing schedules, and contract alignment with organizational procurement rules.
  • IT operations—use the Schedule to set technical acceptance, maintenance windows, and incident-response expectations.
  • Contract managers—track SLA performance, credits, renewals, and dispute resolution against the Schedule.

Essential elements to include in a professional Support Services Schedule

A complete Schedule turns general support promises into measurable commitments. Include measurable SLAs, escalation paths, excluded services, pricing, reporting cadence, and change-control rules so both parties know how performance will be judged and remedied.

Scope of Services

Describe the exact services covered (incident triage, bug fixes, configuration, updates) and list services specifically excluded to prevent scope creep and billing disputes.

Service Levels

Define response and resolution targets for severity levels, measurement windows, and whether SLAs are calendar or business hours; specify uptime metrics if applicable.

Response and Resolution Times

Set initial response times and target resolution times by incident priority, including how measurement starts and ends and whether interim workarounds satisfy obligations.

Fees and Credits

Specify recurring support fees, per-incident charges, overtime or after-hours rates, and remedies such as service credits or fee reductions for missed SLAs.

Escalation & Reporting

Include escalation contacts by role, required incident reports, root-cause analysis timelines, and regular performance reports to meet governance needs.

Change Control & Term

Describe how changes to scope or pricing are approved, notice periods for changes, renewal terms, termination for cause related to support failures, and transition assistance.

Required information to complete the Schedule

Client Legal Name: Full registered entity name
Support Contact: Primary name and contact info
Service Description: Short summary of included services
SLA Metrics: Response and resolution targets
Billing Details: Billing entity and payment terms
Agreement Term: Start and end dates

Step-by-step: completing the Support Services Schedule

Follow these sequential steps to draft or complete the Schedule and align expectations across teams.

  • 01
    Identify scope: List specific systems and services to be supported.
  • 02
    Set severity definitions: Define incident priority levels and triggers for each.
  • 03
    Agree SLA metrics: Confirm response and resolution times and measurement windows.
  • 04
    Document remedies: Record credits, termination rights, and reporting obligations.

Configuring an online workflow for the Schedule

Configure digital routing and automation to ensure signed Schedules are stored, distributed, and enforced consistently.

Configurable Field Name and Purpose Details Field | Configuration
Notification Method and Delivery Channels Email and SMS notifications | immediate alerts to designated contacts
Signer Authentication and Verification Email + optional SMS code | ensures signer attribution and audit trail
Routing Order and Approvals Sequential or parallel routing | sets required approvers and order
Attachments and Evidence Attach SOWs, diagrams | store with signed Schedule for audit

Where to send finalized and signed Schedules

After signature, route copies to internal and external stakeholders and ensure a retained record for compliance and dispute response.

  • Vendor Contract Admin: Store signed Schedule with contract repository and link to MSA.
  • Finance / Billing: Send copy for invoice setup and credit calculations.
  • Operations / NOC: Provide operational teams with SLAs and escalation paths.
  • Legal / Compliance: Retain for audit, termination, or dispute handling.

Digital signing and file formats to prefer

Ensure the signing platform captures timestamps, signer attribution, and an audit trail; verify the chosen format remains accessible for retention and legal purposes.

  • eSignature Support: PDF, DOCX supported
  • Authentication Options: Email, SMS code, or advanced methods
  • Integrations: CRM and storage integrations

Typical timelines and notice periods to include

Specify clear dates and recurring timelines so the parties know when reviews, invoices, and termination windows begin and end.

SLA Effective Date:

Date SLAs become enforceable; often same as agreement Effective Date.

Termination Notice Period:

Commonly 30–90 days written notice for nonrenewal or convenience.

Service Review Cadence:

Quarterly or monthly performance review meetings and reports.

Invoice Due Date:

Net 30 from invoice date unless otherwise negotiated.

Incident Reporting Deadline:

Publish initial incident report within 24–72 hours as defined.

Common mistakes when preparing the Schedule

  • Vague priority definitions—failing to define Severity 1 vs Severity 2 leads to disputed response times and inconsistent remediation.
  • Omitting time zone or business hours—measuring SLAs without a timezone or holiday list causes confusion when parties are in different regions.
  • No measurable remedy—listing a remedy like 'goodwill credit' without a calculation method creates enforcement gaps.
  • Ignoring excluded services—not listing excluded items results in unexpected maintenance charges and contested invoices.

Potential consequences of an incomplete or incorrect Schedule

Service Credit Disputes: Unclear metrics
Contract Termination: Material breach triggers
Regulatory Exposure: Data breach penalties
Billing Errors: Incorrect invoicing
Operational Downtime: Undefined escalation
Enforceability Risk: Missing signatures or consent

eSignature vendor comparison for signing the Support Services Schedule

Compare core pricing and capabilities when selecting a signing platform; signNow is listed first per vendor-layout conventions and to show common capability differences.

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

Real-world examples of using a Support Services Schedule

These brief examples show how organizations apply a Schedule to reduce disputes and improve operational clarity.

Optica Ventures — contract clarity

Optica needed consistent response targets across multiple properties

  • The vendor specified severity definitions and a 24x7 paging contact
  • Brian Fitzgibbons, COO, noted the interface is simple and customers experienced fewer service misunderstandings after adopting the Schedule.

Martin Properties — remote execution

A property manager required remote acceptance and quick escalation for outages

  • The Schedule included on-call support and root-cause timelines
  • Tim Martin, Founder, reported faster resolution cycles while keeping documented evidence for landlord and tenant communications.

Practical tips for accurate and efficient Schedules

Adopt these practices to make the Schedule actionable, auditable, and less likely to cause disputes.

Use measurable metrics
Specify numerical SLA targets, measurement windows, and calculation methods so performance and credit calculations are objective and verifiable.
Standardize severity definitions
Define technical and business impact for each severity level to align operations and reduce ticket classification disputes.
Automate reporting
Schedule automated SLA reports and attach them to monthly governance meetings to catch deviations early and document remediation steps.
Include transition support
Require handover assistance, data export formats, and a defined transition period to reduce risk at termination or vendor change.

Who signs the Schedule and why their role matters

Contract Manager, Senior

A contract manager reviews and signs to bind the organization to operational commitments; they are responsible for monitoring SLA compliance and initiating remedies for breaches.

VP of Operations

An operations executive signs to acknowledge resource allocation and escalation authority, ensuring service teams meet the documented response and resolution obligations.

Frequently asked questions about the Support Services Schedule

Answers to common questions about drafting, signing, and enforcing the Support Services Schedule.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users
Sign Now
Company
Forms
Pricing
Resources
Knowledge base
Other Products
© 2026 airSlate Inc. All rights reserved.