Concrete QA/QC Checklist
Use this checklist to organize the records around a concrete pour. It complements — but does not replace — the project specification, inspection/test plan or qualified QA/QC personnel.
Before the pour
- Confirm project, pour element/location, planned date and responsible field contacts.
- Confirm supplier, mix reference and ordered quantity against the approved project information.
- Review the project specification and inspection/test plan for required inspections, tests, specimens and records.
- Confirm the placement area and required pre-pour inspections have been released by the responsible project personnel.
- Confirm the field-testing plan: who performs the tests, where results are recorded and how samples/specimens are identified.
- Set up a consistent method for delivery tickets and site photos before trucks begin arriving.
During deliveries and placement
- Create a separate record for each delivery/ticket.
- Record delivered volume and relevant truck/ticket references.
- Capture required arrival, discharge or other project-specific times.
- Keep ticket images associated with the correct delivery.
- Record fresh-concrete observations/tests required by the project.
- Track running delivered quantity and truck count.
- Document interruptions, rejected/adjusted deliveries or other notable events when they occur.
For the truck-level structure, see the Concrete Delivery Ticket Log.
Field testing records
Testing requirements vary by project. ACI’s Field Testing Technician—Grade I program specifically covers properly performing and recording basic fresh-concrete field tests, while ASTM maintains current standards covering sampling, temperature, slump, density/yield and air content. Your project documents determine what applies and what constitutes acceptance. ACI reference ↗ · ASTM standards catalog ↗
- Identify the test type and the delivery/pour it relates to.
- Record result, unit, time and sample/specimen reference where applicable.
- Record the person/agency information required by the project procedure.
- Keep field notes factual; do not infer acceptance from an isolated result unless authorized by the applicable procedure.
Issues, deviations and supporting photos
- Describe what happened in factual language.
- Identify the relevant delivery, location or stage of placement.
- Record the action taken and status where applicable.
- Add photos that clarify the event; use captions instead of relying on memory.
- Escalate and obtain approvals through the project’s established QA/QC process.
Before closeout and handover
- Reconcile truck count and recorded delivered quantity.
- Check expected ticket references/images for gaps.
- Check expected temperatures, times and field-test entries.
- Confirm issues and actions are understandable to someone who was not on site.
- Check general pour photos and captions.
- Leave unavailable information visibly “not recorded” rather than guessing.
- Generate or assemble the final field record and route it for the required project review.
Use the pour report template for a structured field list, or view the worked report example.
QA/QC checklist FAQ
Is this a concrete inspection and test plan (ITP)?
No. It is a field-documentation checklist. Your project’s approved ITP/specification governs inspection points, test frequency, acceptance criteria and responsibilities.
Does the checklist determine whether a load passes or fails?
No. It helps you check whether the relevant record exists. Acceptance is determined under the applicable project requirements.
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 →