Template

Most ITPs Are Just Checklists. That’s a Problem.

Craig Harris Published 6 July 2026Updated 29 August 2026 16 min read

An Inspection and Test Plan (ITP) should do more than list checks. It should turn drawings, specifications and contract requirements into a sequence the site team can follow — and leave enough evidence to prove what happened for every lot of work.

This guide gives you an adaptable civil construction ITP template, explains Hold and Witness Points without pretending every contract uses the same rules, and shows what a completed ITP record should look like. It also explains where ISO 9001 fits — and where it does not.

What Is an Inspection and Test Plan?

An ITP is controlled information that sets out the inspections, tests and verification steps for a defined construction activity. It answers six practical questions:

What must be checked or tested?
When in the work sequence must it happen?
How will the check be performed?
What requirement determines acceptance?
Who performs, reviews and releases it?
What record proves the result?

On Australian civil and infrastructure projects, ITP requirements commonly sit within the contract's quality specifications. For example, Queensland TMR's MRTS50 Specific Quality System Requirements and Transport for NSW's Q6 Quality Management System specify detailed ITP content for work under those contracts. They are useful benchmarks, but they are not substitutes for your own contract.

When do you need one?

ITPs are normally prepared for activities or work packages where conformity must be demonstrated in a planned sequence. Common civil examples include:

earthworks, embankment and subgrade preparation
in-situ and precast concrete
drainage pipes, culverts, pits and headwalls
unbound pavement, asphalt and sprayed seals
structural steel, welding and bolting
services, utilities and trench backfill
erosion and sediment controls
protective coatings, waterproofing and commissioning

The right breakdown follows the work, risk and contract — not an arbitrary target number of ITPs.

ISO 9001 and ITPs: The Accurate Connection

Yes, a good ITP can support an ISO 9001-aligned quality management system. But ISO 9001 does not prescribe a universal ITP template, and having an ITP does not by itself demonstrate ISO 9001 compliance.

ISO's official guidance on documented information lists test and inspection plans as information that may add value to a quality management system. Where an organisation uses them, they should be controlled as documented information: approved, identifiable, available where needed, protected from unintended change and retained as appropriate.

ISO 10005:2018 provides guidance on establishing and using quality plans. It is guidance, not a separate set of certification requirements. The practical lesson is simple: use an ITP as part of the wider system of planning, competence, document control, monitoring, nonconformance management and improvement.

The Difference Between a Template and a Quality Record

A blank, approved ITP is the plan. It defines what the team intends to inspect and how conformity will be decided.

Once the team adds the actual lot, results, evidence, names, dates, signatures, releases and nonconformance references, it becomes part of the quality record for that work. This distinction matters: a polished template proves that planning occurred; it does not prove that a particular layer, pour or pipeline was accepted.

For every completed lot, a reviewer should be able to trace:

requirement → inspection or test → result → evidence → acceptance decision → authorised sign-off

Civil Construction ITP Template

Start with document control. At minimum, identify the project, contract, activity, work area, ITP number, revision, status, author, reviewer, approver and approval dates. Define the scope and how lots will be identified. List the governing drawings, specifications, standards and approved procedures by current revision.

Then build the inspection schedule in work order. The TaskRox example below keeps the governing standard or specification separate from the inspection method, acceptance criteria and record produced.

A current TaskRox ITP inspection schedule. Open the image to inspect the full-size interface.

Fields every effective row needs

Activity / description: a specific activity in construction sequence, not a broad heading such as “earthworks”.
Control: the Hold, Witness, Review, inspection or test control that applies, including its type and notice requirement.
Responsibility: who performs the check, reviews the result, decides conformity and closes the lot. These may be different people.
Standard / specification: the exact technical specification clause, Australian Standard, drawing, contract clause or other governing requirement that sets the acceptance basis.
Method: how the inspection or test will be performed, including calibrated equipment or laboratory requirements where applicable.
Frequency: an unambiguous sampling rule — not “as required” unless the governing requirement genuinely says that.
Acceptance: an objective pass/fail basis traceable to the nominated standard or specification.
Records: the evidence expected, such as a checklist, survey, test report, delivery docket, certificate, photograph or NCR reference.
Contractor and principal status: the actual verification outcome for the correct lot and item, supported by the required names, signatures and dates.

Hold Points, Witness Points and Other Control Codes

H, W and R are common labels, but their exact meaning comes from the contract. Some projects also use inspection, surveillance, monitoring, test, milestone or document-review codes. Put a legend in the ITP and never assume a code has the same effect on every project.

Hold Point (H)

A Hold Point is a defined stop in the work. The contractor gives the required notice, submits the required evidence and does not proceed beyond the point until the authorised party releases it in the manner required by the contract. TMR MRTS50, for example, requires written release of its Hold Points.

Typical applications include:

foundation or subgrade acceptance before it is covered
reinforcement and embeds before a concrete pour
material or mix-design approval before use
acceptance of testing before placing the next layer

Witness Point (W)

A Witness Point gives the nominated party an opportunity to attend. The contractor still completes its own inspection and gives the specified notice. Whether work may proceed after the notice period, an attendance waiver or another event is contract-specific. Do not describe a Witness Point simply as a “less strict Hold Point”.

Review Point (R) and inspection/test activities

A Review Point usually involves assessing information such as drawings, certificates, survey records or test results. An inspection or test activity records a check performed on the work. Neither label removes the need to state who acts, what acceptance means and what evidence remains.

A reliable control-point workflow

The contractor completes its own inspection and assembles the required evidence.
The contractor gives the correct notice to the nominated party.
The party attends, waives attendance or allows the notice process to conclude as the contract permits.
Any Hold Point receives explicit release before work proceeds.
The result, evidence and release are recorded against the correct lot and item.
Nonconforming work is identified, controlled and linked to an NCR or other required process.
The next work step begins only when all applicable conditions are satisfied.

Four Adaptable ITP Examples

These outlines show useful sequencing only. The governing project documents must supply the real test frequencies, tolerances, acceptance values, roles and control points.

Earthworks and subgrade

Use rows for survey and clearing limits, foundation preparation, unsuitable material, material-source approval, moisture conditioning, layer thickness, compaction testing, proof rolling where specified, final level and lot closeout. Keep the lot definition aligned with how material, layers, locations and test results can actually be traced.

In-situ concrete

Typical stages include current drawings and approved mix, excavation or substrate, formwork, reinforcement, cast-ins and embeds, pre-pour release, delivery checks, sampling and testing, placement, curing, stripping, finish, dimensions, repairs and closeout records. A single “inspect concrete” row is rarely enough to control this sequence.

Drainage and culverts

Consider material approval and delivery, set-out, excavation, foundation or bedding, line and level, joints, connections, embedment, backfill layers, compaction, end structures, cleaning, testing where required, CCTV where specified, as-built survey and closeout. Record what can no longer be inspected once buried before covering it.

Unbound pavement

Useful stages include underlying-layer release, material-source compliance, delivery and segregation checks, layer placement, moisture conditioning, level and thickness, density or other specified testing, surface shape, proof rolling where required, trimming, protection and final acceptance. Tie every test result to the correct lot and layer.

Five Tests for Every ITP Row

Before approving an ITP, ask:

Can a field user understand exactly what must happen next?
Is the acceptance decision objective and traceable to a requirement?
Is the inspection or testing frequency unambiguous?
Are the responsible person, notified party and release authority clear?
Does the row name the record that will prove completion?

If any answer is no, the row is not ready for the field.

Common ITP Failures — and How to Prevent Them

Copying the previous project

Reusing a structure can save time; reusing its technical content without reconciliation can import the wrong drawings, clauses, frequencies and control points. Build a requirement cross-check for every reused ITP.

Vague acceptance criteria

Terms such as “satisfactory”, “correct” or “as required” do not explain how conformity will be decided. State the measurable criterion or point directly to the controlling clause.

Confusing test frequency with lot size

The lot defines the work represented by the record. The testing frequency defines how much verification is required within or across those lots. State both clearly and make sure the test report identifies the represented lot.

Missing notice and release rules

Marking a row “H” or “W” is incomplete if the ITP does not identify the notified party, required notice and release or attendance process.

Recording results after work is covered

Retrospective entries weaken traceability and may leave hidden work unverifiable. Make the inspection sequence usable in the field and attach evidence when the check occurs.

Losing the NCR connection

If a test or inspection fails, the affected item and lot should not continue to look unconditionally accepted. Link the NCR, disposition, reinspection or retest and final decision to the original record.

Using the wrong revision

Review the ITP when drawings, specifications, methods, suppliers, acceptance criteria or contract control points change. Distribute the approved revision and withdraw superseded field copies.

Treating principal verification as transferred responsibility

Principal or superintendent involvement does not normally remove the contractor's responsibility to control its work. State each party's role without turning third-party attendance into the contractor's primary inspection system.

From ITP Checklist to Connected Quality Control

TaskRox currently provides an ITP register, reusable templates, structured inspection schedules, control-point fields, lot records, a lot-by-item sign-off grid, contractor and principal verification states, connected evidence history, configurable item prerequisites, and a closeout completeness check that produces a controlled closeout pack. Prerequisites are evaluated separately for each lot and can either block a governed action or remain visible as a warning. The screenshots below use demonstration project data and show the shipped interface.

TaskRox today: the ITP register, lot-by-item sign-off record and signed verification history. Open an image to inspect the full-size interface.

Knowing when a lot is actually finished

Closeout readiness is calculated from the record, not asserted by whoever is closing the ITP. Every lot and item is checked for the things that decide completion: outstanding Hold Point releases, unrecorded Witness Point outcomes, pending or rejected verification lanes, failed or missing results, missing measurements, open non-conformances and unsatisfied prerequisites. Each fact is listed with the lot, the item, what is missing and what to do about it.

Facts are separated into two kinds. A blocking fact stops the closeout pack being generated at all. An observation is shown but does not stop closeout, so a missing attachment on a record that is otherwise verified is visible without becoming a false barrier. Items marked Not Applicable for a lot are exempt rather than counted as incomplete.

An ITP that cannot be closed out yet. Generation is unavailable while blocking facts remain, and each fact states its remedy.

The same check on a fully verified ITP. Observations remain visible without blocking, and the closeout pack can be generated.

The closeout pack

Generating a closeout pack produces a PDF filed as a controlled document in the project. It records the ITP identity and revision, a certification summary, and every lot and item with its control level, acceptance criteria, measurements, results, attached evidence and named verifications including who signed, in what capacity and when. Deviations, non-conformances and superseded or corrected records are carried as audit history rather than removed.

Packs are numbered in sequence and cannot be edited or deleted once generated. Regenerating produces a new numbered pack rather than replacing the previous one, so a pack issued to a client stays exactly as issued. The server re-checks completeness at the moment of generation, so a pack cannot be produced from a record that stopped being complete while the page was open.

Verification that carries the signature record

Each lot/item can have separate contractor and principal or superintendent verification lanes. A completed verification records the saved signature mark, signer, capacity, delegated authority where applicable, outcome, and exact date and time. Name-only history does not satisfy a lane, release a Hold Point or count toward closeout.

The verification record keeps the inspection result, control-point state, each party's verification and the signed history together for the correct lot and item. Hold and Witness Points remain process controls, not signature types. The record shows whether the required party accepted, rejected, witnessed or released the point, while preserving superseded and void records instead of deleting the history.

Certified document signing for approval, hold release and closeout

Where the workflow requires a formal controlled document, TaskRox generates an ITP Approval Record, configured ITP Hold Point Release or ITP Closeout Certificate and routes it through a signature envelope. Required contractor, superintendent, principal, designer or client QA signatories can be assigned in sequence.

When every required signatory has signed, TaskRox produces a tamper-evident sealed PDF with a Certificate of Completion, signer and event audit trail, SHA-256 content hash and embedded PAdES digital signature that can be checked in standard PDF tools. This formal signing layer sits above the fast lot/item verification workflow: field records retain their signed verification history, while approval, governed release and closeout produce the controlled certificate.

This structure helps a team see which ITP and revision applies, which items remain outstanding for each lot, and what evidence still needs to be assembled for closeout. Test Requests and NCRs sit in the same QA module, reducing the number of disconnected registers a team must navigate.

The connected ITP workflow

The strongest ITP systems treat each lot/item record as the hub: the requirement, field evidence, measured result, control-point decision, verification history and downstream project consequences remain connected rather than being reconstructed at closeout.

A connected ITP workflow keeps planning, evidence, control-point decisions and project outputs tied to the same lot-specific record.

ITP Review Checklist

Before issue, confirm that the ITP:

The Bottom Line

A good ITP converts project requirements into an inspectable sequence. A good completed ITP then proves — lot by lot — that the sequence occurred, the acceptance criteria were met, the right people acted and the evidence can be found.

A free, no-login ITP builder is available to start one of the four adaptable structures above, or a blank ITP, and export it as a formula-safe XLSX or PDF.

Use the template above as a structure, not as technical content. Build each project ITP from the governing contract and specifications, test every row for field usability, and manage the resulting records as carefully as the physical work they represent.