ITP Development and Ongoing Support

An Inspection Test Plan, or ITP, is the quality rulebook for a build. It names what gets checked, when, by whom, against which Australian Standard or contract specification, and what evidence is captured at each hold-point. A good ITP is the difference between a defensible quality program and a stack of paperwork nobody reads. QBFS develops ITPs for Australian residential, multi-residential, and commercial projects. Each ITP is written against this build's contract, sequence, and risk profile, not pulled from a generic template.

What's Inside

What's inside an ITP we develop

 

A QBFS-developed ITP typically covers:


Trade or work package scope
— the boundaries of what this ITP covers, whether a single trade, a building section, or a phase of work.


Hold-points
— inspections where work must be checked before it's covered up or moved past. Each hold-point names the inspection method, the conformance criteria, the evidence captured, and the sign-off authority.


Witness-points
— inspections that should be observed but don't strictly stop work.


Sample testing requirements
— concrete strength, soil compaction, water tightness, sound transmission, whatever the work requires.


Reference standards
— the Australian Standards, NCC clauses, and contract specifications the inspections test against.


Conformance evidence templates
— standard forms for inspection records, photographs, and sign-offs.


Non-conformance workflow
— what happens when an inspection finds work that doesn't conform.


Sign-off authorities
— who signs off conformance at each hold-point, whether that's the trade, the head contractor's QA lead, an independent consultant, or a regulator.

Why It Matters

Why a purpose-built ITP beats a template

Generic ITPs fail for predictable reasons:


Wrong specifications
— the ITP references standards or clauses that don't apply to this build. Trades stop trusting the document.


Missing hold-points
— a risk-loaded sequence step such as a waterproofing detail, complex flashing, or fire separation penetration isn't called out. The work passes inspection because the inspection wasn't structured to catch it.


Wrong sign-off authority
— the ITP names approval roles that don't exist on this project's org chart. Sign-offs get bypassed or forged.


No link to the contract
— the ITP's specifications don't match what was actually contracted. Disputes follow.

A purpose-built ITP doesn't fail those ways. Each hold-point is justified by the project's specific contract, specifications, and risk profile.

When to Engage

Ongoing support during the build

ITPs change as projects evolve. Variations, RFI responses, design changes, and unforeseen site conditions all need to flow into the ITP. QBFS's ongoing support keeps the document current:


Periodic ITP review
— at agreed intervals, typically aligned with major project milestones, the ITP is reviewed for currency.


Variation integration
— when a variation lands, the ITP updates to reflect the changed scope.


NCR feedback
— patterns from non-conformance reports feed back into ITP tightening, so a hold-point that keeps catching the same issue gets attention.


Trade rotation updates
— where sub-contractors change mid-build, the ITP rolls out to the new trade with a briefing.

The ongoing support is what keeps ITPs from going stale. Without it, the document describes a build that no longer exists by month six.

How it Runs

How the engagement runs

  • Brief and scoping — project scale, contract structure, trade list, existing QA tooling, risk profile.
  • Document review — contract, design documents, specifications, programme, sub-contractor list.
  • Hold-point mapping — every trade or work package gets a hold-point map drafted against the contract and the standards.
  • Drafting — ITPs written per trade or per package.
  • Roll-out — trade briefings, document control setup, conformance evidence kick-off.
  • Ongoing support — periodic reviews, variation updates, NCR feedback.

ITP development across Australia

The methodology is national. The Standards and NCC are the same; state-specific home-building or domestic-building legislation flows into the ITP where it applies. Travel is built into the scope where site briefings are needed and the project sits outside the consultant's regular catchment.

Start With a Call

Tell Paul the project. The next step gets sorted on the 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.
Frequently Asked Questions

Common questions, answered.

  • What is an ITP in construction?

    An Inspection Test Plan is a document that says what gets checked on a construction project, when, by whom, against which standard or specification. It’s the quality rulebook for a build. Each trade or work package usually has its own ITP, and the collection sits inside the broader QA program.

  • Why pay for an ITP when there are templates online?

    Generic templates aren’t written against your contract, your trades, your sequencing, or your risk profile. Trades stop trusting them, hold-points get bypassed, and the document becomes audit theatre. A purpose-built ITP costs less than the first defect it prevents.

  • How long does ITP development take?

    For a typical multi-residential or mid-sized commercial project, the initial ITP suite takes two to four weeks to draft, brief, and roll out. Larger projects with more trades take longer. Ongoing support runs through the build with review hours scaled to project size.

  • Can you work inside our existing QA system?

    Yes. Where the builder has an existing QA system, often through ISO 9001 or a client-required program, QBFS builds the ITP suite to fit that system rather than replacing it. The added value is the construction-specific depth.

  • Do you brief our trades on the ITP?

    Yes. Each sub-contractor is walked through the relevant ITP before their work starts: hold-points explained, conformance evidence required, sign-off process, NCR workflow. The briefings are documented.

  • Will the ITP support a defects dispute?

    Yes, materially. A documented ITP with conformance records is one of the strongest defences a builder has if a defect matter later escalates. The ITP shows what was inspected, when, by whom, against what standard.

  • What does the engagement cost?

    The fee depends on the project’s size, trade count, and whether the engagement is ITP-only or includes ongoing support. Call Paul on 0407 146 737 for a fee proposal.

Construction consultancy and forensic building services for Australian builders, head contractors, developers, and legal teams.

© 2026 QBFS | All Rights Reserved | Developed byweb design brisbane