Watch the overview
80 seconds. A narrated explainer; the transcript is below. The written guide includes additional detail.
Read the video text
- 0:00Both values may fit their individual fields,
- 0:03yet tell conflicting stories. A flexible-pavement record
- 0:07reports severe bleeding alongside very good skid
- 0:10resistance. That relationship needs engineering review. The
- 0:14implemented paired check raises a warning when
- 0:16bleeding degree is at least four and
- 0:18skid-resistance degree is at most two. It
- 0:21is this specific pairing, not a promise
- 0:24to detect every distress contradiction. Our example
- 0:27uses bleeding four and skid resistance two.
- 0:30Compare the survey observations and coding instructions.
- 0:34The software identifies the conflict; it does
- 0:36not choose a replacement rating for you.
- 0:39Another check compares segment length with the
- 0:41implemented rural baseline of two kilometres, with
- 0:44a fifty-percent band. Urban context needs careful
- 0:48review because the current check uses the
- 0:50rural baseline. Reported condition-index fields are checked
- 0:53against zero to one hundred where present.
- 0:56A range check is distinct from recalculating
- 0:59the index or confirming the physical condition
- 1:01on site. Review each finding in context,
- 1:05correct the source evidence when justified and
- 1:07rerun. Preserve legitimate exceptions through the review
- 1:11workflow. Never change a rating merely to
- 1:13make the warning disappear.
Two valid ratings can conflict
Both values may fit their individual fields, yet tell conflicting stories. A flexible-pavement record reports severe bleeding alongside very good skid resistance. That relationship needs engineering review.
The implemented paired check raises a warning when bleeding degree is at least four and skid-resistance degree is at most two. It is this specific pairing, not a promise to detect every distress contradiction.
Inspect the underlying survey
Our example uses bleeding four and skid resistance two. Compare the survey observations and coding instructions. The software identifies the conflict; it does not choose a replacement rating for you.
Another check compares segment length with the implemented rural baseline of two kilometres, with a fifty-percent band. Urban context needs careful review because the current check uses the rural baseline.
Investigate the pair instead of changing one score
The fictional BLEEDING_DEG value 4 and SKID_RESISTANCE_DEG value 2 match the implemented warning pairing described in the film. Both values can fit their individual declared domains while their relationship still requires review. Inspect the assessment notes and coding guidance before deciding whether either field was exported incorrectly.
A reported condition index within 0–100 has passed a range condition only. It has not necessarily been recalculated or confirmed against field evidence. Segment-length warnings also need their stated baseline and project context, especially when urban conditions differ from an implemented rural baseline.
Check index ranges separately
Reported condition-index fields are checked against zero to one hundred where present. A range check is distinct from recalculating the index or confirming the physical condition on site.
Review each finding in context, correct the source evidence when justified and rerun. Preserve legitimate exceptions through the review workflow. Never change a rating merely to make the warning disappear.
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.