Watch the overview
About 2 minutes. A narrated explainer; the transcript is below. The written guide includes additional detail.
Read the video text
- 0:00Our training uploader has corrected a survey. This lesson follows the review decision through co-sign and final approval, with separate responsibilities made explicit.
- 0:09Confirm the current file, template, reference context and processing result. An earlier clean result must not be used as evidence for a changed source.
- 0:19Review error findings and permitted exceptions before requesting co-sign. A raw error count can include an accepted exception, so read the record rather than guessing from a colour.
- 0:29DEMO 001 still contains a reversed segment with no accepted exception. Correct or resolve it through the allowed workflow before asking the next signer to proceed.
- 0:39Use the next action shown on the submission when your permissions allow it. The file then awaits review and co-sign; requesting the step is not the signature itself.
- 0:49An eligible reviewer reads the evidence and records the co-sign. The workflow then moves to awaiting final approval, with that reviewer recorded.
- 0:57The final certifier must differ from both the uploader and the co-signer. The uploader may be allowed to co-sign, but cannot issue final certification for their own upload.
- 1:07In our example, Training uploader supplies the file, Training reviewer co-signs, and Training engineer performs final approval. Role permission and file scope still determine eligibility.
- 1:18Where projects apply, advisory alignment adds information while required alignment can gate sign-off. Read the actual policy and current result; missing-reference skips are not passes.
- 1:29Certification can have a credit requirement. Resolve the displayed shortfall through the billing workflow, then return to the file and confirm the available action.
- 1:38Final certification links the decision to the stored-file fingerprint. It does not guarantee that field measurements are accurate or remove the reviewer's professional responsibility.
- 1:49Pause here. Name the next step for a co-signed file and identify who is eligible to certify it. Explain why the uploader and co-signer cannot be the final certifier.
Prepare a defensible handover
Our training uploader has corrected a survey. This lesson follows the review decision through co-sign and final approval, with separate responsibilities made explicit. Confirm the current file, template, reference context and processing result. An earlier clean result must not be used as evidence for a changed source. Review error findings and permitted exceptions before requesting co-sign. A raw error count can include an accepted exception, so read the record rather than guessing from a colour.
Example: an unresolved error
DEMO 001 still contains a reversed segment with no accepted exception. Correct or resolve it through the allowed workflow before asking the next signer to proceed. Use the next action shown on the submission when your permissions allow it. The file then awaits review and co-sign; requesting the step is not the signature itself. An eligible reviewer reads the evidence and records the co-sign. The workflow then moves to awaiting final approval, with that reviewer recorded.
Keep final approval independent
The final certifier must differ from both the uploader and the co-signer. The uploader may be allowed to co-sign, but cannot issue final certification for their own upload. In our example, Training uploader supplies the file, Training reviewer co-signs, and Training engineer performs final approval. Role permission and file scope still determine eligibility. Where projects apply, advisory alignment adds information while required alignment can gate sign-off. Read the actual policy and current result; missing-reference skips are not passes.
Check credit when prompted
Certification can have a credit requirement. Resolve the displayed shortfall through the billing workflow, then return to the file and confirm the available action. Final certification links the decision to the stored-file fingerprint. It does not guarantee that field measurements are accurate or remove the reviewer's professional responsibility.
Keep the approval evidence independent
The uploader, co-signer and final certifier have different responsibilities. Confirm eligibility for the current file and check whether a new analysis has changed the evidence since an earlier approval. A role label alone does not establish that the person can take the next action on this particular record.
Read unresolved errors, permitted exceptions and the current alignment policy before signing. The recorded decision concerns the reviewed file; it does not automatically extend to a later replacement with the same filename.
Practise and check your interpretation
Pause here. Name the next step for a co-signed file and identify who is eligible to certify it. Explain why the uploader and co-signer cannot be the final certifier.
A co-signed file next awaits final approval. The certifier needs the relevant authority and scope and must differ from both the uploader and co-signer. Our exercise assigns those jobs to Training uploader, Training reviewer and Training engineer. The uploader may be permitted to co-sign, but cannot finally certify their own upload. Check the current source, unresolved findings, alignment policy and any credit prompt before proceeding.
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.