Org level Hivel Score Calculation
Setting Up Your Configuration
Before any scores are calculated, you'll need to complete a one-time configuration. This involves setting the weight you want to assign to each of the three performance buckets:
Speed - How quickly your teams move
Quality - The standard of work being delivered
Throughput -The volume of work being completed
You can distribute the weights according to what matters most to your organization. The only rule is that the three weights must add up to 100%. If they don't, you'll see a validation error and won't be able to save until this is corrected.
Note: Scores will only start being calculated after your configuration is saved. You can revisit and update this configuration at any time from Settings.

How the Org-Level Hivel Score is Calculated
The score is built from the ground up - starting at individual metrics, rolling up to buckets, and finally combining into one org-level number.
Step 1: Metric Scores
Each bucket (Speed, Quality, Throughput) is made up of a fixed set of metrics - things like Commits, PRs Merged, or Review Time. Every metric is scored on a 0β100 scale by comparing a team's value against all teams' performance over the past 6 months. This ensures scores always reflect relative performance across your org, not arbitrary thresholds. Teams with no activity on a metric receive a score of 0.
Step 2: Bucket Scores Per Team
Within each bucket, metrics carry predefined weights that reflect their relative importance. A team's bucket score is the weighted average of its individual metric scores.
Step 3: Org-Level Aggregation
For each bucket, the org score is calculated as a developer-weighted average across all top-level teams. This means larger teams have a proportionally greater influence on the org score, ensuring the number reflects your actual organizational makeup.
Once weighted averages are computed for all three buckets, your configured weights are applied to arrive at the final Org Hivel Score.
Example
A
10
70
80
75
B
5
60
65
70
C
15
85
90
88
With configured weights of Speed 30%, Quality 40%, Throughput 30%, the final Org Hivel Score works out to 79.37.
When Can You View the Score?
Scores are available for completed months only. You won't see a score for the current, in-progress month - this ensures the data is complete and the score is accurate before it's displayed.
Use the Duration Selector to navigate between past months (full month selection only).
What You'll See on the Dashboard
Once configured, the org-level dashboard gives you:
Hivel Score for the selected month, along with a trend vs. the last 6 months
Score Trend Graph - a line chart showing how your org score has moved over the past 6 months
Category Breakdown - a bar view of your Speed, Quality, and Throughput scores. Click on any bar to see the individual metrics within that bucket, their scores, and how they compare to the 6-month average
Team Ranking Table - a flat list of all teams ranked by their Hivel Score, showing:
Team Name
Score
% Change vs. 6-month average
Team score vs. Org score (% difference)
You can also use the "See Users with Lowest Score" toggle to identify individuals who may need additional support, and use "View All Teams" for a fuller view with optional cascading sub-team visibility.
A Few Things to Keep in Mind
Only top-level teams contribute to the Org Hivel Score
If no data is available for a team or metric, a score of 0 is shown
Team vs. Org comparisons are made at the overall score level only, not at the individual bucket level
For questions or help with your configuration, please reach out to our support team.
Last updated