Knowing what maintenance actually costs
Not what you invoiced. What each asset cost you to keep running.
Most organisations know their maintenance spend to the shilling. Very few know their maintenance cost per asset, and the gap between those two facts is where budget decisions go wrong.
Spend is not cost
Spend is organised by who you paid. Cost is organised by what you were maintaining. A single contractor invoice might cover work on eleven assets across three sites; filed as one payment, it tells you nothing about which of those assets is expensive to own.
The fix is unglamorous: every cost line attaches to an asset and a work order at the moment it enters the system. Retrospective allocation does not work, because nobody remembers.
What becomes possible
- Asset costing history — what this specific machine has cost over its life, not over a budget year.
- Cost centre visibility — which department is actually consuming the maintenance budget.
- Repair-versus-replace arguments backed by a number rather than a feeling.
- Budgets built from last year's reality instead of last year's budget plus inflation.
The first report worth building
Cost per asset, ranked descending, for the last twelve months. It is a simple report and it is usually uncomfortable, because the top of the list is rarely where the team assumed it would be. That discomfort is the value.
Related reading
See it against your own workflows
Book a live demo and we will start with your overdue work orders, not our feature list.