The booking screen says a machine is available on Monday. The workshop knows it is waiting for a part. Its inspection record expires during the proposed hire. Transport cannot collect it from the current site in time, and the requested attachment is already committed elsewhere.
Each system contains a reasonable answer. The operation still cannot fulfil the booking.
Plant, powered access equipment, lifting equipment, and small tools do not share one universal workflow. Each hire business needs its own evidence-backed definition of availability across safety, condition, configuration, location, and time. A single yes or no field cannot carry that meaning.
A dependable answer needs a connected operational system. It must combine booking, workshop, inspection, transport, and customer records, then show staff exactly what prevents a hire from being fulfilled.
Replace the available flag with real states
Availability is the outcome of several facts. Treat it as a calculated decision for a period and use case rather than a status someone remembers to update.
Useful asset states may include:
- Reserved for a confirmed hire.
- On hire or awaiting collection.
- Returned and awaiting check.
- Quarantined after damage or a reported fault.
- In workshop or waiting for a part.
- Ready for hire with current evidence.
- Unavailable for the requested use or location.
The exact states should match the operation. More detail is useful only when it changes responsibility or action.
For each transition, define the event, required evidence, and accountable role. A return scan may move an asset to "awaiting check". A completed check with no blocking defect can move it to "ready". A competent examination or repair may be required for another asset.
The booking service then asks whether the specific asset, attachment, and evidence are suitable for the proposed dates. It should explain any blocker and offer a safe alternative where possible.
Make evidence travel with the asset
The HSE guidance on inspection of work equipment says inspection records can be electronic, must be held securely, and should be available to enforcing authorities. Equipment that leaves an undertaking or comes from a hire company should carry physical evidence of the last inspection where inspection is required.
The operational record should connect:
- Asset identity and serial number.
- Current location and custodian.
- Required inspections or examinations.
- The latest valid evidence and next due date.
- Open defects, restrictions, and repairs.
- Attachments and configuration.
- Hire, return, and transport events.
Do not copy an inspection expiry date into several systems and hope they stay aligned. Keep one authoritative record and let booking, workshop, and customer documents read it.
Evidence should be protected from casual alteration. Record who added it, when it became valid, which asset it covers, and whether a later event has superseded it.
HSE's PUWER overview makes clear that businesses providing work equipment for hire have responsibilities for suitability, safe condition, maintenance, inspection, information, and training. Software should make those controls easier to follow and evidence.
Turn defects into blockers
A defect written in a free-text note is easy to miss when the next booking is made.
Capture the observation, asset, time, reporter, photos, operating conditions, and immediate action. Then route the decision to someone competent to assess what it means.
The outcome may:
- Quarantine the asset immediately.
- Restrict a particular use.
- Require a repair before further hire.
- Create a planned action while use continues.
- Close the report with an explanation.
For lifting equipment, HSE's LOLER guidance states that a dangerous defect must be reported and the equipment must not be used until it is remedied. The system needs a hard booking block that only the defined evidence and authority can remove.
Avoid a generic override available to every depot manager. If the business permits an override for a non-safety operational blocker, record the reason, person, time, and scope. Safety controls should follow the competent decision and applicable law.
The same defect event should be visible to booking, workshop, transport, and customer service without each team keeping its own note.
Use AI for assistance around unstructured evidence
Returns create photos, handwritten comments, emails, and varied descriptions. AI can help organise this material.
It may:
- Suggest an asset or component from a note.
- Classify the apparent area of damage.
- Group similar descriptions for workshop triage.
- Compare return photos with checkout photos for review.
- Draft a customer query or internal summary.
These are proposals. A model cannot confirm mechanical condition, perform an examination, establish competence, or decide that equipment is safe.
Photo conditions also vary. Dirt, lighting, angle, previous repairs, and hidden damage limit what an image can show. Keep the original evidence and route uncertain or consequential results to a competent person.
Use ordinary rules for examination dates, booking conflicts, required fields, and authorised state changes. Use AI where interpretation of text or images saves time without weakening the control.
Measure whether the assistance reduces workshop triage time and missed context. Do not judge it by the confidence or fluency of its description.
Start with the unavailable asset report
Most hire businesses already have evidence of the gap. It appears in substitutions, delayed deliveries, workshop calls, credits, and assets that looked free in the booking system.
Take a month of cases where a reserved asset could not fulfil the hire. Classify the reason:
- Inspection or examination.
- Defect or damage.
- Cleaning or preparation.
- Attachment or configuration.
- Location or transport.
- Late return.
- Incorrect master data.
- Unrecorded workshop work.
Then trace when the blocking fact first became known and when booking could see it. The delay identifies the integration or workflow worth fixing.
Start with one asset class at one depot. Define its states, evidence, transitions, and booking rules with the people who check, repair, allocate, and transport it. Connect only the systems needed to make that first availability decision dependable.
The result should answer a practical question: which asset can fulfil this hire safely, with the right evidence, at the promised place and time?
This is the kind of operational system ORBN can help design and build. We work with the people who allocate, inspect, repair, and move the equipment, connect the software they already use, and build the missing workflow where packaged products stop short.
If "available" still starts a round of phone calls before a booking can be promised, bring us a month of substitutions and delayed hires. We can trace where the facts diverge and identify the smallest useful first release.