Maintenance Requests use case

Find repeat equipment failures before you pay for the same repair again

A repeat failure is a machine reported again within 30 days of being marked resolved. KudoTaps lists the top repeat offenders for you, so the conversation moves from "fix it again" to "replace it", with every past request and photo for that machine to back it up.

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

Each repair looks small on its own

One call-out is cheap. The fifth one on the same machine this quarter is not, but nobody sees them together.

The history lives in someone's head

The technician who knows that dryer always fails has left, and the pattern left with them.

Fixed, or just reset?

A machine that is working when the technician leaves can be broken again by the weekend. Without a link between the two visits, it counts as two unrelated jobs.

How it works

How repeat equipment failures works with KudoTaps

1

Every request belongs to a machine

Because reports come from the label on the machine, each request is tied to that exact unit, not a free-text description.

2

Each close records how it ended

Fixed, Cleaned, Replaced, No fault found, Not a real fault or Will not fix, with an after photo.

3

The report flags the repeats

Any machine reported again within 30 days of being resolved shows up in the repeat offenders list.

4

Open the machine's history

See every request on that machine, the photos and the activity log, before you decide what to do.

What you get

What you get

✓

Repeat offenders list

The top machines reported again within 30 days of being resolved, in the maintenance reports.

✓

Requests in the last 30 days

Shown per machine on the equipment list, next to open requests and average fix hours.

✓

Breakdowns by problem type and tag

Tag machines by make, model or area, and see where the faults cluster.

✓

Before and after photos

Photos from the report, before the work and after it, kept on each request.

✓

Activity log per request

Who did what and when, so you can see who worked on each previous failure.

✓

Numbers never reused

A machine's number at a location stays with it, so its history is never mixed with another unit.

Frequently asked questions

What counts as a repeat failure?

A machine that gets a new report within 30 days of a request on it being marked resolved.

Does it tell me when to replace a machine?

No. It shows the evidence: how often the machine fails, how long fixes take and what was done. The decision is yours.

Can I see if one make or model fails more?

Yes, if you tag machines by make or model. The reports break requests down by tag.

Does it track warranties or service intervals?

No. There is no warranty tracking and no scheduled or preventive maintenance. Make, serial and notes are stored with each machine.

What if the machine was replaced?

Close the request as Replaced. If the new unit is a different machine, add it as new equipment so its record starts clean.

Run it at every location

Set up repeat equipment failures 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.