Review session decisions
Use Sessions to investigate recorded activity across the applications you can access. Start with a specific question, then open Time Machine to inspect the evidence behind a result. Filters and actions depend on your role.
Find the relevant sessions
Choose an application and period, or search for a known session using the fields available in your view. Use the question to guide your next filter:
- For a guardrail change, narrow by the affected application, period, and available guardrail or policy filters.
- For audit work, confirm the review period and authorized application scope first.
- For an incident, use its recorded session identifier when available. Check that the result matches the application and event time.
A list with no matches does not prove that no activity occurred. Check the filters and your access before drawing that conclusion.
Investigate a change in results
Suppose governance results declined after a model update. Start with sessions from the affected application around the change date.
- Compare the recorded model or service version, outcome, and policy results where those fields are available.
- Open a session with an unexpected result in Time Machine.
- Inspect the relevant steps and the data supplied to the rule.
- Check whether rules, inputs, or reporting also changed during the period.
A shared model version is a lead, not proof of cause. Keep the suspected explanation separate from what the records establish.
For a before-and-after review, use comparable periods and types of work. Note differences in volume, missing data, and policy versions. Use Analytics for the comparisons available to your role.
Review sessions for an audit
Confirm the audit period and application scope, then use available risk and review-status filters to find records needing attention. Open each session to inspect its evidence. Age alone does not establish that a review is overdue; check the assigned deadline.
If your role allows batch review, inspect the selected sessions and recommendation before submitting a shared decision. Do not group records only because they have the same risk label. Your reason must apply to every selected session.
Auditors review evidence within their engagement scope. Read-only access does not authorize submitting a review or changing a session.
Interpret risk without assuming an outcome
Risk labels help prioritize investigation. Read them with the matched policy, available evidence, and application context. A high-risk label does not prove harm occurred, and a low-risk label does not establish compliance.
A risk label is not confirmation that someone was notified or assigned a review. Check the configured rule and the resulting alert or review record.
Export the evidence you need
Use the export actions available to your role. Check whether the action covers selected sessions, filtered results, or another stated scope before submitting it.
Keep the application scope, period, and selection with the exported file. Review its contents before sharing through an approved channel. Do not assume a list export contains every session detail or an integrity proof.
For an audit package, follow Export compliance evidence. That guide covers package scope, contents, and verification.