Concrete Delivery and Batch Record

Use this record for

Receipt and allocation of ordinary ready-mixed concrete to cast-in-place work, from each batch docket through reconciliation and handover.

Outside this record: Mix design approval; detailed fresh concrete testing; placement quality; specimen/laboratory reports; concrete certification; precast, piles, shotcrete and special infrastructure requirements.

Blank field record. Apply the approved project criteria and record actual facts. Do not authorize a site addition or accept/reject a load by assumption.

Collect these project inputs first

Approved mix/order and revisions: Compare actual docket identity and any changed supply with the controlled project basis.
Pour map and planned truck allocation: Link each load and actual quantity to the location receiving it.
Project timing and site-addition rules: Supply the exact time origin, limit, permission and responsible role where applicable.
Receipt tests and assigned roles: Identify only tests and decisions required by this project.
Discrepancy, unused/returned concrete and NCR process: Keep traceability and closeout for any affected load.

How to use the checklist

Confirm the current approved order/mix, element map, project timing basis and assigned receiving role.
Enter one record per actual truck/batch; transcribe docket, times and quantity from the source.
Document any site addition or altered supply only from an actual written direction and supplier/docket trail.
Link the load to the real pour location and separately required sample/test record.
Keep a discrepancy open until the assigned project role records a decision and evidence; reconcile leftover/returned quantity.
Use the delivery log for repeat entries; continue on another blank copy when needed and retain the linked original evidence.

Checks and the records they need

Fill project criteria from approved documents before inspection. The fields below show what the downloaded form asks you to record; the web page does not save or approve site results.

Delivery log for repeat entries

Use one row for each actual truck/batch. Link split allocations and extra details by reference to a pour map or continuation sheet. Establish the project receipt criteria in the check pages first; record only actual events and the assigned receipt decision.

Columns in the blank log

Docket / truck ID
Batch / mix designation
Element / pour / allocation ref
Batch time / source
Arrival / discharge start-end
Quantity / unit / used-returned
Sample / test record ref
Receipt decision / role / NCR ref

The files provide 6 blank entry rows. Continue on another blank copy as needed; the web page does not record site entries.

CD-01 · Controlled pour and supply basis

Pour/lot boundary, approved order and mix revision, location map, project timing rule and named receipt role.

How to check: Review current controlled documents at the workface and reconcile any revision or allocation conflict before recording receipt.
What defines acceptance: The current controlled documents identify the pour, approved supply basis and assigned receiving role. Any essential missing timing rule or revision conflict is identified for project direction before the affected receipt decision.
Project document to cite: Controlled pour/element register, approved concrete order and mix submission revisions, project delivery procedure and ITP responsibility/decision register.

If a discrepancy is found: Keep affected load Pending and request clarification from document control or the assigned technical/receiving role.

Topic references: Cavoren cast-in-place concrete baseline; Queensland Department of Transport and Main Roads, MRTS70 Concrete (July 2022); Hutchies 040 Concrete Place Report (public Word report template).

Blank record fields

Element / lot / pour-map ref
Approved mix / order revision
Timing clause / source
Assigned receiver / role
Result, inspector and date; issue and recheck reference

CD-02 · Truck docket and batch identity

Supplier, truck, docket, batch/mix designation and the actual ticket particulars required by the project.

How to check: Compare each docket to the approved order; transcribe identifiers and retain the complete ticket reference.
What defines acceptance: The docket identifiers and supplied mix can be reconciled with the current approved order and intended pour, against the project-required ticket details. Missing or mismatched identity remains open for assigned disposition.
Project document to cite: Approved concrete order/mix submission, project docket-detail requirements and the actual supplier delivery docket; cite the relevant identifier and revision.

If a discrepancy is found: Record the mismatch and load; seek supplier and project clarification without silently correcting the docket.

Blank record fields

Supplier / truck / docket
Batch ID / mix label
Ticket quantity / unit
Docket file / photo ref
Result, inspector and date; issue and recheck reference

CD-03 · Mix change and site-addition trail

Any actual site water/admixture or other change, stated quantity, time, requesting person, written authorization and supplier ticket notation.

How to check: Reconcile the order, docket and written instruction; never infer an addition or permission from appearance or verbal custom.
What defines acceptance: Any recorded change has the permission, quantity, time, responsible authority and supplier trail required by the project. An undocumented addition is not treated as permitted; where no addition occurred, record that observation or N/A with its basis.
Project document to cite: Project-approved site-adjustment rule, written load-specific instruction and supplier docket/change record; record the authorising role and locator.

If a discrepancy is found: Identify and preserve the affected load trail; refer to the assigned technical receiver and record written disposition.

Blank record fields

Change / actual amount and unit
Time / docket annotation
Instruction and authority ref
Supplier confirmation ref
Result, inspector and date; issue and recheck reference

CD-04 · Batch, arrival and discharge times

Actual dispatch/batch, arrival and discharge times, sampling time if relevant, and any event used in a project-defined time check.

How to check: Capture times from docket and contemporaneous site logs; calculate elapsed time only where the project defines origin and method.
What defines acceptance: Recorded times have an identifiable source and, where a project time check applies, the elapsed assessment uses its stated origin and criterion. An unclear time basis or departure is referred; no universal time limit is supplied.
Project document to cite: Project specification or approved delivery procedure defining the timing origin, allowed condition and assessment method, plus the source docket and site log.

If a discrepancy is found: Where a required time is missing or potentially outside the project basis, keep decision Pending and refer with source records.

Blank record fields

Batch / dispatch time + source
Arrival and discharge start/end
Project timing clause / origin
Elapsed time if project requires
Result, inspector and date; issue and recheck reference

CD-05 · Quantity and placement allocation

Ticketed and actual used/returned quantity, units, element/grid and any split-load allocation.

How to check: Cross-link docket to the placement diary and pour map; reconcile leftovers to actual return or disposition evidence.
What defines acceptance: The docket quantity and used/returned allocation are traceable to the actual pour locations under the project reconciliation procedure. Any unresolved allocation or quantity discrepancy remains open; no generic tolerance is assumed.
Project document to cite: Project pour/allocation map, supplier docket, quantity reconciliation procedure and actual placement/return record references.

If a discrepancy is found: Trace the affected load and reconcile missing amount/location against supplier and placement records before closing.

Blank record fields

Ticket / used quantity + unit
Element / grid / placement ref
Returned / unused quantity + unit
Placement / return record ref
Result, inspector and date; issue and recheck reference

CD-06 · Receipt observation and separate test links

Observable load condition or reported concern; any project-required fresh test/sample ID and actual test value/unit.

How to check: Record facts without inferring properties; link to the separate tester/method/equipment/sample record required by the project.
What defines acceptance: Observed concerns and required test/sample references are linked to the correct delivery and location. Any measured result is traceable to its original record and evaluated only against the governing project receipt criterion.
Project document to cite: Project receipt inspection/test requirements and linked fresh-test or sample record, including the tester/method and original evidence reference.

If a discrepancy is found: Identify affected load and notify the assigned receiver; retain test evidence and record the authorized disposition.

Blank record fields

Observed condition / time
Sample or test ID
Actual value / unit if measured
Tester / method / evidence ref
Result, inspector and date; issue and recheck reference

CD-07 · Receipt decision, exceptions and handover

Recorded status, authorized receiving decision, open docket/time/mix/quantity/test issues, corrective instruction and closeout evidence.

How to check: Separate recorder observation from decision; link decision maker role, conditions, NCR and recheck/closeout records.
What defines acceptance: The assigned role records the actual load decision, conditions and supporting instruction/evidence; unresolved issues carry into the ITP/NCR. Record completion is separate from any contractual release or permission to place.
Project document to cite: Project concrete ITP receipt decision/notice arrangements, assigned authority, load-specific instruction, NCR and evidence of closure or handover.

If a discrepancy is found: Keep affected load Pending until designated project role records the disposition and receiving handover.

Blank record fields

Load / affected location
Decision / role / instruction ref
NCR / action and recheck ref
Handover recipient / date
Result, inspector and date; issue and recheck reference

When a check cannot be closed

Situation	What to record or resolve
Docket mix or batch differs from the approved order.	Identify the load and location; attach the docket and request the assigned project technical decision. Keep status Pending.
A driver or site worker proposes a water/admixture addition.	Record the actual instruction, authority, time and docket update; follow only project-approved written direction.
A delivery time may exceed the project limit or the timing origin is unclear.	Record source times and exact project clause. MRTS70 numeric limits are not a building default; refer for project decision.
Docket quantity does not reconcile to a placement area or leftover load.	Keep reconciliation open and link dispatch, placement and return/disposal records.
The observer is not assigned the load acceptance role.	Record observations and hand them to the contract/ITP role; this sheet alone cannot accept or reject the load.

Concrete delivery receipt handover

Applies to docket traceability and delivery handover only. It does not approve a mix, prove test conformity, certify concrete, release a project point or authorize placement. Carry open loads into the concrete ITP/NCR.

Record handover status options in the blank record:

Record completed; evidence filed
Action or recheck remains open
Project / technical disposition required

Record the assigned roles: Delivery recorder name / role / date; Assigned receiving decision role / date; Supplier contact / role, if clarification needed; Open NCR / instruction reference.

Fictional ticket-to-pour mapping example — not a supply requirement

Fictional teaching example only. These are illustrative document references, not a real project, engineering values or completed inspection results.

Teaching-only IDs: fictional docket DKT-0007, mix label MIX-A, element P1 / Grid C2 and pour register P-014 Rev B. No real supplier or project is represented.

Requirement to carry into the record: A ticket label is a traceability clue, not proof of approval. Reconcile it to the approved order and actual location; record any change only with its written instruction and docket trail.
Illustrative reference: Fictional DKT-0007 / P-014 Rev B; replace with current project IDs.
What the site record should capture: Show how one ticket links to approved mix, actual truck times, quantity, placement location, linked sample and assigned receiver. Keep assessment, decision and signatures blank until evidence is reviewed.

Source notes and limits

Cavoren cast-in-place concrete baseline
Scope context only; not independent technical authority or project acceptance criteria. Read: Original proposed receipt topics CON-01, CON-09 and interfaces CON-10–11. Checked 2026-10-07.
Queensland Department of Transport and Main Roads, MRTS70 Concrete (July 2022)
Topic guidance only. MRTS70 is for Queensland road/bridge infrastructure contracts (or other specified elements). Its values, timing limits, test frequencies, qualifications, H/W points, project roles and release rules are not generalized into these records. Read: July 2022, Clause 1/Table 1 (infrastructure scope); 10.5 (transport and delivery docket); 11 (plastic concrete checks/departure topics). Clause references are printed specification locators, not PDF viewer page numbers. Checked 2026-10-07.
Hutchies 040 Concrete Place Report (public Word report template)
Contractor-specific example of report layout and handover, not universal criteria. No Hutchies text is reproduced. Read: Public 040 Concrete Place Report: header and closeout fields, rows 6–13 on discharge, placement, protection, curing and final records review. Contractor example only; no technical acceptance conditions are adopted. Checked 2026-10-07.

Continue the work sequence

This field record documents checks after they are carried out. An ITP sets the work sequence, project criteria, responsibilities and required records before the work starts.

Need an ITP prepared for your project?

Send your drawings, specifications and contractor requirements. Receive a project-specific ITP and matching blank site records in Excel, Word and PDF.

USD 99 per defined work package · Within 24 hours after the required project files are complete.

Order project ITP · USD 99 View scope and required files