> For the complete documentation index, see [llms.txt](https://docs.hivel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hivel.ai/using-hivel/process-flow.md).

# Process Flow

The Process Flow Screen in Hivel gives you a visual breakdown of your cycle time—from writing code to merging it into production. This view is designed to help you identify bottlenecks, track engineering efficiency, and make data-driven improvements.

{% embed url="<https://app.storylane.io/share/6fzb73xo4wl8>" %}

### 🔍 View the PRs Behind Any Metric

Click on any metric to instantly see the pull requests contributing to it.\
Noticed a spike? Just click on that time frame to view the PRs involved.

### **Dive Into PR Details**

Drill down into you version control and see the tickets associated with the PR. This gives you a clear picture of where time is being spent and who’s involved.

### ⚠️ Identify Bottlenecks

See how long each stage took for a specific PR. This helps you pinpoint where delays occur - whether it's extended coding time, slow reviews, or lag in merging.

### 🧹 Clean Up Outliers

If a spike is expected or due to a known outlier, you can **exclude specific PRs** from the board. This ensures your averages stay accurate and meaningful.<br>

**You can use data on this screen to:**

* See the stage at which your team is spending most of their time - coding, review, or release process.
* Averages could sometimes be deceiving, so check the right panel for all the PRs and their respective breakdown into various stages.
* You can look at your current sprints or past sprints and use this data during retrospectives.

{% hint style="info" %}
Refer [<mark style="color:purple;">here</mark>](/using-hivel/pull-request/how-to-exclude-outlier-commits-and-prs.md) to know how to exclude certain PRs and commits from the calculation.
{% endhint %}