# Measure and demonstrate the impact of GitHub Copilot

Understanding how Copilot is used across your enterprise is the first step to demonstrating its value. Follow this path to establish a usage baseline, see how code is being generated, and connect adoption to measurable outcomes.

## Links

### Phase 1: Choose metrics to monitor Copilot adoption.

* [GitHub Copilot usage metrics](/en/copilot/concepts/copilot-usage-metrics/copilot-metrics)

  Copilot usage metrics provide visibility into how Copilot is adopted and used across your organization, including engagement, activity, code generation, and pull request lifecycle trends.

* [Data available in Copilot usage metrics](/en/copilot/reference/copilot-usage-metrics/copilot-usage-metrics)

  Copilot usage metrics data is available through the dashboard and APIs, using a consistent set of fields to represent adoption, usage, and code generation activity.

### Phase 2: Monitor usage and adoption

* [Viewing the Copilot usage metrics dashboard](/en/copilot/how-tos/administer-copilot/view-usage-and-adoption)

  Monitor adoption trends and use of Copilot to support long-term enablement.

* [Tracking license activation and initial usage with Copilot usage metrics](/en/copilot/tutorials/roll-out-at-scale/assign-licenses/track-usage-and-adoption)

  Identify and act on GitHub Copilot adoption signals and activation with usage metrics.

* [Interpreting usage and adoption metrics for GitHub Copilot](/en/copilot/reference/copilot-usage-metrics/interpret-copilot-metrics)

  Copilot usage and adoption metrics reveal patterns in how developers engage with Copilot across your enterprise.

### Phase 3: See how code is generated

* [Viewing the code generation dashboard](/en/copilot/how-tos/administer-copilot/view-code-generation)

  The code generation dashboard shows how Copilot generates code across your enterprise, including activity from both users and agents.

* [Lines of Code metrics](/en/copilot/reference/copilot-usage-metrics/lines-of-code-metrics)

  Lines of Code metrics provide a directional measure of Copilot output by quantifying the lines of code suggested, added, or deleted across completions, chat, and agent features.

### Phase 4: Connect adoption insights to engineering outcomes

* [Achieving your company's engineering goals with GitHub Copilot](/en/copilot/tutorials/roll-out-at-scale/drive-downstream-impact/achieve-company-goals)

  Plan your rollout based on GitHub's recommended approach for driving and measuring improvements.

* [Viewing the Copilot impact dashboard](/en/copilot/how-tos/administer-copilot/view-impact-dashboard)

  The impact dashboard shows how deeply your organization has adopted Copilot, and how that adoption connects to pull request output.