Service Level Agreement (SLA) Template: Define Clear Performance Expectations in 45 Minutes

Introduction

This Service Level Agreement (SLA) defines the performance expectations between [VENDOR_NAME] and [YOUR_COMPANY] for the services provided under the contract signed on [CONTRACT_DATE].

Purpose

Define measurable performance metrics
Establish penalties for underperformance
Create a dispute resolution process
Ensure service continuity and quality

1. Scope of Services

Effective from [START_DATE] through [END_DATE], [VENDOR_NAME] provides the following services:

Service	Description	Frequency	Pricing
[Service 1]	[Detailed description]	[e.g., Daily / Monthly / On-demand]	[Price]
[Service 2]	[Detailed description]	[e.g., Weekly / Quarterly]	[Price]
[Service 3]	[Detailed description]	[e.g., As needed]	[Price]

2. Performance Metrics

Each metric below is measured monthly. Failure to meet the target constitutes a performance violation.

Uptime / Availability

Metric	Target	Calculation Method
[System/System Name]	[e.g., 99.9%]	[(Total Time - Downtime) / Total Time] × 100
[Database/Database Name]	[e.g., 99.95%]	[(Total Time - Downtime) / Total Time] × 100

Response Time

Type of Incident	Target Response	Target Resolution
P1 - Critical	[e.g., 15 minutes]	[e.g., 2 hours]
P2 - High	[e.g., 30 minutes]	[e.g., 4 hours]
P3 - Moderate	[e.g., 2 hours]	[e.g., 1 business day]
P4 - Low	[e.g., 8 hours]	[e.g., 2 business days]

Quality Metrics

Metric	Target	Measurement Period
[e.g., Bug count]	[e.g., 0 critical bugs / month]	[e.g., Monthly]
[e.g., Customer satisfaction]	[e.g., 4.5/5]	[e.g., Quarterly]
[e.g., Feature delivery]	[e.g., 100% on time]	[e.g., Sprint/project based]

3. Penalties for Underperformance

When a metric falls below the target, the following penalties apply automatically. No claim is required; penalties are applied to the next invoice.

Penalty Calculation:

Violation Count	Penalty Amount
1st violation in a 30-day period	[e.g., 5% of invoice]
2nd violation in a 30-day period	[e.g., 10% of invoice]
3rd violation in a 30-day period	[e.g., 15% of invoice]
4+ violations in a 30-day period	[e.g., 25% of invoice]

Penalty Cap:

No single penalty may exceed [MAX_PENALTY_PERCENTAGE]% of a single invoice. Cumulative penalties across multiple invoices are capped at [TOTAL_PENALTY_CAP] annually.

Example:

Monthly invoice: $10,000

1st downtime violation: -$500 (5%)
2nd response-time violation: -$1,000 (10%)
3rd quality violation: -$1,500 (15%)
Total penalty: -$3,000

4. Monitoring and Reporting

[VENDOR_NAME] agrees to provide the following reports:

Report Type	Delivery Frequency	Content
Monthly Performance Report	5th business day of each month	Uptime, response times, quality metrics
Incident Log	Weekly	All incidents > 15 minutes
Quarterly Review	Last week of each quarter	Full performance analysis, improvement plan

5. Dispute Resolution

When to Escalate:

If either party believes the other has violated this SLA, the following escalation path applies:

Internal escalation (2 business days): Contact the vendor's designated point of contact and your company's account manager. Document everything in writing.
Signed incident report (5 business days): Create a formal incident report signed by both parties summarizing the issue, the agreed timeline for resolution, and the expected outcome.
Arbitration (30 business days): If the issue is unresolved, submit to arbitration by [Arbitration Provider]. The arbitrator's decision is final and binding.

Example Dispute Process:

Day 1: You notice 98% uptime when target is 99.9%
Day 2: You email the vendor's POC; they respond "We'll investigate"
Day 7: No resolution; you create a formal incident report
Day 12: Vendor agrees to fix but doesn't apologize
Day 14: You submit to arbitration with evidence of underperformance
Day 44: Arbitrator rules in your favor; vendor must pay penalties

6. Communication Channels

Incident Level	Primary Channel	Secondary Channel
P1 - Critical	[e.g., Phone / Emergency hotline]	[e.g., SMS / Pager]
P2 - High	[e.g., Slack / Email]	[e.g., Phone]
P3 - Moderate	[e.g., Email / Ticket system]	[e.g., Slack]
P4 - Low	[e.g., Ticket system]	[e.g., Email]

7. Termination

Either party may terminate this SLA with [TERMINATION_NOTICE_PERIOD] written notice for the following reasons:

Repeated violations of this SLA (≥3 violations in a 90-day period)
Failure to deliver services as specified
Material breach of contract
Unpaid invoices beyond 30 days

Notice must be sent to the contact listed in the main contract. Termination does not waive penalties for prior performance violations.

Signatures

For [YOUR_COMPANY]

_________________________

Name: [Name]

Title: [Title]

Date: [Date]

For [VENDOR_NAME]

_________________________

Name: [Name]

Title: [Title]

Date: [Date]

Next Step: Implement This Template

Fill in the [BRACKETS] to create your SLA. Use the vendor management playbook to assign tiers and schedule your first monthly review.

→ Back to Vendor Management Playbook