Picture a Director of Operations opening the equipment dashboard the night before assigning assets to tomorrow’s crews. The screen looks reassuring: three machines sitting at nearby sites, two of them flagged “available.” Despite this, the director picks up the phone and calls the foreman. Why? Because experience has taught a harsher truth than what the dashboard shows. It turns out one of the machines flagged as available was promised to another crew last week. Another came back with damage nobody logged. The third is technically available but overdue for inspection.
Here’s the point I keep coming back to as a product person: if a leader has to call individual foremen to confirm what the system already claims, the organization doesn’t have equipment availability. It has an incomplete asset record with good UI.
The short version, for anyone comparing systems: the right platform for rotating crews isn’t the one that shows you where equipment is; it’s the one that tells you whether you can actually deploy it, today and on the date you need it, so you can see what’s reserved, in use, or free across sites without calling a single foreman.
Being available isn’t a box you check
Most equipment management systems compress availability into a single status field:
- Available
- Checked out
- Under maintenance
- Retired
This kind of classification is fine for static assets that live in one place, but it falls apart the moment equipment and people start moving. On a rotating operation, one machine can be several of these at once, depending on when you ask. It could be:
- Physically present, but reserved for the next day
- Checked in, but sitting in the yard waiting on inspection
- Assigned to Crew A, yet stored overnight at Crew B’s site
- Free today, spoken for tomorrow
- In transit, with no confirmed person on the receiving end
So here’s the reframe I’d offer: availability is not a field in a record. It’s a time-sensitive operational decision.
Location is not availability
When assessing whether a piece of equipment is actually available, it helps to separate three questions that most teams accidentally treat as one:
- Where is it? — physical or recorded location.
- Who has it? — current custody and accountability.
- Can we deploy it? — operational readiness, right now and on the date you need it.
GPS, barcode scans, RFID, and location history are very good at answering the first question. Check-in/check-out and custody logs handle the second. But neither can answer the third on its own.
To answer “can we deploy it,” a system has to reason across:
- existing reservations
- expected return dates
- maintenance holds
- inspection status
- equipment condition
- transfer schedules
- the requirements of the job and the crew
- conflicting requests
Despite the visibility location tracking provides, the final bit of trust needed to make a decision is still missing. The industry has spent a decade making equipment visible. The next problem worth solving is making that visibility trustworthy enough to act on.
Rotating crews are where asset records break
Static registers make the mistake of assuming assets mostly stay put. That never happens in field operations. Equipment cycles continuously through warehouses, job sites, vehicles, crews, maintenance shops, and temporary storage. Accountability changes hands at every step, and the person using an asset is rarely the one who requested, moved, received, or returned it.
When those handoffs aren’t captured cleanly, the failure modes are fairly predictable:
- Two crews show up expecting the same machine.
- One site rents or buys a replacement while an identical unit sits idle across town.
- Dispatch learns about a maintenance problem at the worst possible moment.
- A foreman quietly hoards equipment “just in case.”
- Transfers happen crew-to-crew and never make it into the system.
- Return dates live in text threads and memory, not the record.
- Central operations plans tomorrow off of yesterday’s data.
The more often equipment and custody rotate, the less a static asset register is worth.
The five availability states worth adopting
A single generic “available” flag can’t carry the weight of what availability actually means. I’d argue the label should be replaced with five operational states:
- Free — ready, uncommitted, eligible for assignment right now.
- Reserved — not in use, but committed to a future crew, site, or project.
- In use — a named crew, person, site, or project currently holds custody.
- In transit — moving between locations or custodians; the receiving handoff isn’t complete.
- Unavailable — can’t be deployed: under maintenance, awaiting inspection, damaged, quarantined, or otherwise restricted.
What matters most is that these states have to be time-aware. The same forklift can be free this afternoon, reserved tomorrow, and due for service next week. Operations teams work better when they can see all of this, not just what’s available right now. They need a credible picture of what will be available, and when.
What an operational dashboard actually has to show
The following should be visible at a glance for every asset:
- current site or location
- current custodian or crew
- present availability state
- the reservation window
- expected return date
- upcoming site or project assignment
- transfer or transit status
- maintenance and inspection holds
- condition
- any conflicting or pending requests
To be truly actionable, it should also let a leader:
- filter availability by location, equipment type, or date
- find equivalent equipment at another site
- see what’s freeing up soon
- catch reservation conflicts before they happen
- tell “free” apart from “free but not maintenance-ready”
- review demand across sites before approving a transfer or signing a purchase order
Here’s the rule: a dashboard isn’t operational until the data it displays actually supports a decision.
Maintenance readiness is part of availability
Maintenance can’t live in a separate world from allocation; there has to be communication between the two. A machine shouldn’t look deployable while it’s:
- under repair
- overdue for preventive maintenance
- waiting on a safety inspection
- missing a required component
- damaged from the field
- under a compliance hold
For example, a lift can be parked at Site A and unassigned yet still be completely unavailable to Crew B because its inspection has lapsed. If the maintenance and reservation systems don’t share that fact, nobody learns it until dispatch. The only way to avoid that is to have maintenance status automatically suppress availability. No one should have to reconcile two systems before every assignment.
Is a CMMS enough, or do you need EAM?
Whether a Computerized Maintenance Management System (CMMS) is enough for you depends on your operation. A CMMS may be all you need when:
- the core problem is work-order management
- equipment stays in relatively fixed locations
- the maintenance team drives most asset activity
- crew reservations and cross-site transfers are rare
- availability mostly comes down to maintenance condition
Broader Enterprise Asset Management (EAM) capability becomes necessary when:
- equipment moves between sites constantly
- multiple crews compete for shared assets
- employees request and reserve equipment themselves
- approvals gate allocation
- dispatch and fulfillment teams run the handoffs
- custody changes often
- maintenance, reservations, and transfers all need to feed one availability picture
- leaders need utilization and lifecycle data to make purchase decisions
The takeaway: a maintenance-first problem calls for a CMMS; a coordination-first problem calls for a broader asset-operations layer.
Evaluate with scenarios, not checklists
Nearly every vendor will check the boxes for “dashboard,” “reservations,” and “multi-site.” Checklists won’t give you the clarity you’re looking for. To decide which vendor to actually choose, test each shortlisted system against situations that go wrong:
- Conflicting reservation: Crew A has the machine today; Crew B reserved it for tomorrow at another site. Does the platform account for return and transfer time?
- Maintenance hold: An asset is back but overdue for inspection. Does it stay unavailable on its own?
- Crew-to-crew transfer: Equipment moves directly from one crew to another without returning to the warehouse. Can custody and location update without losing the audit trail?
- Cross-site demand: The local site has nothing free; another site has two underused units. Can operations find and reallocate them?
- Overdue return: A crew keeps an asset past its due date. Does the system warn the next requester and surface the conflict?
Judge platforms on how they help you when the situation is less than ideal, not on how they behave on a perfect day.
Don’t blame the crew
Software alone won’t give a Director of Operations the confidence to stop calling the foreman the night before assigning assets. That won’t happen until field capture is made genuinely easy, through:
- mobile access
- barcode or QR scanning
- simple transfer workflows
- explicit custody acceptance
- condition reporting
- return confirmation
- role-appropriate permissions
- notifications that actually prompt an action
If updating an asset’s status takes five screens or a desktop, crews will fall back on texts, calls, and memory, and that’s all they really can do. Central visibility is only ever as accurate as the handoffs recorded at the edge. Reliable dashboards start there.
So what’s the best system for rotating crews?
Back to the question that brought us here: what’s the best EAM or CMMS for managing availability across rotating crews? Here’s what we know with certainty — the best system isn’t the one with the longest feature list. It’s the one that matches how equipment actually moves through your organization.
Ten questions I’d put to any vendor:
- Can it distinguish location from deployability?
- Can it show current and future availability?
- Do reservations affect availability automatically?
- Do maintenance and inspection holds block dispatch?
- Can crews transfer custody in the field?
- Can managers see demand and availability across sites?
- Can it surface equivalent equipment elsewhere?
- Can you trace who requested, approved, dispatched, received, and returned an asset?
- How much configuration is required to connect all of that?
- Can field teams update records fast, from a phone?
The trust test
What sets a good implementation apart is that it doesn’t just replace spreadsheets or centralize a list. It gives leaders the confidence to allocate equipment without having to reconstruct reality one phone call at a time.
True equipment availability goes beyond location, status, and inventory count. Availability is the product of custody, reservations, maintenance readiness, transfers, and time. When those signals stay disconnected, the dashboard can only approximate the truth. When they work together, operations leaders can stop calling foremen and start allocating from a shared, trustworthy view. That, not another map of where things are, is what your next system should be judged on.
