How to write a concrete ITP from project documents

Start with the files that control this pour

Set the work-package boundary first: identify the element and pour or lot, concrete type, included activities, exclusions, parties, jurisdiction and required client form. Then build a small source register. Use the contract and its precedence rules to identify the controlling approved revisions; a newer upload does not automatically replace a formally adopted document.

File to inspect	What to extract	How it connects to the ITP and record
Contract scope, specification and quality clauses	Included elements, referenced standards and editions, testing plan, acceptance rules, notices, H/W points, submission and release roles.	Controls CON-01, CON-08–10 and the project’s nominated responsibility, frequency and release fields.
Approved structural / civil drawings and schedules	Element limits, levels and details; cite sheet, revision, detail or schedule item rather than writing only “as per drawings.”	Connects set-out, founding, formwork, reinforcement, cast-ins, joints and finished survey checks in CON-02–08 and CON-15.
Concrete mix submission and supplier approval	Approved mix identifier and only those mix properties or restrictions that the project documents require.	Feeds CON-01 and receipt identity in CON-09; do not turn a template label into an acceptance value.
Project test plan, adopted test methods and lab arrangements	Specified fresh and hardened tests, sample basis, method/edition, specimen identification, test ages and acceptance route.	Defines CON-10 and CON-14. Link every specimen and report back to the delivered batch and pour record.
Approved placement / curing method and interface documents	Project-specific sequence, joints, finishing, curing/protection requirements, permissions and interfaces.	Provides applicable controls for CON-07 and CON-11–13, with approvals and requirements cited at field level.

Map requirements before polishing the rows

List each explicit requirement with its source file, revision and exact page, clause, drawing detail or schedule item.
Place it against the matching baseline step CON-01–CON-15. Split a row if it combines separate triggers, lots, methods or responsible parties. Add a row only when the package has a real uncovered requirement; remove irrelevant baseline items with a scope reason.
Write the method and observable pass condition in the ITP. Carry the actual frequency, role and control point only from the project documents. Where silent, mark a proposed internal check for agreement; do not create a client Hold/Witness point.
Link each plan row to the record that will carry location, observation, report or disposition. Keep the actual result, inspection date and signatures blank until work is performed.

A receipt row, from source to site record

Fictional teaching example only. SPEC-C01 and MIX-M01 below are invented document identifiers. This is a demonstration of mapping a non-numeric requirement, not a real project instruction, delivery or approval.

Illustrative source excerpt

Fictional SPEC-C01, receipt section: “Identify received concrete against the approved mix submission. Retain the delivery docket and link it to the element or pour. Refer an identity mismatch to the assigned project decision role.”

The excerpt says nothing about test frequency, delivery-time limits or external Hold Points. Those fields still need the actual governing project documents; they cannot be inferred from this excerpt.

The nine fields below form one CON-09 receipt row. The filled wording demonstrates the source mapping; bracketed entries identify information still needed from the project.

1. ID and stage: CON-09 · Concrete delivery and batch identity.
2. Inspection: Check the delivered mix identity against the approved submission and link its docket to the element or pour.
3. Method: Compare the mix designation on the delivery docket with the controlling approved mix submission. Record the docket and batch identifiers and the receiving element / pour. Identify any difference or missing traceability.
4. Acceptance criterion: In this fictional example, the docket mix designation matches the cited approved mix submission and the docket can be traced to the receiving element / pour. An identity mismatch remains open for the assigned project decision. Copy a real criterion only after checking the actual approved project source.
5. Reference: Fictional SPEC-C01, receipt section [actual approved revision and locator required]; fictional MIX-M01 [actual approved revision required]. Replace both identifiers with the project's controlled sources.
6. Frequency or trigger: [Enter the receipt inspection trigger from the project ITP / inspection requirements.] The illustrative excerpt provides no frequency; record that precise gap for confirmation.
7. Responsibility: [Enter the assigned receiving inspector and the separate identity-discrepancy decision role.] A supplier's docket and an inspector's observation are not a designer's or contract authority's approval.
8. Control or release arrangement: [Enter any applicable internal readiness step or contractual control, notice and release evidence from the project.] The illustrative excerpt creates no external Hold/Witness Point.
9. Record: Concrete delivery record: element / pour, docket and batch ID, supplied mix designation, approved mix reference, observed match or discrepancy, original docket reference and any written instruction. Actual entries, result, dates and signatures stay blank until the event.

Give CON-10 its own fresh-test and sampling row. Its method, sample basis, timing, performing/testing role and record must come from the project test plan and adopted procedure. Link the test and specimen identifiers to the CON-09 batch and pour; do not bury two different inspection triggers and roles in one combined row.

For a numeric property, locate the stated value, units, tolerance, test method and sample basis in the actual approved documents and cite their revision and locator. If a required value or permitted delivery condition cannot be found, log the exact property and decision needed. Keep the supported receipt row while resolving that gap.

Keep the delivery, test and curing trail joined

Give the pour or lot one project identifier and use it across records. For every delivery, retain the docket reference, supplied mix identifier, batch identity, delivered quantity where required, arrival/discharge times and relevant site observations. Link fresh test results and specimen IDs to that delivery and element. When results arrive, add the laboratory report reference, stated test age and disposition to the strength register while retaining the original report. Link CON-13 curing/protection observations to the same pour/lot and project requirement. This creates a traceable chain without copying the lab’s result into an ITP acceptance field.

Resolve conflicts and control points openly

When a drawing, specification, mix submission or later instruction differs, preserve both document references and revisions. Apply the contract’s actual precedence or obtain a formal instruction from the responsible design / contract authority. Do not silently choose the newest, strictest or most convenient criterion. If an essential acceptance rule is missing, identify the exact pour, property and decision needed while continuing unaffected planning.

H/W/R/S labels, notice periods and release rights come from the contract and project register. Record who performs the check separately from the lab, reviewer, client witness and release authority. Internal readiness checks can be proposed, but label them as proposed until agreed. An inspection signature does not substitute for a separate contractual release or designer’s decision.

Common drafting mistakes

Writing “as per specification” when the supplied file contains a precise criterion, unit or method that could be transcribed and located.
Using the ITP acceptance column to store actual test results; keep the governing criterion in the plan and observations in the linked record.
Assigning a sampling rate, curing duration or client Hold Point from a generic example rather than the project documents.
Retaining all baseline steps despite a narrower package, or losing the connection between a sample, delivered batch and inspected element.

Review before issue

Every retained CON-01–CON-15 step matches this package and actual sequence.
Each criterion can be found in an approved source at the cited revision and locator; unresolved conflicts and missing inputs are visible.
Frequency, test method, H/W status, notice and release role match the project documents or are clearly proposed / pending confirmation.
Docket, fresh test, specimen, lab result and curing records can all be linked to the relevant pour or lot.
The client’s required form is preserved, and no actual result, approval or signature is prefilled.

Continue with the concrete tools

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.

Need an ITP prepared for your project?

Send your drawings, specifications and contractor requirements. Receive a project-specific ITP and matching blank site records in Excel, Word and PDF.

USD 99 per defined work package · Within 24 hours after the required project files are complete.

Order project ITP · USD 99 View scope and required files