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

# Executive Summary

> Three scores for the whole organization, how they move over time, and every team side by side.

The **Executive Summary** tab answers "is our AI coding spend paying off, and where should I look?" in one screen. It is for executives: organization admins, and people whose role has the `ai-roi:executive` permission.

> [!NOTE]
>
> The tab appears once both required setup steps have data arriving. Until then, AI ROI opens on [Setup](https://help.nops.io/ai-roi/setup.md).

## What's on the tab

| Section | Answers | Details |
| - | - | - |
| [Executive summary](#executive-summary) | How are we doing this quarter? | Velocity, Productivity and Efficiency scores, each with the change against last quarter. |
| [Scores over time](#scores-over-time) | Are we getting better or worse? | A line per score across the date range. |
| [Teams](#teams) | Which team needs a look? | Every team's spend, PRs, cost per PR and scores, flagged teams first. |

Use the **On this page** rail on the left to jump between sections. The date range at the top applies to everything.

## Executive summary

Three score tiles, each out of 100:

* **Velocity**: how fast work reaches production.
* **Productivity**: how much AI spend turns into shipped work.
* **Efficiency**: how much AI spend was avoidable.

Each tile shows its band (**Good** at 70 and up, **Moderate** from 40 to 69, **Poor** under 40), the change against the comparison period (for example **+6 vs Q3**), and the figures behind it. Click a tile to pick out its line in the chart below.

How each score is built, and what moves it: [Scores](https://help.nops.io/ai-roi/scores.md).

## Scores over time

A line per score across the selected range. Each point scores the 28 days up to it (fewer near the start of the range), the same way the tiles are scored, so the last point matches the tiles. A point a day for short ranges, a point a week for long ones.

Days with too few released PRs have no point. If the whole range is too short or too quiet, the chart says "Not enough released PRs in this range to score yet."

Use the legend to hide or show a score.

## Teams

One row per team:

| Column | Meaning |
| - | - |
| **Team** | The team name, from [Manage teams](https://help.nops.io/ai-roi/teams.md). |
| **Spend** | AI coding spend of the team's people in the range. |
| **Vs before** | Spend change against the previous period, counting settled days only. Rises of 30% or more show in red. |
| **PRs** | Merged PRs by the team's people. |
| **Cost / PR** | AI cost per merged PR. |
| **Scores** | Velocity, productivity and efficiency, in that order. Hidden for a team with fewer than 5 engineers. |
| **Needs a look** | Why the team is flagged, if it is. |

A team is **flagged** when:

* its **cost per merged PR is up 25% or more** on the previous period (high at 50%), or
* its **spend is up 20% or more and at least 25 points ahead of its merged PRs** (spend is growing faster than output).

Both need at least 10 merged PRs in each period, so a small team's quiet week doesn't raise a flag. **Unassigned**, everyone who is on no team, is listed last and never flagged.

**Click a team to focus the whole page on it.** The tiles, the chart and the other tabs then show that team. The team's name appears at the top of the tab; click its **×** to go back to the whole organization.

> [!TIP]
>
> No Teams card? You haven't set up teams yet, or no team had activity in the range. See [Teams and people](https://help.nops.io/ai-roi/teams.md).

## Related

* [Scores](https://help.nops.io/ai-roi/scores.md): what each score measures and how it is calculated.
* [Engineering Overview](https://help.nops.io/ai-roi/engineering-overview.md): one team in detail.
* [How the numbers work](https://help.nops.io/ai-roi/how-the-numbers-work.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.