Construction ITPs in New South Wales: Link Consent, Certification and Contract Records

Map the building consent and certificate pathway

For building work, first identify the development consent, its conditions and the approved plans. Service NSW describes a construction certificate as confirming that construction plans and specifications are consistent with development consent and applicable building requirements; its application is made through the NSW Planning Portal. Use the certificate and approved documents as controlled inputs to the ITP, and track conditions that affect sequence or evidence.

A construction certificate is not a contractor ITP and does not replace the contract’s inspection, testing, notification or record requirements. Confirm the project’s actual certification route and designated certifier roles rather than copying a generic pathway.

Use TfNSW quality specifications only in their stated contract context

TfNSW QA Specification Q6 states that it was developed for roadworks and bridgeworks contracts let by TfNSW or local councils in NSW and is not suitable for other purposes or contexts. If the contract adopts Q6 or related specifications, follow the contract’s specified edition, precedence, annexures and submission requirements. A building package should not inherit civil contract points by state name alone.

For road or bridge work, use the contract’s specification suite to identify required quality plans, ITP content, notice periods, records, nonconformance process and lot close-out. The published source is a starting point; the contract determines what applies to this job.

Coordinate council, utility and road-reserve interfaces

A work package may also need approvals or consents controlled by a council, road authority, utility owner or another agency. Capture the actual approval, condition, location and required evidence in the source register. Do not infer that a construction certificate authorises excavation or occupation of a public road reserve.

Keep authority evidence separate from the contractor’s verification. If an authority consent sets a pre-start condition, map the document and responsible close-out to the affected ITP stage without converting the condition into an unsupported technical acceptance value.

NSW document-control example: one slab and one road tie-in

Fictional example. On a mixed development package, the document controller tags the building ITP draft with the development consent and construction certificate revision, then cross-references approved structural drawings and the head contract quality clause. A separate road tie-in package cites the council/TfNSW contract specification only if named in that contract and records its road-reserve consent reference. The slab certifier notification, contractor pre-pour check and road contract hold point appear as distinct control rows with distinct roles and records. A pending consent condition remains an open item against the affected location. No numeric technical criterion is assumed.

NSW source-to-row control

Fictional document-control illustration only; the approval pathway and technical requirements must be established for the actual work.

1. List development consent, conditions, approved plans and construction certificate with their controlled revisions.
2. Identify the assigned certifier and contract review roles from project documents.
3. For roadworks, verify whether TfNSW or council specifications are incorporated and record the adopted edition and annexures.
4. Cross-reference each approval condition and contract clause to its own ITP row and evidence record.
5. Track any missing consent or conflicting revision as an open item; submit and close it through the project process.