Industries
Equipment Rental and Dealer Software
Fleet utilisation formulas, the six places rental margin leaks, why late off-rent is silent revenue loss, and what a system does about it.
Quick answer: rental margin leaks in six places and the largest one is invisible. Every day between a customer finishing with a machine and you recording it off rent is revenue given away, it happens on every contract, and no report will show it because those days were never billed. Fix that before anything else.
Why Alberta
The Edmonton region carries an unusually dense rental and dealer population, concentrated around Nisku and Acheson, serving oilfield, construction, and industrial customers across the north. Much of it is privately held, running fleets from a few dozen to several hundred units, with parts and service attached.
Those businesses share a structure worth naming: the same asset earns rental revenue, then parts revenue, then service revenue, and eventually a sale. The question that matters is lifetime return per unit, and most systems are not set up to answer it.
Fleet Utilisation, Both Ways
Two measures, and operators who only track one usually track the less useful one.
Time utilisation = (days on rent / days available) x 100
Dollar utilisation = (annual rental revenue / original equipment cost) x 100Time utilisation tells you whether a unit is moving. A skid steer out 210 days of a 300-day available year is at 70 percent.
Dollar utilisation tells you whether it is earning enough to justify the capital tied up in it. A $90,000 machine returning $27,000 a year is at 30 percent. That is the number that should drive buy, keep, and sell decisions, and it is the one most small fleets never calculate.
Report both per unit, going beyond the category level. A category average of 65 percent comfortably conceals four machines at 90 and three that have not moved since spring. The average is the number that makes idle capital invisible.
Where the Margin Leaks
Ranked by how often each turns out to be the answer.
| The leak | Why it hides | |
|---|---|---|
| 1 | Off-rent recorded late | The days were never billed, so no report can show what you lost |
| 2 | Damage not assessed or recovered | Recovery needs evidence, and evidence needs a process at despatch |
| 3 | Consumables, fuel, delivery | Small per contract, material per year, frequently waived at the counter |
| 4 | Warranty work never claimed | The work was done and the manufacturer was never invoiced for it |
| 5 | Idle assets | Category averages hide the units that never move |
| 6 | Deferred maintenance | Surfaces as mid-rental failure, which costs a replacement unit and a customer’s patience |
The One That Sinks Businesses Quietly
Off-rent deserves its own section because it is different in kind from the others.
Work an illustration. Suppose off-rent gets recorded on average one day after the customer actually finished, a unit goes out 24 times a year, and the day rate is $180.
| Value | |
|---|---|
| Days given away per unit per year | 24 |
| Day rate | $180 |
| Per unit, per year | $4,320 |
| Across a 30-unit fleet | ~$129,600 |
Those are illustrative numbers, and the shape holds at any scale you substitute. What makes it dangerous is that it never appears anywhere. An unbilled day produces no invoice, no credit note, and no variance. It is simply absent, and absence does not show up in a margin report.
Two things fix it, and neither is software alone:
- A defined moment when off-rent is recorded, owned by a named role, with a rule for what happens when a customer calls after hours or drops a unit at the gate.
- Availability that reflects reality, so a machine that is physically back is rentable again today instead of on Thursday when someone updates the sheet.
Configure and rehearse this before go-live. It recurs on every contract you will ever write.
The Dealer Side
Businesses that sell and service as well as rent carry three more things a general system has to handle.
Parts inventory against serialised units. What was fitted to which machine, and when.
Service history belongs on the serial. A decision about one machine should be answerable from that machine’s record. History attached to a model tells you what usually happens instead of what happened here.
Warranty recovery. Work performed under manufacturer warranty has to be identified as claimable, evidenced, and actually claimed. This is item four on the leak list and it is almost always larger than owners expect, because the work gets done under time pressure and the claim is somebody’s paperwork afterwards.
What a System Genuinely Does Here
| Operational reality | The capability | Verified position |
|---|---|---|
| Each unit tracked individually | Serialised products with history on the serial | Native. This is the foundation everything else sits on |
| Rental orders, pickup and return | Rental order with status through pickup and return | Odoo documents a dedicated Rental flow, with order status changing on pickup |
| Daily, weekly, monthly rates | Pricelists with duration rules | Test a rental crossing a rate boundary in the demo |
| Preventive and corrective maintenance | Maintenance scheduling against equipment | Odoo Maintenance covers corrective and preventive work on equipment |
| Meter-driven servicing | Maintenance triggered by reading instead of date | Confirm how meter readings get captured, since that is the weak point |
| Condition at despatch and return | Photographs attached to the contract | Damage recovery depends on evidence instead of recollection |
| Lifetime return per unit | Revenue and cost reporting by serial | The report that should drive fleet decisions |
Two things to press vendors on. Meter capture, because scheduling by hours only works if hours arrive reliably. And the rate boundary test, because a contract that runs six days should not silently price as a week unless you intended it to.
What to Do First
Pull last year’s revenue by individual unit and sort it. Two things fall out immediately: the machines carrying the fleet, and the machines that have not earned since the spring.
Then calculate dollar utilisation on your five largest units. If any of them are returning well under a third of their original cost annually, you have a fleet composition question that no software will answer for you, and knowing it changes the next purchase.
Then time your off-rent gap for a fortnight. Record when the customer actually finished against when the system said so. That number, multiplied out, is usually the largest single item on this page.
Related
- Industrial operations in Edmonton covers the equipment and parts side for businesses that own their machines instead of renting them out
- Shop floor data collection covers capturing what actually happened, which is the same discipline behind meter readings
- Operations software covers the wider category
- Edmonton software planning guide covers sequencing the decision
Frequently Asked Questions
- How do you calculate fleet utilisation rate?
- Two measures, and serious operators track both. Time utilisation is days on rent divided by days available, times 100. Dollar utilisation is annual rental revenue divided by the original cost of the equipment, times 100. Time utilisation tells you whether a unit is moving. Dollar utilisation tells you whether it is earning enough to justify the capital, and it is the one that should drive buy, keep and sell decisions.
- Where does rental margin actually leak?
- In rough order: off-rent recorded late so days are given away, damage not assessed or not recovered, consumables and fuel and delivery not charged, warranty work performed and never claimed back from the manufacturer, assets sitting idle because nobody sees utilisation per unit, and deferred maintenance causing mid-rental failure that costs a replacement unit.
- Why does late off-rent matter so much?
- Because it is silent and it recurs on every contract. Every day between a customer actually finishing with a machine and you recording it off rent is a day you could have billed or re-rented, and no report will ever show it, because those days were never billed in the first place. It is the one thing to configure and rehearse before go-live.
- Should rental units be tracked as inventory or as assets?
- As individual assets. Fleet management is asset accounting more than inventory management, because each unit has its own revenue, cost, condition and service history. That means serialised tracking with the history attached to the serial number instead of to the model, so a decision about one machine can be made on that machine's record.
- How do rental rate structures work in a system?
- Daily, weekly and monthly rates that deliberately do not scale linearly, plus minimums and off-rent timing rules. These are modelled as pricelists with duration rules. The test worth running in any demo is a rental that crosses a rate boundary, because that is where configurations quietly produce the wrong number.