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

# Engineering Overview

> One team at a time, or all teams together. Where its AI spend goes, its people, every merged PR and what it cost.

The **Engineering Overview** tab is for engineering managers. It shows one team at a time, or all teams together, in enough detail to act on: who is spending, what it bought, and which PRs or people need a look.

**Who sees it:** executives, and engineering managers (a role with the `ai-roi:manager` permission). Before teams are set up, the approver of a Wallets group also sees that group here. See [Who sees what](https://help.nops.io/ai-roi/access.md).

> [!NOTE]
>
> The Engineering Overview needs teams. If none are set up, the tab shows a single "set up teams" section. See [Teams and people](https://help.nops.io/ai-roi/teams.md).

## Pick a team

Choose a team, or **All teams**, at the top of the tab. Executives and engineering managers open on **All teams**; others open on their own team.

**All teams** covers everyone who is on a named team. People on no team ("Unassigned"), PRs that matched no one, and spend from automated agents are left out of this tab. The Executive Summary still counts them.

## What's on the tab

| Section | Answers |
| - | - |
| [Engineering overview](#engineering-overview) | How is this team doing, and what does it spend? |
| [Where the PR cost goes](#where-the-pr-cost-goes) | Which workstreams does the team's PR cost go to? |
| [Where the spend goes](#where-the-spend-goes) | How does all AI spend split by repository, work type and outcome? |
| [People](#people) | Who is spending, what did they ship, and who needs a check-in? |
| [Engineering & PRs](#engineering-and-prs) | Every merged PR, its AI cost and what came back. |
| [Teams setup](#teams-setup) | Who is on which team (for people who can manage teams). |
| [Use cases](#use-cases) | Which product domains, technical areas and repositories AI is used on. |

## Engineering overview

The team's three [scores](https://help.nops.io/ai-roi/scores.md) (Velocity, Productivity, Efficiency), compared with the organization. A team with fewer than 5 engineers shows no scores to people outside it.

Below the scores, **Where the team stands** shows five tiles and a spend chart:

| Tile | Meaning |
| - | - |
| **PRs merged** | Merged PRs by the team's people in the range. |
| **Spend tied to PRs** | The share of the team's AI spend credited to a merged PR. The rest is exploration, research, work not merged yet, or spend from someone whose code host login isn't matched yet. |
| **Spend per engineer** | AI coding spend per engineer per month. |
| **Written by AI** | The share of merged lines the AI tools say they wrote. See [Written by AI](https://help.nops.io/ai-roi/how-the-numbers-work.md#written-by-ai). |
| **Engineers using AI** | People on the team with AI coding spend in the range. |

The chart shows daily AI coding spend for ranges up to about three months. Switch it between **Tool**, **Model**, **Person** and, on All teams, **Team**. The largest groups get their own color; the rest fold into "Other".

## Where the PR cost goes

The AI cost of the team's merged PRs, grouped into workstreams (a Linear project or Jira epic when the PR names a ticket, else the repository). Toggle between **Map**, a treemap sized by cost, and **List**, a ranked list. Every PR behind it is in [Engineering & PRs](#engineering-and-prs).

## Where the spend goes

A flow from a source to a **work type** (Build, Fix, Understand, Docs, Ship, Other) to an **outcome**:

* **Merged**: spend tied to a merged PR.
* **No merged PR**: exploration, research, unfinished work, or spend not linked to a PR.

Switch the source between **Repository** and **Team** (it opens on Repository for one team, Team for all teams). All the team's AI spend is in the flow, so it adds up to the team's spend. Use the **Flow / Table** toggle to see the same numbers as a table.

Under the chart, a bar shows **where each work type came from**: the PR title or branch, a linked ticket, the [AI ROI Agent](https://help.nops.io/ai-roi/agent/overview.md), or "Not categorized". The larger the agent's share, the more the split rests on labels chosen on developers' machines. See [Work types](https://help.nops.io/ai-roi/how-the-numbers-work.md#work-types).

## People

One row per person on the team, flagged first:

| Column | Meaning |
| - | - |
| **Person** | Name, work email and, if matched, code host login. |
| **Spend** | AI coding spend in the range. |
| **Vs before** | The change against their own spend over the previous period. |
| **PRs** | Merged PRs. |
| **Cost / PR** | AI cost per merged PR. |
| **Scores** | Velocity, productivity, efficiency, in that order. |
| **Needs a look** | Why they are flagged, in words. |

### Flags

Flags are prompts for a conversation, never a verdict. A person can be flagged for:

| Flag | When |
| - | - |
| **Anomaly** | nOps [Anomalies](https://help.nops.io/inform/anomalies.md) found unusual AI spend for this person, or named them as a main driver of an anomaly on a tool or model. Click it to open the anomaly. |
| **Spend spike** | Spend at least doubled on the previous period and rose by $200 or more (high at 3× and $500). Not raised when an anomaly already covers it. |
| **New spend** | \$500 or more with no spend before: new to AI tools, or a seat that was idle. |
| **Little shipped** | \$300 or more of spend, with under a quarter of it tied to merged PRs. Only for people matched to a code host. |
| **Costly PR** | A PR that cost 5× the team's median PR and at least \$100. Click it to open the PR. |
| **Stuck sessions** | Three or more [AI ROI Agent](https://help.nops.io/ai-roi/agent/overview.md) sessions that repeated the same command or hit a run of failing tool calls. A pairing session or better repository instructions usually help. |

## Engineering and PRs

Every PR merged in the range, framed as return on AI:

* **Return on AI-assisted work** shows the AI cost of the PRs shown, the share that is AI-assisted and the cost per output point, and compares AI-assisted PRs with the rest on median AI cost per PR, output per PR, median time to merge and estimated rework.
* **By type of work** shows each work type's AI cost, PR count against the previous period, cost per PR and rework. Click a type to filter the list.
* **Pull requests** lists every PR. Search, show **All**, **AI-assisted** or **Other** PRs, and sort by **Costliest**, **Newest**, **Most output** or **Slowest**. The figures above follow the filters.

A cost shown with **\~** is an estimate (no agent data for that PR). **Arriving** means the PR merged after the last day with final spend, so its cost isn't counted yet. **—** means the author isn't matched to anyone. See [How the numbers work](https://help.nops.io/ai-roi/how-the-numbers-work.md).

This section follows the page's scope: an executive's focused team, a manager's chosen team, or a developer's own PRs.

## Teams setup

A summary of who is on which team, with a **Manage teams** button. Shown to people who can manage teams. See [Teams and people](https://help.nops.io/ai-roi/teams.md).

## Use cases

Three ranked lists of where AI work goes:

* **Top product domains**: the Linear projects and Jira epics of merged PRs.
* **Top technical areas**: frontend, backend, infrastructure, testing and so on, from changed files and agent edits. Tests count toward the change they test.
* **Top repositories**: the repositories of merged PRs.

## Related

* [Scores](https://help.nops.io/ai-roi/scores.md)
* [How the numbers work](https://help.nops.io/ai-roi/how-the-numbers-work.md)
* [Teams and people](https://help.nops.io/ai-roi/teams.md)


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