9.5 QA/QC Communication and Acceptance Context

Communicate Results Before They Become Surprises

Concrete field testing affects real-time decisions. A low slump, high temperature, unexpected air content, density problem, or specimen-curing failure can stop a placement or trigger a retest. Because the concrete is being placed now, communication must be timely, factual, and routed to the named project contact — usually the testing-agency supervisor, the engineer's representative, or the contractor's QC manager.

Understanding the acceptance context keeps the technician inside their lane. Per NRMCA/ACI practice (summarized in CIP 41):

• Acceptance testing evaluates whether delivered concrete meets the purchaser's specification.
• The sample is taken at the point of discharge into the final placement (or into the conveyance, per spec), under ASTM C172.
• Testing is performed by an ACI-certified field technician working for the owner/engineer or an independent testing agency — not the producer, to preserve independence.
• Results feed an acceptance decision made by the engineer of record, not the field technician.

QA Versus QC and Who Does What

The exam expects candidates to keep the roles straight:

Quality assurance (QA) is the owner's system for gaining confidence the concrete is acceptable; quality control (QC) is the producer's system for keeping the process on target. The Grade I technician usually works within the acceptance/QA side as the person generating the raw data. A standard acceptance strength test is defined as the average compressive strength of at least two 6×12 in. (or three 4×8 in.) cylinders from the same sample, tested at the specified age, typically 28 days.

Stay In Your Lane and Report Up

The technician's authority is to perform tests correctly and report measured results, not to accept or reject concrete. When a result is out of spec, the correct action is to inform the responsible party immediately and document the notification — "air content 3.2%, specified 6 ± 1.5%, producer and QC notified at 09:15" — and let the named decision-maker act. Stopping or approving a placement on personal judgment exceeds Grade I authority and can create liability.

Clear communication lets the contractor, producer, engineer, and testing agency respond before the concrete is placed or records are disputed. The reporting chain typically runs field technician → testing-agency supervisor / lab → engineer of record, with the producer informed so the next load can be corrected. Reports should present unusual results, invalid tests, retests, and notifications factually and without personal blame, so the record supports the project's quality decisions rather than a personality dispute.

What the Specification Controls

The project specification — not the technician's preference — sets the acceptance limits the field results are judged against. The technician must know where to find each target and tolerance before testing:

Knowing these lets the technician recognize an out-of-spec result in the field, immediately, rather than discovering it days later.

Frequency and the Bigger Picture

Acceptance strength testing is performed at a frequency set by the specification or code — for building work under ACI 318, commonly once per 150 yd³ or per 5,000 ft² of surface area, and at least once per day for each class of concrete, with a minimum number of tests per class. Each strength test is the average of the companion cylinders from one sample, so the field technician's sampling discipline directly controls the validity of the acceptance record. The technician does not set the frequency or the limits, but must execute the sampling plan faithfully and flag when a required sample was missed.

Understanding that the field data feeds a code-driven statistical acceptance system — averages, standard deviations, and the ACI 318 strength acceptance criteria evaluated by the engineer — reinforces why a single sloppy or mislabeled sample matters far beyond one truck.

This is also why independence is built into the acceptance system. The technician performing acceptance tests works for the owner or an independent agency rather than the producer, so the data that drives the accept/reject decision is not generated by the party being paid to deliver conforming concrete. The producer still runs its own quality-control tests, but those are separate from acceptance. Keeping these streams distinct — owner-side acceptance and producer-side control — is what gives the engineer confidence that the numbers reaching them are unbiased.