Concrete Pour Report Example
This illustrative report shows how a day of field records can be organized so a reviewer can move from the pour summary to individual deliveries, tests and issues.
Example report header
| Report field | Illustrative value |
|---|---|
| Project | Riverside Office Building |
| Project ref. | ROB-2026-001 |
| Pour | Level 2 – Floor Slab |
| Supplier | Texas Ready Mix |
| Ordered quantity | 120 yd³ |
| Unit system | US Customary |
Example delivery section
A useful report lets the reviewer identify a delivery quickly, then find its associated ticket and observations.
| Ticket | Truck | Volume | Temp. | Status |
|---|---|---|---|---|
| #842371 | #237 | 15.0 yd³ | 78°F | Delivered |
| #842389 | #241 | 15.0 yd³ | 79°F | Delivered |
| #842405 | #226 | 15.0 yd³ | 79°F | Delivered |
These values are illustrative. See what to record for every delivery.
Example field test record
Illustrative result: 5.0 in
Related pour: Level 2 – Floor Slab
Sample reference: ROB-L2-01
Note: Result shown here demonstrates report structure only; acceptance criteria are intentionally not stated.
That last point is important: a field report should preserve the measured record without inventing a pass/fail conclusion. ASTM identifies C143/C143M as the standard test method for slump of concrete, while the project documents govern which tests and criteria apply. ASTM concrete standards ↗
Example issue and action record
Related delivery: #842371
Observation: Delivery interval longer than preceding sequence; placement paused at Grid B4.
Action: Event recorded and site sequence resumed after delivery arrival.
Evidence: Site photo attached.
A useful issue record answers three questions: what happened, what did it relate to, and what was done. Avoid adding a technical conclusion that was not actually made on site.
Example closeout summary
Deliveries
Truck count and delivered quantity summarized, with ticket-level records available below.
Tests
Field test entries shown with result, unit and sample references.
Issues
Events and actions linked to the relevant part of the pour.
Evidence
Ticket images and general site photos kept with the report context.
What makes this different from a daily report?
A general construction daily report may cover labor, equipment, visitors, weather and multiple activities across the site. A concrete pour report is narrower: it creates a traceable record around one placement and its deliveries, tests, issues and supporting evidence. The two can complement each other.
To build the record from scratch, start with How to Document a Concrete Pour.
Report example FAQ
Is this an official ACI or ASTM report form?
No. It is an illustrative field-documentation example created for Concrete Pour Log. Use project-mandated forms where required.
Should a report include photos?
Where useful or required, photos can preserve context for tickets, issues and site conditions. Follow your project requirements.
What if a field was not recorded?
Show that transparently rather than inserting an assumed value.
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 →