Skip to content

IT dashboards

IT dashboard examples

Four dashboards for an IT team: uptime, tickets and resolution times by service, the service desk queue, whether changes are breaking production, and whether IT projects are on budget. Open any of them to see it in full, then use it as a template for your own data.

Customer Support dashboard on sample data: tickets, reply and resolution times, and CSAT, by month and channel.
Engineering Delivery dashboard: Deploys, Lead time (hours), Change failure rate, Time to restore (hours) and Incidents tiles.
IT Operations dashboard: Tickets opened, SLA met, First contact resolution, Mean time to resolve (hours) and Uptime tiles.

Three of the four examples. All figures are sample data.

The examples

Four IT dashboard examples and templates

Click a board to see all of it. Click Use template to start your own copy in Mammoth. All figures are sample data.

  1. IT Operations dashboard: Tickets opened, SLA met, First contact resolution, Mean time to resolve (hours) and Uptime tiles.
    Sample data

    IT dashboard

    Are our services up, and is the service desk keeping up?

    • Tickets opened
    • SLA met
    • First contact resolution
    • Mean time to resolve (hours)
    Use template
  2. Customer Support dashboard on sample data: tickets, reply and resolution times, and CSAT, by month and channel.
    Sample data

    Service desk dashboard

    Are customers hearing back fast enough, and is the queue keeping up?

    • Tickets created
    • Tickets solved
    • Median first reply
    • Median resolution
    Use template
  3. Engineering Delivery dashboard: Deploys, Lead time (hours), Change failure rate, Time to restore (hours) and Incidents tiles.
    Sample data

    IT change management dashboard

    Are changes breaking production?

    • Deploys
    • Lead time (hours)
    • Change failure rate
    • Time to restore (hours)
    Use template
  4. Project Portfolio dashboard: Budget, Actual Cost, Cost Variance and Percent Complete tiles, above Budget by portfolio.
    Sample data

    IT project portfolio dashboard

    Are IT projects on budget?

    • Budget
    • Actual cost
    • Cost variance
    • Percent complete
    Use template

Definition

What an IT dashboard is

An IT dashboard is one screen that shows how an IT team is serving the business: whether systems are up, how many tickets come in and from where, how many are fixed on first contact, how long the rest take, and whether service levels are met. The data usually comes from the service desk or ITSM tool and a monitoring system.

  • Services and the desk

    Uptime beside the tickets each service brings.

  • What could be self-service

    Tickets by category show the repeat requests.

  • From your ITSM export

    ServiceNow, Jira or Freshservice data, joined once.

The metrics

The metrics an IT dashboard is built from

Eight numbers. Most depend on a definition agreed first, such as when a ticket counts as resolved.

  • Tickets opened

    How much work comes in?

    What the data needs

    Tickets by service, category and week. Read it by category to find the requests that repeat.

  • SLA met

    Are tickets resolved within the promised time?

    What the data needs

    Resolution time and the target for each priority. Pausing the clock while waiting on the user needs one rule for everyone.

  • First contact resolution

    How many tickets are fixed in one go?

    What the data needs

    A flag on each ticket for fixed on first contact. A high rate lowers cost and lifts satisfaction together.

  • Mean time to resolve

    How long does a fix take?

    What the data needs

    Opened and resolved times, by priority. A median by priority reads truer than one average over all of them.

  • Uptime

    Are services available when people need them?

    What the data needs

    Up and scheduled minutes per service from monitoring. Planned maintenance should be agreed in or out once.

  • Major incidents

    How many outages hit many people?

    What the data needs

    Incidents flagged major by a fixed rule, with the services affected.

  • Downtime by service

    Which systems fail most?

    What the data needs

    Downtime minutes per service. A small service down often can cost less than a core one down once.

  • Change failure rate

    How many changes cause an incident?

    What the data needs

    Changes and the incidents they caused. Most outages follow a change.

How to build one

How to build your own IT dashboard

From one of the examples above to a live dashboard on your own data.

  1. 1

    Pick a template

    Start from any of the four boards above.

  2. 2

    Add your data

    Upload a spreadsheet, or connect one of 100+ tested connectors.

  3. 3

    Clean it once

    Fix and combine your data once. Mammoth repeats those steps for you.

  4. 4

    Set it to refresh

    The dashboard updates on a schedule and flags data that fails a check.

  5. 5

    Share the link

    Public, password-protected or sign-in only, on every plan.

Start with a template

14-day Pro trial · No credit card

FAQ

IT dashboard questions

Last reviewed against the template catalogue.

What should an IT dashboard show?
Whether systems are up and whether the service desk is keeping up. That means uptime and downtime by service, tickets opened and resolved, first contact resolution, time to resolve by priority and SLA met. The first board covers those; the others show change, the queue and projects.
What KPIs should an IT dashboard track?
Tickets opened, SLA met, first contact resolution, mean time to resolve, uptime and major incidents are the core. The list below shows each one with the data it needs.
How do I build an IT dashboard?
Start with the ticket volume the weekly review already looks at. Then follow five steps.
  1. Export tickets with service, category, priority, opened and resolved times, and whether the first contact fixed it.
  2. Export uptime or downtime minutes per service from monitoring.
  3. Use the same service names in both.
  4. Check one week of tickets against the ITSM tool before anyone relies on the board.
  5. Refresh daily, and give each service owner a view filtered to their service.
What is the difference between an IT dashboard and a DevOps dashboard?
The audience. An IT dashboard serves the people using systems: uptime, tickets and how fast they are fixed. A DevOps dashboard serves the people building them: how often they ship and how often a release breaks. The two meet at change, which is why the third board here is the delivery one. DevOps dashboard examples
Where does IT data come from?
Usually a service desk or ITSM tool such as ServiceNow, Jira Service Management or Freshservice, a monitoring tool, and an asset list. Mammoth has 100+ tested connectors, and can also connect to anything with a REST API. You combine the sources once, and Mammoth repeats the same steps on every refresh.
Can the business see it without a licence?
Yes. Dashboard viewers are unlimited and free on every Mammoth plan, including the free one, so service owners and the people they serve can open it at no per-viewer cost. Only the people building the dashboards count as platform users.

Build the IT dashboard you actually need.

Start from one of these templates or your own spreadsheet. Share it with as many people as you like, free.

  • ✓ 14-day Pro trial
  • ✓ No credit card
  • ✓ Viewers always free