# Review Time

The "Review" stage represents the average time taken to complete the code review of Pull Requests.

For all the merged PRs, Typo calculates the average time between the first review comment on a Pull Request and the time it is approved. In case a Pull Request does not have a review comment, the Review Time will be calculated from the time that the Pull Request was raised for review. In case a Pull Request has been merged without review approval, the Review Time will be considered as ‘0’ for all such Pull Requests.

<div align="left"><figure><img src="/files/2cJ29vYwebDKytNjezuJ" alt="" width="563"><figcaption></figcaption></figure></div>

> Benchmarking review time helps by offering insights into the efficiency of code review processes. It allows teams to identify bottlenecks, streamline workflows, and improve collaboration, ultimately leading to faster code delivery and higher productivity.

<div align="left"><figure><img src="/files/ZTBD8VQI1Oukot1WW9Tq" alt="" width="375"><figcaption></figcaption></figure></div>

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

Measuring review time helps improve Engineering teams' efficiency in several ways:

1. **Optimizing Workflow**: By tracking the time taken for code reviews, teams can identify inefficiencies and optimize their workflow to reduce review times.
2. **Resource Allocation**: It helps in allocating resources more effectively by identifying team members who may need additional support or training to speed up the review process.
3. **Meeting Deadlines**: Understanding review time allows teams to better estimate project timelines and ensure that code is reviewed and merged promptly to meet project deadlines.
4. **Quality Assurance**: Monitoring review time helps ensure that thorough reviews are conducted without unnecessary delays, leading to higher quality code and fewer post-release issues.
5. **Continuous Improvement**: By analyzing trends in review time over time, teams can implement continuous improvement initiatives to streamline processes and further reduce review times.


---

# 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/pull-request-metrics/review-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.