BurntAI

How to build an unused GitHub Copilot seats report per team

By Jiri Sifalda

To build an unused GitHub Copilot seats report per team, take each seat's last activity date, mark the seats with no activity in your chosen window, and group them by the team that owns each person. GitHub gives you the first two parts. The grouping by team is yours to do.

This guide shows where the activity data lives, what it can and cannot prove, and how to turn it into one row per team.

Key takeaways

  • The seat list API and the activity report both give a last_activity_at date for each seat.
  • An empty or old date does not prove a seat is unused. IDE telemetry can be off, and updates can lag up to 24 hours.
  • The assigning_team field shows only the team that granted the seat. For a real per-team view, join the seats to your team membership.
  • A seat you remove stays active, and billed, until the end of the current billing cycle. Run the report before the cycle ends.

What an unused seat costs

GitHub lists Copilot Business at $19 per granted seat per month and Copilot Enterprise at $39 per granted seat per month (GitHub Copilot plans). The price is per granted seat, so a seat costs the same whether its holder uses it every day or never.

Under usage-based billing, the AI credits each person consumes come on top of the seat (usage-based billing for organizations and enterprises). An idle seat consumes no credits, so its full cost is the seat price. You can find it without any usage math.

Where GitHub shows seat activity

GitHub gives organization owners three views of the same activity data (reviewing user activity data).

The Access page

Open your organization's Settings, click Copilot, then Access. The page shows how many seats are assigned and the estimated monthly cost. Under "Access management", you can sort users by when they last used Copilot. This is enough for a quick look at a small organization.

The activity report

On the same page, you can download the Activity report as a CSV file. Its fields are report_time, login, last_authenticated_at, last_activity_at and last_surface_used (metrics data properties). GitHub says the report refreshes every 30 minutes and keeps historical data for 90 days (GitHub changelog). Enterprise administrators can download it from Your enterprise, then Policies, Copilot and Access.

The seat list API

For a scheduled report, use GET /orgs/{org}/copilot/billing/seats. Each seat includes assignee, assigning_team, created_at, last_activity_at, last_activity_editor, last_authenticated_at, plan_type and pending_cancellation_date (Copilot user management REST reference). Only organization owners can call it, and classic tokens need the manage_billing:copilot or read:org scope.

What counts as activity

GitHub updates last_activity_at when a user does any of these (metrics data properties):

  • Receives a code suggestion in an IDE.
  • Chats with Copilot Chat in an IDE or on GitHub.
  • Generates a pull request summary.
  • Uses Copilot on a mobile device or in Copilot Chat for CLI.

Three details stop you from reading an empty date as an unused seat:

  • IDE activity needs telemetry. Users must have telemetry enabled in their IDE for that use to show up. GitHub also notes that telemetry from some third-party IDEs may be incomplete, mainly on older versions.
  • The date can lag. Processing new events can take up to 24 hours. GitHub's advice is to wait 24 hours, then ask the user to check their telemetry settings.
  • A new seat has no history. Compare created_at with your window, so you do not flag a seat granted last week.

last_authenticated_at helps here. A seat with no authentication in your window is a stronger sign of no use than a missing activity date alone.

Why the report needs your team list

The assigning_team field names the team through which a user got a seat, if any. It is not the same as the team that person works in:

  • A seat granted directly to a user has no assigning team.
  • A person can belong to several GitHub teams, but only one team assigned the seat.
  • Your cost owner may be a team that does not exist in GitHub at all.

So decide first which team owns each person. Use your GitHub teams from GET /orgs/{org}/teams/{team_slug}/members (team members REST reference), or a mapping from your HR or finance system. Give each login exactly one owning team, so no seat counts twice.

Build the report

  1. Pull the seats. Call the seat list API, or download the activity report.
  2. Pick a window. A 30-day window matches one billing cycle.
  3. Mark each seat. A seat is a candidate when last_activity_at is empty or older than the window, and created_at is older than the window.
  4. Check authentication. Split candidates into two groups: no authentication in the window, and authentication without recorded activity. The second group may be a telemetry gap.
  5. Join to teams. Add the owning team for each login from your team mapping.
  6. Price it. Multiply each candidate by its seat price from plan_type: $19 for Business, $39 for Enterprise.
  7. Group by team. One row per team: seats held, candidate seats, and the monthly cost of the candidates.
  8. Ask before you remove. Send each team lead their list. A developer on leave or with telemetry off is not an unused seat.

Remove seats before the cycle ends

When you remove a seat, it moves to "pending cancellation". The user loses access at the end of the current billing cycle, unless they keep access through another team (Copilot user management REST reference). If you remove a seat during a cycle, the user keeps Copilot for the rest of that cycle (revoking access).

Two consequences follow:

  • Removing a person does not always remove the seat. If they also get Copilot through another team, an enterprise team or an individual plan, they keep it. Check every assignment path before you count a saving.
  • Timing matters. Run the report a few days before the cycle ends, so the team leads can answer in time.

Idle seats are not the only waste

An unused seat is the clearest waste, but a team can also overspend on credits or on a second tool such as Claude. The per-developer Copilot cost guide shows how to add each person's credits to their seat price.

BurntAI is built to put each person's seat fee and metered spend in one combined cost, across GitHub and Anthropic. See pricing to get on the list.

See every dollar your team spends on AI

See every developer's GitHub Copilot and Claude spend in one dashboard. Track per-person AI costs, set budgets, and catch overspend before the invoice lands.