IT Service Level Management: Complete SLA Template and Playbook

What is Service Level Management?

Service Level Management Defined

Service Level Management (SLM) is the ITIL practice responsible for setting clear business-based targets for service performance and ensuring these targets are met. It encompasses the entire lifecycle of service level agreements from design through retirement.

SLM Objectives:

• Define, document, and agree service level targets
• Monitor and report on service performance
• Conduct service reviews with customers
• Identify improvement opportunities
• Ensure IT services meet business needs

Key SLM Activities:

The SLA Hierarchy

Service levels are managed through a hierarchy of agreements:

Service Level Agreement (SLA)

• Agreement between IT and business customers
• Defines service targets from customer perspective
• Focuses on business outcomes and user experience
• Example: "Email service available 99.9% during business hours"

Operational Level Agreement (OLA)

• Agreement between internal IT teams
• Supports SLA delivery
• Defines internal responsibilities and handoffs
• Example: "Network team provides 99.95% network availability to support email SLA"

Underpinning Contract (UC)

• Agreement with external vendors
• Ensures vendor support for SLA achievement
• Includes penalties for non-performance
• Example: "Cloud provider guarantees 99.99% platform availability"

Relationship Between Agreements:

SLA (Customer-facing)
    ↓
OLA (Internal IT teams)
    ↓
UC (External vendors)

Each lower-level agreement must support the achievement of higher-level commitments.

Designing Effective SLAs

SLA Design Principles

1. Business-Aligned

• Targets reflect business needs, not IT capabilities
• Focus on outcomes users care about
• Language business stakeholders understand

2. Measurable

• Every target can be objectively measured
• Data collection is automated where possible
• Metrics are unambiguous

3. Achievable

• Targets are realistic given resources
• Based on baseline performance data
• Allow for some variability

4. Time-Bounded

• Clear measurement periods defined
• Exclusions documented (maintenance windows, etc.)
• Review and renewal dates specified

5. Documented

• Written, formal agreement
• Signed by both parties
• Accessible to all stakeholders

SLA Structure and Components

Standard SLA Document Structure:

1. Introduction and Purpose

• Agreement overview
• Parties involved
• Effective dates
• Review schedule

2. Service Description

• Services covered
• Service scope and boundaries
• Service hours
• User eligibility

3. Service Level Targets

• Availability targets
• Performance targets
• Support response/resolution times
• Capacity targets

4. Measurement and Reporting

• How metrics are calculated
• Data sources
• Reporting frequency
• Report distribution

5. Roles and Responsibilities

• IT responsibilities
• Customer responsibilities
• Escalation contacts
• Governance structure

6. Service Management

• Change management
• Incident management
• Problem management
• Service requests

7. Exclusions and Assumptions

• Planned maintenance windows
• Force majeure
• Customer-caused issues
• Assumptions about environment

8. Service Credits and Remedies

• Credit calculation (if applicable)
• Credit caps
• Claiming process
• Alternative remedies

9. Agreement Administration

• Amendment process
• Termination conditions
• Dispute resolution
• Signature page

Service Level Metrics and Targets

Availability Metrics

System Availability

Availability % = ((Total Time - Downtime) / Total Time) × 100

Availability Targets by Service Tier:

Availability Calculation Considerations:

Include in Downtime:

• Unplanned outages
• Extended maintenance beyond window
• Degraded performance below threshold
• Partial outages affecting users

Exclude from Downtime:

• Planned maintenance (within agreed windows)
• Customer-caused issues
• Force majeure events
• Third-party failures outside IT control

Availability Measurement Period:

• Monthly: Most common for operational SLAs
• Quarterly: Executive reporting
• Annual: Contract renewals, trending

Performance Metrics

Response Time

Throughput

Capacity

Support Metrics

Incident Response and Resolution:

Priority Definitions:

Service Request Fulfillment:

Quality Metrics

Customer Satisfaction:

• Target: ≥4.0/5.0 or ≥80% satisfied
• Measurement: Post-ticket survey, periodic surveys

First Contact Resolution:

• Target: ≥70%
• Measurement: Tickets resolved without escalation

SLA Compliance:

• Target: ≥95%
• Measurement: Targets met / Total measurements

Repeat Incidents:

• Target: under 5%
• Measurement: Recurring issues within 30 days

SLA Templates by Service Type

Infrastructure Services SLA

Template: Data Center / Server Infrastructure

Service Description: Provision and maintenance of server infrastructure supporting business applications.

Service Hours:

• Production systems: 24x7x365
• Development/Test: Business hours (8am-6pm local, Mon-Fri)

Service Level Targets:

Support Response:

Network Services SLA

Template: Enterprise Network

Service Description: Corporate network infrastructure including LAN, WAN, wireless, and internet connectivity.

Service Hours:

• Core network: 24x7x365
• Office network: 24x7 (reduced support after hours)

Service Level Targets:

Exclusions:

• ISP outages beyond IT control
• User device issues (personal devices)
• Configuration changes requested by users

Application Services SLA

Template: Business Application

Service Description: [Application Name] - [Brief description of application purpose]

Service Hours:

• Production: [Define hours]
• Support: [Define support hours]

Service Level Targets:

Maintenance Windows:

• Standard: Sunday 2am-6am
• Emergency: As required with 4-hour notice
• Extended: Quarterly with 2-week notice

Support Contacts:

Service Desk SLA

Template: IT Service Desk

Service Description: Single point of contact for IT support requests and incident reporting.

Service Hours:

• Phone/Chat: 7am-7pm local time, Mon-Fri
• Self-Service Portal: 24x7
• After-Hours: On-call for P1/P2 only

Service Level Targets:

Incident Resolution Targets:

Cloud Services SLA

Template: Cloud Platform (IaaS/PaaS)

Service Description: Cloud infrastructure and platform services supporting business applications.

Service Level Targets:

IT Value-Add Targets:

Exclusions:

• Provider-side outages covered by provider SLA
• User misconfiguration
• Intentional service termination

SLA Negotiation Process

Preparing for Negotiation

Step 1: Gather Baseline Data

Before negotiating, understand current performance:

• Current availability metrics
• Historical incident data
• Performance measurements
• User satisfaction scores
• Cost of service delivery

Step 2: Understand Business Requirements

Step 3: Assess Capability and Cost

Each "nine" of availability typically requires significant additional investment.

The Negotiation Meeting

Agenda:

1. Current State Review (15 min)

   • Present baseline performance data
   • Review any current SLA performance
   • Acknowledge known issues

2. Business Requirements (20 min)

   • Customer explains business needs
   • Discuss criticality and dependencies
   • Quantify cost of service disruption

3. Target Discussion (30 min)

   • Present proposed targets
   • Discuss trade-offs (cost vs. availability)
   • Negotiate specific metrics
   • Agree on measurement methodology

4. Exclusions and Assumptions (15 min)

   • Agree on maintenance windows
   • Define exclusions
   • Document assumptions

5. Agreement and Next Steps (10 min)

   • Summarize agreed targets
   • Set timeline for formal documentation
   • Schedule review cadence

Negotiation Best Practices

Do:

• Come prepared with data
• Present options with cost implications
• Listen to business priorities
• Be willing to compromise
• Document everything discussed
• Set realistic, achievable targets

Don't:

• Promise what you can't deliver
• Use technical jargon
• Ignore cost implications
• Set targets without measurement capability
• Agree to everything without analysis
• Let perfect be the enemy of good

Handling Unrealistic Expectations

When business demands exceed capability:

1. Quantify the Gap: Show current performance vs. requested
2. Explain the Investment: Detail what's needed to meet target
3. Present Alternatives: Offer tiered options at different costs
4. Propose a Path: Roadmap to improved service levels over time
5. Agree on Interim Targets: Set achievable milestones

Example Conversation:

"You've requested 99.99% availability, which is 52 minutes of downtime annually. Our current architecture achieves 99.5% (44 hours). To reach 99.99%, we'd need to invest $500K in redundant infrastructure. As an alternative, we can achieve 99.9% (8.7 hours) with a $150K investment this year, then plan for 99.99% in Year 2."

SLA Monitoring and Reporting

Monitoring Framework

Real-Time Monitoring:

Monitoring Requirements by SLA Type:

SLA Reporting

Monthly SLA Report Template:

Executive Summary

• Overall SLA compliance: X%
• Services meeting targets: X of Y
• Key achievements
• Areas of concern
• Actions underway

Service Performance Summary

Detailed Performance by Service

For each service:

• Availability chart (daily/weekly)
• Incident summary
• Downtime log
• Performance metrics
• Compliance calculation
• Improvement actions

Support Performance

Incidents Impacting SLA

Actions and Improvement Plan

Reporting Cadence

SLA Review Meetings

Monthly Service Review Agenda:

Quarterly Business Review:

• Comprehensive SLA performance analysis
• Trend analysis (improving/declining)
• Business impact assessment
• Investment recommendations
• SLA target adjustments if needed
• Strategic planning discussion

SLA Breach Management

Breach Detection and Response

SLA Breach Severity Levels:

Breach Response Process:

1. Detection: Automated alert or manual identification
2. Classification: Determine severity and impact
3. Notification: Alert appropriate stakeholders
4. Investigation: Root cause analysis
5. Remediation: Implement fix or workaround
6. Documentation: Record in SLA breach log
7. Prevention: Identify improvements to prevent recurrence

Root Cause Analysis

5 Whys Example:

Problem: SLA breached - P1 incident took 6 hours to resolve (target: 4 hours)

1. Why did resolution take 6 hours? → Waited 2 hours for database team
2. Why did we wait for database team? → On-call DBA not reachable
3. Why wasn't DBA reachable? → Outdated contact information
4. Why was contact info outdated? → No regular verification process
5. Why no verification process? → Never established after last DBA change

Root Cause: No process to verify on-call contact information Action: Implement monthly on-call roster verification

Service Credits

Credit Calculation Methods:

Method 1: Percentage-Based

Credit = Monthly Fee × (Target - Actual) / Target

Example:
- Monthly fee: $10,000
- Target availability: 99.9%
- Actual availability: 99.5%
- Credit: $10,000 × (99.9 - 99.5) / 99.9 = $40

Method 2: Tiered Credits

Method 3: Downtime-Based

Credit Caps:

• Monthly cap: Typically 50-100% of monthly fee
• Annual cap: May be specified
• Exclusions: Scheduled maintenance, customer-caused issues

Credit Claiming Process:

1. Customer submits claim within 30 days
2. IT validates against monitoring data
3. Approve or dispute with evidence
4. Apply credit to next invoice
5. Document in SLA records

Operational Level Agreements (OLAs)

OLA Purpose and Structure

OLAs define internal commitments that support customer-facing SLAs.

OLA Template:

Agreement Between: [IT Team A] and [IT Team B] Effective Date: [Date] Supporting SLA: [Customer SLA Reference]

Service Commitment: [Description of service one team provides to another]

Service Level Targets:

Responsibilities:

Escalation Path:

OLA Examples

Network Team OLA (Supporting Email SLA):

Database Team OLA (Supporting ERP SLA):

Security Team OLA (Supporting All Services):

Continuous Improvement

Service Improvement Process

Identify Improvement Opportunities:

Improvement Planning:

Continual Service Improvement (CSI) Register:

SLA Maturity Model

Level 1: Ad Hoc

• No formal SLAs
• Reactive support
• No performance measurement
• Next Step: Document basic service commitments

Level 2: Basic

• Some SLAs documented
• Manual measurement
• Inconsistent reporting
• Next Step: Implement monitoring tools

Level 3: Defined

• Comprehensive SLAs
• Automated monitoring
• Regular reporting
• Next Step: Establish OLAs and UCs

Level 4: Managed

• Full SLA hierarchy (SLA/OLA/UC)
• Proactive management
• Service credits implemented
• Next Step: Predictive analytics

Level 5: Optimized

• Continuous improvement culture
• Predictive SLA management
• Industry-leading performance
• Next Step: Innovation and transformation

Annual SLA Review

Annual Review Agenda:

1. Year in Review

   • Overall SLA performance summary
   • Achievements and challenges
   • Major incidents and lessons learned

2. Performance Analysis

   • Service-by-service review
   • Trend analysis
   • Benchmark comparison

3. Customer Feedback

   • Satisfaction survey results
   • Service review feedback
   • Complaint analysis

4. Cost Analysis

   • Cost of service delivery
   • Investment vs. performance
   • Cost optimization opportunities

5. Target Adjustment

   • Proposed target changes
   • New services to add
   • Services to retire

6. Improvement Plan

   • Next year initiatives
   • Investment requirements
   • Timeline and milestones

7. Agreement Renewal

   • Updated SLA document
   • Signature collection
   • Communication plan

Implementation Roadmap

Phase 1: Foundation (Weeks 1-4)

Week 1-2: Assessment

• Inventory existing service commitments
• Assess current monitoring capabilities
• Gather baseline performance data
• Identify key stakeholders

Week 3-4: Design

• Define SLA structure and hierarchy
• Select metrics for each service
• Draft SLA templates
• Design reporting framework

Phase 2: Development (Weeks 5-8)

Week 5-6: Documentation

• Complete SLA documents
• Create OLA documents
• Review underpinning contracts
• Develop reporting templates

Week 7-8: Tools and Processes

• Configure monitoring tools
• Set up automated reporting
• Create dashboards
• Document processes

Phase 3: Negotiation (Weeks 9-12)

Week 9-10: Internal Alignment

• Review SLAs with IT teams
• Negotiate OLAs internally
• Validate monitoring accuracy
• Test reporting

Week 11-12: Business Engagement

• Present SLAs to business stakeholders
• Negotiate and finalize targets
• Obtain signatures
• Communicate to organization

Phase 4: Operations (Ongoing)

Monthly:

• Generate SLA reports
• Conduct service reviews
• Track improvement actions
• Update breach log

Quarterly:

• Business review meetings
• Trend analysis
• Improvement planning
• OLA/UC review

Annually:

• Comprehensive SLA review
• Target renegotiation
• Document updates
• Maturity assessment

Common Pitfalls and Solutions

Pitfall 1: Unmeasurable SLAs

Problem: Targets set without ability to measure. Solution: Only commit to metrics you can track; invest in monitoring before finalizing SLAs.

Pitfall 2: IT-Centric Language

Problem: SLAs written in technical jargon business doesn't understand. Solution: Use business language; focus on outcomes users experience, not technical details.

Pitfall 3: Set and Forget

Problem: SLAs signed but never reviewed or measured. Solution: Mandatory monthly reporting, quarterly reviews, annual renegotiation.

Pitfall 4: Unrealistic Targets

Problem: Agreeing to targets IT cannot achieve. Solution: Base targets on baseline data; present cost/benefit trade-offs; negotiate achievable commitments.

Pitfall 5: Missing OLAs

Problem: SLAs exist but internal agreements don't support them. Solution: Create OLAs for every internal dependency; ensure vendor contracts (UCs) align.

Pitfall 6: No Consequences

Problem: SLA breaches have no impact. Solution: Implement service credits, escalation procedures, and tie performance to IT metrics.

Pitfall 7: Too Many Metrics

Problem: Tracking 50 metrics, overwhelming stakeholders. Solution: Focus on 5-10 meaningful metrics per service; use supporting metrics for IT internal management only.

Conclusion

Effective service level management transforms IT from a reactive cost center to a proactive business partner. When you define clear commitments, measure performance consistently, and drive continuous improvement, you build trust with business stakeholders and deliver reliable services.

Your SLA Management Checklist:

• Define service level structure (SLA, OLA, UC)
• Select meaningful, measurable metrics
• Establish realistic, achievable targets
• Implement automated monitoring
• Create standardized reporting
• Establish regular review cadence
• Define breach management process
• Document service credits (if applicable)
• Create improvement register
• Schedule annual SLA review

Related Resources:

• ITIL Foundation Templates - ITIL service management framework
• IT Service Desk Best Practices - Service desk operations
• IT Operations Excellence Guide - ITIL implementation
• IT Governance KPIs Dashboard - IT performance metrics

Build a service level management practice that delivers consistent, reliable IT services aligned with business needs.