OKR Scoring: How to Grade and Score Your OKRs

How do you score OKRs at the end of a quarter? This guide covers the 0-1 scoring scale, how to grade key results, what scores mean, and how to use them to improve.

One of the questions teams ask most often at the end of a quarter is how to score their OKRs. Did they achieve the objective? Was 80% good enough? What does a score of 0.7 actually mean, and what should they do with that information?

OKR scoring is one of the most misunderstood parts of the framework. Done well, it is a powerful tool for honest self-assessment, organisational learning, and calibrating ambition over time. Done poorly, or not done at all, it becomes a ritual that generates a number nobody acts on.

This guide explains how to score OKRs properly, what the scores mean, how to handle the tricky edge cases, and how to use scoring to make your OKR programme better with every cycle.

The OKR scoring scale

OKRs are scored on a scale from 0.0 to 1.0, where 0.0 means no progress was made and 1.0 means the key result was fully achieved. Most OKR frameworks, including the original Google model developed by John Doerr, treat 0.7 to 0.9 as the target range.

That last point surprises many teams. If 1.0 is the maximum score, why is anything less than full achievement considered a good result?

The answer is in how OKRs are designed. OKRs are supposed to be ambitious, stretching beyond what the team is confident it can achieve. If a team consistently scores 1.0 on all its key results, it almost certainly set its targets too low. A score of 0.7 to 0.9 signals that the goal was genuinely challenging and the team made serious progress towards it. A consistent 1.0 is a signal to set bigger goals next quarter.

Score	Label	What it means	What to do
0.0 – 0.3	Did not achieve	Less than 30% progress. The goal was missed significantly.	Investigate root cause. Was this the wrong goal, the wrong measure, or a resourcing failure?
0.4 – 0.6	Partial progress	30 to 60% progress. Movement was made but the outcome was not reached.	Understand what stalled progress. Carry forward if still relevant, rewrite if not.
0.7 – 0.9	Strong result	70 to 90% progress. This is the Google target range, ambitious but achievable.	Celebrate and understand what drove the result. Use as a model for future OKRs.
1.0	Full achievement	100% of the target reached.	Ask whether the goal was ambitious enough. A consistent 1.0 may signal sandbagging.

How to calculate an OKR score

For most key results, scoring is straightforward. Take the actual result, subtract the baseline, and divide by the distance between the baseline and the target.

For example: a key result of "increase trial signups from 20 to 40 per month" that ends the quarter at 31 signups would score as follows. The progress made is 31 minus 20, which equals 11. The total distance to the target is 40 minus 20, which equals 20. The score is 11 divided by 20, which equals 0.55.

That formula works for most quantitative key results. Binary key results, those where the outcome is either achieved or not, score as either 0.0 or 1.0 with no middle ground. A key result of "complete the security audit" is either done or not done.

Scoring an objective

An objective score is typically the average of its key result scores. If an objective has three key results that score 0.8, 0.6, and 0.4 respectively, the objective score is 0.6.

Some teams weight key results differently, treating the most critical key result as carrying more influence over the objective score. This is a reasonable approach when key results are clearly not equal in importance, but it adds complexity. For most teams, a simple average is sufficient and easier to explain.

Scoring in practice: a worked example

Key result	Target	Actual	Score	Interpretation
Increase trial signups	40/month	31/month	0.78	Strong. Close to target, meaningful progress made.
Achieve activation rate	50%	28%	0.56	Partial. Activation is a deeper problem than acquisition volume.
Trial to paid conversion	15%	9%	0.60	Partial. Progress made but the conversion gap remains significant.
Top 3 on Google.no	3 keywords	1 keyword	0.33	Weak. SEO progress is slow, review content and authority strategy.

The objective score in this example would be the average of 0.78, 0.56, 0.60, and 0.33, approximately 0.57. That is a partial result that signals real progress in some areas and a significant gap in others. The scoring immediately points to where the team needs to focus its retrospective conversation.

The 0.7 target: why not aiming for 1.0 is the right approach

The idea that a good OKR score is 0.7 rather than 1.0 is one of the most counterintuitive aspects of the framework, and one of the most important to get right, particularly in organisations with cultures that equate anything less than full achievement with failure.

The logic is this. If your targets are set at a level where you are confident you will achieve them, they are not ambitious enough to drive real improvement. OKRs that can be fully achieved without significant stretch or risk are effectively just targets for the work that would have happened anyway.

The 0.7 target range creates space for genuine ambition. It signals to teams that they should set goals that represent real progress, goals where achieving 70% is still a strong result because the full target was genuinely challenging. It also creates a healthier relationship with failure: missing a 1.0 target is not the same as failing if the target was set correctly.

This requires a specific kind of leadership culture to work. If leaders respond to a 0.7 score with disappointment or consequences, teams will quickly learn to set easier targets that they can reliably hit at 1.0. The scoring system only works when the organisation genuinely treats 0.7 as a good result.

What to do with OKR scores

The score is not the point. The conversation the score enables is the point.

OKR scores should drive the retrospective at the end of each quarter, a structured conversation about what the numbers mean, what drove the results, and what needs to change in the next cycle. A score without a retrospective is a number on a dashboard. A score with a good retrospective is an input to better execution.

For key results scoring 0.7 to 0.9

These are your strong results. Understand what drove them. What decisions were made correctly? What external conditions helped? What habits or processes contributed? These answers are worth capturing and replicating.

For key results scoring 0.4 to 0.6

Partial results require diagnosis, not just acknowledgement. Was the target wrong? Was the initiative wrong? Was there a resource constraint that could have been anticipated? Did something more urgent displace the work? Each of these has a different implication for the next quarter.

For key results scoring below 0.4

Low scores need honest conversation. Three questions matter most. First, was this the right key result, does it actually measure progress toward the objective? Second, was the work done? If the initiatives were completed but the key result did not move, the theory of change was wrong. Third, was this a priority? Low scores are sometimes simply the result of something more urgent displacing the work without the OKR being formally deprioritised.

For key results consistently scoring 1.0

Full achievement across all key results is a signal to set bigger goals. If a team hits 1.0 on everything every quarter, either the targets are too conservative or the team is consistently outperforming its own expectations in ways that should be reflected in more ambitious goals next time.

Common scoring mistakes

Scoring at the end of the quarter for the first time

Scoring should not be a quarterly event, it should happen weekly. Teams that update their key result progress every week arrive at the end of the quarter with a score they have been tracking throughout, not a number they have to reconstruct from memory. Weekly scoring is what makes OKRs a live system rather than a reporting exercise.

Inflating scores to avoid difficult conversations

One of the most corrosive habits in OKR programmes is the tendency to round up, to score a 0.5 result as 0.7 because the team worked hard or because the leader does not want to surface underperformance. Inflated scores destroy the diagnostic value of the system and gradually erode the credibility of the programme. The most important thing a leader can do is model honest scoring, including being honest about their own team's results.

Using scores for performance reviews

OKR scores should not be used directly in individual performance reviews. This is a well-established principle from the companies that developed the framework, and the reason is straightforward: if OKR scores influence compensation or career progression, teams will set targets they can reliably hit at 1.0 rather than targets that represent real ambition. The moment scores become a performance management tool, the ambition disappears.

Scoring outputs instead of outcomes

A key result that says "complete the onboarding redesign" is an output, it either happened or it did not. If the actual measure should be "increase activation rate from 31% to 55%", scoring the output misses the point entirely. Key results should be outcomes with a measurable baseline and target. If they are not, scoring them is not meaningful.

No action following the score

A score that produces no decision is a wasted score. Every quarterly scoring session should end with a clear set of implications for the next quarter: which goals carry forward, which are retired, what changes about the approach, and what the scores reveal about where investment should be focused.

Scoring vs grading: a note on terminology

Some OKR frameworks use letter grades (A, B, C) rather than numerical scores. Others use traffic light systems (red, amber, green). The specific system matters less than the consistency with which it is applied and the quality of the conversations it enables.

The 0.0 to 1.0 scale has one practical advantage over alternatives: it is precise enough to enable meaningful comparison over time. A team that scores 0.62 this quarter and 0.71 next quarter has clear evidence of improvement. A team that moves from amber to green has a more ambiguous signal. For organisations that want to track execution improvement over multiple cycles, the numerical scale tends to be more useful.

How often should OKRs be scored?

OKR scores should be updated weekly as part of the check-in process, and formally reviewed at the end of each quarter as part of the retrospective.

Weekly scoring does not need to be precise to the second decimal place, a quick sense of whether the team is on track, behind, or ahead is sufficient for weekly check-ins. The formal end-of-quarter score is where precision matters, because that is the number that drives the retrospective conversation and informs the next cycle.

Some organisations also run a mid-cycle review at the six-week mark, a checkpoint where teams assess whether they are on course to hit their targets and make adjustments if not. This is particularly useful in the early quarters of an OKR programme, when teams are still calibrating how to set ambitious but achievable targets.

How Futureworks supports OKR scoring

Futureworks tracks key result progress in real time, giving teams a live view of where they stand against their targets throughout the quarter, not just at the end. The personal dashboard shows progress rings for every active OKR, and the 360 Vision tree makes scoring visible across every level of the organisation simultaneously.

The built-in check-in rhythm, delivered through Slack and Teams every week, makes weekly progress updates a habit rather than an admin task. And when the quarter closes, the scoring data feeds directly into the retrospective, giving teams the information they need to have honest, evidence-based conversations about what worked and what to change.

Want to see how scoring and tracking works in practice? Request a demo today.