Resources

Looking for a construction ITP template you can adapt for your own project? Below is the framework QBFS uses on builds across Australia. The template is yours to download and adapt. We've also flagged the parts most builders get wrong when they try to fill out a generic template themselves, because the document only works if it's tied to the actual project.

What the template covers

The template is a single-trade Inspection Test Plan structured around the components every ITP needs:

• Header block. Project name, contract number, trade/work package, version control, sign-off authorities.
• Reference standards. The Australian Standards, NCC clauses, and contract specifications the inspections test against.
• Hold-points. A row per hold-point with inspection criteria, sign-off authority, evidence captured, and a status column.
• Witness-points. Same structure, looser stop-work requirement.
• Sample-testing schedule. Where lab tests are required, the test type, frequency, and acceptance criteria.
• Non-conformance workflow. What happens when an inspection finds non-conforming work.
• Sign-off log. A running record of inspections completed, dates, signatures, evidence captured.

How to use the template

Three steps to make the template work for a real project:

1. Localise the scope. Replace the trade and work-package fields with the specifics of your build. A waterproofing ITP for a multi-residential project looks different from a waterproofing ITP for a single-dwelling renovation, even though the standard reference (AS 3740) is the same.
2. Localise the hold-points. A generic template lists generic hold-points. Your build has specific high-risk steps that the template won't know about. Add them.
3. Localise the sign-off authority. The template lists generic approval roles. Your project has specific people in specific seats. Name them.

A template that hasn't been localised in those three ways is the audit theatre most ITPs become.

Common mistakes filling out the template

A few patterns repeat:

• Listing every Australian Standard the trade might touch. The reference list should be the ones the inspection actually tests against, not the entire library. Trades stop trusting reference lists that read like a catalogue.
• Vague conformance criteria. "Workmanship to a tradesmanlike standard" doesn't survive contact with reality. The conformance criterion needs to be specific enough that two different inspectors looking at the same work would agree on whether it conforms.
• Sign-off authority on a person who isn't on site. The named approver has to actually be available at the hold-point. If they aren't, the sign-off doesn't happen and the hold-point gets bypassed.
• No update mechanism. The ITP needs to flex as variations and design changes land. A document without a version-control plan goes stale by month six.

What's not in the template (and shouldn't be)

A few things the template deliberately omits:

• Statutory inspections. Building certifier inspections, regulator inspections, and other statutory sign-offs sit in a separate document. The ITP supports them but doesn't replace them.
• Health and safety inspections. WHS sits in its own framework under WHS legislation. The ITP focuses on quality and construction conformance.
• Commercial milestones. Progress payments, variations, and contract administration are separate from quality inspection.

Keeping the ITP focused on quality conformance is what makes it useful.

When a template isn't enough

For larger or higher-risk projects, a generic template doesn't cut it. The build needs an ITP suite written against this contract, this trade list, this risk profile. QBFS develops ITPs for builds across Australia where the project scale or risk profile warrants purpose-built documentation.

The template's value is in the structure; the project's value is in the localisation. Both matter.

Get the template

If you want help adapting it for a specific project, or if your build is large or risk-loaded enough to need a purpose-built ITP suite, talk to Paul.

Call Paul on 0407 146 737.

Start With a Call

Best way to start is a phone call. Tell Paul the project, the issue, where you sit in the build cycle. The next step gets sorted on the call: site visit, desktop review, or a referral if QBFS isn't the right fit.