Earthworks records are easier to navigate when the register shows the physical limits of each lot and the layer or stage covered by the evidence. A long list of test reports sorted by date can hide uncertainty about where work occurred. The organising task is to make those relationships visible without making a geotechnical assessment.

Use a lot map as the starting point

Agree a lot identifier with the project team and link it to a dated plan or sketch. Record the area boundary, elevation or layer reference used on the project, work activity and responsible contractor. If a lot is divided or combined, preserve the former identifiers and document the approved relationship rather than silently changing past records.

For each test report, capture its original report number, sample or test reference, recorded location, date, relevant lot and source file. Include a separate field for “location confirmed by” so a clerical assumption does not look like a technical fact.

Show gaps without colouring them as failures

A coverage view can use neutral statuses: no evidence located, evidence received, location link awaiting confirmation, under technical review, and review outcome recorded. These states describe the document workflow. They must not be confused with “passed” and “failed” unless an authorised reviewer has supplied that assessment.

Consider a hypothetical access-road project. Lot EW-08 is described as a chainage range on the register, while three reports use coordinates. The coordinator places the reports in a query list. A survey or technical owner confirms which coordinates fall within EW-08 and identifies one report as belonging to EW-09. The corrected relationships are recorded with the supporting response, preserving the original files.

Keep the evidence view useful

Add a filter for lot, layer, date and review status. A simple map annotation or separate cross-reference sheet can help reviewers find records, provided it is clearly identified as a navigation aid. Do not redraw boundaries from memory or treat a dense cluster of test points as proof of adequate testing.

Before a submission milestone, check that every lot in the agreed deliverable schedule has an explicit status, even where the status is “not applicable—client confirmation required”. Unlisted lots are easy to overlook when a dashboard counts only reports already received.

Transport and Main Roads publishes a Materials Testing Manual and related resources. Those references illustrate why current method and project requirements matter. The project’s appointed technical people must determine testing coverage, interpretation and acceptance; a document register only helps them locate the evidence.