How to Track Equipment Availability
The hardest question in a rental yard is also the most common one: can I get a unit out the door today? Answer it wrong and you either turn away a paying job or promise iron that is still bolted down on a customer's site. Most yards answer it from memory, a whiteboard, or a spreadsheet that one person updates when they remember to. This guide breaks availability into the states that actually matter — on-rent, reserved, in-shop, and ready — and shows why a shared board the whole crew can see beats a file that lives on one laptop. The goal is a picture everyone trusts, so the answer at the counter matches the answer in the yard.
The four states every unit lives in
Availability is not a yes-or-no flag. Every unit in your yard sits in one of four states, and confusing them is where double-bookings start. On-rent means the iron is out earning. Reserved means it is promised to a customer for a future window but still physically present. In-shop means it is back but not rentable — waiting on a hydraulic hose, a tire, or a tech who is buried on something else. Ready means it is fueled, inspected, and can roll today. The trap is treating reserved and ready as the same thing because the unit is parked in the same row. A scissor lift sitting in the yard with a reservation tag is not available, and a counter person who does not know that will rent it twice.
Why the spreadsheet quietly fails you
A spreadsheet looks fine until the yard gets busy. The problem is not the columns — it is that only one person can hold the truth at a time. The counter rents a telehandler, the dispatcher loads a different one for a contractor across town, and the shop pulls a third for parts, all before anyone updates the file. By the time the spreadsheet catches up, you have promised the same unit to two jobs. A spreadsheet also cannot tell you why a unit is unavailable or when it comes back. It shows a blank cell where the real answer is "in-shop, waiting on a part, back Thursday." When the picture lives in one file on one laptop, the yard runs on whoever shouted loudest.
What a shared board shows that a file cannot
A shared availability board flips the model: instead of one person updating a file, every action that changes a unit's state updates the board for everyone at once. When dispatch loads a unit, it leaves the ready pool the instant the ticket is written. When a unit checks back in, it lands in-shop or ready based on the inspection, not on someone's memory. The counter, the yard, and the shop all see the same picture, so the answer to "what can I rent today" is the same no matter who you ask. The board should also carry the next free date for reserved and on-rent units, because the second question after "do you have one" is always "when can I get one."
Tying availability to the actual yard, not the plan
The cleanest board still lies if it drifts from the physical yard. Availability is only trustworthy when state changes are tied to events that actually happen: a unit goes on-rent when the ticket is signed, not when someone meant to write it up; it leaves in-shop when the tech closes the work, not when he says he is close. The cheapest way to keep the board honest is to make updating it the same motion as doing the work — check-in feeds inventory, dispatch feeds the load list, the shop feeds the in-shop count. When the board and the gravel match, your counter can quote a contractor with confidence instead of walking out to count units by hand.
Reading utilization off your states
Once availability is broken into states, your utilization picture comes almost for free. The ready pool is the number you are not earning on — iron that is clean, fueled, and sitting. A persistently large ready pool means you bought too much of something or you are losing rentals you could win. A persistently empty ready pool with units stuck in-shop means your bottleneck is the shop, not the fleet. Watch the in-shop count over time: if telehandlers spend more days waiting on parts than out on jobs, the fix is parts stocking, not another purchase. Availability states turn a vague sense of "we're busy" into a real read on where your money is parked.
Key takeaways
Availability has four real states — on-rent, reserved, in-shop, and ready — and treating reserved units as available is the root of most double-bookings.
A spreadsheet fails in a busy yard because only one person holds the truth at a time, and a blank cell cannot say why a unit is down or when it returns.
A shared board updates for everyone the moment dispatch loads a unit or the shop closes a repair, so the counter and the yard always give the same answer.
Tie every state change to a real event — signed ticket, closed work order, completed inspection — so the board matches the gravel instead of the plan.
Your availability states double as a utilization read: a fat ready pool means idle iron, and units stuck in-shop point at a shop bottleneck rather than a fleet shortage.
Related pages
These pages cover the EquipFlow modules, equipment types, and verticals that intersect with the topic above.
Frequently asked questions
“When the board and the actual yard disagree, which one do I trust?”
Trust the gravel, then fix the board the same shift. A mismatch is a symptom, not a rounding error, so walk it back to the action that did not get recorded — a unit loaded without a ticket, a repair closed in the tech's head. Whoever finds the gap corrects the entry and tells the person who missed it, because silent fixes let the same hole reopen. If you are reconciling by hand every morning, that is your sign updating is not yet wired into the work.
“What is the threshold where a fat ready pool in one class actually justifies buying another unit?”
Look at one equipment class at a time, not the yard as a whole. The line to watch is whether that class is hitting empty during your busy stretch and you are turning paying jobs away — that pressure justifies iron. A class that almost never empties does not, no matter how busy the yard feels overall. Track turn-aways by class alongside the ready pool, because a class can be both heavily rented and oversupplied if you bought ahead of real demand.
“Who on the crew owns keeping availability current when everyone is slammed?”
Nobody owns it as a separate job, and that is the point. The moment a person becomes the designated updater, the board waits on them and drifts the instant they step away. Ownership belongs to whoever takes the action — the counter writes the ticket, the yard loads the unit, the tech closes the work. Each motion records itself. If the board only stays current when one specific person is on shift, you have rebuilt the spreadsheet with extra steps.
“A unit runs but has a small defect — does it go ready or in-shop?”
Decide on safety and disclosure, not convenience. If the defect is cosmetic and does not affect operation, it can go ready, but the flaw rides on the unit's record so the counter can disclose it and the customer is not surprised. If it touches safety, capacity, or could strand a contractor on a job, it stays in-shop until fixed. The board should let you mark a unit rentable-with-a-note so you are not forced to choose between hiding a flaw and parking earning iron.
“A customer wants a unit that is on-rent and pushes when I quote the return date — what do I tell them?”
Quote the next free date off the board and treat it as a soft date, not a promise, because a return can slip if the current job runs long or the unit comes back needing shop time. Offer a substitute class if you have one ready, and take their number so you can call the moment it checks in and passes inspection. Never bump a paying renter to chase a louder one — the reservation you already made is the promise that keeps the yard's word good.
See how EquipFlow handles this on a live yard.
Bring your fleet count and a rough sense of your current workflow. Twenty minutes covers the dispatch board live, MSA billing, and an honest answer on fit.
Book a demoStay in the loop
Yard ops notes, once a week.
Operator-written. Covers dispatch, billing, maintenance, and what we ship. No fluff.