> 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/hivel-score.md).

# Hivel Score

<table data-view="cards" data-full-width="true"><thead><tr><th align="center"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center"><h4>Org level score calculation</h4></td><td><a href="/pages/ZeWHojs64S1TewRU3N2Z">/pages/ZeWHojs64S1TewRU3N2Z</a></td></tr><tr><td align="center"><h4>Team level score calculation</h4></td><td><a href="/pages/b35glHGBjWn2P7rS8SpI">/pages/b35glHGBjWn2P7rS8SpI</a></td></tr></tbody></table>

{% embed url="<https://drive.google.com/file/d/1vlSqUweLQTIdhDFDqeeo7V7HncBHLI5d/view>" %}

Hivel Score provides engineering leaders with a fast, reliable snapshot of overall performance - without the need to navigate multiple dashboards. It brings together key signals like **speed, quality, and throughput** into a single, easy-to-understand score.

#### What is Hivel Score?

Hivel Score is an **aggregate, organization-level indicator** that reflects how your teams are performing across core engineering metrics. Each score is presented out of 100, making it simple to quickly assess performance at a glance.

<div data-with-frame="true"><figure><img src="/files/t6I1F9f0UHd1tvDkcIza" alt=""><figcaption></figcaption></figure></div>

#### How to interpret the score

* **Scores are contextual**: They are most meaningful when compared to a previous timeframe.
* **Trend-focused**: The score highlights whether metrics have improved, declined, or remained stable.
* **Drilldowns available**: Supporting metrics and percentage changes provide deeper insights into what’s driving the score.

#### Why it matters

Hivel Score is designed to help you:

1. **Quickly assess performance health** across teams or the entire organization
2. **Identify areas of improvement** by understanding metric-level changes
3. **Track score progress over time**

<div data-with-frame="true"><figure><img src="/files/C4YYEMHmn1yZE7uzylCH" alt=""><figcaption></figcaption></figure></div>

#### What you can configure

The metrics and weightages to be considered are completely configurable.

* Changes made to **sub-metric configurations** will impact the Hivel Score from the **current month onward only**.
* Changes made to **primary metric configurations** will **impact past, current, and future months**.

<div data-with-frame="true"><figure><img src="/files/wkUNvBKYbkpLDWRpTzra" alt=""><figcaption></figcaption></figure></div>

#### About scoring and stack ranking

The scoring system, along with the stack rank view, is intended to provide **directional clarity** - helping you understand how teams are progressing over time and where attention may be needed.

Rather than serving as a direct comparison tool, it offers a **relative view of performance trends**, making it easier to:

* Spot teams that are improving or facing challenges
* Highlight which metrics may need focus
* Understand how performance evolves across the organization

<div data-with-frame="true"><figure><img src="/files/rylZ4yTyaJEE6k4i9Hnk" alt=""><figcaption></figcaption></figure></div>