Procurement Documents

Service Level Agreement (SLA) Template for IT (Free, Word)

A free, vendor-neutral SLA template for IT services, managed services and SaaS, with availability targets, a downtime conversion table, a severity matrix, service credits and chronic failure terms.

12 pages Microsoft Word Updated November 15, 2026
Download Template
Service Level Agreement (SLA) Template for IT (Free, Word) preview
Service Level Agreement (SLA) Template for IT (Free, Word)

Preview the first pages

See the structure before you download. The Word file has every section listed below, ready to fill in.

What's inside

The sections in the document, in order.

  1. Parties, scope and services covered
  2. Definitions
  3. Service hours
  4. Availability
  5. Availability-to-downtime conversion
  6. Support and severity
  7. Escalation path
  8. Performance reporting and review meetings
  9. Service credits
  10. Chronic failure and the right to terminate

Use this service level agreement template to set the service levels for an IT service, a managed service or a SaaS subscription: availability, support response and resolution times, reporting, service credits and the right to leave after repeated failures. Fill it in and send it to the supplier, or attach it to an RFP and ask each supplier to propose its targets in the same format, so the commitments can be compared side by side. It sits under the main contract as a schedule, next to any statement of work for project work such as implementation.


Every target, time and percent is a [placeholder], because the right level depends on the service and on what an outage costs you. The Word file includes an availability-to-downtime conversion table, so you can see what a percentage allows in minutes before you agree to it. It isn't legal advice: legal counsel reviews the completed SLA, with the agreement it sits under, before it's signed. Clauses such as whether credits are your only remedy and the right to terminate are flagged for counsel.


Before signature, check the SLA against the service level rows of the free contract review checklist: how availability is measured, what's excluded, how credits are claimed, support response times and repeated failures. If the supplier offers its own standard SLA instead, run the same checks on that document.


What's inside this template


  • Parties, the services covered with the core functions users depend on, and definitions of availability, downtime, maintenance window, incident, severity, response and resolution
  • Service hours, maintenance windows with notice and a limit, and an availability target for each service with the measurement period, a measurement method, the formula and the exclusions
  • An availability-to-downtime conversion table for monthly and annual periods, with the arithmetic shown so you can check any target
  • A support severity matrix with response, update and resolution or workaround times for each severity, support rules, root cause reports and an escalation path
  • Monthly service reports and review meetings, plus service credits with [percent] placeholders, the claim process and deadline, and a credit cap
  • Chronic failure and the right to terminate, security incident notification, and roles, responsibilities and contacts on both sides
  • Change control for the SLA, a version history, sign-off and an internal checklist before signature

Download the editable Microsoft Word version below. The full text is on this page, so you can read it before you download.

How to use this template

Fill in Sections 1 to 4 with the service owner, using the conversion table in Section 5, then Sections 6 to 11 on support, reporting, credits, chronic failure and security notification. Agree Sections 12 and 13 with the supplier, and delete the italic guidance and the internal checks in Section 14 before you send it.

  1. List the services and what users need from them. Name each service, the core functions users depend on, its service hours and how critical it is. Availability is measured on those functions as users reach them, not on a server or a component the vendor chooses, so write them down in Section 1.2 before anything else.
  2. Set the targets with the people who use the service. Work out with the service owner when the service is used most and what an outage at that time would cost. Use the conversion table in Section 5 to turn any proposed percentage into minutes, and write the severity definitions in terms of business impact, with an example for each level.
  3. Decide the remedies. Fill in the credit levels and the cap, and choose how credits are claimed. Define chronic failure in terms you can count, such as repeated misses within a set number of periods. Leave the wording on whether credits are the only remedy, and on termination, to legal counsel.
  4. Send it to the supplier, or compare it with the supplier’s own. Attach the SLA to your RFP and ask each supplier to fill in its targets or mark any change it needs, so every proposal answers the same terms. If a SaaS supplier will only sign its standard SLA, compare that document against this one, section by section, and negotiate the gaps that matter.
  5. Review, sign and run it. Have legal counsel review the SLA with the agreement it sits under, and check it with the contract review checklist. After signature, set up monitoring, book the review meetings and read every service report. Rate the supplier over the term with the free vendor scorecard template.

How to set SLA targets that mean something

An SLA is only as useful as what it measures and what happens when a target is missed. A high availability percentage can still allow a long outage at your busiest hour if it’s measured over a year, on a component your users never see, with broad exclusions. Before you agree to a target, check these points:

  • Measure what users experience. Availability should be measured on the functions your users rely on, reached the way they reach them, such as signing in and completing a transaction, not on whether a server answers. Decide in advance how a partial outage counts, such as one that affects one location or some of your users.
  • Choose the measurement period on purpose. A monthly period shows a bad month. Over a year, one long outage can be averaged away and the target still met. The conversion table shows the downtime a target allows in each.
  • Limit the exclusions. Scheduled maintenance should fall in an agreed window, with notice and a limit on hours. Failures at the vendor’s own hosting providers and subcontractors should count against the vendor.
  • Define response as a person starting work. An automated acknowledgment isn’t a response. Set update frequencies and resolution or workaround targets as well, so a critical incident can’t sit acknowledged but untouched.
  • Treat credits as a price adjustment, not compensation. A credit reduces the fee for a period of poor service. It’s capped and isn’t sized to cover what an outage costs the business, so don’t set a target around the credit. Make credits automatic where you can, so they don’t depend on a claim filed before a deadline.
  • Look for a chronic-failure exit. For a service that keeps failing, the remedy that matters is the right to leave without a termination fee, with your data and help moving to another provider. Define chronic failure in the SLA in terms you can count.
  • Check targets against something you can see. If the vendor’s monitoring is the only record, ask for access to it or run your own, and agree what happens when the two disagree.

The full template

This is the complete text of the Word document. Fill in the [bracketed] placeholders and delete the italic guidance before you use or send it.

Drafting instructions: use this SLA as a schedule to the main
contract for an IT service, a managed service or a SaaS subscription.
Send it to the supplier, or attach it to an RFP and ask each supplier to
propose its own targets in the bracketed fields. Every target, time and
percent is a [placeholder] for you to set. Delete what doesn’t apply,
and the italic guidance, before you send it.

Not legal advice. This template is business guidance
for drafting service levels. It isn’t legal advice, and legal counsel
reviews the completed SLA, with the agreement it sits under, before it’s
signed. Clauses marked “(Legal)” need counsel’s wording.

Public bodies: the rules on which contract terms you can accept
vary by jurisdiction and agency, so check with your procurement office
or counsel before you negotiate.

Item Details
SLA reference and version [SLA number, version and date]
Customer [Customer legal name] (“Customer”)
Vendor [Vendor legal name] (“Vendor”)
Agreement this SLA forms part of [Master agreement or subscription agreement] dated [date] (the
“Agreement”), and [order form or statement of work]
Effective date and term [Date]; [the term of the Agreement / other term]

1. Parties, scope and
services covered

1.1 Parties and scope

This service level agreement (“SLA”) between Customer and Vendor
forms part of the Agreement and sets the service levels for the services
in Section 1.2. Terms defined in the Agreement have the same meaning
here. [If this SLA and the Agreement conflict on a service level, [this
SLA / the Agreement] takes precedence.] (Legal: counsel confirms the
order of precedence.)

1.2 Services covered

Give a service its own row when it has its own target, and name
the core functions users depend on: availability is measured on them in
Section 4.

Service ID Service Core functions measured Users or locations covered Criticality
[SVC-1] [Service name, as on the order form] [e.g. Sign-in, [key transaction], reporting] [All users / named sites] [Critical / High / Standard]
[SVC-2]

1.3 Out of scope

  • [Services, environments or locations not covered, such as test
    environments]
  • Project work such as implementation, which belongs in a statement of
    work such as RFPhub’s free Statement
    of Work (SOW) Template

2. Definitions

Term Meaning in this SLA
Availability The percentage of service hours in a measurement period, outside
excluded time (Section 4.3), in which a service and its core functions
are usable by Customer’s users, calculated as in Section 4.2
Downtime Time during service hours when a service, or any of its core
functions, is unavailable to Customer’s users or too slow to use [e.g.
[function] takes longer than [time] to respond], as measured under
Section 4.2
Maintenance window The agreed times in Section 3.2 when Vendor may carry out scheduled
maintenance, with notice
Incident An unplanned interruption to a service, a reduction in its quality,
or a fault that will affect it if it isn’t fixed
Severity The level, from 1 (Critical) to 4 (Low), given to an incident by its
business impact, as defined in Section 6.2
Response A qualified member of Vendor’s support staff acknowledges the
incident to the person who raised it, confirms the severity and starts
work on it. An automated reply isn’t a response
Workaround A temporary measure, accepted by Customer, that restores the
affected function to normal use until the incident is resolved
Resolution The cause of the incident is fixed and the service works as
specified, confirmed by Customer [or not disputed within [period] of
Vendor’s notice]
Measurement period The period over which availability is calculated: [each calendar
month]
Business day [Monday to Friday, excluding public holidays in [location]]
Monthly fee The fees for the affected service for the measurement period. Where
fees are billed annually, one-twelfth of the annual fee
Security incident Actual or reasonably suspected unauthorized access to, or loss,
change or disclosure of, Customer data, or a compromise of the systems
that hold it

3. Service hours

3.1 Service and support hours

Service ID Service hours (availability measured) Support hours Severity 1 support Time zone
[SVC-1] [Around the clock / [hours] on business days] [[hours] on business days] [Around the clock / Support hours only] [Time zone]

3.2 Maintenance windows

  • Scheduled maintenance takes place only in these windows: [days,
    times and time zone], with at least [period] written notice of its
    duration and impact.
  • Scheduled maintenance is limited to [hours] in each measurement
    period. Anything beyond that counts as downtime.
  • Emergency maintenance is urgent work outside a window, such as
    fixing a vulnerability that’s being exploited. It counts as downtime
    [unless Customer agrees otherwise in writing], and Vendor gives what
    notice it can and explains the reason in writing within [period].
  • Customer may ask Vendor to move maintenance away from
    [business-critical dates, such as a period-end close].

Set the windows outside the hours your users rely on the service
most.

4. Availability

4.1 Availability targets

Service ID Availability target Measurement period Service credits apply (Section 9)
[SVC-1] [target] [Calendar month] [Yes / No]
[SVC-2] [target] [Calendar month] [Yes / No]

Before you agree to a target, convert it to minutes with Section
5 and ask whether the worst case it allows, as one outage at your
busiest time, is one the business could accept.

4.2 How availability is
measured

Availability (%) = (Service minutes − Excluded minutes − Downtime
minutes) ÷ (Service minutes − Excluded minutes) × 100

Service minutes are the minutes of service hours in the measurement
period: every minute, for a service with round-the-clock service
hours.

  • Method: Vendor checks each core function every
    [interval], from [number] locations outside its own network, the way
    Customer’s users reach it. [Customer may also run its own
    monitoring.]
  • Start and end: downtime starts at the earlier of
    [number] consecutive failed checks or Customer’s report of an incident
    later confirmed as downtime, and ends when the function works normally
    again.
  • Partial outages: when only some users, locations or
    functions are affected, [the full time counts as downtime / downtime
    counts in proportion to the users affected / downtime counts when
    [percent] or more of users are affected].
  • Records: Vendor keeps the monitoring data for
    [period] and gives Customer access to it [through a status page / on
    request]. Where Customer’s records show downtime that Vendor’s don’t,
    the SLA owners review both and escalate under Section 7 if they can’t
    agree.

4.3 Exclusions

Time is excluded only for these reasons, and only if Vendor records
it, with the reason, in the service report (Section 8.1):

  • scheduled maintenance within the limits in Section 3.2;
  • downtime caused by Customer’s breach of the Agreement, Customer’s
    own equipment or networks, or a change Customer made against Vendor’s
    written advice;
  • [events beyond Vendor’s reasonable control, as defined in the
    Agreement’s force majeure clause, which don’t include failures at
    Vendor’s own hosting providers, suppliers or subcontractors]
    (Legal);
  • suspension of a service that the Agreement allows;
  • features Vendor labeled in writing as preview or beta when Customer
    used them.

Read a supplier’s standard exclusions closely. Broad wording,
such as any cause outside the vendor’s control, can take real outages
out of the calculation.

4.4 Other service levels
(optional)

Add other measures the service needs as rows in Section 4.1, each
with a target, a measurement method and whether credits apply: for
example, the response time of a key function, time to complete service
requests, or recovery time and recovery point objectives that match your
disaster recovery plan, such as one built from RFPhub’s free Disaster
Recovery Plan Template
.

5.
Availability-to-downtime conversion

This table is arithmetic, not a recommendation. The percentages
are sample inputs to show the math: set your own target in Section 4.1.
Allowed downtime = minutes in the period × (100 − availability target) ÷
100. Times in parentheses are rounded to the nearest second.

Availability Downtime allowed in a 30-day month (43,200 minutes) Downtime allowed in a 365-day year (525,600 minutes)
99% 432 minutes (7 h 12 min) 5,256 minutes (87 h 36 min)
99.5% 216 minutes (3 h 36 min) 2,628 minutes (43 h 48 min)
99.9% 43.2 minutes (43 min 12 s) 525.6 minutes (8 h 45 min 36 s)
99.95% 21.6 minutes (21 min 36 s) 262.8 minutes (4 h 22 min 48 s)
99.99% 4.32 minutes (4 min 19 s) 52.56 minutes (52 min 34 s)
[target] 43,200 × (100 − [target]) ÷ 100 525,600 × (100 − [target]) ÷ 100
  • Other periods: a 28-day month has 40,320 minutes, a
    29-day month 41,760, a 31-day month 44,640 and a 366-day year 527,040.
    For a calendar-month period, use the minutes in that month.
  • Service hours only: if availability is measured
    only in service hours, use the minutes of service hours in the period:
    service hours a day × service days in the period × 60.
  • Longer periods: the same percentage over a longer
    period allows a longer single outage. Over a year, all of the year’s
    allowed downtime could come in one outage and the target would still be
    met.

6. Support and severity

6.1 Raising an incident

  • Customer’s [named support contacts / users] raise incidents through
    [support portal, email or phone]. Severity 1 incidents are raised by
    phone on [phone number], [at any time / during support hours].
  • Customer gives what it knows: the function affected, when the
    problem started, who is affected, the business impact and any error
    messages.
  • Customer sets the initial severity using Section 6.2. Vendor may
    propose a change, with its reasons, and the severity changes only when
    Customer agrees.

6.2 Severity matrix

Write the definitions in terms of business impact for this
service, with an example for each. Response and update times run [around
the clock for Severity 1 and during support hours for the rest / during
support hours].

Severity Definition Response Update frequency Resolution or workaround
1: Critical A service or core function is unavailable, or Customer data is lost,
corrupted or exposed, and there is no workaround. [Example]
[time] [Every [time]] [time]
2: High A core function fails, gives wrong results or is too slow to use,
and any workaround is difficult or temporary. [Example]
[time] [Every [time]] [time]
3: Medium A function fails or performs poorly, but a reasonable workaround
exists, or the impact is limited to a few users. [Example]
[time] [Every [time]] [time]
4: Low A minor or cosmetic issue, or a question about using the service,
with little or no business impact. [Example]
[time] [Every [time]] [time or next release]

6.3 Support rules

  • The resolution clock pauses only while Vendor waits for information
    or access it has asked Customer for in writing.
  • Once a workaround is in place, the incident [moves to a lower
    severity / keeps its severity], and Vendor gives a date for the
    permanent fix within [period].
  • For each Severity 1 and Severity 2 incident, Vendor sends a root
    cause report within [period] of resolution: what happened, why, the
    impact, the fix, and the actions to stop it recurring, with owners and
    dates.
  • An incident that’s also a security incident is notified under
    Section 11 as well.

7. Escalation path

Use escalation for missed targets, disputes about reports or
credits, and repeated problems. Contacts are in Section 12.2.

Level Customer Vendor Escalate to the next level if not resolved within
1 [Service owner] [Support lead or service manager] [time] for Severity 1; [number] business days otherwise
2 [IT manager or head of the business area] [Head of support or delivery director] [time] for Severity 1; [number] business days otherwise
3 [Executive sponsor] [Executive] Then dispute resolution under the Agreement

A Severity 1 incident that misses its response or update target may
go straight to level 2.

8. Performance
reporting and review meetings

8.1 Service report

Within [number] business days after each measurement period, Vendor
sends a written service report covering:

  • availability of each service against its target, with the
    calculation;
  • each period of downtime: start and end, functions and users
    affected, and cause;
  • excluded time, with the reason for each entry;
  • incidents by severity, with times against the targets and each miss
    explained;
  • service credits due (Section 9) and security incidents notified
    (Section 11);
  • maintenance carried out, and open root cause actions with owners and
    dates.

Customer may dispute a report within [period] of receiving it. A
disputed figure goes to escalation (Section 7), and undisputed credits
are applied in the meantime.

8.2 Review meetings

Meeting Frequency Attendees Purpose
Service review [Monthly] Both SLA owners and support leads The service report, misses, open actions and upcoming changes
Relationship review [Quarterly] SLA owners and sponsors Trends, any risk of chronic failure, improvement plans and changes
to this SLA
Renewal review [Before the renewal notice deadline] Sponsors and procurement Performance over the term, for the renewal decision

To rate the vendor over the term, use the service reports as
evidence in a scorecard, such as RFPhub’s free Vendor
Scorecard Template
.

9. Service credits

A credit reduces the fee for a period in which the service fell
short. Credits are capped and aren’t sized to cover what an outage costs
the business, so set targets for the service you need rather than for
the credit.

9.1 Availability credits

Availability of the service in the measurement period Credit (percent of the monthly fee for that service)
Below [target] and at or above [lower level] [percent]
Below [lower level] and at or above [lowest level] [percent]
Below [lowest level] [percent]

9.2 Support credits (optional)

Missed target Credit (percent of the monthly fee for the affected service)
Severity 1 response [percent] for each incident
Severity 1 resolution or workaround [percent] for each incident
Severity 2 resolution or workaround [percent] for each incident

9.3 How credits are claimed

Choose one option. Option A means a credit doesn’t depend on
someone filing a claim before a deadline.

  • [Option A: Vendor calculates the credits due in each service report
    and applies them to the next invoice, without a claim.]
  • [Option B: Customer claims a credit in writing within [period] of
    receiving the service report. Vendor confirms or disputes it within
    [number] business days and applies confirmed credits to the next
    invoice.]
  • A credit that can’t be applied because the service or the Agreement
    has ended is paid to Customer within [period].

9.4 Credit cap

Total service credits for a service in a measurement period won’t
exceed [cap] of the monthly fee for that service.

Once the cap is reached, the credit stops growing however long
the outage lasts. That’s when Section 10 matters.

[Service credits are a price adjustment for reduced service and don’t
limit Customer’s other rights and remedies under the Agreement. /
Service credits are Customer’s only financial remedy for a missed
availability target, except for the rights in Section 10 and as the
Agreement provides.]

Counsel chooses and drafts this clause. A supplier’s standard SLA
may make credits the only remedy: record what it proposes, with what an
outage would cost and how much the business depends on the
service.

10. Chronic
failure and the right to terminate

10.1 Chronic failure

A chronic failure occurs if, for a service:

  • availability is below target in [number] measurement periods within
    any [number] consecutive periods;
  • availability is below [lowest level] in any single measurement
    period;
  • [number] or more Severity 1 incidents occur within [period];
  • Vendor misses Severity 1 or Severity 2 resolution or workaround
    targets [number] times within [period]; or
  • credits reach the cap in Section 9.4 in [number] measurement periods
    within [period].

10.2 Remediation plan

After a missed availability target or a missed Severity 1 resolution
or workaround target, Vendor sends a written remediation plan within
[number] business days, with causes, actions, owners and dates, for
review at the next service review. A plan doesn’t delay or remove
Customer’s rights in Section 10.3.

After a chronic failure, Customer may terminate [the affected service
/ the Agreement] by written notice within [period]. If it does:

  • no termination fee, early termination charge or other penalty
    applies;
  • Vendor refunds prepaid fees for the period after termination within
    [period];
  • Vendor provides transition assistance, data return and deletion as
    the Agreement sets out, [at no charge / at the Agreement’s rates];
    and
  • credits already earned remain payable.

Counsel drafts the final wording against the Agreement’s
termination clauses. Without this right, a service that keeps failing
earns only capped credits, and Customer stays committed for the rest of
the term.

11. Security incident
notification

  • Vendor notifies Customer’s security contact (Section 12.2) within
    [time] of [becoming aware of / confirming] a security incident affecting
    Customer data or the services, including one at a Vendor subcontractor
    or sub-processor.
  • The first notice says what’s known: what happened and when, the
    data, systems and users affected, actions taken and a contact. Updates
    follow every [time] until containment, then a written report within
    [period] with the cause, impact and actions to prevent a repeat.
  • Vendor cooperates with Customer’s investigation, keeps the relevant
    logs and evidence, and helps Customer meet its own notification
    duties.
  • Notification applies whether or not the incident caused downtime.
    [If the Agreement or the data processing agreement sets a shorter time,
    the shorter time applies.]

Set the time with your own legal deadlines in mind, and match the
data processing agreement. Some sectors have their own rules: for
example, the US federal banking agencies require bank service providers
to notify affected bank customers as soon as possible of certain
computer-security incidents that materially disrupt or degrade the
services they provide (for national banks, see 12 CFR
part 53
). Check with your compliance team or counsel which rules
apply.

12. Roles and
responsibilities

12.1 Responsibilities

Area Vendor Customer
The service Delivers the services to these service levels, and is responsible
for its hosting providers and subcontractors
Uses the services as the Agreement allows
Monitoring and reports Monitors, sends the service report and calculates credits Reads each report and raises disputes in time [and runs its own
monitoring]
Incidents Meets the targets and sends root cause reports Raises incidents as in Section 6.1 and gives the access Vendor asks
for
Changes Gives maintenance notice and warns of changes that affect users Shares business-critical dates and keeps its connected systems on
supported versions
Security Meets the Agreement’s security terms and notifies under Section
11
Manages its users’ access and reports suspected misuse
Reviews Presents the report and owns its actions Sends a decision maker and owns its actions

A Customer failure excuses a missed service level only to the extent
it caused the miss, and only if Vendor told Customer in writing at the
time.

12.2 Contacts

Role Customer Vendor
SLA owner [Name, title, email, phone] [Service manager: name, title, email, phone]
Support and Severity 1 line [Team, email] [Portal, email, phone, hours]
Security contact [Name, email, phone] [Name, email, phone]
Escalation levels 2 and 3 [Names, titles] [Names, titles]
Invoices and credits [Name, email] [Name, email]

13. Change and review of this
SLA

  • This SLA changes only by written amendment signed by authorized
    representatives of both parties.
  • Vendor may not reduce a service level, narrow a definition or add an
    exclusion during the term, including by changing a policy or document on
    its website.
  • The SLA owners review this SLA [once a year], and also when a
    service is added or changes significantly, after a chronic failure and
    before each renewal.
Version Date Change and reason Approved for Customer Approved for Vendor
[Version number] [Date] [First version] [Name] [Name]

14. Sign-off

This SLA forms part of the Agreement. This template isn’t legal
advice: legal counsel reviews the completed SLA and the Agreement
together before either party signs.

Detail Customer Vendor
Name
Title
Signature
Date

Customer’s internal checks before signature (delete before
sending):

Frequently asked questions

What should a service level agreement include?

The services covered and their service hours, definitions of availability, downtime, incidents and severity, an availability target with how it’s measured and what’s excluded, and support response and resolution times for each severity. It should also cover escalation, reporting and review meetings, service credits with a claim process and a cap, the right to terminate after chronic failure, security incident notification, each side’s responsibilities and how the SLA can change. This template has all of them, with placeholders for your own targets.

What is the difference between an SLA, an SOW and a contract?

The contract, often a master agreement or a subscription agreement, sets the legal terms for the whole relationship, such as liability, data protection and termination. A statement of work describes one piece of project work: its scope, deliverables, schedule and acceptance. An SLA sets the ongoing service levels for a running service, such as availability, support response times and credits, and forms part of the contract, often as a schedule to it.

What availability target should an SLA have?

Start from the business: when the service is used, what an hour of downtime would cost at the busiest time, and what workaround users have. Convert any proposed percentage into minutes of downtime for the measurement period, and check that the worst case it allows is one the business could live with. Then compare it with what each supplier will commit to in writing, and pay for a higher target only where the service needs it.

How do service credits work?

When the vendor misses a service level in a measurement period, the customer gets a credit, set as a percentage of that period’s fee for the affected service, against a future invoice. The SLA sets the credit for each level of miss, how credits are claimed and by when, and a cap on the total. A credit lowers the price of a period of poor service and is capped, so it isn’t sized to cover what an outage costs the business. Pair credits with a right to terminate after chronic failure.

Who monitors the SLA?

In this template, the vendor measures availability and support performance and sends a service report after each measurement period, with any credits due. The customer names an SLA owner who reads each report, checks it against its own monitoring and incident records, raises disputes in time and runs the review meetings. Where you can, run your own monitoring of the service as your users reach it, so the vendor’s figures aren’t the only record.

Related guides and templates

Download Template

More procurement documents templates