Skip to content
    // Operations · 18 Apr 2026

    Reading a batch ticket: 7 things every site engineer should check

    A batch ticket is a contract, not a delivery slip. Here's the 30-second checklist that catches 90% of disputes.

    The ticket is the contract

    Most site engineers glance at the truck number and the grade. The other 18 fields on a batch ticket are where every dispute is won or lost.

    The 7 fields that matter

    1. Plant ID + batch time — fixes the chain of custody
    2. Grade and design mix code — must match your PO
    3. Cement type and quantity — verify against approved mix design
    4. W/C ratio (calculated) — single biggest predictor of site performance
    5. Admixture dosage — under-dosed retarder = early stiffening
    6. Departure time + km from plant — drives slump-loss compensation
    7. Driver signature + QC approval — the legal anchor
    Sample ticket header
    TKT-2026-04-09812
    Plant: ALP-EAST-02
    Batch time: 09:42 IST
    Grade: M40 PUMP
    Design code: ALP-M40-PMP-V3
    

    "If your ticket doesn't have a QC signature, you didn't receive concrete — you received a slurry."

    What to do at site

    • Photograph every ticket on arrival
    • Cross-check slump within 5 minutes of unloading
    • Reject any truck with a transit time > 90 minutes
    • File tickets by pour, not by date

    Ut enim ad minim veniam.

    Tagged
    operationsbatch ticketssite practice
    // Subscribe

    Field Notes, in your inbox.

    Engineering write-ups and operating data from real pours. Roughly twice a month. Unsubscribe in one click.

    // Your privacy

    We use cookies to make this site work better.

    Essential cookies are always on. Analytics and marketing cookies are off by default — turn them on if you'd like to help us improve. See our Cookie Policy and Privacy Policy.