Concrete Pour Delivery Delay Cold Joint Case Study

A concrete pour is a logistics operation and a materials operation at the same time. The concrete must arrive, be placed, consolidated, finished, protected, and inspected before time, temperature, workability loss, and setting behavior create defects that cannot be corrected by schedule pressure.

This case study follows a foundation slab pour interrupted by ready-mix delivery delays. The field team wants to continue placing concrete when trucks resume. The engineering problem is to decide whether the interruption can be treated as a normal placement delay, whether a cold joint has formed, and what evidence is required before the work can be accepted.

The central question is:

Did the delivery delay create a cold-joint risk that requires stopping, preparing a construction joint, and validating the placed concrete before acceptance?

The case is simplified for education. Real projects must follow the concrete specification, approved method statement, mix design, admixture data, hot- or cold-weather procedure, engineer-of-record direction, testing plan, and contractor quality system.

Case Context

The slab is a reinforced concrete foundation zone for a plant room. The planned pour volume is 120 m^3. The slab thickness is 0.30 m, and the pour is scheduled for one continuous placement using a line pump.

The approved plan assumes:

Item	Planned value
truck capacity	8 m^3
target pump rate	32 m^3/h
planned truck arrival interval	15 min
maximum layer interval at concrete temperature above 28 deg C	60 min
concrete temperature at delivery	30 deg C
ambient temperature	31 deg C
approved retarder	included in mix
engineer hold point	any interruption above 60 min

The first six trucks arrive close to plan. Then a batching-plant dispatch problem and gate congestion create a long gap before truck 7 reaches the pump.

Step 1: Check the Planned Delivery Rate

The planned pump rate is:

Each truck carries:

Required truck arrival rate:

The planned interval between trucks is:

Engineering Comment

The 15-minute interval is not arbitrary. It follows from pump rate and truck capacity. If trucks arrive slower than this, the pump must slow, stop, or place discontinuously. That changes the concrete quality risk.

Step 2: Measure the Actual Interruption

The site log records:

Event	Time
truck 6 discharge completed	10:18
truck 7 arrived at gate	11:37
truck 7 began discharge after slump check	11:50

The interval between completed discharge and resumed discharge is:

Compare with the approved hold point:

The interruption exceeds the hold point by:

Engineering Comment

The hold point is already triggered. The team should not restart placement as if nothing happened. The engineer must decide whether the existing edge is still plastic enough for monolithic continuation or whether it must be treated as a construction joint.

Step 3: Check the Interface Age

The critical concrete at the leading edge was placed before truck 6 finished. Suppose the field log shows that the edge zone was placed at 10:02. Truck 7 begins discharge at 11:50.

Interface age at restart:

The mix supplier reports a laboratory initial set time of 150 min at 23 deg C. For this simplified case, the project hot-weather procedure applies a 20% reduction for the measured 30 deg C concrete temperature:

The interface age margin is:

Engineering Comment

The interface has only a 12-minute screening margin before adjusted initial set. That is not enough to rely on ordinary vibration into the previous layer, especially with hot weather, workability loss, uncertain actual set behavior, and inspection delay. The correct decision is conservative.

Step 4: Estimate the Affected Area

Before the interruption, six trucks were placed:

With a slab thickness of 0.30 m, the placed area is:

If the active placement front is about 12 m wide, the approximate length of slab already placed is:

Engineering Comment

The affected interface is not a small local blemish. It may extend across a wide placement front. That affects inspection, documentation, surface preparation, and any decision to designate a construction joint.

Step 5: Decide Whether to Continue

The field team proposes to restart immediately and vibrate the new concrete against the old edge. The engineer rejects that plan for four reasons:

1. the 60-minute hold point was exceeded;
2. adjusted set screening leaves only a 12-minute margin;
3. the affected front is long enough to require planned joint treatment;
4. ordinary vibration cannot be relied on to restore bond to a stiffened surface.

The directed action is:

• stop the pour at a controlled line;
• mark the affected interface on the drawing;
• protect reinforcement and prevent contamination;
• remove laitance and weak paste after the concrete reaches safe preparation condition;
• roughen, clean, and inspect the surface before restart;
• apply the approved bonding or joint preparation method if specified;
• record the nonconformance and engineer disposition;
• restart only after the construction joint is accepted.

Engineering Comment

This is a quality decision, not a punishment for late trucks. Continuing without joint treatment could hide a weak plane inside the slab. A controlled construction joint is usually more defensible than an accidental cold joint.

Step 6: Risk Priority Before and After Controls

Use a simplified Risk Priority Number:

For an unprepared cold joint in the slab:

• severity S=8 because bond, durability, water migration, and serviceability may be affected;
• occurrence O=4 because the 92-minute delay and hot concrete make the defect plausible;
• detection D=5 because the weak plane may not be obvious after finishing.

Baseline risk:

After stopping, preparing a construction joint, mapping the interface, and adding post-pour inspection, assume:

• occurrence reduces to O=2;
• detection improves to D=2.

Controlled risk:

Engineering Comment

The RPN does not prove the joint is structurally adequate. It shows why the control action is rational: it turns an unplanned hidden defect into a documented joint with preparation and acceptance evidence.

Step 7: Acceptance Evidence

The acceptance plan should include:

• delivery tickets for all trucks, including batch time, arrival time, discharge start, slump, temperature, and water additions;
• pump log showing stop and restart times;
• photographs of the interrupted front before preparation;
• marked drawing showing the joint line;
• engineer disposition of the nonconformance;
• surface preparation inspection record;
• reinforcement condition check before restart;
• post-pour inspection for visible cracking, honeycombing, leakage path, delamination, or surface distress;
• targeted non-destructive testing or cores if the engineer requires verification;
• updated pour report and lessons learned for future logistics planning.

Engineering Comment

The evidence must show both what happened and why the final condition is acceptable. A vague note saying “pour delayed” does not support future asset management, dispute resolution, or engineering review.

Root Cause

The immediate cause was delayed ready-mix delivery. The deeper causes were:

• the gate was shared with unrelated deliveries;
• there was no protected delivery window for concrete trucks;
• truck tracking was not visible to the pour supervisor early enough;
• the contingency plan did not define what to do at 45, 60, and 90 minutes of interruption;
• the quality hold point was known but not embedded in the logistics control board.

This is why concrete placement belongs in construction planning, not only materials testing. The material risk emerged from a logistics failure.

Corrective Actions

For future pours, the contractor changes the method statement:

1. reserve the gate for concrete during critical placement windows;
2. use live truck tracking and a dispatch call threshold at 30 minutes;
3. require engineer notification at 45 minutes without a truck at the pump;
4. stop and prepare a joint if the approved interval is exceeded;
5. define backup pump and truck resources before the pour;
6. include cold-joint risk in the pre-pour briefing;
7. capture delivery, temperature, slump, and pump-stop records in one pour log.

Final Decision

The affected slab zone is accepted only after the accidental interface is converted into a documented construction joint and the engineer accepts the preparation evidence. The original plan to restart and vibrate new concrete into the delayed edge is rejected.

The final disposition is:

Conditional acceptance after joint preparation, engineer inspection, documented restart, and post-pour validation.

The case shows that schedule recovery is not the same as quality recovery. Once a concrete interface has aged beyond the approved placement interval, the engineering decision must protect the finished asset, not the original pour sequence.

Lessons for Engineers

• Concrete logistics should be calculated from pump rate, truck capacity, travel time, and gate constraints.
• Time gaps are material conditions, not just schedule events.
• Hot concrete can reduce working time and shrink the margin before set.
• A hold point must trigger a real engineering decision.
• A controlled construction joint is preferable to an undocumented cold joint.
• Acceptance evidence must include the event timeline, surface preparation, inspection, and final disposition.
• The lessons learned should update the next look-ahead plan and site logistics controls.