# Avg Resolution Time

Avg Resolution Time represents the average hours spent to resolve a production incident.

Typo calculates the average time it takes for an incident ticket to transition from an ‘In Progress’ state to a ‘Done’/’Completed’ state.\
For tickets that do not have an ‘In Progress’ state, their time is calculated from the ‘Created’ state to ‘Done’/’Completed’ state.

<div align="left"><figure><img src="https://813988662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FeCZyG1kSmV84geZ9Ws6s%2Fuploads%2Fd3TSeUdY6Dj2ePEJQAL7%2FScreenshot%202025-06-26%20144733.png?alt=media&#x26;token=3c65a2a9-eef5-4ba3-93f7-bf736d653da2" alt=""><figcaption></figcaption></figure></div>

### **How does measuring average resolution time help in improving the Engineering teams' efficiency?**

Measuring the average resolution time of production incidents provides valuable insights that empower engineering teams to continuously improve their incident response capabilities, enhance operational efficiency, and deliver a better experience for users and customers.

1. **Rapid Response:** By tracking resolution times, teams can ensure prompt responses to production incidents, minimizing downtime and mitigating the impact on users or customers.
2. **Incident Management Improvement:** Analysis of resolution time data helps teams identify areas for improvement in their incident management processes, such as incident triaging, escalation procedures, and communication protocols.
3. **Root Cause Analysis:** Understanding the average time taken to resolve production incidents enables teams to conduct thorough root cause analysis, identifying underlying issues and implementing preventive measures to prevent similar incidents in the future.
4. **Continuous Learning:** Monitoring resolution times allows teams to learn from past incidents and apply lessons learned to future incidents, improving their ability to respond effectively and efficiently to similar situations.


---

# 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://typo.gitbook.io/typo-help-docs/engineering-metrics/incident-metrics/avg-resolution-time.md?ask=<question>
```

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.