> For the complete documentation index, see [llms.txt](https://guides.tability.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.tability.io/docs/become-a-tability-power-user/ai-mode-how-tos/review-your-teams.md).

# Review progress across your teams

Compare your teams using their plans, key results, and initiatives, then focus on where support is needed.

Get a consistent view of how your teams are tracking without opening every plan separately. AI Mode can summarise each team's progress and highlight where your attention would help this week.

**For:** Managers and execs · **Where:** AI Mode inside Tability

## Watch the walkthrough

{% embed url="<https://318707989-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMULqjSmZyGczPy2I6FGH%2Fuploads%2Fgit-blob-94226ba5b6bc6fb9517f6b180c0b236796e1b353%2Ftability-ai-mode-review-teams.mp4?alt=media>" %}
See how each team is tracking and where it needs attention this week. 30-second demo, no audio; fictional workspace data.
{% endembed %}

## 1. Confirm which teams to include

Open **AI Mode**. Name the teams, or ask it to resolve your teams from the workspace and confirm the scope.

```
Review my teams for this week. Confirm which teams and active plans you are including; if the workspace does not identify them clearly, ask me for names or links.

For each team, review plans, key results, recent check-ins, and initiatives. Show a compact table with team, plan, how it is tracking, what needs attention, and the most useful next step. Link the evidence. Keep missing updates visible and separate proposed actions from existing commitments. Do not change any records.
```

Different teams may use different measures or have different reporting coverage. Compare the evidence and support needed, rather than treating a single progress percentage as a team ranking.

## 2. Focus the discussion

Verify that each expected team appears and that the right plans are included. Open the sources behind the highest-priority issues.

```
For the teams needing attention, explain the main blocker, any cross-team dependency, and the decision or support needed from me. Suggest one focused question for each team lead. Do not infer a person's performance from missing updates.
```

If the main question is which goals need intervention, continue with [the weekly risk review](https://guides.tability.io/docs/become-a-tability-power-user/ai-mode-how-tos/review-weekly-risks.md).

## 3. Prepare the meeting and follow-up

Use the summary in your team-lead meeting and add the context people provide. For presentation materials, [prepare a team review deck](https://guides.tability.io/docs/become-a-tability-power-user/ai-mode-how-tos/prepare-team-review-deck.md) with one slide per team, or [export a review spreadsheet](https://guides.tability.io/docs/become-a-tability-power-user/ai-mode-how-tos/export-review-spreadsheet.md) for more detail.

After the meeting, ask AI Mode to turn the agreed decisions into proposed actions with owners and dates. Review any workspace changes before approving them.

**Done when:** every team in scope has a clear summary and you know where to provide help this week.

Explore the other [AI Mode how-tos](https://guides.tability.io/docs/become-a-tability-power-user/ai-mode-how-tos.md).
