Sign up free

Solution · For IT managers

Run IT service on numbers the business can understand.

An IT manager’s job is translation: turning the team’s work into numbers the business trusts, and turning the business’s expectations into targets the team can meet. That needs evidence — not opinions, and not a feeling that the team is busy.

By itserva Editorial Team Updated November 20, 2026 Reviewed by [REVIEWER NAME, CREDENTIAL]

Service levels agreed in writing, with numbers behind them.

Staffing and costs worked out from real ticket volume.

Software chosen on sourced facts, not sales pitches.

The problem

Why managing IT service is hard to defend

The hardest part of managing IT service is not the technology. It is the conversations: justifying headcount, defending a budget, explaining an outage to people who were affected by it.

Asked to prove the team is busy

The business sees a quiet team and wonders what it does all day. Without ticket volumes, resolution times and costs, the manager has anecdotes — and anecdotes lose to a spreadsheet every time.

Targets agreed without numbers

A service level is promised in a meeting, with no calculation behind it. Months later the team misses the target, and the manager discovers the promise was never achievable with the staff available.

Hiring on a hunch

The desk feels understaffed, but nobody can say how many agents the volume actually needs. The hire is approved or refused on the strength of a feeling, and the queue stays long either way.

Software bought on a demo

A vendor demo looks good, the contract is signed, and the tool turns out to miss the one feature the team needs. The price was known; the fit was not checked, because the comparison never happened.

The process

Five steps, and the itserva page for each

Five steps, from the promise to the proof.

  1. 01

    Set the service levels

    Agree what each service promises, in writing, with the people who rely on it. An agreement that names its targets and its exclusions is a document the manager can point to in a difficult conversation.

    SLA Template →

  2. 02

    Turn targets into numbers

    Convert each uptime percentage into allowed downtime per week, month and year. Minutes are numbers the business can argue about honestly; a percentage hides the real allowance.

    SLA Uptime Calculator →

  3. 03

    Staff the desk to the volume

    Work out how many agents the ticket volume actually needs at the service level you promised. Staffing becomes a calculation the business can check, instead of a request it has to take on trust.

    Help Desk Staffing Calculator →

  4. 04

    Know what each ticket costs

    Work out the fully loaded cost of resolving one ticket, including the time and the tools behind it. The number makes the case for automation, for self-service, or for the extra hire.

    IT Support Cost Per Ticket →

  5. 05

    Choose the software

    Compare help desk software on price, channels and fit for a team your size. The comparison shows what each vendor publishes — and marks what it does not — so the decision rests on facts.

    Best Help Desk Software →

What’s included

Tools, templates and guides for it managers

Tool

SLA Uptime Calculator

Turn an uptime percentage into allowed downtime per week, month and year.

Tool

Help Desk Staffing Calculator

Estimate how many agents a ticket volume needs at a given service level.

Tool

IT Support Cost Per Ticket

Work out the fully loaded cost of resolving one support ticket.

Template

SLA Template

A service level agreement you can adapt: targets, exclusions and remedies.

Guide

What is ITSM?

What IT service management covers, who it is for, and where to start.

Product

SLA Tracker

Track uptime against target for every service, and see the downtime budget that is left.

Measure it

The four numbers worth tracking

Four numbers belong in every service review. Bring them to the meeting, and the conversation changes from opinions to decisions.

SLA met rate

The share of incidents resolved within the agreed target. It is the number the business cares about most, and the one that justifies the next investment.

Check your SLA allowance →

Cost per ticket

What one resolved ticket actually costs, fully loaded. When it rises, something in the process is getting more expensive — and that is where the manager should look.

Calculate cost per ticket →

Staffing against volume

Agents on the desk compared with the number the volume needs. A gap here explains a long queue better than any complaint about effort.

Calculate staffing needs →

MTTR trend

Whether the team is recovering faster or slower over time. A rising trend is an early warning — usually a training, access or coverage gap, not a lack of effort.

Calculate your MTTR →

Frequently asked questions

What should an IT manager report each month?

Four numbers: the SLA met rate, the cost per ticket, the MTTR trend, and the ticket volume by service. Add one sentence per number explaining what changed and why — the numbers alone do not tell the story.

How do I justify another hire?

With the staffing calculator: show the volume, the service level promised, and the agents that volume needs. A shortfall in agents is a fact the business can check, and it explains the queue better than any anecdote.

Should I adopt ITIL?

Only if your team needs a shared vocabulary or a checklist for what good looks like. If the incident process is broken, fix the process first — a framework will not fix it for you.

How do I compare software fairly?

Start from what your team needs, then check each vendor’s published facts: price, deployment, and the features that matter. Where a vendor does not publish a fact, mark it as not published instead of guessing.

Bring numbers to the next service review.

Run the SLA calculator on your most important service and the staffing calculator on your ticket volume. A free workspace saves both, so the review starts from evidence.

Create a free workspace