> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wejam.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Interpreting Team Reports

> Read team completion rates, score distributions, and trends in team reports.

## Overview

JAM's reporting lives on the **Progress** page (with the [Activity dashboard](/external/coach/user-documentation/monitoring-team-progress) covering engagement trends). Two filters scope everything you see: a team filter and a time-range filter, so the same tabs serve a weekly check-in and a quarterly review. Hover any **ⓘ** icon for the exact definition of a metric.

## Before you start

* You need the **Coach** role - the Progress page only shows data for teams you manage.

## What the key metrics mean

* **Average Score** - the mean score across all rounds in the selected scope. The completion bar is 70: a mission round scoring 70+ counts as **Completed**.
* **Average score improvement** - how much users improve from their *first* attempt to their *best* attempt on each mission, averaged across all missions. This is your best signal that practice is working: a team can have a modest average score and a healthy improvement number.
* **Rounds played vs. Rounds to complete** - on the **Missions** tab, rounds to complete is the average number of attempts needed to pass a mission. A high value flags hard content; combined with a low average score it tells you a mission needs coaching support (or a rethink) rather than more pressure.
* **Last time played / active users** - engagement metrics; a user counts as active in a week when they completed at least one roleplay round.

## Reading the patterns

Front-load your review with three comparisons:

* **Improvement vs. score.** Low score + positive improvement = learning in progress; low score + zero improvement = intervention needed.
* **One learner vs. the team.** If the team averages 75 on a mission and one person sits at 40, [drill into their rounds](/external/coach/user-documentation/reviewing-learner-performance). If everyone sits at 40, the mission is the problem.
* **This period vs. last.** The **Members** tab's last-week deltas and the Activity charts show direction - a falling active-user count predicts falling scores a week later.

## Sharing a report

There's no export button on the dashboards today. For a recurring leadership report, the practical options are a screenshot of the filtered view, or asking [Jammy](/external/coach/user-documentation/using-jammy) for the numbers in chat ("How's the Onboarding sprint going?") and pasting its summary.

## What happens next

* A metric worth acting on usually ends in one of three places: [a coaching conversation](/external/coach/user-documentation/coaching-with-scorecards), [a new assignment or sprint](/external/coach/user-documentation/assigning-sprints), or a deadline change ([due dates](/external/coach/user-documentation/setting-due-dates)).
* For engagement problems rather than performance problems, start with the [Activity dashboard](/external/coach/user-documentation/monitoring-team-progress) instead.

## Related articles

* [Monitoring Your Team's Progress](/external/coach/user-documentation/monitoring-team-progress) - the dashboards these metrics live on
* [Reviewing a Learner's Performance](/external/coach/user-documentation/reviewing-learner-performance) - following a number down to one person
* [Coaching with Scorecard Results](/external/coach/user-documentation/coaching-with-scorecards) - acting on what the report shows
* [Getting Answers and Taking Action with Jammy](/external/coach/user-documentation/using-jammy) - pulling the same numbers in chat

***

*Last updated: June 2026*