---
title: "Monitor training and prepare evidence"
description: "Use team progress, compliance views, reports and engagement findings together."
url: https://helpcenter.complytrain.net/en/articles/160-monitor-training-and-prepare-evidence
collection: "Training"
updated: 2026-09-22
language: en
---

# Monitor training and prepare evidence

Use team progress, compliance views, reports and engagement findings together.

Use team progress, compliance views, reports and engagement findings together.

## Start with the dashboard

Product location: `/training/dashboard`

Open **Training**, then **Dashboard**. Review active learners, open overdue assignments, completions in the displayed period, expiring certifications and the required-assignment completion measure. Check the date window and population before comparing results.

Open **Team** for member-level assignments, completion records and validity dates. A direct-report view is narrower than an organisation-wide compliance view.

## Investigate compliance gaps

Product location: `/training/compliance`

In **Compliance**, choose **Role** or **Department** under **Group by**. Open a heatmap cell to inspect its required population and the completed, overdue and not-started counts. An empty population or unavailable data should not be interpreted as full compliance.

In **Reports**, review the curriculum compliance rollup and completions trend. Use **Export pack** on the relevant curriculum row to prepare its PDF evidence pack. Review the resulting scope summary, population, per-user status and evidence detail before sharing it for an inspection.

## Review engagement anomalies

Product location: `/training/reports/anomalies`

Open **Engagement Anomalies** and filter by review status. Signals include unusually fast completion, reading-time violations, suspected video skimming, repeated-attempt patterns and sustained focus loss.

Investigate the underlying course, learner and circumstances. Then **Acknowledge** or **Dismiss** the finding, enter the required reason and **Confirm**. A signal is a reason to review the evidence, not a finding that the learner acted dishonestly.

Oversight permissions differ between team trends, compliance rollups and heatmap data. If access is refused, request the permission needed for the specific oversight task.
