Watch the overview
75 seconds. A narrated explainer; the transcript is below. The written guide includes additional detail.
Read the video text
- 0:00A block-pavement record carries more than a
- 0:02collection of ratings. It ties block type,
- 0:05laying pattern and observations to a particular
- 0:08road interval and measurement date. The current
- 0:11template declares specific codes for block type,
- 0:14laying pattern and chamfers. For example, H
- 0:17B is a permitted laying-pattern code. Free
- 0:20text in that coded field is not
- 0:23equivalent. The segment-length check uses a zero
- 0:26point two kilometre baseline with a fifty-percent
- 0:29band. A zero point four kilometre example
- 0:32is outside the band and needs review.
- 0:35A disallowed code is a schema error;
- 0:37the assessment-length issue is a warning. Read
- 0:40the finding category and affected row instead
- 0:43of treating every highlighted value as the
- 0:45same problem. Where supplied, condition indices must
- 0:49remain within zero to one hundred. This
- 0:52check does not recalculate an index or
- 0:54prove that the block-pavement rating matches field
- 0:57conditions. Use the original assessment to resolve
- 1:00the code or interval. Preserve the approved
- 1:03version and evidence, then rerun the applicable
- 1:05checks. A clean file supports review; it
- 1:09does not replace the assessor.
Keep the block assessment together
A block-pavement record carries more than a collection of ratings. It ties block type, laying pattern and observations to a particular road interval and measurement date.
The current template declares specific codes for block type, laying pattern and chamfers. For example, H B is a permitted laying-pattern code. Free text in that coded field is not equivalent.
Retain the kilometre interval
The segment-length check uses a zero point two kilometre baseline with a fifty-percent band. A zero point four kilometre example is outside the band and needs review.
A disallowed code is a schema error; the assessment-length issue is a warning. Read the finding category and affected row instead of treating every highlighted value as the same problem.
Preserve the block-pavement record as a unit
Check that the chosen block-pavement definition matches the export, then inspect its codes and kilometre interval together. A fictional 0.400 km interval can trigger the implemented length warning even when the individual kilometre fields are numeric and ordered. This is a review signal with a stated baseline.
Do not substitute a concrete or flexible-pavement definition simply because several fields look similar. Keep the original assessment, project segmentation and exchange edition available. Resolve each finding from source evidence and repeat the relevant checks on the corrected export.
Check the condition index
Where supplied, condition indices must remain within zero to one hundred. This check does not recalculate an index or prove that the block-pavement rating matches field conditions.
Use the original assessment to resolve the code or interval. Preserve the approved version and evidence, then rerun the applicable checks. A clean file supports review; it does not replace the assessor.
Sources and scope
This guide describes the platform workflow; it does not establish a requirement of a TMH manual. Platform review and certification are described in the product documentation.
Put it into practice
Review check templatesSign-in and the relevant account permissions are required.