IT Service Level Agreement Sample with Response Times & Escalation

IT Service Level Agreement Template

This Service Level Agreement (SLA) defines the formal commitment between the service provider and the client regarding IT support, system availability, and performance expectations. It serves as a binding reference to ensure both parties understand the scope of services, response times, and escalation procedures.

---

1. Agreement Overview

This agreement is entered into on [Date] between [Service Provider Name] and [Client Company Name]. The services covered under this agreement include [List of IT Services, e.g., Network Management, Help Desk Support, Server Maintenance].

2. Service Scope

The service provider agrees to provide the following IT services:

• [Service Item 1]: [Brief description of scope]
• [Service Item 2]: [Brief description of scope]
• [Service Item 3]: [Brief description of scope]

3. Service Availability and Uptime

The service provider guarantees a monthly uptime of [Percentage, e.g., 99.9%] for the following systems:

• [System Name]: [Uptime Percentage]
• [System Name]: [Uptime Percentage]

4. Incident Response and Resolution Times

Support requests are prioritized based on the following severity levels:

5. Escalation Procedure

If a service issue is not resolved within the agreed-upon timeframe, the following escalation path applies:

1. First Level: [Contact Name/Department] at [Email/Phone]
2. Second Level: [Manager Name/Title] at [Email/Phone]
3. Third Level: [Executive Name/Title] at [Email/Phone]

6. Client Responsibilities

The client agrees to:

• Provide timely access to systems and personnel as required.
• Report incidents through the designated channel: [Support Portal URL or Email].
• Maintain necessary hardware and software licensing as specified in [Reference Document].

7. Agreement Term and Termination

This agreement shall remain in effect from [Start Date] to [End Date]. Either party may terminate this agreement with [Number] days' written notice.

---

Pro Tips

• Define "Business Hours": Clearly state whether your response times apply to 24/7 coverage or standard local business hours (e.g., 9 AM – 5 PM).
• Exclude Maintenance: Always include a clause that excludes scheduled maintenance windows from your uptime calculations.
• Review Annually: IT needs change rapidly; schedule a formal review of this document every 12 months to ensure it still aligns with your operational requirements.

Execution and Signatures

The Parties sign this agreement as of the Effective Date: [Date].

First Party

• Signature: ______________________
• Name: [Full name]
• Title: [Job title]
• Date: [Date]

Second Party

• Signature: ______________________
• Name: [Full name]
• Title: [Job title]
• Date: [Date]

FAQ

What is the primary purpose of an SLA?

The primary purpose is to establish clear expectations between a service provider and a client regarding performance, availability, and responsibilities, reducing the risk of disputes.

How should I handle "Critical" vs "Normal" issues?

Categorize issues based on the impact on your business operations. Critical issues should involve high-level system failures, while normal issues typically cover routine requests or minor bugs.

Can an SLA be modified after it is signed?

Yes, an SLA is a living document. Both parties should agree to amendments in writing, typically through an addendum or a formal contract renewal process.

What happens if the service provider fails to meet the SLA?

Most SLAs include a "Service Credit" section (which you can add to Section 4) that outlines financial rebates or service discounts if the provider fails to meet the agreed-upon uptime or response metrics.