Quick answer
Team Copilot analytics should answer three questions: how many seats are active, how many credits each active seat consumes, and which workflows consume the most. Segment by team and model, not by individual, and report monthly against a forecast.
Set up the segments
- Map seats to teams in your identity provider or a spreadsheet.
- Pull usage for the billing period.
- Join the two and aggregate by team.
- Split premium and default-model usage.
- Compare with the previous period, noting plan changes.
Avoid surveillance
- Report by team first; individual detail only for a specific investigation.
- Do not publish a leaderboard of credits.
- Explain that high usage can mean high value or a loop.
- Give developers their own balance before managers see aggregates.
Decisions the data supports
| Signal | Decision |
|---|---|
| Many inactive seats | Reclaim or reassign |
| One team far above others | Check workflow, not discipline |
| Premium share rising | Add model guidance |
| Consistent overage | Change plan or add a cap |
| Low adoption after training | Fix onboarding |
Reading team analytics
Organization analytics answer seat questions: who is active, which teams use the allowance, and whether the purchased seats match demand. They are poor tools for judging individuals, because usage follows task mix more than effort.
- Compare active seats with paid seats first.
- Look at the distribution, not the average.
- Check whether one team's heavy use is a project phase.
- Only then consider changing seat counts.
For per-person policy, see business seat usage; for the metric definitions, Copilot usage stats.
Questions, answered
Can Copilot analytics show team-level usage?
Organization reports provide seat and usage data that you can aggregate by team. Teams are not a native dimension in every plan.
Should managers see individual usage?
Only with a stated purpose and consent. Aggregate reporting answers most budget questions without it.
How often should team analytics refresh?
Monthly for budget decisions, weekly for an active rollout. Daily detail encourages noise-chasing.