SLA rule changes: what goes into the next report?

A new calendar from an agreed date

A client and a service company agreed to extend support hours from the next period. That changes the calendar used to measure the SLA. The person preparing the report edits the shared calendar in the helpdesk, and from that moment earlier periods are counted under the new rules, so the previous report no longer adds up.

In the proposed application, the service owner prepares a new version of the rules beside the agreements with this client and records the date from which it applies. The current version stays available. Before approval, they compare the same set of tickets under the current and the new rules, and where there is a difference they see the explanation: the new calendar counts time that used to fall outside working hours. An older report keeps a pointer to the definitions it was built on.

What it costs and when it pays back

The count covers the work around a case: searching, reading, writing and handing over. What remains is the time to check the result, 25% of today's work in the scenario. Before the quote, we measure both times on 20 to 100 cases the team has already handled, in a free test that takes 5 working days.

The scenario assumes 40 SLA reports a month at an hour of work each, including corrections by hand after rule changes. When the tool changes, the export covers the versions of the rules with their dates, decisions and a pointer to the reports that used them.

What to check in your current helpdesk

Jira Service Management lets you edit SLA goals: the target time, the priority, the calendar and the conditions for which tickets are covered. Using the last change as an example, work out how the tool keeps earlier definitions, shows the difference and links rules to a period and a client. If the available features support review and approval, configuration is enough. An integration makes sense when the helpdesk measures well but preparing and approving changes happens in emails and spreadsheets. Gathering ticket history every month is covered in the article on automating SLA reporting.

Where to start

At launch you need the current rules, the changes in preparation and the definitions used in older reports. The team names the versions it can confirm from its records, and we do not reconstruct missing history from guesses. We build this kind of rollout as part of AI applications. For the free analysis, a description of one case from recent weeks and of the tools it passed through is enough. You do not need to send confidential documents, and you get a written plan within 2 working days.