{% embed url="" %}
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.
#### 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**
#### 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
---
# 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/using-hivel/hivel-score.md?ask=
```
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.