Codes referenced
Immediately before discharge, producer provides a preprinted ticket with the minimum information per Annex G. Will form the basis of invoicing.
Plant-completed fields (a, b, c, d, e, f, g, h, j, k, m, n, p, q, r, s, t) + site-completed fields (arrival, discharge complete, water added, signature, location).
Records per load: mass batched, estimated slump, total water added, delivery ticket number, time loaded into truck.
Similar field set; adds batch ticket number, batch time, name of driver, name of purchaser, location of pour, mix design identification.
Why the delivery ticket is a legal contract
Three points settle this. IS 4926 Cl 9.4 says the delivery ticket will form the basis of invoicing. Annex G says the purchaser or his representative shall sign confirming discharge of the load. Cl 10.2.1.4 requires the plant to keep the ticket number on file with the time loaded. The ticket is therefore the only document that simultaneously establishes (a) what was ordered, (b) what was loaded, (c) what was delivered, and (d) what was received. When there is a complaint — too much water, late delivery, low strength, short quantity — the ticket is the first document every dispute resolution looks at.
That role makes the integrity of the ticket non-negotiable. A ticket that has been edited after issue cannot be relied on for any subsequent cube-result investigation, insurance claim, or contract dispute. The audit trail is only as strong as the write-once nature of the original ticket.
Mandatory plant-completed fields (IS 4926 Annex G, G-1)
| Ref | Field | Example |
|---|---|---|
| a | Name or number of the ready-mixed concrete depot | ConcreteInfo Plant-01 |
| b | Serial number of the ticket | 2026-09-29-00734 |
| c | Date | 29-SEP-2026 |
| d | Truck number | MH-12-AB-1234 |
| e | Name of the Purchaser | Acme Builders Pvt Ltd |
| f | Name and location of site | Tower-B, Wakad, Pune |
| g | Grade or mix description of the concrete | M30 pump mix · design mix DM-2026-117 |
| h | Specified target workability | 125 ± 25 mm slump |
| j | Minimum cement content (if specified) | 380 kg/m³ |
| k | Type of cement and grade (if specified) | OPC 53 + 25 % fly ash |
| m | Maximum free water-cement ratio (if specified) | 0.42 |
| n | Nominal maximum size of aggregate | 20 mm |
| p | Generic type or name of any chemical and mineral admixtures included | PCE superplasticiser (1.0 L/m³) |
| q | Quantity of concrete in m³ | 7.0 m³ |
| r | Time of loading | 09:42 IST |
| s | Signature of the plant operator | RK / digital cert |
| t | Warning statement about cement and wet concrete precautions | Standard PPE / wet-concrete caution |
Reference: IS 4926:2003 Annex G G-1 (items a–t). Sequencing letters per BIS document — items (i) and (l) are reserved.
Site-completed block (IS 4926 Annex G, G-2)
Annex G G-2 reserves a separate block on the same ticket for site-side completion:
| Ref | Field | Filled by |
|---|---|---|
| a | Time of arrival on site | Site engineer / driver on arrival |
| b | Time when discharge was completed | Site engineer after chute clear |
| c | Any water/admixture added by the supplier to meet the specified workability | Driver with site witness |
| d | Any extra water/admixture added at the request of the purchaser, with his signature | Purchaser representative |
| e | Pouring location | Site engineer |
| o (G-1) | Signature of the purchaser or his representative confirming discharge of the load | Site representative |
Reference: IS 4926:2003 Annex G G-2 (items a–e) plus G-1 item (o).
IS 4926 Cl 9.4 — the ticket rule
The two paragraphs of Cl 9.4 are short and load-bearing:
- "Immediately before discharging the concrete at the point of delivery, the producer or his representative shall provide the purchaser with a preprinted delivery ticket for each delivery of concrete on which is printed, stamped or written the minimum information detailed in Annex G."
- "The delivery ticket will form the basis of invoicing."
Source: IS 4926:2003 §9.4. Verified against the BIS reprint, page 7.
Best-in-class optional fields
Annex G sets the floor. Top-quartile RMC plants add the following fields without rewriting the ticket, mostly in the same single-page format:
| Optional field | Why it matters |
|---|---|
| GPS stamp on dispatch | Confirms truck was at plant at load time; settles "truck left late" disputes |
| GPS stamp on arrival | Settles "truck arrived late" disputes; supports 2-h clock tracking |
| Slump at plant exit | Confirms dispatch was within tolerance; pairs with slump at receipt |
| Slump at site receipt | Catches water addition on route; documents acceptance decision |
| Concrete temperature at exit | Confirms hot-weather compliance per IS 7861 Pt 1 |
| Ambient temperature at site | Validates cold/hot-weather provisions |
| Cube mould ID range for this load | Makes cube traceability automatic — no manual entry later |
| Driver name + mobile | Closes the communication loop for site-call-ahead |
| Customer PO / work-order reference | Binds the ticket to the contract without separate paperwork |
| Digital signature / QR for retrieval | Enables paperless workflow per ISO 9001 clause 7.5 |
Sequential numbering across the day
Annex G item (b) requires the ticket to carry a serial number. The simplest and most defensible convention is YYYY-MM-DD-NNNNN, resetting the counter at midnight. That format is both human-readable and machine-sortable. A gap in the sequence — ticket 00732 followed by 00734 — is an immediate red flag that something was lost or discarded, and should trigger a daily reconciliation against the batch-controller log per Cl 10.2.1.4.
Plants that allow dispatch software to generate ticket numbers on-the-fly at print time lose this audit property. The number must be assigned at the moment the load is committed to the truck, and locked before the truck moves.
The integrity rule — tickets are never edited
Three integrity rules apply to the ticket once the truck has left the plant:
No strike-through, no overwrite, no re-printing on top of the original. Even the driver cannot correct a typo on the slip.
A separate document, signed by both plant and site representatives, referencing the original ticket number and the corrected field.
The original ticket stays on file as the legal record. The addendum sits beside it. Together they form the auditable history.
This rule is not in IS 4926 Annex G by name, but it is implied by the standard's treatment of the ticket as a contract document and by the QCI-RMC-Plant-Certification scheme audit checklists. Dispatch software that allows field-level editing after issue is creating a liability the next dispute will expose.
Dispute resolution — how the ticket settles claims
| Dispute | Field(s) on the ticket that settle it |
|---|---|
| Over-delivery (customer claims short pour) | [q] Quantity · [o] Site signature |
| Under-delivery (plant claims full delivery) | [q] Quantity · [o] Site signature · return slip |
| Late delivery (site blames plant) | [r] Time of loading · arrival time on site · IS 4926 Cl 6.2.1 |
| Low strength (28-d cube failure) | [g] Mix ID · [p] Admixture · [r] Loading time · cube mould ID link |
| Excess water added on route | Site block [d] extra-water signature · slump at receipt |
| Wrong grade poured | [g] Grade · [k] Cement type · site signature on receipt |
Common ticket failures on Indian plants
Truck returns without arrival/discharge times or site signature. The dispute clock cannot start; the ticket fails Annex G G-2 and the audit trail is incomplete. The fix: driver refused to leave site without site signature.
IS 4926 Cl 5.2.2.2 defines time of loading as the moment water is added to the dry mix. Operators record the batch-panel start time instead, gaining 1–3 min on the 2-h clock per Cl 5.2.2.1. The fix: log time of loading from the water-meter open signal, not the batch-panel "start".
Ticket says 7.0 m³ for every load from a 7 m³ truck, regardless of actual batched volume. Yield variance is hidden. The fix: ticket quantity must come from the batch-controller, not the truck plate.
Site signature smudged, illegible, or on the customer's copy only. The audit trail loses the customer's acknowledgement. The fix: require original signature on the plant copy and on the customer copy separately, or use a digital acknowledgement system that captures both.
Field-checklist blocks
A short questionnaire, an inspector's checklist, and three worked examples that show how the ticket resolves into a decision: invoice the load, reject the load, or raise an addendum and keep the original on file.
Questionnaire — asked at the dispatch desk, before the ticket is printed and the truck is released
- Is there a preprinted ticket for this load, issued immediately before discharge? One ticket per delivery, per IS 4926:2003 Cl 9.4.
- Does the ticket carry the whole Annex G G-1 field set, and is the purchaser's acknowledgement item (o) on the same sheet? The ticket is the only document that establishes what was ordered, what was loaded, what was delivered and what was received.
- What is the serial number, and is it sequential with no gap in the day's series? A gap in the sequence is an immediate red flag.
- Does field [r], time of loading, come from the water-meter open signal? Not the batch-panel start. Cl 5.2.2.2 puts the clock start at water addition, and Cl 5.2.2.1 counts the 2 hours from there.
- Does field [q], quantity in m³, come from the batch controller's actual batched volume? Not the nominal truck capacity typed on every slip.
- Who signs the site block at discharge, and is there a printed name, company and time with the signature? A signature alone is not adequate.
- If extra water or admixture was added at the purchaser's request, is there a signature against the second acknowledgement, Annex G G-2 (d)?
- Has anything on this ticket been struck through, overwritten or re-printed since issue? Corrections are signed addenda that reference the original number.
Inspector's checklist — what to verify on site
- One preprinted ticket per load, printed from the batch controller and issued immediately before discharge, per IS 4926:2003 Cl 9.4.
- The plant-side fields present, complete and legible, with particular care on the ones plants get wrong: [g] grade and mix identification (M30 pump mix, design mix DM-2026-117), [h] specified target workability (125 ± 25 mm), [j] minimum cement content (380 kg/m³), [m] maximum free water-cement ratio (0.42), [n] nominal maximum aggregate size (20 mm), [p] admixtures (PCE superplasticiser, 1.0 L/m³), [q] quantity (7.0 m³), [r] time of loading (09:42 IST), [s] plant operator signature, [t] the warning statement about cement and wet concrete.
- Site block G-2 complete on return: time of arrival, time discharge was completed, any water or admixture added by the supplier, any extra water or admixture added at the purchaser's request with his signature, and the pouring location, plus the purchaser's signature under item (o) confirming discharge.
- Quantity from the batch controller, not the truck plate. If every load off a 7 m³ truck reads 7.0 m³, the yield variance on the plant is invisible.
- Time of loading from the water-meter open signal, so the 2-hour discharge clock is measured from the right moment.
- Serial number assigned when the load is committed to the truck and locked before the truck moves, in the YYYY-MM-DD-NNNNN format with the counter resetting at midnight.
- Daily reconciliation of the day's ticket series against the batch-controller log, per IS 4926:2003 Cl 10.2.1.4, with the per-load records held: mass batched, estimated slump, total water added, delivery ticket number and time loaded into the truck.
- Write-once discipline: no strike-through, no overwrite, no re-print over the original. Any correction is a separate signed addendum referencing the original ticket number, and the original stays on file as the legal record. Signatures captured on the plant copy and the customer copy.
What happens if… three worked examples
What happens. Ticket 2026-09-29-00734 carries 7.0 m³ of M30 pump mix, design mix DM-2026-117, at a target workability of 125 ± 25 mm. The arrival time, the discharge-complete time, the pouring location and the purchaser's signature under item (o) are all missing. The ticket fails Annex G G-2, and Cl 9.4 says this slip is the basis of invoicing, so 7.0 m³ is on the invoice with no acknowledgement of receipt behind it.
Likely outcome. The dispute clock cannot start. Where a customer later claims a short pour, the two fields that settle it are the quantity and the site signature, and the signature is the missing half. The driver does not leave site without the site block signed, and where it has been left blank, the load is not invoiced as delivered until the addendum is produced.
What happens. One number in the day's series is unaccounted for: 00734 − 00732 − 1 = 1, so ticket 00733 has gone missing. The serial number has to be assigned when the load is committed to the truck and locked before the truck moves, so a gap cannot be a printing artefact. Either the ticket was lost or the load was discarded and the ticket never issued.
Likely outcome. A gap in the sequence triggers the daily reconciliation against the batch-controller log under IS 4926:2003 Cl 10.2.1.4, and the batch record either produces the missing ticket or shows a load that was never dispatched. It is not papered over with a re-numbered re-print, because a re-print breaks the write-once property that makes the series evidence in the first place.
What happens. Field [r] on the ticket reads 09:42 IST, but it was copied from the batch-panel start rather than the water-meter open signal, and those two moments are 1–3 minutes apart. Under Cl 5.2.2.2 the 2-hour discharge limit of Cl 5.2.2.1 is counted from water addition, so every load carries that error into the clock, and it is 1–3 minutes gained before the driver flags a load that is close to the limit. The deadline the driver works to from a 09:42 ticket is 11:42.
Likely outcome. Take [r] from the water-meter open signal, and if a wrong time is already on an issued ticket, correct it with a signed addendum that references the original ticket number and states the corrected field, with the original left on file. A ticket whose clock start is wrong is a ticket that cannot settle the late-delivery dispute, because that dispute turns on [r] and the arrival time together.
Frequently Asked Questions
What fields are mandatory on an RMC delivery ticket per IS 4926?
Can a delivery ticket be edited after the truck leaves the plant?
Who signs the RMC delivery ticket at site?
Related articles
Amit Haridas
Founder & Proprietor, ConcreteInfo. 25+ years experience in construction QA/QC, concrete technology, RMC plant operations, consulting and technical training across India. For ticket-format design, dispatch-software reviews, or audit-prep support, contact amit@concreteinfo.in.
Technical updates, not sales emails
One email when a new article goes out on concrete technology, QA/QC and construction quality. No promotions, and your address is never sold or passed to advertising networks. Subscribing is separate from making an enquiry.