Maintenance Requests use case

Maintenance reporting for head office, location by location

Head office needs a few maintenance numbers for every location: how much is open, how much was reported, how fast it gets fixed, what has waited longest and which machines keep failing. KudoTaps reports all of them for the last 7, 30, 90 or 365 days, with requests per machine so small and large sites compare fairly.

At a glance

  • Plan: Operations plan, $59 per location per month
  • Trial: 14 days free on your first paid plan
  • Reporting: Anyone scans a label with their phone camera. No app, no account.
  • Results: Reported per location, so sites can be compared fairly
  • Users: Unlimited equipment and technicians
The problem

Why this is hard today

Reports arrive late and rolled up

A monthly summary from each site, in a different format, tells you what happened weeks ago and not where.

Raw counts punish big sites

The largest location always has the most faults. That says nothing about whether it is well run.

You cannot tell if the backlog is growing

A count of open jobs today does not show whether the team is catching up or falling behind.

How it works

How maintenance reporting for head office works with KudoTaps

1

Sites report as they go

Every scan and every close is recorded at the time, so nobody compiles a report.

2

Pick a period

Last 7, 30, 90 or 365 days.

3

Read the location table

Equipment count, requests per machine, median fix time and oldest open request for each location.

4

Look at the detail

Breakdowns by problem type, tag and technician, repeat offenders, and the weekly trend.

What you get

What you get

✓

Headline numbers

Open now, reported, resolved, median fix time, 90th percentile slow tail and oldest open.

✓

Fair comparison by location

Requests per machine, so a 20-machine site and a 200-machine site sit on the same scale.

✓

Repeat offenders

The machines reported again within 30 days of being resolved.

✓

Opened vs resolved by week

Shows whether each week closed more than it opened.

✓

Ageing of open requests

Under 1 day, 1 to 3 days, 3 to 7 days and over a week.

✓

Breakdowns

By problem type, by tag and by technician.

Frequently asked questions

Why requests per machine instead of total requests?

Total requests grow with the size of a site. Dividing by equipment count shows which locations have more faults for what they have.

What time periods can I report on?

The last 7, 30, 90 or 365 days.

Can I see which machines cost us the most call-outs?

The repeat offenders list shows machines reported again within 30 days of being fixed, and the equipment list shows requests in the last 30 days per machine.

Can the data flow into Power BI or our ERP?

Not automatically. There are no integrations, no webhooks and no public API. Your equipment list downloads as a CSV file, and you can ask for a CSV of your maintenance requests from Settings, which we email to you.

Does it report on planned maintenance compliance?

No. There is no preventive or scheduled maintenance, so the reports cover reported faults and how they were handled.

Run it at every location

Set up maintenance reporting for head office at one location, run it for two weeks, and see what the numbers tell you. See how maintenance requests work or talk to us about 10+ locations.