ITP vs inspection checklist: plan the check and record the result

Same receipt and test activity, two different jobs

Trace one fictional delivery from plan to evidence

Fictional teaching example only. All references and identifiers below are placeholders. No actual concrete result, project requirement, test outcome or release is claimed.

1. Plan before the pour. The ITP row cites [approved project specification, revision and clause], [mix submission and revision] and [project test plan / method and edition]. It identifies which docket details, specified fresh checks and sampling basis are required. The project values and frequency are copied from those files or flagged as missing.
2. Record the delivery. The site record captures the actual pour / lot, element, docket and batch IDs, mix designation, quantity if required, arrival and discharge times, and relevant observations. It leaves measurement/result fields blank until the event occurs.
3. Link test evidence. The fresh-test entry links the actual procedure, operator, sample ID and delivery batch. The lab report later links the specimen to the same element / pour, its stated test age, report identifier and project disposition. Preserve the original report; a checklist summary is only an index.
4. Close the trail. Link the pour to placement and curing records, outstanding issues, authorised instructions and any required release. Keep the assigned contractor, laboratory, reviewer, witness and release roles distinct.

What the checklist cannot replace

A completed checklist records observations and references. It does not replace the laboratory’s original raw data, test certificate or report; the contract specification; the approved mix submission; a designer’s technical decision; or evidence that a contractual Hold Point was released by the assigned authority. Do not reduce a required test report to a tick marked “passed.” If the project’s ITP form is intentionally completed progressively as its checklist, the form can combine plan and record fields, but the planned criterion and actual result still need to be identifiable separately.

Who controls each decision?

The contract and approved project documents control the requirement, method, test frequency, notice and external release rights. The contractor’s assigned person records the check; the nominated testing provider performs the required test; and the designated reviewer, witness or release authority acts only within the role given by the project. Never infer that an absent witness permits work to proceed, or that an inspector’s signature approves concrete strength.

Common record failures to prevent

• A single tick says “concrete accepted” but does not identify the batch, docket or criterion.
• The sample number exists, but no record connects it to the delivery, pour/lot, element or original lab report.
• The ITP cites “as per specification” without enough detail to locate the governing requirement.
• A template assigns an assumed sample rate, curing period, hold point or release role that the project never adopted.
• A checklist is treated as proof of a test even though the original report or required raw evidence is missing.
• A deviation is closed by the person who observed it without an instruction from the project’s assigned decision-maker.

Use a field record that matches the planned work

For the concrete receipt/testing sequence, start with the delivery record and test record; follow the same pour/lot identifier into the curing record. The records are blank prompts. Populate acceptance criteria, test method, frequency and roles from the actual approved project files. Then review the concrete ITP baseline or open its browser editor.

Sources and limits

• CQA, “How to create an Inspection and Test Plan”

  Checked 7 October 2026; sections “Developing the ITP” (requirements, sequence and row controls) and “Using ITPs” (review, briefing and records). This is general planning guidance, not a concrete acceptance specification or authority to set project values.

• NSW Government, Quality Management Guidelines for Construction

  Checked 7 October 2026; page sections for quality management, contract examples and Appendix D (ITP guidelines and checklist download listing). Contract clauses shown on the page apply only when included in the relevant contract; the linked Appendix D file is listed here but was not inspected for detailed requirements.

• Queensland Department of Transport and Main Roads, MRTS70 Concrete, July 2022

  Checked 7 October 2026; Sections 9–12 (mix, delivery, fresh concrete and hardened concrete testing), 14 (defects and rectification), 15 (in-situ concrete), and 17 (normal-class concrete). It is a Queensland transport and infrastructure contract specification. It supports topic selection when relevant, not default building criteria; use its clauses only if the actual project adopts the applicable edition and provisions.

• Hutchinson Builders, Safety & Quality Planning downloads

  Checked 7 October 2026; the page lists “040 Concrete Place ITP” and its report as examples. Used only to corroborate a practical sequence and the separation of plan and report; these examples are not standards and establish no universal values, test rates or contract control points.