How should an IT service desk define meaningful service levels?

Meaningful service levels are agreed standards that describe what support users can expect, how service performance will be assessed and which business outcomes the IT service desk is responsible for supporting. They should be based on the organisation’s operational needs, not copied from generic targets or measured solely by the number of tickets closed.

A useful service-level framework connects three elements: the importance of the supported service, the effect of an incident or request on the organisation, and the resources needed to restore or deliver that service. This makes the standard relevant to the business rather than treating a minor access request and a widespread operational outage as equivalent work.

Start with business services, not just ticket types. Map the service desk’s commitments to the services employees and customers rely on. These may include line-of-business applications, connectivity, user access, collaboration tools, data storage or site infrastructure. For each service, identify:

• Which business activities depend on it
• Which users, locations or departments are affected by a failure
• What level of disruption the organisation can tolerate
• Whether a workaround exists
• Which internal teams, suppliers or technical owners are involved

This service-based view prevents the desk from defining performance around its own workflow while overlooking the consequences for the wider organisation.

Use clear priority definitions. A priority model should explain how impact and urgency are assessed. Impact considers the scale and significance of the disruption; urgency considers how quickly the situation could worsen or how soon action is needed. A documented matrix can then classify tickets consistently.

For example, a ticket affecting a critical operational process for many users may receive a higher priority than an individual request with no immediate business consequence. The criteria should be specific enough that different service desk analysts reach broadly consistent decisions. They should also explain what happens when a ticket’s impact changes during investigation.

Define each service level in operational terms. A meaningful standard should state exactly what is being measured and when the measurement starts and stops. Common measures include:

• Acknowledgement: confirmation that the ticket has been received and recorded correctly
• Initial response: the point at which an analyst begins substantive investigation or provides useful guidance
• Progress communication: the agreed frequency or trigger for updating the requester
• Restoration: returning an affected service to an acceptable working condition, even if a permanent fix follows later
• Fulfilment: completing a standard request, such as granting approved access
• Resolution: addressing the underlying fault or completing the requested outcome

Separating restoration from permanent resolution is particularly important. A workaround may reduce business disruption while technical teams continue investigating the root cause. Recording both stages gives a more accurate picture of service performance than using one broad completion measure.

Set targets that reflect capability and dependency. Targets should be based on historical ticket data, service criticality, staffing arrangements, technical complexity and dependencies on third parties. An unrealistic target can encourage superficial ticket updates, premature closure or unnecessary escalation. A target that is too broad provides little accountability.

Where a service depends on an external provider, hardware replacement or customer approval, the service level should explain how that dependency is handled. The desk may remain responsible for ownership and communication even when it cannot directly control the technical action. Any pause conditions, exclusions or customer responsibilities should be written in plain language rather than left to assumption.

Distinguish service levels from internal operating targets. A service level is an externally understood commitment between the service desk and its stakeholders. An internal target may be more demanding and used to create operational headroom. Keeping the two separate allows managers to improve internal performance without repeatedly rewriting the formal agreement.

Service levels should also define what is outside scope. This might include unsupported systems, unapproved software, incomplete information, missed appointments or changes made without authorisation. Exclusions should not be used to avoid accountability; they should clarify which conditions affect measurement and who must take the next action.

Measure quality as well as speed. A desk can appear to meet its targets while delivering a poor user experience. The service-level framework should therefore combine time-based measures with quality indicators such as:

• Whether tickets are categorised and prioritised accurately
• Whether the requested outcome was achieved first time
• How often tickets are reopened
• Whether updates contain useful, understandable information
• Whether recurring incidents lead to problem-management or preventative work
• Whether changes to priority or ownership are properly recorded

These measures help distinguish genuine service improvement from activity that merely makes the ticket queue look healthier.

Make the agreement understandable to users. Users do not need a technical contract to know what information to provide, how priority is determined and what communications they will receive. Publish concise guidance alongside the detailed service-level documentation. Explain that priority is based on business impact rather than the seniority of the person submitting the ticket, and state what information may be requested during diagnosis.

Finally, review the service levels using evidence rather than isolated complaints or a single reporting period. Examine missed targets, recurring incidents, changes in business processes, user feedback and the cost of maintaining each commitment. Adjust definitions when the organisation’s dependencies or risk profile changes. A service level remains meaningful only when it reflects current business requirements, can be measured consistently and leads to decisions that improve the services the organisation depends on.