What Is an ITP in Construction? A Plain-English Guide

What is an ITP?

An ITP — Inspection and Test Plan — is a document that lists every stage of a piece of work, in order, and records how each stage gets checked and by whom. It’s the paper trail (or digital trail) that proves the work was actually inspected, not just done.

If a builder has said “we need your ITPs,” they’re not asking for a quality slogan. They want a specific document, tied to a specific package of work, that shows what checks happen at what point, and who signs off on each one.

Why builders ask for them

Builders don’t ask for ITPs because they enjoy paperwork. They ask because someone above them — a client, a certifier, an auditor, sometimes a bank funding the project — is asking the builder for the same thing, and the builder can’t produce it without you.

A few reasons ITPs show up in subcontracts:

• Quality management systems. Most head contractors run a formal QMS (often aligned to ISO 9001 principles), and that system requires documented evidence that work was inspected before it got covered up or handed over.
• Defects liability and handover. When the defects liability period starts, whoever owns the building wants proof of what was checked and when — not a memory of “yeah, we looked at that.”
• Audits. Builders get audited by their own clients, by certifiers, sometimes by financiers. An incomplete ITP register is the kind of thing that turns a routine audit into a bad week.
• Progress claims. On a lot of jobs, you can’t get a stage paid until the inspection record for that stage exists. No ITP entry, no claim line.

None of this is really about you. It’s about the builder needing to prove, up the chain, that the building went together the way the spec said it would. Your ITP is their evidence.

Is there a standard for ITPs?

No — not one that tells you what an ITP has to look like. No ISO or Australian Standard prescribes an ITP format, and the National Construction Code doesn’t require ITPs at all. What exists is a chain of documents that ask for one:

• ISO 9001 (adopted here as AS/NZS ISO 9001) is the quality management standard most head contractors are certified to. It requires work to be done under controlled conditions, with documented evidence that it was checked before it was released. An ITP is the usual way a subcontractor supplies that evidence — but the standard never mentions ITPs or a format.
• ISO 10005 gives guidance on quality plans: the activities, criteria, inspections, responsibilities and records a plan should cover. It’s the closest thing to an ITP standard, and it’s guidance, not a template.
• On building work, the format comes from the builder’s own QA system, flowed down through your subcontract and the project specification — which is also where hold and witness points are nominated. Regulators such as Building Commission NSW and Queensland’s QBCC want evidence and compliance declarations, not a particular form.
• On civil and government work it’s far more prescriptive. Specifications such as Transport for NSW’s Q6 and Queensland TMR’s MRTS50 spell out ITP content in detail: criteria, frequency, hold/witness/review points, records and responsibility.

So the right ITP is the one your builder’s system and your spec ask for. Software can’t make an ITP meet a standard on its own; what it can do is keep the inspection evidence those systems ask subcontractors for. See what to look for in ITP software and an example signed ITP.

Who prepares the ITP

Usually you do — the subcontractor doing the actual work. The builder might supply a template, reference a spec, or set the format they want it in, but they’re not on site watching every opening go in. You are. So the record of what happened, stage by stage, has to come from your crew.

In practice this means:

• The builder (or their QA manager) tells you an ITP is required, sometimes with a template attached.
• You fill it in as the work happens — not two weeks later from memory.
• The builder reviews it at handover points, sometimes attends specific inspection stages in person (more on that below).
• The completed, signed ITP goes into the project’s QA records.

If nobody’s told you the format, ask early. Reconstructing three levels of installation history from phone photos after the fact is a miserable way to spend a weekend.

Some builders hand you a blank spreadsheet and expect you to work it out. Others have a formal QA package with a pre-built ITP template you’re contractually required to use. Either way, the earlier you know which stages need recording and in what format, the less scrambling you do later.

What’s actually in an ITP

Every builder’s template looks slightly different, but most cover the same ground. As an example structure — not a standard, just how it commonly breaks down:

• The activity or stage. Each discrete step in the work. For a window or facade package this might be things like frame delivery check, opening prep, frame fixing, flashing and waterproofing, glazing, and final seal — but the exact stages depend on the job and the trade. Don’t assume any one breakdown is universal.
• The reference. What the check is being measured against — the project spec, a drawing revision, an approved sample, or a manufacturer’s install instructions. (Some ITPs cite Australian Standards where relevant; check your own spec rather than assuming a standard applies — don’t guess at a number.)
• The inspection type. Whether the stage needs a hold point, a witness point, or just a self-check with a record kept. These aren’t interchangeable — see the section below.
• Who signs off. Could be your leading hand, your site supervisor, the builder’s site manager, or in some cases an external certifier or engineer.
• The record. What evidence gets kept — a signature, a date, a photo, a test result. This is the bit that turns “we checked it” into something you can actually produce six months later.

Hold points and witness points

Two terms that trip people up early on:

• A hold point means work physically stops until the required person has inspected and signed off. You cannot proceed past it without that sign-off — if you do, you’re exposed if anything’s later found wrong.
• A witness point means the inspector has the right to be there and watch, but if they don’t show up in a reasonable time, you can usually proceed and just record that they were notified.

Getting this distinction wrong is an easy way to end up redoing covered-up work, or copping the blame when a stage gets missed. It deserves more space than a paragraph — we’ve written a full guide on hold points vs witness points that covers who signs, what happens if someone doesn’t show, and how to handle it when the builder’s inspector is a no-show three times running.

What ITP day-to-day actually looks like

On a job running ITPs properly, the pattern is usually:

1. Crew does the work. Each stage gets completed as normal — frames go in, flashing goes on, glazing happens.
2. Stage gets recorded at the time. Whoever’s responsible marks the stage off, ideally the same day, with a photo if the ITP calls for one.
3. Hold points get flagged. If a stage is a hold point, someone lets the relevant person know it’s ready for inspection, and work on that item stops until they’ve been through.
4. Sign-off happens. The nominated person signs, dates, and the record locks in.
5. The whole thing gets handed over. At practical completion, or whenever the builder asks, the completed ITP — every stage, every signature — goes to the builder as one document.

The part that kills most subbies isn’t the concept, it’s step 2. If stage completions don’t get recorded as they happen, you’re stuck reconstructing three months of installation history from a phone camera roll the week before handover. That’s where most of the “urgent ITP” panic on a Friday afternoon comes from.

Paper ITPs still exist on plenty of jobs — a clipboard on site, ticked off by hand, photographed and emailed at the end. It works, but it’s slow to produce and easy to lose track of once you’re running several levels at once. Some crews run it in Excel instead, one row per opening per stage, which is better for keeping a live record but still means someone has to sit down and update it rather than it happening automatically as the work’s done. Either way, the ITP itself doesn’t care how it was built — the builder just wants to see that every stage was checked, by the right person, and that the record can’t have been backfilled after the fact.

Where WNDW fits

WNDW records each stage as your crew marks it off on-site — no separate paperwork step at the end of the day. When a level’s finished, the ITP report generates from that data automatically: every opening, every stage, every sign-off, laid out like the ITP the builder asks for. If you’re building your ITP process for window or facade installation specifically, see our guide to ITPs for window installation, or check out automatic ITP report generation.

FAQ