Concrete Delivery Ticket Log
The simplest way to make a concrete delivery traceable is to keep its ticket reference, quantity, timing, observations and source image together.
What is a concrete delivery ticket log?
It is a chronological record of the concrete deliveries associated with a pour. Rather than treating the supplier ticket as a loose piece of paper, the log gives each delivery a searchable reference and connects the information you need on site with the original ticket image.
A delivery log is one part of the wider concrete pour documentation workflow.
Recommended fields for each truck
| Field | What to record | Purpose |
|---|---|---|
| Ticket / delivery # | Unique supplier ticket reference | Primary traceability key |
| Truck # | Truck identifier, if used | Secondary reference |
| Volume | yd³ or m³ delivered | Running quantity / reconciliation |
| Timing | Relevant batch, arrival and discharge times | Sequence and delay record |
| Temperature | Recorded fresh concrete temperature | Field test/observation context |
| Status | Delivered, adjusted, rejected, etc. | Explains quantity/status |
| Ticket image | Readable image of source ticket | Preserves source evidence |
| Notes | Factual delivery-specific observations | Context for later review |
Worked delivery example
| Field | Example |
|---|---|
| Project | Riverside Office Building |
| Pour | Level 2 – Floor Slab |
| Supplier | Texas Ready Mix |
| Ticket | #842371 |
| Truck | #237 |
| Volume | 15.0 yd³ |
| Concrete temperature | 78°F |
| Status | Delivered |
| Evidence | Ticket image attached to delivery record |
This is an illustrative record, not a prescribed project form. Add or remove fields based on your contract documents and procedures.
Five mistakes that make delivery logs harder to use
Ticket photos only in the camera roll
A photo without a delivery reference creates matching work later.
One total instead of truck-level records
A final volume alone cannot explain which delivery an issue or test relates to.
Inconsistent units
Keep the project in a consistent unit system and label values clearly.
Vague issue notes
Identify the delivery and write what happened and what action was taken.
Rebuilding the log after the pour
Capture records as deliveries occur, when the source information is in front of you.
From ticket log to final pour report
The delivery log should not be an isolated spreadsheet that must be copied into another document. It is most useful when it feeds the final pour report together with tests, issues and photos. Before closeout, use the QA/QC documentation checklist to identify gaps.
Delivery log FAQ
Do I need a truck number if I have a ticket number?
The ticket/delivery number is normally the stronger unique reference. A truck number can still be useful as a secondary identifier where your supplier uses it.
Should I photograph every delivery ticket?
Follow your project procedure. Where ticket images are part of the record, attach them to the matching delivery rather than storing them without context.
Does a delivery log prove the concrete was accepted?
No. It records the delivery. Acceptance depends on the project requirements and responsible personnel.
Capture the record while the pour is happening.
Keep deliveries, ticket photos, tests, issues and site photos connected to one pour. Review documentation completeness and generate a structured PDF with Pro.
Download on the App Store →