25 August 2026 · TechSlideITS
Why your transit mixer fleet feels short when it is not
Most RMC plants that believe they need more mixers actually need shorter trip cycles. The two look identical from the dispatch desk.
When an RMC plant cannot service its orders, the conclusion is usually that the fleet is too small. Sometimes that is true, and buying a mixer is the answer.
More often the fleet is adequate and the trip cycle is long. The difference matters, because one costs several lakhs and the other costs attention.
The trip cycle, broken down
A mixer's cycle is: load → travel out → wait at site → discharge → travel back → wash and turn around.
Only two of those six are genuinely fixed by geography. The rest are variable, and the variable ones are usually where the cycle bloats.
Waiting at site
The largest and most under-measured. A mixer sent to a site that is not ready to pour becomes a very expensive storage vessel, and the concrete is ageing while it waits.
Plants rarely record this because the driver is not paid by the hour and nobody is tracking. Once it is measured, a specific customer or site usually accounts for a disproportionate share — and that is a conversation you can have with evidence.
Loading and turnaround at the plant
Time between a mixer arriving back and leaving again. Washing, queueing behind another mixer, waiting for the next batch to be ready. Individually small, and multiplied by every trip every day.
Travel
Genuinely fixed, mostly. Worth knowing per site so scheduling is realistic rather than optimistic, but not something you can improve much.
Why measuring changes the decision
If your average cycle is four hours and two of those are waiting at site, your effective fleet is half what you paid for. Adding a mixer adds capacity at the same poor efficiency — you buy two hours of waiting along with it.
Cutting site waiting by an hour, across a fleet of six, recovers roughly the capacity of a seventh mixer at no capital cost. That is not a theoretical argument; it is arithmetic on numbers most plants already could collect.
What scheduling against readiness means in practice
The usual pattern is a morning plan: so many cubic metres to so many sites. Mixers dispatch against the plan, and the plan does not know that the third site's pump has not arrived.
Scheduling against confirmed readiness means the dispatch decision is made closer to the event, with the site's actual state considered. It requires a call or a confirmation rather than a system, and it removes a large part of the waiting.
The system's job is to make the consequences visible — which sites consistently keep mixers waiting, and what that costs in trips not made.
What to record
- Departure and return times per trip, per vehicle
- Arrival and discharge-complete at site, so waiting is separable from travel
- Quantity per trip, so cycle time relates to delivered volume
- The site, so patterns can be attributed
Four data points. They are enough to answer whether you need a mixer or need a conversation.
The uncomfortable finding
Plants that measure this usually discover their best customer is also their worst site. High volume, chronic waiting, and nobody had connected the two because the volume made the relationship feel valuable.
It may still be valuable. But it should be a decision made with the cost visible rather than absorbed.
If you want to see trip cycles reported per vehicle and site, see our RMC plant ERP or book a demo.
Frequently asked questions
Measure the trip cycle first — load, travel out, wait at site, discharge, travel back, turnaround. If a large share of the cycle is waiting at site, the fleet is not too small; it is being used at low efficiency, and adding a mixer buys more waiting along with more capacity.
Waiting at site, because mixers are dispatched against a morning plan that does not know whether the site is actually ready to pour. It is also the least measured, since nobody is tracking driver hours — so it stays invisible until someone records arrival and discharge times separately.
Departure and return times per vehicle, arrival and discharge-complete times at site so waiting is separable from travel, quantity delivered, and the site. Four data points are enough to tell whether the answer is a new mixer or a conversation with a customer.
It is simple arithmetic on your own numbers. If the average cycle is four hours and two are spent waiting, effective fleet capacity is roughly half. Cutting an hour of waiting across a fleet of six recovers something close to a seventh mixer without any capital spend.
Making the dispatch decision closer to the event, based on the site's actual state rather than a plan made that morning. It usually requires a confirmation call rather than software. The system's role is to show which sites consistently keep mixers waiting and what that costs in trips not made.