Resolve demand to one eligible unit
Record the requested equipment type and period, then identify the serialised unit only after reservation conflicts, serviceability, location and any existing hold have been reviewed.
Workflow blueprint
Equipment rental software that separates presence from availability
A custody-control blueprint for teams that need to know which exact unit may leave, who accepted it, what came back, and why it may still be unavailable.
Connect customer records, serialised equipment, condition evidence and commercial references without claiming a booking marketplace, dispatch engine, telematics system or tax platform.
TL;DR — Connect customer records, serialised equipment, condition evidence and commercial references without claiming a booking marketplace, dispatch engine, telematics system or tax platform.
Evidence the release condition
Capture meter or usage reading, photographs, accessories, inspection reference, customer site, responsible employee and customer acknowledgement before custody changes.
Watch custody and expected return
Keep the due-back time, extension decision, customer contact and active commercial document visible without marking the unit physically returned from a phone promise.
Inspect the return before release
Create a separate return event for condition, missing accessories, new damage, usage and customer response, then require named review of any repair or maintenance hold.
Page-specific decision aid
An availability-to-return custody board
The board follows one electric scissor lift from a dated request to a resolved serial number, issue photographs, charger handover, customer custody and due-back watch. The return records new guardrail damage and a missing charger, so physical presence opens a review instead of making the lift rentable again.
- ✓At the depot does not mean available for hire.
- ✓A return event cannot overwrite the signed issue condition.
- ✓Only a named review can remove the maintenance hold.
Scope first
What Codeblix would confirm before implementation
This page is an operational blueprint. The final workflow, screens, permissions and integrations depend on your current process and agreed implementation scope.
- ✓Equipment type and serialised unit identity stored separately
- ✓Reservation evidence never treated as proof of physical issue
- ✓Issue and return condition events retain their own observations
- ✓Booking optimisation, dispatch, telemetry, payments and tax treatment excluded
Relevant Codeblix foundations
Review the existing product areas that support the proposed workflow.
Use the related planning tools
Run the operational calculation, save the result in the URL and share it with your team.
Map this workflow to your operation
Tell Codeblix how work moves today. We will confirm the practical scope before proposing an implementation.
Discuss your workflow