Concrete Pour Card and Placement Record

This template captures the key details of a single concrete pour in one place: pour identification, batch ticket and delivery details, fresh concrete test results, placement and consolidation, and final sign-off. It is useful when you need a field-ready record that ties the delivered mix to the actual placement conditions. The form helps reduce missing information that can slow down QA review or dispute resolution.

Use it for any pour where you want a traceable record, especially structural slabs, foundations, walls, columns, or work that will be reviewed by QA/QC or an inspector. It is also helpful for smaller pours when multiple trucks, changing weather, or staged placement make the record harder to reconstruct later. For very simple, low-risk work, you may choose a lighter version with fewer test fields.

The pour supervisor, field engineer, QC inspector, or concrete technician can complete it, depending on your workflow. The person filling it out should be present during the pour or have direct access to the batch tickets and test results. The final sign-off should come from the person responsible for confirming the record is complete and accurate.

Complete one record per pour, not one record per project. If a placement spans multiple truckloads, the delivery records section should capture each load within the same pour record. If the pour is split across days or locations, create a separate record for each distinct placement event so the audit trail stays clear.

Common mistakes include leaving out batch ticket numbers, recording test results without the test time, and failing to note deviations such as delayed discharge or retempering. Another frequent issue is writing vague placement notes instead of identifying the exact location or lift. The form works best when every field is completed with specific, time-based information.

Yes. You can add fields for project-specific acceptance criteria, cylinder or cube sampling, admixture checks, finish type, or inspector comments. Keep the form lean by using conditional logic so extra fields only appear when they apply. That supports data minimization and makes the record easier to complete in the field.

It can be connected to document storage, QA/QC logs, project management tools, or a digital audit trail if your workflow supports integrations. Many teams also link it to batch ticket uploads, photo attachments, and test result records. The goal is to keep the pour record tied to the rest of the project documentation without duplicating data entry.

Document the deviation in the exceptions section, describe what changed, and record the corrective action taken before sign-off. Examples include a delayed truck arrival, out-of-range slump, unexpected weather, or a consolidation issue at a specific location. If the pour cannot be accepted as placed, the record should clearly show the decision and who made it.