How to Score and Grade OKRs: Complete Scoring Guide

OKR scoring is the process of evaluating how much progress a team has made toward its Objectives and Key Results at the end of an OKR-cyclus. Without a consistent scoring system, OKRs become subjective and lose their power as a performance management tool.

This guide explains the most widely used OKR scoring methods, how to interpret scores correctly, how scoring differs between committed and aspirational OKRs, and the most common mistakes organisations make when grading their OKRs.

The OKR Institute has supported over 1,000 organisations across 50+ countries in implementing OKR systems, including enterprise clients such as IBM, Bosch, KPMG, and Allianz. The scoring frameworks in this guide reflect both established OKR methodology and real-world implementation experience.

What Is OKR Scoring?

OKR scoring is a structured method of measuring how close a team came to achieving its Key Results at the end of an OKR cycle, typically a quarter. Each Key Result receives a numerical grade, and those grades are averaged to produce an overall Objective score.

The purpose of OKR scoring is not to judge performance in a traditional sense. It is to generate honest, data-driven conversations about what worked, what did not, and what the organisation should do differently in the next cycle.

Key principle: OKR scores are diagnostic tools, not performance ratings. A score of 0.7 on an aspirational OKR is a strong result. A score of 1.0 on an aspirational OKR may signal the goal was not ambitious enough.

Why OKR Scoring Matters

Organisations that skip formal OKR scoring often report the following problems:

• Goals drift without accountability checkpoints
• Teams lose confidence in the OKR system over time
• Senior leaders cannot tell whether the organisation is making real progress
• Learning from failure does not happen because failure is never formally acknowledged
• Goal-setting quality does not improve cycle over cycle

A consistent scoring process solves all of these problems by creating a structured close to each OKR cycle that drives reflection, learning, and continuous improvement.

The Standard OKR Scoring Scale

There are four main OKR scoring methods used in practice. Each has different strengths depending on the type of Key Result, team maturity, and organisational context.

1. The Decimal Scale (0.0 to 1.0)

The decimal scale is the most widely used OKR scoring system, popularised by Google. Key Results are graded on a scale from 0.0 (no progress) to 1.0 (fully achieved). The score is calculated by dividing actual performance by the target value.

Formula: Score = Actual Result divided by Target Result

Voorbeeld: If the Key Result was to grow monthly active users from 10,000 to 20,000, and actual growth reached 16,000, the score is 16,000 divided by 20,000 = 0.80.

For aspirational OKRs, a score between 0.6 and 0.7 is considered strong. For committed OKRs, the expected score is 1.0.

2. The Percentage Scale (0% to 100%)

The percentage scale is functionally identical to the decimal scale but expressed as a percentage. It is particularly useful for teams new to OKRs or for organisations where percentage-based reporting is the norm.

Voorbeeld: A Key Result targeting 50 new enterprise customers, achieved with 38, scores 76%.

Many OKR software platforms including FlowyTeam use percentage completion as the default view because it is immediately intuitive for most employees.

3. The Traffic Light (RAG) System

The traffic light or RAG (Red, Amber, Green) system provides a quick visual status for each Key Result. It is widely used in executive dashboards and weekly check-ins.

• Green: On track or achieved (typically 70% or above)
• Amber: At risk or behind schedule (typically 40% to 69%)
• Red: Off track or no meaningful progress (below 40%)

Some organisations extend the system to include a fourth colour: Blue to denote a Key Result that has exceeded its target. This RAG+B system is particularly useful for aspirational OKRs where exceeding expectations is noteworthy.

4. Binary Scoring (Pass / Fail)

Binary scoring applies to Key Results that are either completed or not completed. There is no middle ground. This method is appropriate for milestone-based deliverables where partial completion has no meaningful value.

Voorbeeld: A Key Result to complete an ISO 27001 audit by Q3 is binary. Either the audit was completed (score: 1.0) or it was not (score: 0.0).

Binary scoring is recommended exclusively for committed OKRs. It is not appropriate for aspirational stretch goals.

OKR Scoring Methods Compared

The table below summarises the four main OKR scoring methods and when to use each one.

Method	Scale	Best For	Aspir. / Commit.	Complexity
Decimal (0.0-1.0)	0,0 tot 1,0	Aspirational stretch goals; teams with OKR experience	Aspirational target: 0.6-0.7; Committed target: 1.0	Low-Medium
Percentage (0-100%)	0% to 100%	Operational and numeric key results; beginners	Aspirational: 60-70%; Committed: 100%	Low
Traffic Light / RAG	Red / Amber / Green	Quick status reviews; executive dashboards	Both; Green = on track	Very Low
Binary (Pass/Fail)	0 or 1	Milestone-based or delivery-focused key results	Committed OKRs only	Very Low
Confidence Score	1 to 10	Dynamic tracking during the cycle; forward-looking	Both; updated weekly	Medium

Committed vs Aspirational OKRs: Different Scoring Rules

One of the most important distinctions in OKR scoring is the difference between committed and aspirational OKRs. Applying the same scoring standards to both is one of the most common mistakes organisations make.

Committed OKRs

Committed OKRs are goals the organisation has agreed to achieve without exception. They represent operational requirements, delivery commitments, or strategic must-wins. The expected score for a committed OKR is always 1.0. Any score below 1.0 is a failure that requires explanation and remediation.

Aspirational OKRs

Aspirational OKRs, sometimes called stretch goals or moonshots, are designed to push the organisation significantly beyond its current capabilities. They should feel slightly uncomfortable. A score of 0.6 to 0.7 on an aspirational OKR is considered a strong result. A consistent score of 1.0 on aspirational OKRs is a warning sign that the goals are not ambitious enough.

Google popularised this distinction. The company expects teams to achieve an average of 70% on aspirational OKRs. Anything above 0.7 is exceptional. Anything below 0.4 requires a serious retrospective.

Attribute	Committed OKRs	Aspirational OKRs
Definition	Non-negotiable targets the team is expected to achieve fully.	Ambitious stretch goals intended to push the organisation beyond its comfort zone.
Expected score	1.0 (100%)	0.6 to 0.7 (60%-70%)
Scoring method	Binary: pass (1.0) or fail (below 1.0)	Decimal or percentage scale; spectrum scoring
Score of 1.0 means…	Success. The team delivered.	Possible under-ambition. Review whether the goal was truly aspirational.
Score of 0.7 means…	Failure. The committed result was not fully delivered.	Strong success. The team made outstanding progress on a stretch goal.
Score of 0.4 means…	Significant failure requiring urgent review.	Below expectations. Analysis is needed but the team is not penalised.
Voorbeelden	Launch product feature by Q3; Achieve 100% compliance; Complete migration.	Expand to 3 new markets; Double NPS from 30 to 60; 10x revenue in a segment.

How to Calculate Your OKR Score Step by Step

Follow these five steps at the end of each OKR cycle to produce accurate and meaningful scores.

1. Gather final data for each Key Result. Do not estimate. Pull actual numbers from your data sources: CRM, analytics platform, financial reporting system, or project management tool.
2. Score each Key Result individually. Divide the actual result by the target result to produce a score between 0.0 and 1.0. For binary Key Results, assign 1.0 for completed and 0.0 for not completed.
3. Average the Key Result scores to produce the Objective score. Each Key Result carries equal weight unless your OKR framework specifies weighted scoring. Sum the individual KR scores and divide by the total number of KRs.
4. Apply a self-assessment layer. The numerical score tells you what happened. The self-assessment tells you why. Rate the quality of the OKR itself: was the goal well-defined? Was the target realistic? Was the right data available?
5. Document the score and learning in your OKR review. Record final scores, key learnings, and carry-forward actions in your OKR review meeting. This documentation is the foundation for better OKR quality in the next cycle.

Worked Scoring Example

The following example shows how to score an Objective with three Key Results.

Objectief: Accelerate enterprise revenue growth in Q3

Belangrijkste resultaat	Target	Actual Result	Score (0-1)
Increase monthly recurring revenue from $200K to $300K	$300,000	$270,000	0.70
Grow net promoter score (NPS) from 32 to 50	50	41	0.50
Launch enterprise onboarding programme for top 20 clients	20 clients	20 clients	1.00
OBJECTIVE SCORE (Average of Key Results)			0.73 (Green)

Interpretation: A score of 0.73 falls within the 0.7 to 0.89 range, indicating strong performance on an aspirational Objective. The team fully delivered on the enterprise onboarding commitment (1.0) and made solid progress on revenue (0.70), while the NPS Key Result (0.50) needs attention in the next cycle.

OKR Score Interpretation Table

Use the following table to interpret scores and determine the appropriate response at the end of each cycle.

Score (0-1)	Percentage	RAG Status	Interpretation	Recommended Action
0.9 – 1.0	90% – 100%	Green	Fully achieved. If aspirational, the goal may have been too easy.	Celebrate; set more ambitious targets next cycle.
0.7 – 0.89	70% – 89%	Green	Strong performance. Sweet spot for aspirational OKRs.	Identify what drove success; replicate conditions.
0.6 – 0.69	60% – 69%	Amber/Green	Acceptable for stretch goals. Solid progress with room to grow.	Review blockers; adjust ambition or resources.
0.4 – 0.59	40% – 59%	Amber	Partial progress. Goal was partially met but fell short.	Root-cause analysis; identify systemic barriers.
0.1 – 0.39	10% – 39%	Red	Significant shortfall. Consider whether the goal was realistic or well-defined.	Deep retrospective; reassess goal quality and team capacity.
0.0	0%	Red	No measurable progress. May indicate a priority conflict or unclear ownership.	Investigate root cause; consider removing or redesigning the OKR.

Common OKR Scoring Mistakes

Even experienced teams make these mistakes when grading OKRs. Understanding them in advance helps organisations build a more reliable scoring culture.

Scoring effort instead of outcomes. OKR scores should reflect measurable results, not how hard the team worked. A team that worked intensively but failed to move the metric still scores low. This is a feature of OKRs, not a flaw. It redirects focus from activity to impact.

Applying the same scoring standards to committed and aspirational OKRs. A score of 0.7 is a failure on a committed OKR and a success on an aspirational one. Organisations that do not make this distinction consistently misread their performance data.

Treating a score of 1.0 on aspirational OKRs as always positive. Consistently scoring 1.0 on stretch goals signals under-ambition. OKRs are designed to be difficult. If every goal is fully achieved every quarter, the goals are probably not pushing the organisation far enough.

Skipping the self-assessment entirely. Numbers without context mislead. A score of 0.5 could mean the team made excellent progress against a genuinely hard goal, or it could mean the goal was poorly defined. Self-assessment provides the narrative that explains the number.

Delaying scoring to the last moment. Quarterly scoring works best when supported by weekly or bi-weekly confidence score updates throughout the cycle. Teams that only score at the end lose the early warning signals that allow course correction.

Not documenting learnings. The scoring conversation is where OKR quality compounds. Organisations that skip structured retrospectives at scoring time repeat the same goal quality mistakes cycle after cycle.

OKR Scoring Best Practices

• Define how you will measure each Key Result before the cycle begins, not at the end.
• Establish the scoring scale and expected score thresholds (committed vs aspirational) in your OKR guidelines document before rollout.
• Use confidence scores (1-10) during weekly check-ins to give teams a forward-looking signal before the final quarterly score.
• Score at the Key Result level first, then average to produce the Objective score.
• Never modify a Key Result target after the cycle has started to make the score look better. This destroys the integrity of the entire system.
• Separate scoring from performance reviews. OKR scores are learning tools, not performance ratings. Conflating them causes teams to set conservative, easily achievable goals.
• Review score distributions across the organisation. If most Objectives score above 0.9, targets are too low. If most score below 0.4, targets may be unrealistic or resources are misaligned.

OKR Scoring in the OKR Review Cycle

OKR scoring is one component of the broader OKR review process. The review cycle includes three interconnected stages:

1. Weekly Check-in: Track progress using confidence scores (1-10) or RAG status. Identify blockers early. Adjust tactics without changing targets.
2. Mid-cycle Review: Assess progress at the midpoint of the quarter. Score provisional Key Results using available data. Identify whether the team is on pace to hit the expected range.
3. End-of-cycle Scoring and Retrospective: Final scoring using actual data. Self-assessment and qualitative reflection. Documentation of learnings. Input into the next cycle’s OKR planning process.

The OKR Institute’s Team-to-Impact Cycle framework integrates scoring into a continuous performance rhythm rather than a single end-of-quarter event. This approach significantly improves OKR adoption and goal quality over successive cycles.

OKR Scoring and Software

Most OKR software platforms automate the scoring calculation once actual results are entered. When evaluating OKR software, look for these scoring features:

• Automatic score calculation from numeric inputs
• Support for both decimal (0-1) and percentage scoring
• Visual RAG or traffic light status indicators
• Confidence score tracking with historical trend view
• Separation of committed and aspirational OKR scoring rules
• Integration with data sources (CRM, analytics, financial systems) to auto-populate Key Result actuals

FlowyTeam, the OKR software platform associated with the OKR Institute, supports all of the above scoring modes and integrates with major business intelligence tools to automate Key Result tracking in real time.

Frequently Asked Questions About OKR Scoring

What is a good OKR score?

A good OKR score depends on the type of OKR. For aspirational or stretch OKRs, a score of 0.6 to 0.7 (60% to 70%) is considered strong. For committed OKRs, the expected score is 1.0 (100%). A score above 0.7 on an aspirational OKR is excellent, while consistently scoring 1.0 may indicate the goals were not ambitious enough.

How do you score OKRs on a 0-1 scale?

To score an OKR on a 0-1 scale, divide the actual result by the target result for each Key Result. For example, if the target was 100 new customers and 75 were acquired, the score is 0.75. Average the individual Key Result scores to produce the Objective score. For binary Key Results such as milestone deliverables, assign 1.0 for achieved and 0.0 for not achieved.

What is the difference between scoring committed and aspirational OKRs?

Committed OKRs are expected to be fully achieved and score 1.0. A score below 1.0 represents a failure that requires analysis and corrective action. Aspirational OKRs are stretch goals where a score of 0.6 to 0.7 is considered a success. Scoring both types the same way leads to systematically conservative goal-setting, as teams will aim for certainty rather than ambition.

Should OKR scores be used in performance reviews?

No. OKR scores should not be directly linked to individual performance ratings or compensation. When OKR scores are tied to performance reviews, teams set easier goals to protect their ratings. OKR scores are diagnostic and learning tools. Performance management should use a separate process that considers broader contribution, values, and impact beyond OKR metrics.

How often should OKRs be scored?

Key Results should be updated with a confidence score or RAG status at least weekly during the OKR cycle. A formal mid-cycle review should happen at the halfway point of each quarter. Final scoring takes place at the end of the cycle, typically during an end-of-quarter review meeting that combines scoring, retrospective, and planning for the next cycle.

What does a score of 0.7 mean in OKRs?

A score of 0.7 on an aspirational OKR means the team achieved 70% of a stretch goal. This is generally considered a strong and healthy outcome. It indicates the goal was genuinely ambitious while the team made substantial progress. On a committed OKR, a score of 0.7 represents a shortfall that requires explanation and remediation planning.

Why does Google consider 0.7 the ideal OKR score?

Google popularised the principle that 70% achievement is the target for aspirational OKRs because it represents the right balance between ambition and achievability. If a team consistently scores 1.0, their goals are probably too easy. If they consistently score below 0.4, the goals may be unrealistic or the team may lack necessary resources. The 0.6 to 0.7 range indicates goals that genuinely stretch the organisation while remaining grounded in strategic logic.

Can OKR scores be weighted?

Yes. Some organisations assign different weights to Key Results within an Objective to reflect their relative strategic importance. For example, if an Objective has three Key Results and one is significantly more important than the others, it might receive a weight of 50% while the other two each receive 25%. Weighted scoring requires more configuration but can produce more accurate Objective scores when Key Results have unequal strategic value.

What is self-assessment in OKR scoring?

Self-assessment is a qualitative layer added to the quantitative OKR score. After calculating the numerical score, the team rates the quality and appropriateness of the OKR itself: Was the goal well-defined? Was the right data available to measure it? Were external factors outside the team’s control a significant factor in the outcome? Self-assessment ensures that scores are interpreted in context and that learning from each cycle improves future OKR quality.

How does OKR scoring connect to the next planning cycle?

Final OKR scores feed directly into the next cycle’s planning process. Key Results that scored below 0.4 need a root-cause analysis before being carried forward or replaced. Key Results that scored 0.9 or above on aspirational OKRs may need to be replaced with more ambitious targets. The scoring retrospective should identify two or three specific improvements to OKR quality, goal-setting process, or resource allocation that will be applied in the next cycle.

Advance Your OKR Skills with OKR Institute Certification

Scoring and grading OKRs accurately requires more than a formula. It requires a deep understanding of goal-setting theory, cycle management, leadership alignment, and performance culture. The OKR Institute offers a structured certification pathway that builds these capabilities at every level of your organisation.

Certified OKR Professional (C-OKRP): Foundational certification for practitioners. Learn to write, implement, and score OKRs across teams and business units.

Certified OKR Leader (C-OKRL): Leadership-level certification for managers and executives. Covers OKR strategy, culture, and review cadence design including scoring frameworks.

Certified OKR Officer (C-OKRO): Organisational OKR design for senior leaders. Includes advanced scoring frameworks, weighted OKR systems, and enterprise implementation.

Certified OKR Professional Master (C-OKRPro): The highest-level OKR credential globally. Covers all OKR scoring methodologies and complex multi-level OKR architecture.

All OKR Institute certifications are affiliated with Copenhagen Business School and are recognised across 50+ countries. More than 800 organisations have used OKR Institute programs to build world-class goal management systems.

Explore OKR certification programs at okrinstitute.org or contact the OKR Institute team for enterprise and corporate training options.

Estimated reading time: 15 minutes