Watch the overview
About 2 minutes. A narrated explainer; the transcript is below. The written guide includes additional detail.
Read the video text
- 0:00Harbour Roads Training has an invalid segment finding. We will trace it to the affected rows, correct the cause, and distinguish an exception from a passed check.
- 0:09Errors, warnings, passed checks and skipped checks mean different things. Read the selected template and the checks that actually ran before relying on the totals.
- 0:19Read its severity, reference, explanation and affected-row count. A finding describes an issue; the affected rows show where to investigate the source.
- 0:29The sample row starts at kilometre 2.5 and ends at 2.0. The end lies before the start under this file's definition, so inspect the intended segment.
- 0:39Check the survey record and fix the original export. Do not swap numbers merely to remove an error if the underlying road or section is wrong.
- 0:48Two findings can affect the same row. Three rows in one finding and two in another do not necessarily mean five distinct bad rows.
- 0:57A warning may not block progression, but it still deserves review. Record your reasoning where the workflow provides a place for it.
- 1:05A skipped check was not executed. Missing fields, unsuitable file types or unavailable references can explain the gap. It must never be counted as a pass.
- 1:16If the rules and your permissions permit an exception, give a specific, evidence-based reason. The record preserves the finding and the reason; it does not make the measurement correct.
- 1:26Processing notes can be non-overridable because they record how the file was read. Correct the cause where possible and keep the interpretation with the result.
- 1:34Pause here. Identify the affected row and explain the evidence needed to correct it. Then distinguish a correction, a warning review and an allowed exception.
Investigate one cause
Harbour Roads Training has an invalid segment finding. We will trace it to the affected rows, correct the cause, and distinguish an exception from a passed check. Errors, warnings, passed checks and skipped checks mean different things. Read the selected template and the checks that actually ran before relying on the totals. Read its severity, reference, explanation and affected-row count. A finding describes an issue; the affected rows show where to investigate the source.
Example: reversed kilometre range
The sample row starts at kilometre 2.5 and ends at 2.0. The end lies before the start under this file's definition, so inspect the intended segment. Check the survey record and fix the original export. Do not swap numbers merely to remove an error if the underlying road or section is wrong. Two findings can affect the same row. Three rows in one finding and two in another do not necessarily mean five distinct bad rows.
Warnings still need judgement
A warning may not block progression, but it still deserves review. Record your reasoning where the workflow provides a place for it. A skipped check was not executed. Missing fields, unsuitable file types or unavailable references can explain the gap. It must never be counted as a pass. If the rules and your permissions permit an exception, give a specific, evidence-based reason. The record preserves the finding and the reason; it does not make the measurement correct.
Some notes remain permanent
Processing notes can be non-overridable because they record how the file was read. Correct the cause where possible and keep the interpretation with the result.
A reversed interval needs source evidence
In the training example, START_KM is 2.500 and END_KM is 2.000. That ordering deserves investigation, but the finding does not reveal which endpoint was intended. Compare the original survey record and the applicable road reference. Only use a replacement end value of 3.000 if the source evidence actually supports it.
An exception records an authorised judgement about a finding. It is not a way to conceal missing information or invent measurements. Keep the reason specific to the current file, rule and affected records.
Practise and check your interpretation
Pause here. Identify the affected row and explain the evidence needed to correct it. Then distinguish a correction, a warning review and an allowed exception.
In training-road-condition-reversed.blc, data row 2 has START_KM 2.500 and END_KM 2.000. The local quality engine records TMH18§1.7/DQ-05. The corrected exercise changes END_KM to 3.000 because that is the intended fictional segment. The corrected range still produces a 500-metre segment-length warning under the current template; inspect the remaining findings. The separate 200-metre example has no findings in the recorded local run. In real work, establish segment intent from the survey evidence. An allowed exception preserves a finding and a reason; it does not turn the underlying measurement into a correct one. Overlapping row counts must not be added as distinct bad rows.
Use the signed-in onboarding library to record viewing progress and return to unfinished lessons. Watching the public article is useful for reference, but does not update your account’s lesson completion record.
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.