Maintenance Requests use case

Equipment fix time tracking that needs no timesheets

Tracking equipment fix time needs two timestamps on every job: when the fault was reported and when it was resolved. KudoTaps records both automatically from the scan and the close, then reports the median fix time, the slow tail and the oldest open request, overall and for each location.

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

Averages hide the real story

Nine quick fixes and one job that took three weeks produce an average that describes none of them.

Nobody records when it was fixed

The machine is working again but the request was never closed, so the clock never stopped and the numbers are useless.

No timestamps means arguments

The contractor says it was done Tuesday. The site says Friday. Without a record, neither can prove it.

How it works

How equipment fix time tracking works with KudoTaps

1

The clock starts at the report

A scan, or a request raised from the dashboard, is stamped with the time it was created.

2

Work starts

A technician marks "I am working on it". The request moves to In progress and is assigned to them.

3

The clock stops at resolve

The technician marks it fixed and picks how it ended: Fixed, Cleaned, Replaced, No fault found, Not a real fault or Will not fix.

4

Read the numbers

Choose 7, 30, 90 or 365 days and see fix times overall, per location and per technician.

What you get

What you get

✓

Median fix time

The middle job, not the average. One disaster does not distort the figure.

✓

The slow tail

The 90th percentile: how long the slowest 1 in 10 jobs take. This is where complaints come from.

✓

Oldest open request

The one job that has waited longest, overall and at each location.

✓

Ageing of open work

Open requests grouped into under 1 day, 1 to 3 days, 3 to 7 days and over a week.

✓

Average fix hours per machine

Shown on the equipment list, next to open requests and requests in the last 30 days.

✓

Breakdown by technician

The reports break requests down by technician, so you can see how the work is spread.

Frequently asked questions

Why median fix time rather than average?

One request left open for a month can double an average. The median shows a typical job, and the 90th percentile shows the slow ones separately.

When does the clock start and stop?

It starts when the request is created and stops when it is marked resolved.

Does it show how long a request waited before someone picked it up?

Not as a separate number. The reports measure the full time from report to resolved, plus how long open requests have been waiting.

What if we are waiting on a part?

There is no separate waiting or blocked status. The request stays In progress and the technician can add a note, which goes in the activity log.

Does it alert us when a job goes over a target time?

No. There are no time-based alerts. The ageing view and oldest open request show what is overdue.

Can we compare fix times between locations?

Yes. The per-location table shows median fix time and oldest open request for every site.

Run it at every location

Set up equipment fix time tracking 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.