# Standardize and automate DORA benchmarks
To configure your Cortex workspace for DORA excellence, we recommend the following actions:
* **Connect Data**: [Ingest data and ensure ownership](#step-1-ingest-data-and-solve-ownership) is assigned to your entities
* **Improve**: [Review Eng Intelligence metrics to understand baseline metrics and take action](#step-5-review-and-act-on-eng-intelligenc) when issues are surfaced
* **Standardize**: [Configure a Scorecard](#step-2-configure-a-scorecard-for-production-readiness) to enforce and measure DORA standards
* **Streamline**: Use [Cortex MCP](#step-4-streamline-processes-via-cortex-mcp) to increase efficiency in incident response, leading to a decrease in MTTR
## Use Cortex features to meet DORA standards
Expand the tiles below to learn about configuring Cortex features to help you meet DORA standards.
Step 1: Ingest data and solve ownership 🔌
{% hint style="success" %}
**Action Items:**
* [**Import your data**](/ingesting-data-into-cortex/overview.md)
* [**Ensure ownership is set**](/ingesting-data-into-cortex/entities-overview/entities/ownership.md)
* [**Configure integrations**](/ingesting-data-into-cortex/integrations.md)
{% endhint %}
Before getting started on any use case, it is crucial to import your services, resources, infrastructure, and other entities, and to have clear visibility into the ownership of your entities.
Connecting your entities to Cortex establishes a single source of truth across your engineering organization. It enables the ability to track progress via Scorecards, automate Workflows, and gain insights from Eng Intelligence.
Setting ownership of entities ensures that every service and system is clearly linked to accountable teams or individuals, enabling faster incident response, reducing handoff friction, and making it possible to enforce standards consistently.
The more data you have available, the more actionable and insightful your Scorecards can be.
#### Relevant integrations
Cortex calculates your DORA metrics by connecting directly to your delivery and incident management tools.
To focus on DORA metric improvements, configure integrations in the following categories:
* **Version control**: [Azure DevOps](/ingesting-data-into-cortex/integrations/azuredevops.md), [Bitbucket](/ingesting-data-into-cortex/integrations/bitbucket.md), [GitHub](/ingesting-data-into-cortex/integrations/github.md), [GitLab](/ingesting-data-into-cortex/integrations/gitlab.md)
* Cortex pulls cycle time and other PR-related metrics from version control integrations.
* **Deploys**: Add deploy data to Cortex via the [deploys API](https://docs.cortex.io/ingesting-data-into-cortex/entities/deploys)
* This powers the metrics for deployment frequency and change failure rate.
* **Incidents**: [PagerDuty](https://docs.cortex.io/ingesting-data-into-cortex/integrations/pagerduty)
* Cortex pulls incident metrics, like incident frequency and MTTR, from PagerDuty.
* [**Custom metrics**](https://docs.cortex.io/improve/eng-intelligence/custom-metrics)
* If you use internal tools, configure custom metrics to ensure you are tracking events that impact DORA metrics
To increase efficiency across your processes, we also recommend that you integrate with other tools in your ecosystem. While these integrations don't populate your DORA Dashboard, they do contribute to ensuring reliability and quality in your software processes:
* **Project management**: [GitHub](https://docs.cortex.io/ingesting-data-into-cortex/integrations/github), [Jira](https://docs.cortex.io/ingesting-data-into-cortex/integrations/jira), [Azure DevOps](https://docs.cortex.io/ingesting-data-into-cortex/integrations/azuredevops), [ClickUp](https://docs.cortex.io/ingesting-data-into-cortex/integrations/clickup)
* Track incidents and bugs, allowing you to collaborate with your team and speed up resolution times
* **Code quality and security**: [Checkmarx](https://docs.cortex.io/ingesting-data-into-cortex/integrations/checkmarx), [Codecov](https://docs.cortex.io/ingesting-data-into-cortex/integrations/codecov), [Mend](https://docs.cortex.io/ingesting-data-into-cortex/integrations/mend), [Snyk](https://docs.cortex.io/ingesting-data-into-cortex/integrations/snyk), [SonarQube](https://docs.cortex.io/ingesting-data-into-cortex/integrations/sonarqube), [Veracode](https://docs.cortex.io/ingesting-data-into-cortex/integrations/veracode), [Wiz](https://docs.cortex.io/ingesting-data-into-cortex/integrations/wiz)
* Enforce code coverage, vulnerability scanning, and other quality measures
Cortex also recommends [inking to runbooks and documentation](https://docs.cortex.io/ingesting-data-into-cortex/entities/external-docs) for your entities, ensuring your users have access to critical information when solving an incident.
With your data in Cortex, you have a jumping-off point to start measuring DORA metrics and driving improvements.
Step 2: Review Eng Intelligence baseline metrics 📈
{% hint style="success" %}
**Action Items:**
* [**Review Eng Intelligence metrics**](/improve/eng-intelligence.md)
* If you track DORA metrics through unsupported or internal systems, **configure** [**custom metrics**](https://docs.cortex.io/improve/eng-intelligence/custom-metrics)
{% endhint %}
Use Eng Intelligence features — the [DORA dashboard](/improve/eng-intelligence/dashboards/dora-dashboard.md), [Velocity Dashboard](/improve/eng-intelligence/dashboards/velocity-dashboard.md), and [Metrics Explorer](/improve/eng-intelligence/metrics-explorer.md) — to surface and track key engineering metrics related to the software development lifecycle.
Review trends across the key DORA metrics to understand your team's baseline performance levels and use this information to identify areas where teams are not meeting standards. Launch [Scorecards](#step-3-create-a-dora-scorecard) to drive broader changes (e.g., set standards and improve all DORA metrics) and [Initiatives](/improve/initiatives.md) to drive targeted change (e.g., an Initiative that aims to improve MTTR over the next two months.)
#### Configure custom metrics
If your organization already tracks DORA-related metrics or other delivery KPIs through unsupported tools or internal systems, you can send that data into Cortex as [custom metrics](/improve/eng-intelligence/custom-metrics.md).
Step 3: Create a DORA Scorecard 📋
{% hint style="success" %}
**Action Item:** [**Create a Scorecard**](/standardize/scorecards/create.md) **for DORA**
{% endhint %}
Scorecards automate the process of checking whether services meet criteria such as ownership, on-call coverage, runbooks, monitoring, and security requirements.
Cortex's DORA Operational Readiness template includes a set of predefined rules which can be customized based on your organization's requirements and goals. It is based on the [established DORA standards of performance](/solutions/dora.md#understanding-dora-benchmarks-and-performance-levels). The Scorecard is structured into four levels, with each representing increasingly higher standards against DORA benchmarks.
#### Step 2.1: Create the Scorecard and configure the basics
1. On the [**Scorecards** page](https://app.getcortexapp.com/admin/scorecards) in your workspace, click **Create Scorecard**.
2. On the `DORA Operational Readiness` template, click **Use**.
3. Configure basic settings, including the Scorecard's name, unique identifier, description, and more.
1. Learn about configuring the basic settings in the [Creating a Scorecard documentation](/standardize/scorecards/create.md).
#### Step 2.2: Review and modify the rules
While Cortex's template is based on DORA standards, you may want to adjust the rules based on how your organization prioritizes standards and requirements. You can reorder, delete, and edit rules, you can add more rules to a level, and you can assign more points to a rule to signify its importance.
The Scorecard template contains rules that enforce increasingly higher DORA standards in each level, such as:
* MTTR less than 12 hours in the "Established" level and less than 60 minutes in the "Elite" level
* Change failure rate less than 30% in the "Established" level and less than 10% in the "Elite" level
When adding or changing the template rules, you can select from a list of available pre-built rules. Behind each rule is a [Cortex Query Language (CQL) ](/standardize/cql.md)query; you can also write your own queries to further refine your rules.
Step 4: Streamline processes via Cortex MCP 🤖
{% hint style="success" %}
**Action Item:** [**Configure Cortex MCP**](/get-started/mcp.md)
{% endhint %}
[Cortex MCP](/get-started/mcp.md) can significantly help during an incident by providing instant, conversational access to critical service and team information directly from your MCP client. This more efficient process can have a direct effect on reducing your MTTR.
Cortex MCP supports incident response by providing:
* **Real-time, structured answers**: Ask questions like "Who is on call for backend-server?" or "Give me all the details for parser-service." MCP fetches the data in real time from Cortex's API, ensuring accurate and up-to-date information about service health, ownership, and operational readiness.\
* **Actionable recommendations**: MCP can suggest next steps or remediation ideas based on Scorecard and Initiative data, helping you identify and address gaps in incident response.\
## DORA metrics in action
Learn about what ongoing DORA metric improvements look like in [DORA Metrics in action](/solutions/dora/in-action.md).
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.cortex.io/solutions/dora/configure.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.