Maintenance work order app
- What reacting costs a month
- $9,273.60
- Breakdown jobs a month
- 84
- Avoidable hours a month
- 193.2
Every figure printed on this site is arithmetic on the worked example we publish: 180 assets, 240 work orders a month, 35% of them raised as breakdowns, a breakdown job at 3.4 hours against 1.1 hours planned, a loaded technician cost of $48 an hour. Change any of those on the worksheet and the numbers change with them. Nothing here is a market statistic and nothing is quoted from a third party.
A maintenance work order app is bought to stop jobs being passed on by text message, and that is a fair reason, but it undersells what the work order is for. The work order is the unit that turns a maintenance function into a record: one job, on one asset, with who did it, when, and what they found. Without it there is no history, and without history every interval on the schedule is a guess that nobody can check. This page sets out what has to be on one and what it is worth to have them.
Open the Maintenance log Free to use. No account, no card, no trial clock.
One job, one asset, one work order
The temptation is a work order per visit or per day. It reads tidier and it destroys the history: three jobs on three assets recorded as one visit tells you nothing about any of the three when you come to review the intervals.
Capture what was FOUND, not just what was done
'PM completed' is a compliance record. 'PM completed, belt showing wear, replaced' is maintenance knowledge, and it is the only thing that ever justifies changing an interval. This is the field technicians skip and the field the schedule depends on.
Count reactive against planned, monthly
The ratio is the whole health of the function in one number. On the worked example we publish, 240 work orders a month at 35% reactive is 84 breakdowns and 193.2 avoidable hours; watching that share move is worth more than any dashboard.
Maintenance work order app: common questions
What has to be on a work order? The asset, the date, who did it, what the job was, what was found, and how long it took. The last two are the ones that get dropped and the two the schedule needs.
Should technicians raise work orders themselves? Yes, on a phone, at the machine. A work order raised at a desk from memory at the end of the week is a report, not a record, and its hours are always rounder than the real ones.
What is a good reactive share? Lower than last quarter. An absolute target imported from another site's plant is a benchmark you cannot act on; your own trend is one you can.
Will it do what you need for Maintenance work order app?
Tell us what you maintain and how the schedule is kept today, and we will tell you plainly whether this is the right shape of tool for it.