Scope: an operational guide, not legal advice. Your own hire terms govern your contracts, and they vary. Check what is actually incorporated before relying on anything here.

Two things cost hire businesses more than almost anything else on the operational side, and neither appears as a line in the accounts.

The first is hire that stops earning before it should, because a customer said “that’s finished” on a phone call and somebody wrote it on a pad. The second is damage that gets absorbed, because when the customer pushes back nobody can prove the machine left in a different condition to the one it came back in.

Both are evidence problems. Both are decided long before the argument starts.

Know what your own terms say, then build the process around them

Most UK plant hire runs on the Construction Plant-hire Association’s Model Conditions, often with supplementary conditions bolted on, and larger contractors frequently negotiate amendments. Outside the UK none of that applies and you will be working to your own terms or local practice.[1]

So the first job is not learning a template. It is knowing three things about the terms you actually issue:

  1. What defines the start and end of the hire period. Depot to depot is common, which means transit time and time sitting on site over a weekend are usually chargeable. Whatever yours says, it is the definition your invoices have to match.
  2. Who carries risk for loss, theft and damage during the hire, and what happens to charging while a settlement is agreed.
  3. What notice is required for collection, and what happens if the item is not made available within it.

Write those three answers down and give them to the hire desk. Half of all off-hire disputes are people arguing from different assumptions about the same contract.

Everything after this point is true regardless of which terms you use.

The hire period is whatever your records can evidence

If your dispatch time comes from a scanned movement and your return time comes from a scanned receipt at the depot, the hire period is a fact.

If either comes from memory, a text message or a delivery note in a van, it is a negotiation. And in a negotiation the customer’s version is free, while yours costs you the time to argue it.

Practical rule: two timestamps bracket every hire. If you cannot produce both from a system, you do not have a hire period, you have a position.

Off-hire is a process, not a phone call

The failure pattern is always the same. A site foreman rings on a Thursday afternoon and says the machine is done. Nobody records it against the contract. Collection happens the following Tuesday. The customer expects charging to stop on Thursday, the invoice says otherwise, and you are arguing about five days on an invoice worth less than the time the argument will take.

Three things fix it.

Acknowledge in writing, with a time. Every off-hire request gets confirmed against the contract, with the time it was received and a reference the customer can quote back. That single artefact ends most of these disputes before they start.

State what happens next. Under most terms the off-hire request and the end of charging are not the same event. Say when charging stops and on what condition, at the point the request comes in rather than on the invoice six weeks later.

Record availability for collection. If your terms require notice and the item then is not accessible, that matters. A closed site, a locked compound or plant buried behind a stack of materials is a fact worth recording with a photograph and a time, because it is usually what decides who carries the following week.

What a defensible recharge needs

A damage recharge is an assertion that an item left in one condition and came back in another. It stands or falls on being able to show both ends.

ElementWhat it provesHow it usually fails
Dated dispatch condition record, per assetThe state the item left inOne form covering a mixed load of eight items
Timestamped photographs at dispatchPre-existing damage, specificallyPhotos in a WhatsApp thread with no asset reference
Signature at handoverWho accepted the item, and whenSign-off collected days later, or never
Dated return condition recordThe state it came back inChecked in as available before anyone looked at it
Named person at both endsWho to ask when it is queried“The yard”
Repair quote or invoiceThe amount claimedA round number with nothing behind it
Link to booking and customerThat this is the right contractEvidence filed by date rather than by asset

The pattern down that right-hand column is not carelessness. It is what happens when evidence is captured somewhere other than on the movement it describes.

The five reasons recharges fail

Only one of them is about the damage.

No dispatch baseline. The most common by a distance. You can show the item is damaged. You cannot show it was not damaged when it went out.

Aggregated condition records. A multi-asset booking with a single condition form. The customer accepts that the load was broadly fine and disputes one specific item, and the record cannot separate them.

The item went straight back to available. A return scan that moves an asset from on hire to available with no checked state in between destroys the return-side evidence before anyone has looked at the machine. This is why the returns control point is a commercial control, not just an operational one.

Evidence that cannot be assembled quickly. A charge queried eleven weeks later, with photographs on a phone belonging to a driver who has since left. If it takes three days to pull together, the commercial instinct is to write it off, and everyone learns that queries work.

No owner and no deadline. Disputes with neither drift until they are too old to pursue.

Cause matters, so record it

Where an item comes back damaged, the conversation usually turns on how it happened. Misuse, wrong fuel, an unsuitable site, theft from a compound and ordinary mechanical failure sit very differently under most terms.

That means the record has to support a view on cause, not just a view on condition.

A defect the customer reported on day three with a photograph is a different conversation to a defect discovered at return with no history behind it. Breakdown reporting is worth formalising for the same reason: get it in writing, timestamped, against the contract, because most terms treat the point of written notification as the point that counts.

The recharge pack

When a charge is queried, what goes back should take minutes to assemble:

  • the asset, by serial number, and the contract it was on
  • dispatch date, time, and who released it
  • dispatch condition record and photographs
  • the signature captured at handover
  • return date, time, and who received it
  • return condition record and photographs
  • the specific difference being claimed
  • the repair cost, with the quote or invoice behind it

If you cannot produce that inside a working day, the recharge is worth less than the number on the invoice, whatever its merits.

How Equipy fits: Equipy captures condition, photographs, notes and signatures against the movement rather than the day, keeps them attached to the asset and the booking, and holds returns in a checked state so nothing goes back out before someone has looked at it. It will not win an argument for you. It means the argument is about the damage rather than about whether you can prove anything at all.

Frequently asked questions

When does the hire period end?

Whatever your terms say, which for most UK plant hire is when the item is received back at the owner’s depot or another agreed location rather than when the customer stops using it. Check the terms actually incorporated in your contract, then make sure your invoicing matches them.

Does an off-hire phone call stop the charge?

Usually not on its own. Treat the request as the start of a process: acknowledge it in writing with a time, state when charging stops and on what condition, and record when the item was made available for collection.

What evidence is strongest in a damage dispute?

A dated, asset-linked condition record with photographs at both dispatch and return, signed by a named person and tied to the booking. The dispatch side is the half most often missing and the half that decides the outcome.

Why do multi-item bookings cause so many disputes?

Because condition is usually recorded once for the load. Record it per asset and one completed form cannot hide five undocumented items.

How long should condition evidence be kept?

Long enough to cover your dispute and limitation exposure, which is longer than most people assume. Keeping it attached to the asset rather than in dated folders makes long retention cheap.

Can we recharge for cleaning and missing accessories?

Only if your terms provide for it and you can evidence the state at both ends. Accessories are where per-asset recording earns its keep, because a load-level form will not show that two of six buckets came back.

Does any of this apply outside the UK?

The contract detail does not. The evidence principle does. A recharge in Dubai fails for the same reason it fails in Leeds: no dated, asset-linked record of the condition the item left in.

References

  1. Construction Plant-hire Association, “CPA Hire Conditions.”