Construction planning guide

Contract Defined Road Pavement Works ITP Preparation and Inspection Records

Build a road-pavement ITP around the actual contract, adopted specifications and annexures, pavement layers and chainage/lots. Reconcile material, placement, testing and survey evidence to the same layer and work boundary before recording its disposition.

Scope of this guide

A defined road-pavement package from released formation/subgrade through selected unbound layers and the specified surfacing interface. Drainage, structures, traffic management design, pavement/geotechnical design and unselected stabilised or concrete systems are separate scopes. TMR documents apply only when the contract adopts them.

Collect the files that control this package

Input to reviewWhat to identify
Contract and adopted specification listIdentify jurisdiction, contract items, relevant specification editions, annexures, project amendments and precedence rules.
Pavement and lot definitionSupply layer schedule, drawings, chainage/lane limits, project lot boundaries and release stages.
Material and method submissionsIdentify approved sources, materials/mixes, delivery traceability and applicable construction procedures.
Project testing and release requirementsExtract methods, frequencies, lot/sample rules, acceptance sources, reports, H/W points and authorised disposition roles.
Survey and closeout requirementsLocate datum, conformance/as-constructed survey instructions, NCR traceability and the recipient lot-dossier list.

Map the inspection sequence to the actual work

Keep formation/subgrade release distinct from receiving and placing a base/subbase layer. For each test and survey report, reconcile the layer, material source, location and lot against the planned requirement. Treat asphalt or another surfacing system as an interface until its specific adopted requirements and scope are available.

Check the scope and adjoining responsibilities

Queensland TMR MRTS05 July 2022 covers unbound pavements; its quality system, material source, construction and testing sections do not automatically govern a private building driveway or another jurisdiction. MRTS04 March 2025 is an earthworks/interface source, not a complete surfacing specification. Do not assign their numerical limits, lot sizes or Hold Points without the actual adopted contract documents.

Keep an unresolved requirement visible

A test report identifies a chainage range but omits which pavement layer and contract lot it represents. Record the report identifier, stated range and missing layer/lot linkage, request the controlled traceability clarification, and keep the affected conformance review open.

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 Contract / jurisdiction and Adopted specs / annexure list for the basis, Chainage / lane / lot and Base / subbase layer ID for the work, and Report / result / disposition ref. for testing. Link survey evidence and NCR decisions to that same layer/lot; a report index alone is not a lot release.

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 roadworks 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.

  1. Identify the fictional lane, chainage boundary and unbound layer under the contract-adopted specification and annexure.
  2. Map material-source, placement and specified test rows to their actual clauses.
  3. Raise the missing test-report layer/lot link as a traceability query; do not infer it from the report date.
  4. Reconcile the clarified original report, survey and any NCR disposition before recording the separate authorised release evidence.

Before issuing the plan

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.

Related resources