Renting equipment: availability is the only number that matters

An equipment rental business is a calendar with a workshop attached. The number that runs it is not what sits in the yard; it is whether one specific item can go out on the 14th and be back on the 19th. Two promises on one item are a quantity problem only in the moment they are made — after that they are an argument, and only the calendar prevents it.

Why is availability a calendar rather than a quantity?

Because "we have twelve" and "eleven are out until Thursday" are different answers, and only the second can be given to a customer. A quantity says how much exists; a calendar says when each unit is free.

So the record is the individual unit, serialised, with a state for every date range it occupies: out on a contract, in the yard, in maintenance, reserved, written off. Twelve units are twelve rows, not one row with a twelve in it. Collapse them into a count and the system states a total and cannot answer a booking.

The units are not interchangeable either: same model, different wear, and the customer who rented the good one last time will ask for it again.

What are the two states nobody models?

Out, and out-and-damaged. The second one is the failure: an item returned with a bent frame gets marked "in", and its state is now a lie that the next booking will act on.

The return has to end in one of three places, and someone has to choose: back in service and bookable; in assessment or repair, with an owner and a promised date; or written off with a reason. While it sits in assessment it must be unbookable, or it goes out again and comes back worse — which is how a fleet dies quietly, one optimistic return at a time.

Why is a deposit an accounting event and not a note?

Because the money moves twice and only the first move gets recorded. A deposit is not income; it is money held, returned later or applied against damage, and each outcome is a document.

Applied means a recorded decision: what the damage was, what assessment cost, what was withheld, who decided. Returned means a payment out with a method, a date and its own number — not the reversal of a note in a margin. A business that tracks deposits in a notebook can answer "did they pay" and cannot answer "did we give it back".

The customer's copy matters as much as the ledger line: a receipt for the deposit and for its return ends most disputes at the counter.

What must the hand-over record capture?

The condition at the moment it leaves, because the argument always happens weeks later, when the item is back and nobody remembers how it was. Photos with a timestamp, a short checklist per item type, and a signature from the person taking it.

The checklist is what makes the photos usable: six to ten lines per type — housing, cable, blade, tyre, guard, accessories, fuel — pass or fail, plus one free-text field. A checklist without photos is an opinion; photos without a checklist, files nobody reads.

Use the same form at hand-out and hand-in. The comparison is the point: a fail that was not a fail on the way out is the damage.

What else has to block availability?

Maintenance, and everything that behaves like it. A service window has to occupy the calendar the way a booking does, or the diary promises an item that is in the workshop and the workshop takes the blame. Cleaning, calibration, a safety inspection and transport count too: an item that leaves at 07:00 for a site three hours away is not available at 07:00.

Keep the workshop queue and the rental calendar on the same unit record. Two lists that know about the same machine will disagree, and the disagreement surfaces as a customer in the yard.

When do you write an item off?

When the repair, the downtime and the chance it comes back again are worth more than keeping it — and the decision needs a record either way: the assessment, the estimate, who decided, the date, what became of the item. Scrapped, sold for parts or cannibalised for spares are three endings with three effects on the count.

Without that record a write-off is a hole in the count that looks like theft, and the next physical count spends a day on an item scrapped on purpose.

Question	A stock system	A rental calendar
Can it go out on the 14th?	Maybe; it counts stock	Yes or no, per unit
What is happening to it now?	Nothing	Out, in, repair, reserved
Is the deposit back?	A note	A payment, with a number
Who had it when it broke?	A customer name	A contract, photos, a signature
Why is it gone?	A missing row	A write-off, with a reason

What should be settled before you choose a system?

1. Number every unit with its serial and purchase date. Anything not individually identified will never be bookable.
2. Draw one week for your busiest model: who has what, when it returns, what is in the workshop.
3. Add the maintenance windows to that week and count the promises that break. That count is the requirement.
4. Write the checklist for your two most-rented item types, six lines each, and try it on a real hand-over.
5. Follow one deposit from receipt to return, and write down every document it should produce along the way.
6. Decide who may write off an item, and what they attach to it.
7. Only then compare products. Ask each one to show a return with damage, not a fresh booking.

Where this goes wrong

• Items stay a quantity. The system counts twelve, the yard has nine, and the gap is discovered by a customer.
• "Returned" is one button. Damage is discovered at the next hand-out, by the next customer, who is now the one complaining.
• The deposit lives in a notebook. It is taken, remembered, and returned in cash with no line anywhere.
• Photos live on someone's phone. They exist until the phone is replaced, which is before the argument.
• Maintenance is a separate list. The calendar promises a machine the workshop has had for a week.
• Write-offs are silent deletions. The item vanishes from stock and the next count treats it as a loss.

What this does not cover

This is about the record around a rented item: the calendar, the condition, the deposit and the end of its life. It does not touch contract wording, liability, insurance or what a deposit may legally be applied to — that is a lawyer's text, and no software decision substitutes for it. It quotes no prices, because rental rates age faster than anything else in this article. It also assumes one yard; several depots turn every promise into a transport question this does not settle.

We build rental systems around the unit and its calendar — availability, condition at hand-over, deposits that are accounting events, maintenance that blocks, and write-offs with a reason.