Watch the overview
About 2 minutes. A narrated explainer; the transcript is below. The written guide includes additional detail.
Read the video text
- 0:00The training team needs to understand a review handover. We will use activity history to find a recorded action and connect it to the affected file.
- 0:08The page shows recorded actions, when they occurred, the person or system involved, and the affected item. These records are not edited on this page.
- 0:17Start with the period covering the event. A narrow range reduces unrelated activity, but widen it if the expected record may fall outside that window.
- 0:27Our training reviewer is looking for the action that requested co-sign on DEMO 001. Filter by an appropriate event type and inspect the affected item.
- 0:36The actor can be a person or a system. In this course all identities are fictional role labels, so no real names or emails appear.
- 0:45An upload, completed analysis and review action are distinct events. Their order provides context, but does not prove that every engineering issue was resolved.
- 0:55Open the relevant file or supporting record to read its current result. An old activity event should not replace checking the current state.
- 1:03If you have export permission, use the filtered CSV export for an appropriate audit task. Treat the exported activity information with the same care as the platform view.
- 1:14Pause here. Find a training review event, identify its affected file and explain what further evidence you need before concluding that the file was approved.
Answer who changed what
The training team needs to understand a review handover. We will use activity history to find a recorded action and connect it to the affected file. The page shows recorded actions, when they occurred, the person or system involved, and the affected item. These records are not edited on this page.
Set a useful time range
Start with the period covering the event. A narrow range reduces unrelated activity, but widen it if the expected record may fall outside that window. Our training reviewer is looking for the action that requested co-sign on DEMO 001. Filter by an appropriate event type and inspect the affected item.
Use the actor filter carefully
The actor can be a person or a system. In this course all identities are fictional role labels, so no real names or emails appear. An upload, completed analysis and review action are distinct events. Their order provides context, but does not prove that every engineering issue was resolved.
Follow the affected record
Open the relevant file or supporting record to read its current result. An old activity event should not replace checking the current state. If you have export permission, use the filtered CSV export for an appropriate audit task. Treat the exported activity information with the same care as the platform view.
Use events as a trail, not a verdict
An upload event at 08:00 and a co-sign request at 08:10 establish an order of actions in the training example. They do not prove that every applicable check passed between those times. Open the affected file and inspect the result associated with the event.
Keep the actor, action, time and item together when reviewing activity. Similar filenames or events near each other can concern different records. The history helps explain who did what; it does not replace the underlying findings or source evidence.
Practise and check your interpretation
Pause here. Find a training review event, identify its affected file and explain what further evidence you need before concluding that the file was approved.
Find the co-sign request event and inspect the affected file and actor. A request does not prove a co-sign or final approval occurred. Follow the current file state and later events. Narrow the period and event filter, then widen it if needed. Export only the records needed for the authorised audit task.
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.