Scope of this guide
Ordinary building ductwork, supports, joints, insulation/lining and specified in-duct or terminal-device interfaces. Refrigerant circuits, equipment electrical work, controls, design, balancing, commissioning execution and building performance certification are separate activities.
Collect the files that control this package
| Input to review | What to identify |
|---|---|
| Coordinated mechanical layout | Identify systems, zones, duct runs, sections, terminals, tags and current coordinated drawing revisions. |
| Approved duct and component submittals | Provide the duct construction, insulation/lining, seals, dampers and terminal selections and applicable installation instructions. |
| Support and penetration details | Identify support details, structure interfaces, firestop responsibility, access needs and other-service coordination decisions. |
| Inspection and testing requirements | Locate the project-specified duct inspection/test method, scope, acceptance source, report requirements and assigned testing party. |
| Mechanical handover requirements | Identify as-built drawings, product evidence, unresolved coordination issues and dependencies on later balancing or commissioning. |
Map the inspection sequence to the actual work
Map support/route readiness before duct assembly, joints and cleanliness, insulation/lining, and devices/access. Create a separate test-report interface only when the actual package requires it. A terminal-device installation check is not evidence that airflow has been balanced or the complete system commissioned.
Check the scope and adjoining responsibilities
The installation template does not prescribe leakage classes, pressure, duration or balancing values. If a supplied test report covers only part of a system, preserve that boundary and record the outstanding zone rather than marking the complete system accepted.
Keep an unresolved requirement visible
The coordinated layout identifies duct runs above a ceiling, but the source set has no approved support detail at a congested service crossing. Identify the system, grid/zone and affected crossing, then request the applicable detail and coordination decision before closing that support check.
Record the affected step and location, source documents and revisions checked, precise decision requested and the project role or route assigned to resolve it. Incorporate an authorised response with its reference and revise the affected plan and record. Do not hide the gap behind “as per standard”.
Use the blank fields already matched to the plan
Use System / zone ID and Grid / run locator to identify the installed work, Device tag / type and Access / coordination ref. for device interfaces, and Project method / clause with Test report / date ref. for a required test. The report reference indexes the original report and is not its replacement.
The public package downloads include both the plan and its matching blank records in Excel, Word and PDF. The browser editor changes the plan; it does not collect site observations or perform tests. Use a repeatable record for each actual event and preserve original reports and photographs under the project procedure.
Separate results from authorised decisions
The ITP holds planned requirements. The inspection record holds actual observations, results and evidence. The project procedure assigns who reviews a discrepancy, authorises treatment, releases a contractual point and accepts a handover. Keep their names, dates and decision references distinct.
Use the cross-package register to index the current plan and actual event records. If a departure is identified, link the NCR to the affected work and requirement, the authorised disposition and any required recheck before closure.
Request project-specific drafting for this work
Send the existing project files and required client form with one clearly defined package and its interfaces. The named hvac service also supports a customer-defined scope beyond this public baseline when the required controlled sources are supplied.
The service is USD 99 per defined package, delivered within 24 hours after payment and complete usable required project files. It prepares the ITP and matching blank records; design decisions, actual inspections/tests, commissioning, approvals and certification remain with their assigned project parties.
Fictional package mapping example
Illustrative workflow only. No real site result, numerical acceptance requirement, test outcome or authorised release is represented.
- Define the fictional supply-air duct system and ceiling zone; keep equipment and balancing outside the installation boundary.
- Map supports, assembly and insulation to their specific sources and sequence.
- Log the unapproved support crossing and identify the affected run without inventing a support arrangement.
- If testing is required, link the assigned party’s original report to its actual tested zone; keep the commissioning dependency visible.
Before issuing the plan
- Define the actual area, system or lot and adjoining-trade interfaces.
- Identify approved inputs by document, revision and usable locator.
- Map criteria, method, frequency, roles and points from the actual project source.
- Retain the package-specific location and traceability fields in the blank records.
- Log missing decisions and keep original evidence separate from its index.
- Keep results, signatures and release decisions blank until their actual event.
Sources and their limits
Public sources explain the planning topics below. Confirm their jurisdiction, contract context and applicable edition; use controlled project documents for the actual requirements.
- CPCPMS3035 Install and test ducting systems
Release 2 PDF generated 24 December 2024: installation, insulation, terminal devices, project-file testing requirements and completion records.
Vocational scope context, not a leakage criterion or commissioning procedure. The contract and approved documents control whether and how testing applies.
Source reviewed: 2026-10-07
- NSW Government Quality management guidelines for construction
Webpage updated 1 December 2019: scope and purpose; typical QMP contents; client records; example GC21 clauses on ITPs, nonconforming work and conformity records register. Appendix D is listed but its DOCX contents were not inspected.
NSW Government construction procurement guidance. The example clauses apply only where the contract adopts them. Used for document relationships and records, not universal acceptance criteria or project approval rights.
Source reviewed: 2026-10-07