WEBVTT

1
00:00:00.000 --> 00:00:02.870
Our training uploader has corrected a survey.

2
00:00:02.911 --> 00:00:05.008
This lesson follows the review decision through

3
00:00:05.011 --> 00:00:08.250
co-sign and final approval, with separate responsibilities

4
00:00:08.254 --> 00:00:11.904
made explicit. Confirm the current file, template,

5
00:00:12.037 --> 00:00:15.154
reference context and processing result. An earlier

6
00:00:15.166 --> 00:00:17.157
clean result must not be used as

7
00:00:17.157 --> 00:00:20.010
evidence for a changed source. Review error

8
00:00:20.017 --> 00:00:23.714
findings and permitted exceptions before requesting co-sign.

9
00:00:23.722 --> 00:00:25.335
A raw error count can include an

10
00:00:25.342 --> 00:00:28.114
accepted exception, so read the record rather

11
00:00:28.121 --> 00:00:30.959
than guessing from a colour. DEMO 001

12
00:00:30.962 --> 00:00:33.072
still contains a reversed segment with no

13
00:00:33.074 --> 00:00:35.734
accepted exception. Correct or resolve it through

14
00:00:35.734 --> 00:00:37.953
the allowed workflow before asking the next

15
00:00:37.956 --> 00:00:40.606
signer to proceed. Use the next action

16
00:00:40.618 --> 00:00:42.568
shown on the submission when your permissions

17
00:00:42.662 --> 00:00:45.021
allow it. The file then awaits review

18
00:00:45.033 --> 00:00:47.772
and co-sign; requesting the step is not

19
00:00:47.772 --> 00:00:50.850
the signature itself. An eligible reviewer reads

20
00:00:50.858 --> 00:00:53.276
the evidence and records the co-sign. The

21
00:00:53.440 --> 00:00:56.014
workflow then moves to awaiting final approval,

22
00:00:56.022 --> 00:00:58.774
with that reviewer recorded. The final certifier

23
00:00:58.776 --> 00:01:00.736
must differ from both the uploader and

24
00:01:00.736 --> 00:01:02.909
the co-signer. The uploader may be allowed

25
00:01:02.910 --> 00:01:05.618
to co-sign, but cannot issue final certification

26
00:01:05.619 --> 00:01:08.199
for their own upload. In our example,

27
00:01:08.286 --> 00:01:11.190
Training uploader supplies the file, Training reviewer

28
00:01:11.199 --> 00:01:14.968
co-signs, and Training engineer performs final approval.

29
00:01:14.977 --> 00:01:17.487
Role permission and file scope still determine

30
00:01:17.535 --> 00:01:21.245
eligibility. Where projects apply, advisory alignment adds

31
00:01:21.249 --> 00:01:24.727
information while required alignment can gate sign-off.

32
00:01:24.769 --> 00:01:27.247
Read the actual policy and current result;

33
00:01:27.251 --> 00:01:31.018
missing-reference skips are not passes. Certification can

34
00:01:31.020 --> 00:01:33.476
have a credit requirement. Resolve the displayed

35
00:01:33.478 --> 00:01:36.007
shortfall through the billing workflow, then return

36
00:01:36.009 --> 00:01:37.742
to the file and confirm the available

37
00:01:37.889 --> 00:01:40.863
action. Final certification links the decision to

38
00:01:40.875 --> 00:01:43.962
the stored-file fingerprint. It does not guarantee

39
00:01:43.973 --> 00:01:46.489
that field measurements are accurate or remove

40
00:01:46.501 --> 00:01:50.578
the reviewer's professional responsibility. Pause here. Name

41
00:01:50.578 --> 00:01:52.817
the next step for a co-signed file

42
00:01:52.817 --> 00:01:55.342
and identify who is eligible to certify

43
00:01:55.358 --> 00:01:58.356
it. Explain why the uploader and co-signer

44
00:01:58.372 --> 00:02:00.596
cannot be the final certifier.