{"meta":{"title":"Viewing the Copilot impact dashboard","intro":"The impact dashboard shows how deeply your organization has adopted Copilot, and how that adoption connects to pull request output.","product":"GitHub Copilot","breadcrumbs":[{"href":"/en/copilot","title":"GitHub Copilot"},{"href":"/en/copilot/how-tos","title":"How-tos"},{"href":"/en/copilot/how-tos/administer-copilot","title":"Administer Copilot"},{"href":"/en/copilot/how-tos/administer-copilot/view-impact-dashboard","title":"View impact dashboard"}],"documentType":"article"},"body":"# Viewing the Copilot impact dashboard\n\nThe impact dashboard shows how deeply your organization has adopted Copilot, and how that adoption connects to pull request output.\n\nInstead of a flat active-user count, the impact dashboard groups users into adoption cohorts based on how they engage with Copilot, and connects that engagement to pull request throughput. This gives you a more meaningful signal of adoption depth than daily or weekly active user counts alone.\n\nFor a detailed explanation of what the dashboard shows, including adoption cohorts, engagement trends, potential return on investment, and recommendations, see [GitHub Copilot usage metrics](/en/copilot/concepts/copilot-usage-metrics/copilot-metrics).\n\n## Prerequisite\n\nTo access Copilot usage metrics, the **\"Copilot usage metrics\"** policy must be enabled:\n\n* [Managing policies and features for GitHub Copilot in your enterprise](/en/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-enterprise-policies#defining-policies-for-your-enterprise)\n* [Managing policies and features for GitHub Copilot in your organization](/en/copilot/how-tos/administer-copilot/manage-for-organization/manage-policies#enabling-copilot-features-and-models-in-your-organization)\n\n## Accessing the dashboard\n\n1. Navigate to your enterprise. For example, from the [Enterprises](https://github.com/settings/enterprises?ref_product=ghec\\&ref_type=engagement\\&ref_style=text) page on GitHub.com.\n2. Click the **Insights** tab.\n3. In the left sidebar, click **Copilot impact**.\n\n## Estimating potential return on investment\n\nThe \"Potential return on investment\" section provides a directional comparison of cost and pull request output across adoption phases.\n\n1. Under \"Average developer cost in your organization\", select a compensation band.\n2. In the \"Transition your developers to be agent-first\" card, compare the cost, payroll, and pull request estimates for \"Phase 0-1 Passive and Code First Users\" and \"Phase 2-3 Agent First Users\".\n\nTreat the figures as directional estimates rather than exact financial results. Use them with the adoption multiplier metrics for code shipped and time to merge pull requests."}