9.3 Documentation and Report Accuracy

A Field Report Is a Chain of Evidence

A field report should let someone reconstruct what concrete was sampled, where it came from, when it was tested, which methods were used, what was measured, and whether anything unusual happened. The report is not just a place to copy final numbers. It is the project record that connects fresh concrete results, strength specimens, batch information, environmental conditions, and communication decisions.

The best documentation starts during the work. Write down sample time, test time, truck or batch identification, placement location, weather or exposure concerns when relevant, technician name, and method-specific readings. Do not rely on memory after the placement is over. Several trucks can look similar on a busy jobsite, and one wrong identifier can make a correct test result useless.

Correction factors and calculations need the same discipline as raw readings. For pressure air testing, the aggregate correction factor must be handled according to the method and recorded where the project form requires it. For volumetric air testing, alcohol correction and final reading logic need careful attention. For density, the empty measure mass, filled measure mass, measure volume, and unit conversions should be checked before the final value is reported.

Specimen documentation is often where a small mistake becomes a long problem. Cylinders or beams may not be broken until days or weeks later. If the labels are incomplete, duplicated, smeared, or inconsistent with the report, the lab may not be able to connect strength results to the correct placement. Initial curing conditions and transport notes also matter because poor early curing can affect strength and create disputes unrelated to the mixture itself.

Good reports separate facts from interpretation. A fact is that the measured slump was a stated value, the air meter reading was adjusted by the recorded correction factor, or the second slump test also sheared. An interpretation is that the contractor caused the problem or that the structure will fail. The technician should record the facts and any required notification, then let the responsible quality personnel make acceptance or engineering decisions.

Use this field documentation checklist:

1. Record sample identification and time before moving to final numbers.
2. Capture method-specific raw readings and corrections, not just the polished result.
3. Note repeated, invalid, delayed, or abandoned tests with a concise reason.
4. Label specimens immediately using the project-required format.
5. Match specimen IDs to the report before leaving the sampling area.
6. Document required QA/QC notifications, including time and recipient when required.
7. Review the report for blanks, unit errors, impossible values, and mismatched truck numbers.

On the exam, documentation questions often reward the answer that keeps the record objective, complete, and traceable. A neat report with missing sample identity is not a quality report. A report that honestly identifies an invalid test and a repeat test is stronger than one that hides the problem and leaves future reviewers guessing.