Concrete Delivery Docket Control

Definition

A concrete delivery docket — also called a delivery ticket or batch ticket — is the printed record that accompanies every truck of ready-mixed concrete from the batching plant to the site. It carries the mix reference, cube strength class, slump, workability, water content, admixtures, batch time, truck number and volume. Docket control is the site process that checks each ticket against the specification, records it, and archives it as evidence for the life of the structure.

Why It Matters

Concrete is the one material you cannot inspect after the fact. Once it is placed and cured, the only proof that the right mix went in is the delivery docket and the cube results. Missing or unchecked dockets create a permanent gap in the evidence chain. That gap surfaces years later — during a dispute, an insurance investigation, a structural upgrade, or a criminal inquiry after a failure. There is no reconstructing a docket from memory.

What a Docket Must Show

• Producer name and plant reference.
• Truck number and driver signature.
• Date, time of batching, and time of arrival on site.
• Mix reference and specification (e.g. C32/40 XC4 XF3 CIIIA 32 S3).
• Nominal maximum aggregate size.
• Volume delivered (m³).
• Water added at plant and, critically, any water added on site — with signature.
• Admixture types and doses.
• Chloride and sulfate class where relevant.

Real-World Example

On a bridge deck pour in southern Spain, cube results at 28 days came back at 32 MPa against a specified 40 MPa. The client froze payment and instructed core drilling. The contractor's site engineer produced the docket archive: every one of the 42 trucks had a signed ticket, plant slump matched on-site slump, no water added on site, admixture doses correct. The plant records showed one batch had used cement from a suspect silo. The producer accepted liability, replaced the deck section at their cost, and the contractor kept their reputation. Without the docket discipline, the argument would have collapsed the other way.

How to Run It Properly

1. Nominate a docket controller for every pour — usually the site engineer or a trained concrete supervisor.
2. Check every ticket at the gate before the truck reaches the pour: mix reference, batch time, slump class.
3. Time-stamp arrival — most codes require concrete to be placed within 90 to 120 minutes of batching depending on ambient temperature.
4. Perform on-site slump test on the first, middle and any suspect truck, and record the result on the docket.
5. Refuse and reject any load outside spec — with a written reason on the docket and a photograph.
6. Log all cube samples against the docket number, so a later cube failure traces back to a specific truck.
7. Scan and archive every signed docket to the project document management system by end of shift.

Practical Lessons Learned

• Never sign a blank docket. Drivers occasionally hand over a ticket with the "water added on site" field empty. Fill it in yourself — zero if none.
• Watch the pour rate versus the batching interval. If trucks are queuing longer than the maximum retention time, you are pouring stale concrete regardless of what the ticket says.
• Match dockets to cubes. Cube numbers should reference truck numbers so a failed cube can be traced.
• Physical dockets get lost. Photograph each docket the moment you sign it. The phone image is your backup.
• Reject cheerfully. A polite, documented rejection of a bad load costs a driver an hour. Accepting it costs the client a slab.

Expert Tips

• Print a simple pour-day tracker: docket number, arrival time, slump, cube reference, location placed. Fill it in live.
• Colour-code cubes and dockets by pour section so a strength issue maps directly to a physical zone of the structure.
• Randomly cross-check plant tickets against the producer's own batching-plant printout at month-end. Discrepancies point to plant issues before they turn into structural ones.
• On night pours, position the docket controller under a fixed light — legible signatures matter more than heroic gestures.
• Include the docket archive process in the ISO 9001 audit trail; the auditor will thank you.

Common Mistakes

• Docket controller absent during peak pour, so unchecked trucks discharge under time pressure.
• Water added on site to improve pumpability, unrecorded — a specification breach that voids the mix design.
• Dockets stored in a cardboard box in a site cabin, destroyed in the first winter storm.
• No cube reference on the docket, so a cube failure cannot be traced to a truck or location.
• Producer's paper dockets not backed up digitally; when the producer changes hands, the historical records vanish.

Key Takeaways

• Delivery dockets are the durable evidence of what went into the structure — treat them accordingly.
• Nominate a controller for every pour; unstaffed docket control fails during the busiest twenty minutes.
• Reject non-conforming loads with documented reason and photograph.
• Link every cube result to a docket and a physical location.
• Scan and archive digitally the same day — paper alone will not survive the project.

Related Concepts

Pairs with Concrete Pour Card, Concrete Cube Testing, Non-Conformance Report, and Materials Reconciliation Report.