How to Document a Concrete Pour
A concrete pour record should let someone who was not on site understand what was delivered, what was recorded, what happened and where the supporting evidence lives.
What does “documenting a concrete pour” actually mean?
It means building a traceable field record as the work happens. The record normally starts with the project, placement location, supplier, mix reference and planned quantity, then grows with every delivery, ticket, test, observation, issue and photo. The objective is not paperwork for its own sake. It is to preserve enough context that the pour can be reviewed later without reconstructing the day from notebooks, text messages and an unlabeled camera roll.
For a focused list of fields, use the Concrete Pour Report Template. If you need a pre/during/post-pour check, use the Concrete QA/QC Checklist.
1. Set up the pour before the first truck
Identify the work
Record project, pour name or element, placement location, planned date, supplier, mix reference and ordered quantity. Use a naming convention another person can understand later.
Know what the project requires
Review the project specification and inspection/test plan before placement. Determine which delivery data, tests, specimens, photos, signatures or other records are required and who is responsible for them.
2. Treat every truck as a traceable delivery
A delivery should not become “one of the trucks from that morning.” Record a unique ticket/delivery reference and connect the quantity, times, observations and ticket image to it. This makes later questions much easier to answer.
| Delivery record | Why it helps later |
|---|---|
| Ticket / delivery number | Primary reference back to the supplier ticket. |
| Truck number | Useful secondary identifier where used by the supplier. |
| Delivered volume | Supports running quantity and closeout reconciliation. |
| Arrival / discharge timing | Preserves the actual site sequence and delays. |
| Concrete temperature | Keeps a recorded field observation with that delivery. |
| Ticket photo | Keeps source evidence with the delivery instead of the camera roll. |
See the dedicated Concrete Delivery Ticket Log guide for a worked truck example.
3. Keep field tests and sample references with the pour
Record the test type, result, unit, time, sample/specimen reference and relevant notes. Do not turn the log into an acceptance engine: whether a result is acceptable depends on the applicable contract documents, procedures and standards.
ACI describes its Concrete Field Testing Technician—Grade I program as demonstrating the ability to properly perform and record seven basic field tests on freshly mixed concrete. ASTM’s current concrete standards catalog includes standards for sampling, temperature, slump, density/yield and air content. That is why a field record should preserve test context rather than just a loose number. ACI field testing reference ↗ · ASTM concrete standards ↗
4. Record exceptions while the details are fresh
Delays, adjusted or rejected deliveries, interruptions, unusual observations and corrective actions are difficult to reconstruct accurately days later. Write a factual description, identify the delivery or part of the pour involved, record the action taken and add photos when they clarify the record.
“Delivery #842371 arrived 18 minutes behind the preceding truck. Placement paused at Grid B4. Crew resumed after delivery arrived; no additional action recorded.”
Less useful: “Truck was late.”
5. Review documentation before closing the pour
- Do recorded deliveries reconcile with the field truck count?
- Are ticket references and expected ticket photos attached?
- Are required timing and temperature fields recorded?
- Are field tests and sample references captured?
- Are issues, actions and relevant photos understandable?
- Does the final record clearly show information that was not recorded?
A completeness review is not a quality approval. It tells you whether expected documentation appears to be present. The Concrete Pour Report Example shows how those records can be organized for handover.
Worked example: Level 2 floor slab
Pour: Level 2 – Floor Slab
Supplier: Texas Ready Mix
Ordered: 120 yd³
Example delivery: Ticket #842371 · Truck #237 · 15.0 yd³ · 78°F
Records: delivery ticket image, field test entry, issue/action note and general pour photos.
The value is not the individual fields; it is that they remain connected. A reviewer can move from the pour summary to a delivery, its ticket and related observations without rebuilding the sequence manually.
Common questions
What should be recorded for every concrete pour?
At minimum, keep a clear pour identity and the delivery, test, issue and supporting records required by your project. The exact requirements come from the project documents and responsible QA/QC team.
Should missing information be filled in later?
Only enter information you can substantiate. A clear “not recorded” is more transparent than an assumed value.
Can an app replace certified field testing?
No. A documentation app organizes records. It does not replace qualified personnel, required test procedures, laboratory work or formal acceptance.
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 →