Civil subdivisions are repetitive by nature. The same road pavement ITP, the same stormwater ITP, the same sewer and water ITP runs on every lot in the stage. The engineering doesn't change — Lot 1's kerb and channel is the same specification as Lot 40's.
What does change is the documentation volume. A 40-lot stage with 4 ITPs per lot is 160 documents. A 120-lot subdivision across 3 stages is almost 1,500 individual inspection records that need to be created, completed, signed, and handed back to the developer at practical completion.
This is where most civil contractors either drown in paperwork or cut corners. This guide covers how to structure ITP documentation for multi-lot civil works so that quality records are complete without the administrative overhead scaling linearly with lot count.
The documentation challenge
On a civil subdivision, the typical ITP set per lot includes:
- Earthworks and subgrade preparation — proof rolling, density testing, level checks
- Stormwater drainage — pipe installation, bedding, jointing, CCTV inspection
- Sewer and water reticulation — pressure testing, chlorination, connection verification
- Road pavement and kerb — subbase compaction, pavement thickness, kerb alignment, line marking
Each of these ITPs contains multiple inspection items, hold points requiring the superintendent's attendance, and test certificates (density, pressure, CCTV) that must be attached.
Multiply this across every lot in a stage, and the administrative burden becomes the bottleneck — not the construction work itself.
Common approaches and their problems
The spreadsheet register
Many civil contractors maintain a master Excel spreadsheet that tracks which ITPs have been completed for which lots. The actual ITPs are Word documents saved in a folder structure like Stage 1 > Lot 1 > Earthworks ITP.docx.
Problems:
- The register and the actual documents can get out of sync
- Version control is manual — which revision of the earthworks ITP is Lot 23 using?
- Sign-offs are wet signatures on printed documents that need to be scanned and filed
- Producing the handover pack means manually collecting and compiling documents for each lot
The copy-paste approach
The ITP template is duplicated for each lot — literally copied, renamed, and saved. For 40 lots, this means creating 40 copies of each template at the start of the stage.
Problems:
- If the template changes (a hold point is added, an acceptance criterion is updated), every existing copy is now out of date
- Managing 160+ individual documents across a file system is error-prone
- There's no centralised view of "which lots are complete" without manually opening each document
The "one big ITP" approach
Some contractors try to consolidate by creating a single ITP per trade that covers all lots, with a matrix showing lot-by-lot completion.
Problems:
- A single document with 40 rows per inspection item becomes unwieldy
- Sign-off is all-or-nothing — you can't send Lot 12's earthworks for sign-off independently of Lot 13's
- Lot-specific issues (non-conformances, additional testing) don't fit neatly into a shared document
- At handover, the developer wants a per-lot pack, not a trade-wide matrix
The right structure
The approach that works — the one that survives both the daily grind of a civil site and the scrutiny of a handover audit — has three characteristics:
1. One template, many instances
The earthworks ITP template is created once, maintained centrally, and instantiated per lot when needed. Each lot gets its own independent copy derived from the master. If the master is updated, new copies pick up the changes; existing in-progress copies are not disrupted.
2. Area-based organisation
Lots are not flat. A subdivision has a hierarchy: the project contains stages, stages contain lots, lots contain their ITP set. This hierarchy should be reflected in the document structure, not flattened into a folder system.
When someone asks "what's the status of Stage 2?", the answer should be visible at the stage level — how many lots are complete, how many have outstanding hold points, how many are ready for handover.
3. Per-lot handover packs
At practical completion, the developer receives a quality documentation pack for each lot. This pack contains every signed ITP, every test certificate, every non-conformance record for that lot — combined into a single, paginated PDF.
Producing this pack should be a one-click operation, not a week-long document assembly exercise.
Setting up a 40-lot stage
Here's the practical workflow for setting up ITP documentation on a 40-lot civil subdivision stage:
Step 1: Create the project and define the area structure.
The project represents the subdivision (or the contract). Within the project, create a parent area for the stage (e.g., "Stage 2"), then add child areas for each lot ("Lot 201" through "Lot 240").
The area type should be set to "lot" — this tells the system (and anyone looking at it) that these are lot-level areas, not levels, zones, or chainages.
Step 2: Create or import the ITP templates.
The company template library should contain the standard civil ITPs — earthworks, stormwater, sewer/water, road pavement. These templates define the inspection items, hold points, acceptance criteria, and responsible parties.
If the templates don't exist yet, create them once. They'll be reusable across every future project and stage.
Step 3: Bulk-apply templates to lots.
Rather than manually creating 160 documents, select the templates and apply them across all 40 lots in one action. Each lot receives its own independent copy of each ITP, pre-populated with the template's inspection items and hold points.
Step 4: Work through the lots.
As construction progresses lot by lot (or in batches — it's common for earthworks to run across multiple lots simultaneously), the site team fills in each ITP as work is completed. Hold points are triggered when the relevant inspection items are reached, and sign-off requests are sent to the superintendent.
Step 5: Hand back per-lot packs.
When a lot is complete — all ITPs signed, all test certificates attached — the lot's documentation is bundled into a sign-off pack and sent to the developer. The pack is a single PDF containing every document for that lot, in order, with a cover page summarising the contents.
Handling non-conformances
Lot-based work inevitably produces non-conformances — a density test that fails, a pipe joint that leaks, a subgrade level that's out of tolerance. The key is that the non-conformance is recorded against the specific lot and the specific ITP item, not in a separate register that has to be cross-referenced.
When the non-conformance is rectified and re-inspected, the ITP item is updated with the corrective action and the re-inspection result. The full history — original failure, corrective action, re-inspection — is captured in the document and appears in the handover pack.
Scaling to larger subdivisions
The same structure scales to larger subdivisions by adding stages. A 120-lot subdivision with 3 stages of 40 lots each is just three parent areas, each containing 40 child areas. The project-level view shows overall progress; the stage-level view shows per-lot status; the lot-level view shows individual ITPs.
For very large civil projects (greenfield estates with hundreds of lots across multiple stages and precincts), additional hierarchy levels can represent precincts or sectors. The principle is the same: the hierarchy mirrors the physical structure of the work, and documentation is attached at the lowest level.
Getting started
If you're running a civil subdivision and still managing ITPs via spreadsheets and Word documents, the transition to a structured system is straightforward:
- Start with your next stage (don't try to migrate existing completed stages)
- Set up the lot structure in HoldPoint's Areas feature
- Import or create your standard civil ITP templates
- Bulk-apply across all lots
- Work through the stage as normal, using the system for inspections and sign-off
The administrative overhead of managing per-lot documentation drops from hours per week to minutes. The handover pack that used to take a week to assemble is produced in one click.
For a walkthrough of the lot setup process, see ITP per Lot: Quality Documentation for Civil Subdivisions.