Ready-mix concrete's higher cost compared to site-mixed concrete is frequently justified purely on convenience and schedule grounds, but the batch-to-batch consistency argument is equally real and considerably under-emphasised in that typical cost-justification conversation.
| Method | Typical batch-to-batch strength variance | Primary consistency driver |
|---|---|---|
| Site-mixed concrete | Higher variance - commonly a wider spread across batches | Manual batching control (volumetric rather than weight-based dosing common on smaller sites), variable operator diligence, less rigorous moisture correction for aggregate |
| Ready-mix concrete (RMC) | Lower variance - tighter, more consistent spread | Weight-batched, computer-controlled dosing at the plant, consistent quality control processes, and typically better raw material sourcing consistency |
Why the Consistency Gap Matters Beyond the Average Strength Figure
A concrete supply exhibiting high batch-to-batch variance requires a higher target mean strength to reliably achieve the specified characteristic strength across all batches, following standard statistical mix design margin requirements - which means inconsistency has a direct, quantifiable cost implication through cement over-specification, not merely a general quality-perception concern that could be dismissed as abstract. RMC's consistency advantage becomes most valuable specifically on projects requiring predictable, genuinely uniform structural performance across large pour volumes, where batch-to-batch variability compounds into real structural design margin concerns that a smaller, less critical pour would be less exposed to.
A Scenario Showing Where Site-Mix Remains a Perfectly Reasonable Choice
Picture a smaller project pouring a modest quantity of concrete for non-critical elements, where the batching plant maintains reasonable discipline through weight-based (rather than purely volumetric) dosing even without RMC's full computer-controlled infrastructure. In this context, site-mix remains genuinely cost-effective and appropriate, since the consistency premium RMC offers isn't proportionally as valuable when the pour volume is modest and the structural criticality of the specific elements being poured is comparatively lower - the decision to use RMC versus site-mix should track the project's actual scale and structural criticality, not default reflexively to whichever option seems more "modern" regardless of whether the premium is actually earning its keep for that specific project.
Why Code Compliance Doesn't Automatically Mean Equivalent Real-World Consistency
Site-mixed concrete can genuinely meet the same IS code strength requirements as RMC when properly controlled, since the code doesn't distinguish between the two mixing methods by requirement - but the practical consistency actually achieved in real-world execution differs meaningfully between them, which is a distinction worth being clear about rather than assuming code compliance alone guarantees equivalent real-world batch-to-batch reliability between the two approaches.