Civil Works ITPs: Route Each Package to the Right Scope

Split civil scope into work packages

Start by defining assets, work areas, interfaces, design responsibility and handover boundaries. Then separate packages with different processes, specifications, acceptance sources or record owners. Common divisions include earthworks and compaction, trenching and backfill, drainage installation, concrete and structural steel. One contractor may own several packages, but a shared contract does not make their inspection requirements interchangeable.

Keep project-wide controls such as document approval, survey, nonconformance and handover in the project quality system or a clearly linked common section. Keep trade-specific checks and evidence in the relevant package ITP so reviewers can follow source-to-row traceability.

Choose an existing template by the work actually performed

Use the earthworks route for excavation, fill placement and compaction; the drainage route for stormwater assets and installation; and the structural-steel route for steelwork inspection and traceability. Where the package is narrower, prefer the matching focused template. Review the included stages against the project scope instead of treating a template title as proof it fits.

Where no listed package matches, begin with the project-specific ITP process and identify missing inputs before drafting. Do not promise an orderable trade package or custom technical criteria that the available workflow does not support.

Map public infrastructure specifications to the contract

Transport agencies publish specification libraries that may be incorporated into public infrastructure contracts. The applicable contract identifies the edition, annexures, precedence, lot controls and submission requirements. Agency publication alone does not mean every local or private civil package adopts those documents.

For example, TMR Queensland organizes specifications into suites and categories and says the specifications must be read with overarching specifications. TfNSW Q6 explicitly states that its quality-management specification is for specified roadworks and bridgeworks contracts in NSW. Use those as jurisdiction-specific examples only when the package contract makes them applicable.

Keep interfaces and handover evidence connected

Civil packages often meet utilities, roads, structures and building work. Assign an interface identifier and define the point where one package hands over to another. Link the receiving package to survey, inspection, test or approval evidence it actually relies on; do not duplicate or silently change the originating acceptance decision.

Use lot, chainage, structure, asset or location identifiers consistently across the ITP and field records as specified by the contract. Preserve revision and status so completed evidence can be traced back to the approved requirement.

Example: drainage trench through compacted fill

Fictional example. A civil contractor separates excavation, bedding, pipe installation, connection and backfill into related but traceable stages. Drainage checks cite the approved layout and applicable pipe specification; backfill checks cite the project earthworks requirements and retain the specified compaction evidence. The ITP records the interface at which drainage inspection evidence is accepted before covering, only where the project source establishes that release. The example supplies no universal test frequency, value or hold point.

Civil package selection and cross-reference

Fictional package-planning example only. Technical requirements and release roles must come from the actual project documents.

1. Draw a boundary for the civil package and name included assets, locations, interfaces and handover points.
2. Select focused earthworks, drainage, trench/backfill or structural-steel template routes for matching work.
3. Record contract specifications and approved drawings with revision and relevant clause or drawing locator.
4. Link the field record and evidence identifier to the corresponding ITP row and location/lot.
5. Track shared interfaces and unresolved requirements without merging unrelated trade acceptance criteria.