Concrete Delivery Ticket Log Template
Download a concrete delivery ticket log template to track truck loads, batch tickets, quantities, arrival times, placement details, rejected loads, and pour totals.
Keep Concrete Deliveries Organized by Pour
A concrete delivery ticket log gives contractors a consistent way to track ready-mix deliveries from the first truck through the final load. It can help the field team record ticket numbers, truck arrival times, ordered and delivered quantities, mix information, placement locations, rejected loads, returned concrete, and other details that affect the pour.
This concrete delivery ticket log template is designed for concrete subcontractors managing slabs, walls, footings, grade beams, foundations, pads, and other cast-in-place work where multiple truck deliveries need to be documented clearly.
What Is a Concrete Delivery Ticket Log?
A concrete delivery ticket log is a jobsite record used to summarize individual ready-mix deliveries associated with a specific concrete placement. Each row typically represents one truck or batch ticket and captures enough information to match the delivery with the correct pour.
The log can be used alongside supplier batch tickets, pour cards, daily reports, testing records, and job-cost information. It helps contractors see how much concrete arrived, when it arrived, where it was placed, and whether any loads were rejected, partially used, or returned.
When to Use a Concrete Delivery Ticket Log
Use the log whenever a concrete placement involves one or more ready-mix deliveries that need to be tracked and reconciled.
- Slab-on-grade pours
- Elevated slab placements
- Footings and grade beams
- Foundation walls
- Retaining walls
- Columns and piers
- Equipment pads
- Sidewalks and site concrete
- Large placements with multiple trucks
- Pours where actual delivered quantity needs to be compared with the planned order
Who Should Use This Template?
The template is intended for concrete subcontractors and specialty contractors that need a simple field-to-office record of concrete deliveries.
- Concrete foremen
- Superintendents
- Project managers
- Field engineers
- Operations managers
- Office staff reconciling concrete invoices
- Estimators reviewing actual material usage after completion
What to Include in a Concrete Delivery Ticket Log
A useful log should identify each load clearly enough that the field record can later be matched to the supplier ticket, pour location, and total quantity placed.
| Log Field | What to Record |
|---|---|
| Ticket information | Batch ticket number, truck number, supplier, batch plant, and mix designation |
| Delivery timing | Batch time where available, site arrival, placement start, placement finish, and departure time |
| Quantity | Ticket quantity, accepted quantity, rejected quantity, returned quantity, and cumulative delivered quantity |
| Placement location | Pour number, area, slab section, wall, footing, grade beam, column, pad, or other placement reference |
| Load status | Accepted, partial, rejected, returned, or other applicable status |
| Testing reference | Sample, cylinder, test-set, or inspection reference when a particular load is associated with testing |
| Field notes | Delivery delay, site access issue, pump interruption, rejected load reason, returned material, or other relevant event |
| Totals | Total delivered, total accepted, total rejected, total returned, and comparison with planned or ordered quantity |
How to Use the Concrete Delivery Ticket Log
- Enter the pour information. Identify the project, pour number, date, placement location, supplier, and planned concrete quantity before the first truck arrives.
- Record each ticket as it arrives. Enter the ticket number, truck number, mix designation, quantity, and arrival time from the supplier documentation.
- Track placement timing. Record when each load begins and finishes discharging when that information is useful for the project record.
- Identify the load status. Mark each delivery as accepted, partially used, rejected, returned, or otherwise handled.
- Note the placement location. If one pour includes multiple areas, record where each load was used so unusual quantity or performance issues can be traced later.
- Reference testing where appropriate. Connect sampled loads with the applicable test-set or cylinder reference without replacing the formal testing record.
- Record unusual events. Note rejected loads, long delivery gaps, pump downtime, access problems, or other conditions that affected the placement.
- Reconcile the totals after the pour. Compare planned, ordered, delivered, accepted, rejected, returned, and actual placed quantities before closing the record.
Example Delivery Log Entry
Ticket 64218, Truck 17: 10.0 cubic yards, Mix C-4, arrived at 7:42 a.m. for Pour 12, Level 1 slab, Area B. Placement began at 7:48 a.m. and finished at 7:59 a.m. Load accepted in full. Test Set 3 was associated with this delivery. No exceptions noted.
Concrete Delivery Ticket Logging Best Practices
- Use one row for each truck or supplier ticket.
- Record ticket numbers exactly as shown on the supplier documentation.
- Keep planned quantity, ordered quantity, delivered quantity, and actual placed quantity separate.
- Record rejected and returned concrete instead of reducing the delivered total without explanation.
- Identify the exact placement area when a pour covers more than one location.
- Preserve original batch tickets with the project records.
- Use test-set references when a load is tied to field sampling.
- Document unusual delivery gaps, access issues, pump downtime, or placement interruptions.
- Reconcile supplier totals before approving invoices when that is part of the contractor's process.
- Compare final delivery totals with the estimated and ordered quantity after the pour.
Common Concrete Delivery Ticket Log Mistakes
Recording Only the Daily Total
A single end-of-day quantity does not show which trucks arrived, when delays occurred, or whether any loads were rejected. Individual ticket entries provide a more useful project record.
Mixing Delivered and Accepted Quantity
A supplier may deliver a load that is later rejected or partially returned. Track delivered, accepted, rejected, and returned quantities separately so totals remain understandable.
Failing to Record the Mix Designation
When a project uses more than one approved mix, the mix designation helps confirm which material was delivered to each placement. Avoid relying only on compressive-strength descriptions.
Leaving Rejected Loads Undocumented
If a load is rejected, record the ticket, quantity, reason, and disposition. Do not remove the row from the log, because the delivery still occurred and may need to be reconciled later.
Not Matching Tickets to the Correct Pour
Large projects may have multiple placements on the same day. Use pour numbers and location references so tickets can be connected to the correct work.
Discarding Supplier Tickets After Entering the Log
The log summarizes delivery information but should not replace the original batch tickets. Preserve source documents according to the project's recordkeeping requirements.
Keeping Concrete Delivery Records Connected With the Job
A spreadsheet log is a practical way to standardize concrete delivery tracking. As the number of pours and active jobs increases, tickets, daily logs, photos, expenses, purchase information, and job-cost records can become harder to manage across separate files.
SimplySub is construction management software built for subcontractors and specialty contractors. It helps teams organize jobs, daily logs, documents, photos, expenses, purchase-order workflows, and job-cost information, making it easier to keep field and office records connected around active work.
Frequently Asked Questions
What should be recorded from a concrete delivery ticket?
Useful fields include the ticket number, truck number, supplier, mix designation, ticket quantity, delivery times, pour location, load status, testing reference, and notes about rejected, partial, or returned loads.
Should rejected concrete still appear in the log?
Yes. Record the delivery and mark it as rejected, along with the quantity, reason, and disposition when known. That preserves a complete record of what arrived on site.
What is the difference between delivered and placed quantity?
Delivered quantity is the amount represented by the loads brought to the site. Placed quantity is the amount actually incorporated into the work. Rejected loads, returned concrete, partial loads, or other conditions can cause those totals to differ.
Should the log include arrival and discharge times?
They can be useful for understanding truck spacing, delivery interruptions, waiting time, and placement progress. The level of detail should match the project's documentation needs.
Can the delivery log help reconcile supplier invoices?
Yes. The ticket numbers and quantities recorded in the field can provide a useful reference when comparing supplier billing with project records. Original supplier tickets should still be retained for verification.
Is the delivery ticket log a replacement for concrete testing records?
No. The log may reference a test set, sample, or inspection associated with a load, but formal testing and inspection documentation should remain in the appropriate project records.
Build a Clear Record of Every Concrete Load
A consistent concrete delivery ticket log gives contractors a clearer record of truck deliveries, quantities, timing, mix information, placement locations, rejected loads, and final pour totals. Keeping each ticket organized by pour can support field documentation, supplier reconciliation, job costing, and post-pour review.