> For the complete documentation index, see [llms.txt](https://runporter.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://runporter.gitbook.io/docs/reviewing-a-conversation/coaching.md).

# Coaching

The **Coaching** tab is Porter's read on how you handled the conversation.

## The score

One number, top right, out of 100.

| Score            | How it reads                     |
| ---------------- | -------------------------------- |
| **90 and above** | Green. A strong conversation.    |
| **70–89**        | Neutral. Solid, with room in it. |
| **Below 70**     | Red. Worth going back over.      |

If it says **Not scored yet**, the coaching pass has not finished. It runs after the summary, so it is normal for the summary to be there first.

{% hint style="info" %}
Scores are out of 100, both overall and for each step. A 90 is 90%, not 9 out of 10.
{% endhint %}

## Coach's corner

Two sentences on the conversation as a whole — what worked, and what to do differently. Short on purpose: it is meant to be read between calls.

## The step breakdown

Tap **Show step breakdown** to expand it. Each step of your playbook gets its own score out of 100 and its own note.

The toggle always tells you how many steps came back, even before you expand it. That count is worth glancing at — if a conversation was scored against fewer steps than usual, the overall number is averaging over less than you think.

If you see **No step-by-step breakdown came back with this score**, take the overall number as less explained than usual rather than as a full verdict.

## What the score is for

It is a prompt for the next conversation, not a performance rating. The useful move is to open the [transcript](/docs/reviewing-a-conversation/transcript.md) at the step that scored lowest, read what you actually said, and then ask [Porter](/docs/ask-porter.md) what to say instead.