Complete QA/QC documentation guide for concrete construction — pour cards, cube registers, ITPs, NCRs, delivery tickets, inspection checklists, and digital record management
A professional guide to all records required for concrete construction, from pre-pour inspections through material delivery, testing, non-conformance management, and long-term retention — aligned with ACI 311, ISO 9001:2015, and international project QA standards for 2026.
Jump to any section using the links below
Concrete is irreversible. Once placed, compacted, and cured, the quality of a concrete pour is permanently locked in — it cannot be adjusted, refined, or improved. If the concrete fails to meet its design strength, has been contaminated, or was placed under non-compliant conditions, the only remedies are expensive core testing, structural assessment, and potentially demolition and reconstruction. Comprehensive record keeping is the mechanism by which project teams capture verified evidence that every concrete placement met its specification — before, during, and after the pour. These records are not administrative overhead; they are the factual foundation of structural safety, contractual compliance, and long-term asset performance.
Record keeping for concrete works serves five distinct functions: quality assurance — verifying that materials, processes, and results conform to project specifications; traceability — enabling any concrete element in a structure to be linked back to its delivery batch, mix design, test results, and placement conditions; contractual protection — providing the contractor with documented evidence of compliance in the event of disputes, claims, or defect allegations; regulatory compliance — satisfying the requirements of structural standards (ACI 318, BS EN 1992, IS 456), special inspection programs, building code requirements, and ISO 9001:2015 quality management systems; and asset management — providing future owners, facility managers, and engineers with reliable data on the as-built concrete quality for maintenance planning, structural assessment, and renovation works.
In quality management terminology, documents and records are distinct: Documents are controlled instructions used to guide work before it is done — examples include Method Statements, ITPs, drawings, specifications, work instructions, and quality plans. They can be revised and updated. Records are evidence that work has been performed — examples include concrete cube test results, pour cards, inspection checklists, and delivery tickets. Records are static: once created they should not be altered. Both are essential to a complete concrete QA system, but records are the legal and technical proof that the work was done correctly. Under ISO 9001:2015, records must be controlled, legible, identifiable, retrievable, and retained for defined periods.
The most critical window for preventing concrete quality failures is before the pour begins. Pre-pour inspection ensures that formwork is correctly set, reinforcement is properly placed and fixed, embedments and blockouts are correctly positioned, the substrate is prepared, and all preliminary requirements are met. A pre-pour inspection that identifies a problem — misplaced reinforcement, inadequate cover, damaged formwork — can be corrected in minutes. The same problem discovered after the pour requires coring, structural assessment, and potentially expensive remedial works. Pre-pour records document that all checks were completed and signed off by the responsible parties before any concrete was placed.
Completed before every concrete pour
The pre-pour checklist (also called a pre-concreting inspection report or pour approval form) is the gatekeeper document that must be signed off by the QA/QC engineer, site engineer, and — on many projects — the client's representative or consultant inspector before any concrete can be placed. It confirms that all preparatory works have been inspected and approved. No concrete should be placed without a signed pre-pour checklist on file.
Typical checklist items include:
Formal request for consultant/client inspection
A Work Inspection Request (WIR) — sometimes called a Request for Inspection (RFI-Inspection) or Inspection Notice — is the formal written request submitted by the contractor to the consultant/client representative to attend and sign off a stage of work before proceeding. For concrete works, WIRs are typically raised for: reinforcement inspection (before formwork closure); formwork inspection (before concreting); pre-pour final inspection (combining formwork, reinforcement, and embedments); and post-pour surface inspection. The WIR specifies the work location, element, date and time of proposed inspection, and references the relevant ITP hold or witness point. The consultant's signed response (accepted / rejected / with comments) forms the official approval record. WIRs are mandatory on most government, infrastructure, and large commercial projects and are a key audit trail document.
Signed off before formwork closure
The reinforcement inspection record documents the results of checking the reinforcing steel installation against the structural drawings and project specifications before formwork is closed and the element is poured. It is one of the most important pre-pour records because once concrete is placed, reinforcement cannot be inspected, corrected, or verified without destructive investigation. This record must be signed by the site engineer, QA/QC engineer, and consultant representative (if a hold point). It should be cross-referenced to the specific structural drawing revision used for the inspection and attached to the relevant pour card in the project QA file.
Records generated during the concrete pour capture the actual conditions under which the concrete was placed — information that cannot be reconstructed after the fact and is essential for demonstrating compliance with the specification, investigating problems, and validating test results. During-pour records must be completed in real time, on site, by qualified personnel. They should never be reconstructed from memory after the event. The primary during-pour record document is the Concrete Pour Card (covered in detail in Section 4), but several supporting records are generated simultaneously.
Issued by ready-mix plant with every truck load
The concrete delivery ticket (dispatch ticket or batch ticket) is issued by the ready-mixed concrete plant for every truck load and must accompany the concrete to site. It is the primary traceability link between the as-placed concrete and the approved mix design. The site QC engineer must check the delivery ticket against the specification before the load is discharged — any non-compliance (wrong grade, excessive transit time, wrong admixture, water added without authorisation) must trigger rejection of the load. All delivery tickets must be retained as part of the permanent project record.
Slump, temperature, air content — for every sample
Fresh concrete tests are performed on site on a sample taken from the middle third of the load (ASTM C172 or BS EN 12350) and must be completed within 5 minutes of sampling. Tests typically include slump (ASTM C143 / BS EN 12350-2), concrete temperature (ASTM C1064), and air content (ASTM C231) where air-entrainment is specified. Results must be recorded immediately on the pour card and compared to the specification acceptance limits. Any fresh concrete that fails slump or temperature limits must be rejected — it must not be discharged. The test result record must include the sample location, truck number, delivery ticket reference, test time, test results, acceptance criteria, pass/fail determination, and tester's signature.
Cube mould filling, curing, and dispatch log
When concrete strength test samples are taken (typically one set of cubes or cylinders per specified frequency — e.g., one set per 50 m³ or per pour, whichever is more frequent), a cube making record must be completed. This record establishes the traceability chain from the sample through the curing process to the laboratory test result. It must be completed at the time of sampling — not retrospectively. Each set of cubes/cylinders must be clearly labelled with a unique identification mark and the label information must match the cube making record exactly. Mislabelled or undocumented samples are a common source of QA audit failures and potential structural liability.
The Concrete Pour Card (also called a Pour Record Sheet, Concreting Log, or Pour Register entry) is the central QA document for every concrete placement. It consolidates all key pour-specific information onto a single controlled form, providing a complete snapshot of the pour for quality assurance, traceability, and future reference. One pour card should be completed for each discrete pour event — defined by a single continuous placement into one structural element or section. Pour cards must be signed by the responsible QC engineer and countersigned by the consultant/client representative where specified by the ITP. They are retained as permanent project records.
One pour card per pour event — never combine multiple pours or multiple elements on a single card. Complete in real time — fill in during the pour, not from memory afterward. All fields mandatory — blank fields are not acceptable; use "N/A" if genuinely not applicable. Attach all delivery tickets — staple or clip all delivery dockets for that pour to the back of the pour card. Reference cube IDs — the cube sample identification number on the pour card must exactly match the label on the cubes. Sign before concrete is placed — pre-pour sections must be signed before discharge begins; post-pour sections completed within the same working day. File within 24 hours — submit to document control within one working day of pour completion. Consultant signature — always obtain consultant's counter-signature where required by the ITP; a pour card without a required signature is an incomplete record and a non-conformance.
Material records establish that all constituent materials in the concrete — cement, aggregates, water, admixtures, and supplementary cementitious materials — meet the project specification and relevant material standards before being used. These records must be obtained before the first use of each material and updated whenever a new batch or source is introduced. Material records are a prerequisite for the mix design approval process and a key component of any QA audit or dispute investigation.
Manufacturer's conformity certificates for all materials
Material Test Certificates (MTCs) — also called Mill Certificates, Test Reports, or Certificates of Conformity — are documents issued by the material manufacturer or supplier confirming that a batch of material has been tested and meets the requirements of the applicable material standard. For concrete works, MTCs are required for: cement (per batch / delivery); coarse and fine aggregates (per source and frequency); admixtures (per product / batch); supplementary cementitious materials — fly ash, GGBS, silica fume (per batch). MTCs must reference the specific standard tested against (e.g., ASTM C150 for Portland cement; ASTM C33 for aggregates; ASTM C494 for admixtures) and must be issued by an accredited testing laboratory.
Log of all materials received on site
The Material Incoming Register (Material Receipt Register or Goods Received Register) records every delivery of concrete materials and related items received on site. It provides a chronological log of all materials — with batch/delivery details, quantities, and approval status — that can be cross-referenced with pour cards to demonstrate traceability from material delivery through to placement in a specific structural element. It also records inspection results at the time of delivery — any material received with a damaged batch, missing MTC, or visible non-conformance should be quarantined and an NCR raised before it is unloaded.
Approved mix proportions with supporting data
The Mix Design Approval Record documents the concrete mix proportions approved for use on the project — including the sources of all constituent materials — and the trial mix and historical strength data supporting the design. Per ACI 301 and ACI 318, the mix design must demonstrate that the proposed proportions will consistently achieve the specified compressive strength with an adequate margin. ACI 318 requires that strength test records used to establish mix proportions be not more than 24 months old. The mix design approval record must be submitted to and approved by the consultant/engineer before the first pour — it is a prerequisite for any concrete placement on site.
Compressive strength testing of concrete cube or cylinder samples is the primary method by which the specified concrete strength is verified. The test programme, sampling frequency, acceptance criteria, and record keeping requirements are typically defined by the project specification, the structural design standard (ACI 318, BS EN 1992, IS 456), and the applicable test standard (ASTM C39 for cylinders; BS EN 12390-3 for cubes). Strength records are among the most important permanent project records — they are the documented proof that the as-placed concrete met its design strength.
A Concrete Cube Register (or Cylinder Strength Register) is a cumulative log of all compressive strength test results for the project, organised by element, pour date, and concrete grade. It is maintained in parallel with individual laboratory test reports and provides a project-level overview of concrete quality performance. The register allows the QA engineer to identify trends, flag results approaching the acceptance limit before they become non-conformances, and demonstrate to the client and auditors that all specified testing has been completed and that results are compliant.
| Field | Description | Source | Acceptance Check |
|---|---|---|---|
| Sample ID | Unique reference matching cube label and pour card | Cube making record / pour card | Must match exactly — mismatch = NCR |
| Pour date & element | Date of pour and structural element reference | Pour card | Cross-reference with pour card |
| Concrete grade | Specified design grade (e.g., C25, C30, 4000 psi) | Delivery ticket / mix design | Matches specification for that element |
| 7-day strength result | Average compressive strength at 7 days (MPa or psi) | Laboratory test report | Typically ≥ 65–70% of 28-day target |
| 28-day strength result | Average compressive strength at 28 days (MPa or psi) | Laboratory test report | ACI 318: each result ≥ f'c − 3.5 MPa; average of any 3 ≥ f'c |
| Pass / Fail | Compliance determination vs. ACI / BS EN / IS criteria | QA Engineer assessment | Fail triggers NCR and investigation |
| Lab report reference | Laboratory report number for full traceability | Laboratory | File with pour card in project records |
| Lab accreditation | Laboratory UKAS / A2LA / NABL accreditation number | Laboratory | Must be valid at date of test |
| NCR reference | NCR number if result triggered a non-conformance | QA Engineer | NCR must be raised if any acceptance criterion fails |
ACI 318 (USA): One strength test (= one set of 2 cylinders) for each 115 m³ of concrete, for each 500 m² of slab surface area, OR for each day's pour — whichever gives the most frequent sampling. Minimum one test per pour regardless of volume. BS EN 206 / Eurocode (Europe): Initial production — one sample per 25 m³; established production — one sample per 200 m³ or one per day, subject to minimum frequency per conformity family. IS 456 (India): One sample per 50 m³ or per 5 m³ for small pours; minimum 4 samples per structure. General rule: When in doubt, sample more frequently than the minimum — over-sampling is never a problem; under-sampling means inadequate traceability and potential structural liability. For critical elements (columns, transfer structures, post-tensioned slabs), many specifications require more frequent testing than the code minimum.
A Non-Conformance Report (NCR) is a formal QA document raised whenever a material, process, or work result does not conform to the project specification, drawings, or approved procedures. NCRs are not a sign of poor quality — on the contrary, a project with zero NCRs is more likely to have a dysfunctional QA system than a perfect project. NCRs demonstrate that the QA system is working: deviations are being identified, documented, investigated, and resolved rather than being overlooked or concealed. Effective NCR management is one of the most important indicators of project quality maturity.
As soon as a non-conformance is identified — by the site engineer, QC technician, or consultant — an NCR must be raised immediately. Delay in raising an NCR is itself a quality management failure. The NCR form must document: the unique NCR number (from the project NCR register); date and time of identification; location of the non-conforming work or material; description of the non-conformance; the specification clause, drawing, or procedure being violated; and the name of the person who identified it. The non-conforming material or area must be clearly marked on site (e.g., with red tags or paint marks) and segregated or placed on "hold" — no further work should proceed on the affected element until the NCR is reviewed and a disposition decision is made.
The contractor's QC manager and site engineer investigate the non-conformance to determine its cause and extent. The NCR disposition decision must be one of four options: (1) Use As Is — the non-conformance is within acceptable tolerance or has been technically justified by the engineer as not affecting structural performance; formal engineer approval required. (2) Repair — the non-conformance can be remediated to bring it back to specification (e.g., applying a concrete repair mortar to honeycombing; adding additional cover protection). (3) Rework — the affected work must be redone to specification (e.g., demolish and reconstruct the non-conforming element). (4) Reject — the material is rejected and removed from site. The disposition must be approved in writing by the consultant/engineer before any remedial work proceeds. "Use As Is" dispositions for structural non-conformances require a formal engineer's assessment and written acceptance.
Once the disposition is approved, the agreed corrective action is implemented: repair is carried out per the approved repair method statement; additional testing (e.g., core tests to verify in-situ strength) is completed; rejected material is removed. All corrective actions must be documented with photographs, test results, and inspection sign-offs. A Corrective and Preventive Action (CAPA) record is raised alongside the NCR to document the root cause of the non-conformance and the preventive actions put in place to prevent recurrence. Root cause analysis should address not just the immediate failure but the underlying process or system weakness that allowed it to occur.
The NCR is formally closed only when: the approved corrective action has been fully implemented and verified; all required additional testing has been completed with satisfactory results; any required engineer approvals for "Use As Is" dispositions have been obtained in writing; and the NCR form has been countersigned as "Closed" by the consultant/client representative. The closed NCR, with all supporting documentation (photographs, test reports, repair records, engineer approvals), is filed in the project QA records as a permanent document. The project NCR Register (log of all NCRs) must be updated to reflect the closed status. Regularly review the NCR register at project quality meetings to identify trends and systemic issues requiring preventive action.
The Inspection and Test Plan (ITP) is the master quality control document that defines every inspection and test activity required for each work package — including who performs it, when, at what frequency, to what acceptance criteria, and what type of checkpoint applies (Hold Point, Witness Point, or Review Point). The ITP for concrete works is prepared by the contractor's QA manager, reviewed and approved by the client/consultant, and becomes a contractual quality requirement. It is the roadmap for the entire QA programme and the reference against which all inspection records (WIRs, pour cards, checklists) are issued.
Hold Point (H): Work MUST NOT proceed past this point without the written approval of the designated party (typically the client/consultant). The contractor raises a WIR and waits for the consultant to attend, inspect, and sign off before proceeding. Example: reinforcement inspection before formwork closure; pre-pour sign-off before concrete placement. Failure to observe a Hold Point is a serious contractual and safety non-conformance. Witness Point (W): The designated party is notified and given the opportunity to attend and witness the inspection or test — but work may proceed after the notification period even if the party does not attend, provided the contractor has completed their own inspection. Example: concrete cube sampling; formwork survey. Review Point (R): The designated party reviews the inspection record or test result after it has been completed and submitted — no physical attendance is required. Example: reviewing cube test reports; checking daily QA reports. The ITP lists every activity, the responsible party (C = Contractor, QA = QA Engineer, CL = Client, CON = Consultant), checkpoint type, frequency, and reference standard for each inspection or test.
| Activity | Checkpoint | Responsible Party | Frequency | Reference Standard | Record |
|---|---|---|---|---|---|
| Mix design submission & approval | H — Hold Point | Contractor / Consultant | Before first pour of each mix class | ACI 318 / ACI 301 | Mix Design Approval Record |
| Material approval (cement, aggregates) | H — Hold Point | Contractor / Consultant | Before first use; each new batch | ASTM C150, C33 | MTC, Material Approval Register |
| Reinforcement installation inspection | H — Hold Point | QC Engineer / Consultant | Each element before closure | ACI 318 / BS 8110 | Rebar Inspection Report + WIR |
| Formwork inspection | W — Witness Point | QC Engineer / Consultant | Each pour element | ACI 347 | Pre-Pour Checklist + WIR |
| Pre-pour final inspection | H — Hold Point | QC Engineer / Consultant | Each pour | Project Spec | Pre-Pour Checklist + WIR |
| Delivery ticket check | W — Witness Point | QC Engineer | Every load | ASTM C94 / BS EN 206 | Pour Card (attached delivery tickets) |
| Slump test | W — Witness Point | QC Technician | Each sample set; min 1 per load for first 3 loads | ASTM C143 / BS EN 12350-2 | Pour Card / Fresh Concrete Test Record |
| Temperature check | W — Witness Point | QC Technician | Every load | ASTM C1064 | Pour Card |
| Cube / cylinder sampling | W — Witness Point | QC Technician / Consultant | Per ACI 318 or project spec frequency | ASTM C172 / C31 | Cube Making Record + Pour Card |
| 7-day cube result review | R — Review Point | QC Engineer / Consultant | Every set | ASTM C39 / BS EN 12390-3 | Cube Register + Lab Report |
| 28-day cube result review & acceptance | R — Review Point | QC Engineer / Consultant | Every set | ACI 318 acceptance criteria | Cube Register + Lab Report + NCR if fail |
| Post-strip surface inspection | W — Witness Point | QC Engineer / Consultant | Each element after formwork removal | Project Spec / ACI 301 | Post-Strip Inspection Report |
Quality records for concrete works must be retained for defined periods after project completion — both to satisfy contractual and regulatory requirements and to support future structural assessments, investigations, or litigation if structural problems arise years or decades after construction. Retention requirements vary by jurisdiction, contract type, and record category. The following are typical guidance periods — always check the project contract and local regulations for project-specific requirements.
Physical records: Store in a fireproof, waterproof cabinet or dedicated fire-resistant document store on site during construction; transfer to permanent project archive on project completion. Protect from moisture, pests, and UV degradation. Digital records: Maintain backups on at least two separate media (server + cloud or server + USB archive), in separate physical locations. Use non-proprietary file formats (PDF/A, CSV, JPG) to ensure readability long after the software used to create them is obsolete. Photographs: Embed date/time metadata; store with GPS location tags where possible. Legibility: All handwritten records must be legible and signed in permanent ink — pencil or erasable ink is not acceptable. Security: Records are legal documents; restrict amendment access; maintain version control for any revised records; never overwrite original records.
Digital record keeping and quality management software are increasingly replacing paper-based systems on construction sites, offering significant advantages in traceability, speed, and auditability. A well-implemented digital QA system eliminates illegible handwriting, lost documents, and delayed submissions — and enables real-time visibility of quality performance across the project for all parties. However, digital records must satisfy the same fundamental requirements as paper records: they must be accurate, complete, tamper-evident, retrievable, and retained for the required period.
ACI 311.4R (Guide for Concrete Inspection) and ACI 311.5 (Guide for Inspection of Concrete) are the primary ACI references for concrete inspection and record keeping. ACI 311.4R covers inspection procedures for all stages of concrete work; ACI 311.5 provides guidance on inspector qualifications, duties, and documentation. Together they define the inspection activities, records, and reporting requirements that form the basis of any concrete QA programme on ACI-aligned projects worldwide. ACI 318 Section 26 (Construction Documents and Submittals) defines the record keeping requirements tied directly to the structural design standard.
ACI Standards →ISO 9001:2015 (Quality Management Systems — Requirements) is the international framework governing quality records in construction. Clause 7.5 (Documented Information) defines the requirements for creating, updating, and controlling quality records — including retention periods, access controls, legibility, and protection against unintended alteration. Clause 8.5 (Production and Service Provision) requires traceability records throughout the construction process. Most large construction projects and contractors are ISO 9001 certified — meaning their concrete QA records must satisfy both the project specification and the ISO standard simultaneously.
ISO Standards →Explore the full library of free professional concrete guides, QA/QC resources, structural calculators, and technical references on ConcreMetric.com — covering concrete design, construction, testing, waterproofing, durability, and repair for residential, commercial, and infrastructure projects. All content is aligned with ACI, BS EN Eurocode, and IS standards and updated for 2026 to reflect current best practice in concrete construction and quality management globally.
All Guides →