> ## 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.

# Coaching with Scorecard Results

> Use scorecard task results to prepare targeted coaching conversations.

## Overview

Every completed roleplay round produces a scorecard: a 0-100 score plus a verdict for each task the mission asked the learner to accomplish. The score tells you *whether* to coach; the task verdicts tell you *what* to coach. You'll find both on any session you open from [a learner's profile](/external/coach/user-documentation/reviewing-learner-performance) - reviewing other people's sessions requires the **Coach** role.

## Reading the scorecard

The headline number - 70 or above marks the mission **Completed** - sits at the top of the feedback page, and the substance is in the task cards. Each task carries one of four statuses: **solved**, **partly solved**, **not yet solved**, or **not yet discussed**, with a sentence explaining the verdict. Expand **More details** to see the evaluated behaviours and the **Tips for next time** the AI gave the learner.

## Turning verdicts into coaching

The status patterns map to different conversations:

* **not yet discussed** usually means the learner never steered the conversation to that topic - practice call openings and agenda-setting, not the topic itself.
* **not yet solved** means they engaged and missed - the verdict text names what was missing, so roleplay that moment together and have them [retry the mission](/external/coach/user-documentation/feedback).
* **partly solved** across many rounds suggests a habit, not a one-off - quote the verdict text in your 1:1 and agree on one behaviour to change.
* **One bad task in an otherwise green scorecard** beats a vague "your score is low" conversation: it gives you and the learner one concrete, fixable thing.

Use the **Add comment** box on the session to anchor the conversation - the learner sees your comment next to the AI's feedback, and it's still there when they retry.

## What happens next

* A retry on the same mission shows whether the coached behaviour stuck - watch their next round's verdict on that task.
* Recurring weak tasks across the whole team point at content difficulty, not individual gaps - check [the Missions tab](/external/coach/user-documentation/monitoring-team-progress) before coaching anyone.
* The learner's lowest-scoring mission is always surfaced as **Areas for Improvement** on [their profile](/external/coach/user-documentation/reviewing-learner-performance) - a ready-made next assignment.

## Related articles

* [Reviewing a Learner's Performance](/external/coach/user-documentation/reviewing-learner-performance) - finding the sessions worth coaching on
* [Understanding Your Feedback](/external/coach/user-documentation/feedback) - the learner's view of the same scorecard
* [Assigning a Track to a Learner](/external/coach/user-documentation/assigning-tracks) - following up with targeted practice
* [Monitoring Your Team's Progress](/external/coach/user-documentation/monitoring-team-progress) - separating individual gaps from content problems

***

*Last updated: June 2026*