GitHub released a new Copilot impact dashboard on July 22, 2026. It gives enterprise administrators and organization owners a visual view of how deeply teams use Copilot, not only whether users are active.
What the new dashboard shows
The dashboard groups engaged users into Phase 1 (code-first), Phase 2 (agent-first) and Phase 3 (multi-agent or Copilot app). Licensed users who are not engaged appear in a passive cohort. Assignments use Copilot activity from a rolling 28-day window.
- Average pull requests merged per user per month and median pull request merge velocity for each cohort.
- User counts, cohort share and average lines of code per user per day.
- A six-month view of cohort growth and pull request throughput.
- Recommended actions intended to help administrators deepen adoption.
Why this matters for QA engineers
QA leaders can use the cohorts to see whether teams are moving from basic code completion toward agent-driven workflows. That can help target enablement, test-policy reviews and additional controls where agent use is growing fastest.
However, faster merges and more generated code are not proof of higher quality. Pair the dashboard with escaped-defect rates, flaky-test trends, CI pass rates, review rework and rollback frequency. GitHub also recommends combining usage data with developer feedback when evaluating Copilot’s impact.
Availability and measurement caveats
The impact dashboard is available to enterprise administrators and organization owners who can access Copilot usage metrics. GitHub says dashboard data can lag by up to three full UTC days. Detailed IDE activity also depends on telemetry, while Copilot CLI metrics are reported separately, so teams should avoid reading short-term dips as immediate behavior changes.
Sources
- GitHub Changelog: New Copilot usage metrics impact dashboard — July 22, 2026.
- GitHub Docs: Viewing the Copilot usage metrics dashboard — accessed July 22, 2026.
- GitHub Docs: Reconciling Copilot usage metrics — accessed July 22, 2026.