ISO 20000 Operational Level Agreement (OLA) Template
Introduction
An Operational Level Agreement (OLA) is an agreement between various service desk internal groups (or other internal organizational units) relating to the service being delivered. In other words, it is an agreement or contract between two internal departments of an organization.
Imagine an intricate IT service such as "Employee Onboarding." Such service would possibly entail the cooperation of the HR system team, the network team, the desktop team, and the application team. An OLA would define what each internal team commits to deliver to the other team/s in terms of timing, scope, etc. in order to successfully deliver on the service requested by the customer

OLA vs. SLA vs. UC: Clarifying the Service Pyramid
It is best to understand the OLA in relation to two other critical agreements, namely Service Level Agreement (SLA) and Underpinning Contract (UC). Together, these three agreements constitute the service pyramid, as illustrated below.
Service Level Agreement (SLA): is an agreement between the service provider and the (internal or external) customer, setting out the service to be provided, general obligations, and service levels, and the responsibilities of both parties.
Operational Level Agreement (OLA): is an agreement between an organization's internal (IT) teams to support the achievement of the service levels defined in an SLA. It sets out the service levels to be delivered by the different teams that jointly provide the service and specifies any required reporting, communication, and escalation procedures.
Underpinning Contract (UC): is a legal agreement between an IT organization and an external service provider (e.g., a hardware supplier or a telecommunication company) identifying what services the external organization must provide and what service levels it must achieve.
While an SLA is typically the agreement between the service provider and the customer, an OLA is an internal agreement between two or more parties, and UC is an agreement between an IT organization and an external service provider. Ideally, the SLA obligations must be achievable, given the support of the relevant OLAs. In turn, the UCs must support the achievement of the OLAs.
Why OLAs Are Indispensable to ISO 20000?
OLAs are considered an integral component of an SMS, as well as a critical success factor in achieving ISO 20000. Organizations that are ISO 20000-certified or seeking to become certified understand the value of an OLA in ensuring effective service management.
1. Bridging the Internal Gaps: With increasingly complex products and a growing number of customers, companies are realizing the risks posed by internal silos. Team A delivers excellent services but is completely unaware of how its activities affect Team B or Team C. An OLA bridges such internal gaps and promotes collaboration and accountability
2. Driving Clarity and Accountability: An OLA defines the roles and obligations of the teams or departments involved, establishing a baseline for enhanced clarity and accountability. By defining KPIs (Key Performance Indicators), the OLA sets performance measurement benchmarks.
3. Supporting ISO 20000 Certification: ISO 20000 is a process-driven standard, and an OLA is critical in demonstrating that the SMS is fit for purpose. An OLA provides evidence of processes in place to deal with services provided to customers.
4. Enhancing Service Quality and Customer Satisfaction: Although it is an internal agreement, an OLA facilitates the delivery of high-quality services to the customer, which ultimately enhances customer satisfaction.
5. Facilitating Continuous Improvement: An OLA provides a baseline for measurement, upon which improvement initiatives can be based. By reviewing the OLA measurement results, the involved teams can initiate process improvement projects. In this respect, continuous improvement of processes is a key requirement of ISO 20000.
Understanding the Key Elements of an ISO 20000 OLA Template
An OLA is a formal document and, as such, it should include certain mandatory sections to ensure that it is comprehensive and effective.
1. Document Control
This section contains instructions and notes related to the document control process.
- Document title: the title of the document, e.g., "OLA for [Service Name] – [Team A] and [Team B]"
- Document ID: unique document identifier
- Version number: the version number of the document
- Date of creation/revision: the date of creation or the last revision
- Review cycle: the period after which the document should be reviewed
- Document owner: the person/group responsible for the document
2. Introduction and Purpose
This section should briefly introduce the document and indicate the purpose and scope of the OLA.
- Purpose: the purpose of the document
- Scope: the scope of the OLA, including the services not covered by the OLA
- Objectives: objectives of the OLA
- ISO 20000 context: relevance to the SMS and ISO 20000
3. Parties Involved
This section should list the parties involved.
- Service provider (internal): the name of the team/function providing a component of the service under the OLA
- Service recipient (internal): the name of the team/function receiving the component of the service under the OLA
- Contact: the primary and secondary contact persons
- Escalation: the escalation policy applicable to the OLA
4. Services Covered and Excluded
This section should describe the services covered by the OLA, as well as any services that are excluded.
- Service description: description of the service or the component of the service (the service to be provided by the internal service provider)
- Dependencies: the services or functions that the service component relies on to be delivered
- Exclusions: items not covered by the OLA
5. Service Levels and Other Performance Measures (KPIs)
This is the most critical section of the OLA, as it indicates the required service levels. Generally, these should be aligned to the SLAs.
- Availability: the agreed percentage of time during which the service component will be available to the service recipient
- Performance: the expected performance of the service component
- Incident resolution: the maximum timeframes for resolving incidents at different priority levels
- Request fulfilment: the timeframes for fulfilling service requests
- Capacity management: capacity-related targets
- Information security: information security requirements
- Collection of metrics: the metric collection procedure
6. Roles and Responsibilities
This section should detail the roles and responsibilities of the parties involved.
- For the internal service provider: responsibilities under the OLA
- For the internal service recipient: responsibilities under the OLA
- Shared responsibilities: responsibilities that apply to both parties
7. Communication and Reporting
This section should outline the communication and reporting requirements.
- Reporting on SLAs and OLA: frequency and content of reporting
- OLA review: when the OLA will be reviewed
- Escalation procedures: procedures for escalating issues that cannot be resolved at the operational level
8. Incident, Problem, and Change Management Procedures
This section should describe the incident, problem, and change management procedures.
- Incidents and problems: procedures for managing incidents and problems related to the service component under the OLA
- Changes and releases: procedures for requesting, approving, scheduling, and implementing changes and releases
9. Service Continuity and Disaster Recovery
This section should describe service continuity and disaster recovery requirements and procedures.
- Backup and recovery: requirements and procedures for backing up and restoring the service component
- Disaster recovery: procedures and roles related to disaster recovery
10. Information Security Considerations
This section should describe any additional information security requirements.
- Data handling and access controls: how data will be handled and protected
- Compliance: any other information security or regulatory compliance requirements
11. Review and Amendment Process
This section should describe how and when the OLA will be reviewed and amended, as applicable.
- Review triggers: triggers for initiating the OLA review process
- Amendment process: process for amending the OLA
12. Terms and Termination
This section should set out the terms and conditions of the OLA. This could include the following:
- Length of agreement: the duration of the OLA (if applicable)
- Termination: any terms related to the termination of the OLA
Best Practices for Creating Effective ISO 20000 OLAs
Creating an OLA template is one thing, but implementing it effectively across internal stakeholders is a much bigger challenge. Here are some key considerations when developing and implementing OLAs.
1. Involve All Stakeholders: It is critical to involve relevant people when designing the OLA requirements and processes. In many cases, the OLA will impact multiple teams. Collaboration is needed to ensure that all are on board and understand their role and expectations.
2. Keep it Realistic and Measurable: The specified service levels in the OLA should be realistic and contribute to the achievement of the service levels defined in the SLA. It must be possible to measure and monitor the relevant KPIs.
3. Review and Update the OLA on a Regular Basis: The OLA should be a living document that is reviewed and updated on a regular basis. Such reviews also help determine whether the OLA remains a valuable tool.
4. Link to SLRs and SLAs: It is critical to ensure that the OLA is aligned to the SLRs and SLAs.
5. Provide Clear Instructions and Communication: After developing the OLA and identifying the roles and responsibilities, it is important to communicate the requirements clearly to the relevant teams and provide any required training.
6. Leverage Technology: Leverage information technology to help measure, monitor, and report on the relevant KPIs and service levels.
Common Challenges and How to Overcome Them?
When implementing OLAs, it is important to be aware of the common pitfalls and know how to address them.
1. Resistance to Change
People tend to resist changes, especially if it means doing things differently. This is especially the case when they have been accustomed to the old ways of operating.
Solution: Demonstrate the benefits and involve the relevant stakeholders in the change management process.
2. Lack of Ownership
With multiple teams and functional areas being involved, it may sometimes not be clear who is accountable or responsible for a specific process or activity.
Solution: Specify roles and responsibilities in the OLA.
3. Vague Metrics
Sometimes, the metrics or KPIs may be too vague or subjective.
Solution: Make sure that the KPIs are measurable and specific.
4. Lack of Buy-In
Sometimes, senior management may be hesitant to approve the OLA.
Solution: Highlight the benefits of the OLA to senior management.
Conclusion
As this article illustrates, the OLA is much more than just a document in the ISO 20000 framework. It is the key to unlocking the power of synergy among the various teams and functions supporting the provision of high-quality services to the customer. By providing clarity on roles and responsibilities, as well as service levels, the OLA sets the stage for enhanced efficiency, collaboration, and accountability. In this respect, an effective OLA template is an invaluable tool in the quest for ISO 20000 certification and excellence in SMS.
Implement ISO Faster with a Complete Documentation System
ISO Toolkit for Your Standard
Pick your toolkit from 8 ready-to-use ISO toolkits available: ISO 27001, 9001, 14001, 45001, 22301, 20000, and 42001 (AI Governance).
✔ Complete ISO documentation framework
✔ Policies, procedures, templates, and records
✔ Risk management & internal audit templates
✔ Management Review and Nonconformance
✔ ISO Standard Mapped Implementation Plan
💡 All toolkits come with instant download, one-time payment, and unlimited email & chat support.
ISO PowerPack Bundle
Designed for teams, organizations, and consultants managing multiple ISO implementations across projects and clients.
✔ Unlimited internal and client use
✔ Deliver ISO services from day one
✔ Impress clients and auditors
✔ Skip months of document creation
✔ Grow your consulting business
💡All the benefits of our ISO toolkits combined in one powerful bundle — save over $1,000 compared to buying the toolkits individually.
