---
title: "Scorecards"
canonical_url: "https://docs.getdx.com/scorecards/overview/"
md_url: "https://docs.getdx.com/scorecards/overview.md"
last_updated: "2026-05-19"
---

# Scorecards
Scorecards help you drive visibility and action around operational excellence, production readiness, and infrastructure migrations.

Common uses cases for scorecards include:

- **Operational readiness:** Check if services are production-ready by looking at factors like ownership, documentation, runbooks, and infrastructure setup.
- **Service maturity:** Grade factors like code coverage, versioning, README quality, and other code health metrics.
- **Migrations:** Get visibility into progress, blocking issues, and other key metrics as you migrate services to new platforms or technologies.
- **DORA metrics:** Scorecards can track DORA metrics like deployment frequency, lead time for changes, and change fail rates. This provides insight into engineering efficiency and quality.

## Getting started

1. Ensure that your Software Catalog is populated with entities (either by [defining your services](https://docs.getdx.com/catalog/overview) or connecting your existing service catalog to DX).
2. Connect data sources like GitHub, Datadog, and IncidentIO using [DX data connectors](https://docs.getdx.com/using-dx/connectors) and [APIs](https://docs.getdx.com/apis/overview).
3. Create scorecards in DX to enable self-service reporting and drive action.

Scorecards are configured in the DX UI and define different levels (e.g., Gold, Silver, Bronze) with checks. Scorecard checks automatically re-evaluate every two hours.

![Scorecard settings](https://docs.getdx.com/assets/images/scorecards/scorecard-settings.png)

## Checks

Checks are written in SQL and run against entities using variables in your SQL query.

See the [Writing scorecard checks](https://docs.getdx.com/scorecards/writing-checks/) guide for more details and best-practices for writing checks.

![Scorecard checks editor](https://docs.getdx.com/assets/images/scorecards/scorecard-check-editor.png)

## Reporting

DX offers out-of-the-box reporting on scorecards so you can measure current progress towards standards as well as track trends over time. Out-of-the-box reports provide an overview of all scorecards as well as the ability to drill into an individual scorecard and filter and segment by various properties.

Additionally, you can create custom reporting and dashboards through [Data Studio](https://docs.getdx.com/using-dx/data-studio) to visualize your data in a way that answers questions specific to your teams and goals.

### Overview

The out-of-the-box report shows detailed breakdowns of check results across all entities. You can group this report by owner team and entity type to better understand how different teams and types of software are tracking towards standards.

![Scorecard checks report](https://docs.getdx.com/assets/images/scorecards/scorecard-checks-report.png)

### Trends

See check results over time either by the entire scorecard passing rate, or broken down by individual checks.

![Scorecard check trends](https://docs.getdx.com/assets/images/scorecards/scorecard-trends-checks.png)

Trends can also be broken down to view entity level achievement over time:

![Scorecard level trends](https://docs.getdx.com/assets/images/scorecards/scorecard-trends-levels.png)

## Performance Expectations

### Speed

Scorecard evaluations follow a simple formula: **1 minute per 1,000 queries**, with a minimum of 5 minutes.

In practice, this looks like:

| What's happening                            | How it's calculated                       | Time it takes |
| ------------------------------------------- | ----------------------------------------- | ------------- |
| Scorecard evaluates on schedule             | 6 checks × 2000 entities = 12,000 queries | 12 minutes    |
| Updating a scorecard with 800 entities      | 12 checks × 800 entities = 9,600 queries  | 10 minutes    |
| Start a scorecard evaluation with 24 checks | 24 checks × 100 entities = 2,400 queries  | 5 minutes     |

### Scorecard evaluation

- Scorecards automatically re-evaluate every two hours after the previous evaluation completes
- After you update a scorecard, changes show up within the expected processing time
- When you update an entity, all its scorecard checks re-evaluate within the expected processing time

### Computed properties

Properties such as file matching rules, or properties computed via SQL queries, have the folllowing performance expectations when invovled in a scorecard check:

- Evaluation of the property refreshes once per hour (i.e. property value is updated)
- Processing time follows the same formula based on the number of queries across all entities

### Data syncing

- Entities associated with scorecards sync on the scorecard's two-hour evaluation schedule
- Entities associated with initiatives sync on the initiative's scorecard evaluation schedule
- Entity updates sync to Data Cloud immediately
---

## Sitemap

[Overview of all docs pages](/llms.txt)