
SaaS Service Level Agreement
Docs + Word8 pages
Free
Clients buy managed IT on promises that are hard to check, and disputes follow when an outage happens. This agreement sets out the service in one place: what is covered, the helpdesk escalation, how monitoring measures availability, the patch cycle, onsite visits, the work breakdown and the exclusions. Each commitment has a number, a method and a credit.
The sample is an agreement between Umberfield Digital and Carrowmore Estates Ltd, a property firm with three sites and 140 users, with availability of 99.9%, a P1 response in 15 minutes and a credit of 5% when email falls short. Every name, site and figure is fictional. Replace the services, targets and contacts with yours, and have counsel review the terms before signing.
Click Make a copy in Google Docs, then confirm on the Google page. The copy is saved to your own Google Drive.
Replace the services, tiers and customer sites in the scope with the ones this SLA covers.
Set availability, response and resolution targets you can already meet from last quarter's data.
Define the measurement point, calculation window and exclusions, then have counsel review the credits.
Delete the guide page, then share the SLA with the client's procurement team and the service owner.
Yes. Umberfield Digital, Carrowmore Estates Ltd, the people, the sites and every target, credit and figure are fictional. Replace them with your own before the SLA goes to a client.
No. It is a draft to adapt. Availability definitions, service credits and liability caps carry legal risk, so counsel should review them for your jurisdiction and your own risk before anyone signs.
Response is the time until an engineer starts work on a ticket. Resolution is the time until the fault is fixed or a workaround is in place. Keep the two targets separate, so a fast reply is not mistaken for a fix.
More Google Docs templatesMore developer workflows templates

Docs + Word8 pages
Free
Docs + Word7 pages
Free
Slides + PowerPoint11 slides
Free