WEBVTT

1
00:00:00.000 --> 00:00:02.545
Harbour Roads Training has an invalid segment

2
00:00:02.555 --> 00:00:04.232
finding. We will trace it to the

3
00:00:04.232 --> 00:00:07.146
affected rows, correct the cause, and distinguish

4
00:00:07.146 --> 00:00:10.149
an exception from a passed check. Errors,

5
00:00:10.384 --> 00:00:12.813
warnings, passed checks and skipped checks mean

6
00:00:12.934 --> 00:00:15.401
different things. Read the selected template and

7
00:00:15.407 --> 00:00:17.684
the checks that actually ran before relying

8
00:00:17.690 --> 00:00:21.062
on the totals. Read its severity, reference,

9
00:00:21.113 --> 00:00:25.127
explanation and affected-row count. A finding describes

10
00:00:25.138 --> 00:00:27.647
an issue; the affected rows show where

11
00:00:27.659 --> 00:00:30.534
to investigate the source. The sample row

12
00:00:30.646 --> 00:00:33.120
starts at kilometre 2.5 and ends at

13
00:00:33.120 --> 00:00:36.138
2.0. The end lies before the start

14
00:00:36.177 --> 00:00:38.321
under this file's definition, so inspect the

15
00:00:38.360 --> 00:00:41.184
intended segment. Check the survey record and

16
00:00:41.278 --> 00:00:44.059
fix the original export. Do not swap

17
00:00:44.071 --> 00:00:46.195
numbers merely to remove an error if

18
00:00:46.207 --> 00:00:48.865
the underlying road or section is wrong.

19
00:00:49.007 --> 00:00:51.512
Two findings can affect the same row.

20
00:00:51.685 --> 00:00:53.593
Three rows in one finding and two

21
00:00:53.593 --> 00:00:56.138
in another do not necessarily mean five

22
00:00:56.149 --> 00:00:58.865
distinct bad rows. A warning may not

23
00:00:58.883 --> 00:01:01.890
block progression, but it still deserves review.

24
00:01:02.039 --> 00:01:04.563
Record your reasoning where the workflow provides

25
00:01:04.581 --> 00:01:06.615
a place for it. A skipped check

26
00:01:06.624 --> 00:01:10.263
was not executed. Missing fields, unsuitable file

27
00:01:10.273 --> 00:01:13.119
types or unavailable references can explain the

28
00:01:13.128 --> 00:01:15.260
gap. It must never be counted as

29
00:01:15.270 --> 00:01:17.256
a pass. If the rules and your

30
00:01:17.262 --> 00:01:20.047
permissions permit an exception, give a specific,

31
00:01:20.047 --> 00:01:23.283
evidence-based reason. The record preserves the finding

32
00:01:23.289 --> 00:01:25.082
and the reason; it does not make

33
00:01:25.082 --> 00:01:27.518
the measurement correct. Processing notes can be

34
00:01:27.598 --> 00:01:30.149
non-overridable because they record how the file

35
00:01:30.154 --> 00:01:32.480
was read. Correct the cause where possible

36
00:01:32.560 --> 00:01:34.736
and keep the interpretation with the result.

37
00:01:34.880 --> 00:01:38.244
Pause here. Identify the affected row and

38
00:01:38.456 --> 00:01:41.161
explain the evidence needed to correct it.

39
00:01:41.185 --> 00:01:44.361
Then distinguish a correction, a warning review

40
00:01:44.574 --> 00:01:46.526
and an allowed exception.