Watch the overview
75 seconds. A narrated explainer; the transcript is below. The written guide includes additional detail.
Read the video text
- 0:00Our training reviewer receives an update about a survey. This lesson turns a notification into a verified action on the actual file.
- 0:07The page shows recent file and account updates. Unread styling identifies items you have not marked as read; it does not rank engineering severity.
- 0:16Check the notification's subject, time and related item. A request for review is different from confirmation that a review has already been completed.
- 0:25A training notification refers to DEMO 001. Open the related file and inspect its current status before deciding what action is appropriate.
- 0:35Another authorised person may have acted since the notification was created. The current file record is more reliable for deciding the next step than an older message alone.
- 0:45Mark read changes your notification state. It does not co-sign, certify or resolve findings on the survey.
- 0:52The page shows the latest fifty notifications. Mark all notifications as read also includes older notifications, so use it deliberately.
- 1:00Pause here. Open the sample update, locate its related record, and explain what marking the notification as read does and does not change.
Pick up the next step
Our training reviewer receives an update about a survey. This lesson turns a notification into a verified action on the actual file. The page shows recent file and account updates. Unread styling identifies items you have not marked as read; it does not rank engineering severity.
Read the message
Check the notification's subject, time and related item. A request for review is different from confirmation that a review has already been completed. A training notification refers to DEMO 001. Open the related file and inspect its current status before deciding what action is appropriate.
Allow for later changes
Another authorised person may have acted since the notification was created. The current file record is more reliable for deciding the next step than an older message alone. Mark read changes your notification state. It does not co-sign, certify or resolve findings on the survey.
Understand the list limit
The page shows the latest fifty notifications. Mark all notifications as read also includes older notifications, so use it deliberately.
A read notification does not resolve a finding
Marking a notification read changes its unread state for the account. It does not correct the survey, approve a result or record an engineering exception. Follow the related-file link and inspect the current state before taking the next action.
Notifications can refer to work that has changed since the event was created. Use them as a route to the record, then check the latest findings and available action. Keep review decisions in the supported file workflow rather than treating message state as evidence of approval.
Practise and check your interpretation
Pause here. Open the sample update, locate its related record, and explain what marking the notification as read does and does not change.
Open the related file to confirm its present state. Another person may already have acted after the notification was created. Mark read changes the notification’s unread flag; it does not approve, certify or resolve a finding. Mark all read also affects older notifications beyond the displayed latest fifty.
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.