An Inspection and Test Plan (ITP) is a structured quality document that defines, for every construction activity, what needs to be inspected or tested, how it should be done, how often, and who has authority to sign off before work continues. On most civil and infrastructure contracts in Australia, an ITP is a contractual requirement — not optional.

What Goes in an ITP

A properly structured ITP has a row for each significant construction activity, covering:

• Item number — hierarchical (1.0, 1.1, 1.2…) following construction sequence
• Activity description — specific to the scope, not generic boilerplate
• Reference documents — exact AS/NZS standard clause or spec clause number
• Inspection or test method — how the check is actually performed on site
• Acceptance criteria — a measurable pass/fail threshold, never just "as per spec"
• Frequency — how often the check occurs (1 per 200m³, each pour, etc.)
• Hold, Witness, and Review points — who must be present and when work can proceed
• Sign-off columns for both contractor and client or engineer

Why Vague ITPs Fail

The most common failure in ITPs is acceptance criteria written as "as per specification" or "to engineer's satisfaction." These phrases are unenforceable on site. If your inspector can't determine pass or fail without picking up a separate document, the ITP isn't doing its job. Every criterion should be self-contained: the threshold, the test method, and the standard — all in the same row.

The Business Case for a Good ITP

Beyond contract compliance, a thorough ITP creates an auditable record that protects you if defects are disputed. It removes ambiguity about what constitutes acceptable work, which reduces arguments between contractor and superintendent. And it creates a sequenced inspection checklist that site supervisors can actually use rather than ignore.

Projects with well-structured ITPs consistently report fewer non-conformances, faster principal approval of work, and a reduced rework rate — because problems are caught at the inspection stage, not after concrete is poured or fill is covered.

How Long Does It Take to Write One?

A thorough ITP for a medium-complexity civil package — earthworks, drainage, and pavement — can take a full day or more to write from scratch. Researching the applicable standards, cross-referencing the project specification, and formatting the document correctly is time-consuming work that takes an experienced engineer away from the site.

That's the problem InstantITP solves. Upload your project drawings and specification sheets, and the AI produces a structured, standards-referenced ITP in minutes. You review, adjust for site-specific conditions, and issue. The heavy lifting is done.

Rework on earthmoving projects is expensive in a way that's hard to overstate. Removing and recompacting fill that failed density testing costs machine hours, delay, and sometimes sub-base or pavement material above it. Almost every instance is traceable to one of two causes: a missed inspection, or an acceptance criterion that wasn't clear enough to enforce.

Where Rework Comes From

The most common rework triggers on earthmoving jobs are:

• Compaction testing not done at the required frequency, so failing areas aren't caught until later layers are in place
• Layer thickness not controlled, resulting in compaction that can't be achieved regardless of effort
• Subgrade not inspected before sub-base placement — soft spots hidden until pavement failure
• Fill material accepted without adequate classification testing, meaning unsuitable material ends up in a structural zone
• Hold points skipped under schedule pressure, with sign-off obtained retrospectively (or not at all)

How a Properly Structured ITP Closes the Gaps

A good earthworks ITP specifies testing frequency with actual quantities — not just "test each layer" but "1 nuclear densometer test per 200m³ per lift, minimum 3 tests per lot." This removes the ambiguity that allows testing to be skipped when the site is busy.

Hold points at subgrade inspection and formation level survey mean that work physically cannot proceed past those stages without a signature. The superintendent or engineer has to attend, or the contractor has proof they notified and can document the missed attendance.

The Cost of Getting It Wrong

On a typical civil earthworks package, rework from a failed compaction zone — stripping back, reprocessing, and retesting — can cost $15,000 to $50,000 depending on the extent. That's before you account for delay to follow-on trades, extended hire of plant, and the impact on project programme.

A thorough ITP costs a day of an engineer's time to write — or minutes with InstantITP. The return on investment for catching one compaction failure early is immediate.

Practical ITP Improvements for Earthmoving

• Define lot sizes so testing coverage is unambiguous
• Include a moisture content check alongside every density test (within ±2% of OMC)
• Add a separate row for fill material acceptance at delivery — classification, PI, grading
• Make proof rolling a mandatory hold point before any pavement layer
• Include formation level survey as a review point — as-built vs design tolerance

Tailings storage facilities are among the highest-consequence structures built in the mining industry. When they fail — as has happened catastrophically at Brumadinho and Mount Polley — the result is loss of life, environmental destruction, and liability that ends companies. The quality assurance framework around TSF construction exists for exactly this reason, and an ITP is at the centre of it.

What Makes TSF QA Different

Standard civil earthworks QA is rigorous. TSF QA is a step above that. Key differences include:

• Mandatory independent verification — an Owner's Engineer or Independent Tailings Review Board often reviews all ITP records, not just spot-checks
• More hold points — every lift, every zone change, every drainage layer typically requires sign-off before proceeding
• Material traceability — where fill came from, when it was tested, and what the results were must be fully traceable for the life of the facility
• Regulatory reporting — in Queensland and WA, DNRME and DMIRS require documented QA records as part of ongoing compliance

The ITP Structure for a TSF Raise

A TSF raise ITP typically covers: foundation preparation and subgrade inspection, filter and drainage layer placement and testing, embankment fill zoning (core, shell, rockfill), compaction testing per zone and lift, piezometer and instrumentation installation, crest level survey and freeboard confirmation, and spillway and decant structure inspection.

Every one of these has a Hold Point at the completion of each stage. The consequences of proceeding without sign-off are not just a non-conformance — they're a potential structural integrity failure.

Documentation Standards

TSF ITPs must be retained for the life of the facility, which in practice means decades. All test records — density tests, gradation analyses, permeability tests — must be filed against specific lots and coordinates. Digital documentation platforms are increasingly required by clients precisely because paper records are inadequate for this purpose.

The Cost of QA Shortcuts

There is no scenario in which skipping a hold point or inadequately documenting a test on a TSF is worth the risk. The liability exposure for a dam failure vastly exceeds any schedule saving. On these projects, the ITP is not a compliance box-tick — it is the primary mechanism for demonstrating that the structure was built to design intent.

Paper ITPs have been the default on civil construction sites for decades. They work — until they get wet, torn, left in a ute, or filled out in pencil and scanned at 40% quality into a project management system that no one can navigate. The shift to digital ITP documentation is underway across the industry, and for contractors who make the switch properly, the benefits are immediate.

The Problems with Paper

• Sign-off can't be tracked in real time — superintendents are chasing paper at hold points
• Version control is a nightmare — field teams may be using outdated ITP revisions
• Test results sit in lab reports disconnected from the ITP row they belong to
• Audit preparation means physically finding and scanning hundreds of pages
• Non-conformances are hard to identify until someone manually compiles the records

What Digital ITP Platforms Actually Offer

The best digital QA platforms — and even a well-structured Excel ITP — solve the most painful paper problems. Real-time hold point sign-off via mobile, automatic version control so everyone always has the current ITP, linked test results directly against the relevant row, and instant reporting for audits and client progress reviews.

Excel Is Still a Valid Starting Point

Not every contractor needs a full QA platform on day one. A well-formatted Excel ITP — with properly structured columns, locked headers, and consistent row formatting — is far more usable than a Word document or a paper form. It's searchable, version-controllable, and can be shared instantly.

InstantITP generates structured Excel ITPs directly from your project specifications. The output is a formatted, print-ready workbook with all the right columns, referenced standards, and hold point assignments — ready to use or import into your existing platform.

The Transition Step Most Contractors Skip

Most contractors go from paper straight to trying to implement an expensive QA platform — and then go back to paper when adoption fails. The missing step is a standardised ITP template that works digitally. Get that right first, then the platform migration is straightforward because the data structure is already clean.

H, W, and R are the three notification and control types on any ITP. They're straightforward in principle — but mixed up constantly in practice, which leads to either non-conformances (work proceeding past a mandatory stop) or unnecessary project delays (treating a review point as though it requires on-site attendance).

Hold Point (H) — Mandatory Stop

A Hold Point is a mandatory stop. Work cannot proceed past this activity without an authorised sign-off from the nominated party. If the hold point is not signed, the next activity is a non-conformance — regardless of how good the work looks.

Hold Points belong at activities where: the work will be permanently concealed; a defect at this stage cannot be rectified without major rework; safety-critical connections are being made; or the contract explicitly requires it. Typical Hold Points: subgrade inspection before fill placement, pre-pour inspection before concrete, foundation completion, and utility crossings.

Witness Point (W) — Attendance Expected, Not Mandatory to Halt

A Witness Point means the nominated party should attend and observe, but if they've been given reasonable notice and don't attend, the contractor can proceed and document that notice was given. Work is not stopped by a missed witness point — provided the notification process is followed correctly.

Witness Points suit: concrete sampling (slump, cylinders), in-situ compaction testing, pipeline pressure tests, material delivery inspections, and critical plant installation.

Review Point (R) — Documentation Review

A Review Point means submitted records — certificates, test reports, survey data, method statements — are reviewed by the nominated party. No site attendance required. This is the most common point type and applies to most activities on a properly structured ITP.

A Simple Decision Rule

• H — if you can't undo it without demolishing something, it's a Hold Point
• W — if a test is being run on site and the result matters to the client in real time, it's a Witness Point
• R — everything else with a paper trail goes here

Most activities will have an R. Many will have a W. Only the genuinely critical, irreversible stages get an H. Over-assigning Hold Points slows a project unnecessarily; under-assigning them removes the protection both sides of the contract rely on.

The subgrade is the foundation for every pavement layer above it. If the subgrade is soft, uneven, or inadequately compacted, the pavement fails — regardless of how well the base course and wearing surface are constructed. The ITP at this stage is your last line of defence before that foundation is buried forever.

What Subgrade Preparation Covers

A complete subgrade ITP section should cover: bulk earthworks trimming to formation level, proof rolling to identify soft spots, in-situ strength testing (DCP or plate load), moisture conditioning and remediation of wet or dry areas, final compaction testing, formation level survey, and the hold point inspection before any sub-base material is placed.

Compaction Testing Frequencies

Vague frequency is the most common weakness in earthworks ITPs. Typical acceptable frequencies for subgrade compaction testing:

• Road subgrade: 1 nuclear densometer test per 500m² minimum, or as directed by the project specification
• Pavement subgrade (MRTS05): 1 test per lot, lot size defined in specification (typically 500–2000m²)
• Trench backfill: 1 test per lift, every 20–50LM depending on trench criticality
• Structural zones: 1 test per 50m² per lift

Acceptance Criteria to Specify

• Density: ≥95% Standard Maximum Dry Density per AS 1289.5.4.1 (or ≥98% for pavement subgrade per project spec)
• Moisture content: within ±2% of Optimum Moisture Content
• DCP: CBR ≥ 3% (formation) or ≥ 15% (subgrade) depending on the layer and specification
• Surface tolerance: ±15mm from design formation level

The Subgrade Hold Point

The subgrade inspection before any sub-base placement is always a Hold Point. It is the most important single inspection on a pavement project. If this hold point is skipped — even under schedule pressure — and a defect is found later, the cost of investigation and potential remediation (including removing sub-base material placed above) far exceeds any time saved.

Your ITP should state it plainly: "Subgrade inspection and sign-off required prior to placement of any granular sub-base material. Work shall not proceed without authorised sign-off from the Superintendent."

A Quality Management Plan that gets returned for revision costs you time, delays contract start, and signals to the client that your QA capability is uncertain. Most revision requests are entirely avoidable — they come from the same structural gaps and content omissions that experienced reviewers flag every time.

What a QMP Must Cover

A QMP for a civil infrastructure project typically requires:

• Quality policy and objectives — your organisation's commitment and measurable targets for this project
• Organisation chart and responsibilities — who is responsible for QA on site, who they report to, who the independent reviewer is
• Document control procedure — how drawings, specs, ITPs, and non-conformance reports are managed and version-controlled
• ITP register — a list of all ITPs that will be prepared, referenced by work package
• Non-conformance procedure — what happens when something fails inspection, how it's documented, resolved, and closed out
• Corrective and preventive action process — how systemic issues are identified and addressed
• Inspection and testing register — cross-reference of all testing required across the project
• Hold point management — how hold points are notified, attended, and signed off
• Records management — how QA records are stored, retained, and made available for audit

The Most Common Rejection Reasons

• No named individuals in the org chart — generic job titles without names are rejected on most government and major contractor projects
• ITP register that doesn't match the scope of works — listing generic ITPs rather than the actual work packages in the contract
• Non-conformance procedure that describes the concept but doesn't include the actual NCR form or workflow
• No reference to the specific project specification clauses that govern QA requirements

The One Thing That Speeds Approval

The fastest path to approval is showing the reviewer that your QMP was written for this project — not copied from a previous one with the project name changed. Reference the specific contract number, the principal's QA requirements document, and the relevant specification clauses. Reviewers can tell within two pages whether a QMP is genuine or a template job.

Mining infrastructure projects operate under a different set of QA expectations to standard civil work. The clients are more sophisticated, the hold point requirements are stricter, the tolerances are tighter, and the consequences of a non-conformance — particularly on haul roads, ROM pads, and processing plant foundations — can shut down operations worth millions of dollars per day.

What's Different About Mining QA

• More hold points per activity — mine sites routinely require hold points at stages that would only be witness points on a civil road project
• Independent verification — an Owner's Representative or Independent Certifier reviews ITP records, often in real time via a shared digital platform
• Tighter compaction specs — haul road subgrades at ≥98% Modified MDD are standard; standard civil specs of 95% Standard MDD won't be accepted
• Full material traceability — every load of fill, every batch of concrete, every tonne of aggregate must be traceable to source, delivery docket, and test certificate
• Zero tolerance for retrospective sign-off — on most tier-1 mine sites, a hold point signed after the fact is an automatic NCR

Haul Road ITP Requirements

Haul road construction ITPs on mining sites typically require: subgrade CBR ≥ 15% (some sites require ≥ 20%), compaction to ≥ 98% Modified MDD at every lift, separate lot-by-lot testing rather than statistical sampling, drainage layer grading verification, and capping layer DCP testing. Formation level surveys are required before each layer and compared against design at every section.

Lessons from the Field

The most consistent lesson from contractors working on mine sites for the first time: underestimating the documentation burden. A hold point on a mine site may require a written notification 24 hours in advance, attendance by the Owner's Rep, a signed ITP record, a geotechnical certificate, and a photograph file — all before the next layer can start. Build this time into your programme from the start.

The second lesson: don't recycle your civil road ITPs for mine site work. The acceptance criteria are different, the standards referenced are often company-specific rather than purely AS/NZS, and the hold point frequency needs to be significantly higher. A generic ITP on a mine site will be rejected at the first review.

Concrete ITPs are among the most important — and most audited — quality documents on any civil project. Once concrete is poured, defects are expensive to remediate and sometimes impossible to fix without demolition. The ITP is what ensures every pre-pour condition is verified and every test is captured before the next stage begins.

Pre-Pour: The Critical Hold Point

The pre-pour inspection is always a Hold Point. Every item on the pre-pour checklist must be verified and signed off before any concrete is placed. The checklist typically covers:

• Formwork dimensions, levels, and stability — checked against approved shop drawings
• Reinforcement placement — bar size, spacing, cover (to AS 3600 or MRTS35 as applicable)
• Embedments, anchor bolts, and cast-in items — position and orientation verified
• Construction joints — surface preparation, cleanliness, and bond breaker application
• Concrete mix design approval — mix confirmed as per approved design and batch plant records
• Delivery dockets — batch plant, mix ID, water-cement ratio, admixture records

During Pour: Witness Points

Concrete placement testing is typically a Witness Point. The nominated party should attend to observe sampling and testing. Tests to specify:

• Slump test per AS 1012.3.1 — at point of discharge, frequency per spec (typically every 50m³ or each truck for critical pours)
• Air content (if air-entraining admixture specified) per AS 1012.4
• Concrete cylinder sampling per AS 1012.9 — typically 3 cylinders per 50m³, or as per spec
• Temperature — in hot or cold weather concreting, temperature at point of discharge

Post-Pour: Curing and Strength

• Curing method and duration confirmed — wet hessian, curing compound, or formwork retention as specified
• Formwork strike time — verified against minimum strength requirement (typically 15 MPa compressive, confirmed by cylinder test or maturity method)
• 28-day cylinder results — Review Point, results submitted to engineer and compared against specified characteristic strength (f'c)
• Surface finish and tolerance — checked against specification before any follow-on trades

Acceptance Criteria to Specify

Never leave concrete acceptance criteria as "as per AS 3600." Write them out: "28-day compressive strength ≥ f'c = 32 MPa per AS 1012.9. Slump 80–120mm per mix design. Cover to reinforcement: 40mm minimum to AS 3600 Table 4.10.3."

Sub-contractor ITP non-compliance is one of the most consistent frustrations for principal contractors and project quality managers. The common assumption is that subs don't care about quality. The reality is different: most sub-contractors aren't anti-quality — they've just never been given a clear, usable ITP and the practical training to implement it on site.

Why Sub-contractors Struggle

• They receive the ITP too late — handed over after mobilisation, after some work has already started
• The ITP wasn't written for their scope — a generic earthworks ITP given to a drainage sub doesn't tell them what they need to check
• Hold point notification process isn't explained — they don't know who to call, how much notice to give, or what documentation is needed
• The ITP format is intimidating — a 15-column spreadsheet with 80 rows is not intuitive to a small business operator whose background is operating machinery
• There's no follow-up — if no one reviews their ITP records for the first three weeks, they assume it doesn't matter

What Actually Works

Scope-specific ITPs. A drainage sub should receive an ITP that covers only drainage — pipe bedding, jointing, pit construction, backfill, and CCTV. Not a 10-section document where they have to find their three relevant rows.

A 10-minute induction to the ITP. Walk the sub-contractor foreman through the ITP on day one. Cover the three hold points in their scope, show them how to fill out the sign-off column, and explain the notification process for witness points. Ten minutes saves ten arguments.

Weekly ITP record reviews. If a quality manager checks ITP completion weekly and gives feedback — even a five-minute conversation — sub-contractors catch on fast. The records improve because someone is paying attention.

The Structural Fix

The root cause is usually that the principal contractor doesn't have time to write scope-specific ITPs for every sub-package. A full project might have 8–12 sub-contractor scopes, each needing a tailored ITP. That's where InstantITP changes the equation — generate a scope-specific ITP for each sub-package in minutes, not a day per package.

Writing a thorough ITP from scratch has always been one of the more time-consuming tasks in civil QA. A complex package — earthworks, drainage, pavement, and concrete — done properly takes a full day or more. Researching applicable standards, cross-referencing the specification, structuring the document, formatting it correctly. It's important work, but it's a poor use of an experienced engineer's time when the bulk of it is systematic and repeatable.

What AI Changes About ITP Writing

AI-powered ITP generation doesn't remove the engineer from the process — it removes the repetitive, time-consuming part. The AI reads your project drawings and specification sheets, identifies the relevant work activities, matches them to the applicable Australian Standards and MRTS requirements, assigns hold points and witness points based on the nature of each activity, and generates a structured, formatted ITP in minutes.

The engineer's job becomes review, refinement, and the application of site-specific knowledge that no AI can supply — the subcontractor relationship nuances, the specific client preferences, the site constraints that aren't in the drawings.

What the Output Actually Looks Like

An InstantITP-generated ITP for a civil earthworks and pavement package typically includes:

• Pre-construction activities — mobilisation, survey, services identification
• Earthworks — clearing, excavation, fill placement, compaction testing with correct AS 1289 references and frequency
• Subgrade — formation level, proof rolling, hold point inspection before sub-base
• Pavement — sub-base, base course, wearing surface with MRTS references where applicable
• Drainage — where identified in the uploaded documents
• Concrete — pre-pour hold point, placement witness points, 28-day review points

Every row has specific, measurable acceptance criteria — not "as per specification." Every hold point is correctly assigned. The output is a formatted Excel workbook, ready to review and issue.

The Right Way to Use It

Upload your specification sheets — not your full drawing set. The specification sheets contain the quality and testing requirements; the full drawing set contains geometric information the ITP doesn't need. A focused 5–10 page specification upload produces a better output than a 200-page drawing set.

Review the output against your contract before issuing. The AI doesn't know your specific client, your sub-contractor arrangements, or any verbal requirements from the pre-construction meeting. Add those details after generation. The result is an ITP that would have taken a day to write, produced in minutes and finalised in an hour.