Scope of this guide
Building automatic sprinkler distribution/range pipe installation within an identified design and package. Pumps, hydrants, hose reels, alarm/detection work, specialist hazards, system design, head fit-off outside the stated package, test execution and statutory certification need their own defined coverage.
Collect the files that control this package
| Input to review | What to identify |
|---|---|
| Approved sprinkler design and package boundary | Identify the building/system/zone, included pipework, adopted standard or approval basis and controlled design revisions. |
| Approved materials and joining procedures | Provide pipe, fittings, supports and relevant components with accepted product evidence and the joining-method source. |
| Coordination and penetrations | Locate pipe routes, service interfaces, support details, rated-element penetrations and the assigned firestop/access owner. |
| Test and commissioning responsibility | Identify the project-required tests, source method and acceptance criteria, testing party, report coverage and subsequent commissioning dependencies. |
| Approval and completion evidence | Locate notice/release requirements, as-built scope, outstanding issue disposition and any separately required statutory documents. |
Map the inspection sequence to the actual work
Keep route/support readiness, joining/installation and concealment evidence distinct. For a specified pipe-integrity test, plan the report interface and required traceability without treating the public template as test instructions. Link later commissioning reports and authority documents only to the scope they actually cover.
Check the scope and adjoining responsibilities
Confirm the project-adopted NCC and system-standard edition from the controlled approval/contract sources and relevant jurisdiction. Do not assume the newest published edition is adopted. An installer observation or original pipe test report does not itself demonstrate complete fire-system commissioning or statutory certification.
Keep an unresolved requirement visible
The pipe layout shows a penetration through a rated element, but the supplied package does not identify the assigned firestop detail or interface owner. Record the floor/grid, penetration and drawing revision, request the approved detail and responsibility, and leave that interface pending.
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 and Pipe run / joint locator for installed pipework, Opening / fire-rated element ref. and Assigned interface owner / evidence ref. for penetrations, and Project test method / clause with Report / date locator for the specified test. Track Outstanding interface / approval ref. separately from a test result.
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 fire-protection 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 sprinkler distribution-pipe zone and its approved design revision.
- Map joining and support checks to their sources, and identify the penetration interface separately.
- Raise the missing firestop detail and owner as a query rather than designing a solution.
- Index the original pipe-test and commissioning evidence supplied by their assigned parties, preserving each coverage boundary and any outstanding approval.
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.
- CPCPFS3044 Install distribution and range pipes
Release 2 PDF generated 24 December 2024: design/work specification identification, supports and joining, existing-system isolation/drainage interfaces and documentation.
Vocational work-scope context; not restricted to every possible sprinkler configuration. Does not replace approved sprinkler design, project-adopted AS/NCC requirements, testing procedures or statutory certification.
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