# Why do some metrics like PRs reviewed or merged have more than 100%?

For PRs reviewed and merged the metric can go beyond 100% based on the duration.

{% hint style="info" %}
Logic is: **# of PRs merged or reviewed / # of PRs created**
{% endhint %}

If the number of PRs reviewed or merged exceeds the number of PRs created within the selected time frame, this metric can exceed 100%. This situation often occurs due to two main factors:

1. **Spillover PRs:** The team may be resolving PRs that were created in a previous time period but only reviewed or merged in the current one, leading to more PRs reviewed or merged than created. 
2. **Backlog Resolution:** Teams might focus on clearing out older PRs, especially if there was a backlog, which again increases the number of PRs reviewed or merged compared to the number of PRs created in the selected time frame.

A metric above 100% can therefore indicate that the team is not only keeping up with the new PRs but also catching up on older work, improving codebase quality and process flow.


---

# 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.hivel.ai/faqs/metrics-and-data-faqs/why-do-some-metrics-like-prs-reviewed-or-merged-have-more-than-100.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.