What the SLA covers
- ticket priorities
- response time
- availability hours
- outage escalation and scope of responsibility
An IT SLA is part of a subscription agreement. It defines what we are responsible for, how we take tickets, what the priorities are and how quickly we respond.
We do not assume that a subscription includes every change. First we establish the responsibility boundary, the type of work and the current state of the environment.
| Model | What it is for | Boundary |
|---|---|---|
| Subscription | Recurring support, agreed systems, ticket flow, monitoring and SLA where it is in the agreement. | The agreed subscription is billed in advance. Agreed additional work carried out during the month is added to the next invoice. |
| Project | Diagnosis, migration, implementation or a defined change with an agreed result. | Scope, outcome, cost and estimated schedule are agreed before work starts. The project is paid in advance against a pro forma invoice; it is not ongoing on-call cover. |
| Separate quote | Larger rebuilds, work outside the agreed pool, application code, or third-party costs. | We agree the scope and cost before work starts. Separate projects are paid in advance against a pro forma invoice; other agreed work outside the subscription is added to the next invoice. |
Number and role of systems, business criticality, support availability, documentation quality, backup state and the scope of project work.
A responsibility map, ticket route, priorities, available documentation and a plan for the next agreed actions.
First we establish the current state and the required diagnostic scope. For ongoing subscription support, we then agree responsibility, SLA, ticket flow and a plan for taking over access, documentation and monitoring.