End-of-Quarter OKR Review: How to Close a Quarter and Set Up the Next One

The end-of-quarter OKR review is the moment where most OKR programs fail quietly. Teams rush through scoring, someone writes "we hit 73%" next to each KR, and the organization moves on to next quarter's planning without processing what actually happened. The review that works takes about two hours, asks uncomfortable questions, and produces specific insights that change how the next quarter's OKRs are set. Here's how to run it.

Published May 2026 · OKIAR Editorial

How to score OKRs honestly

OKR scoring is typically done on a 0.0–1.0 scale. Each Key Result gets a score based on how much of the target was achieved. The Objective score is the average of its KR scores.

Example KR scoring:
KR: Grow organic sessions from 18,000 to 42,000/month.
Actual result: 31,200 sessions.
Progress: (31,200 − 18,000) / (42,000 − 18,000) = 13,200 / 24,000 = 0.55
Score: 0.55

The formula: (actual − baseline) / (target − baseline). This avoids inflating scores when baselines are large. A team that went from 0 to 31,200 would score differently than one that went from 18,000 to 31,200 — the baseline matters.

Classic guidance from Google/OKR literature: a score of 0.6–0.7 is a success. Consistent 1.0 scores mean your targets were too easy. Consistent scores below 0.4 mean either the targets were too hard or there was an execution problem. The scoring is designed to be uncomfortable — a 0.7 average means you didn't reach your full ambition, and that's okay if the ambition was genuine.

The retrospective questions that produce insight

Scores without analysis are useless. A 0.55 on a traffic KR could mean your SEO strategy was wrong, your execution was slow, or you had a Google algorithm update that changed the rules mid-quarter. The retrospective distinguishes between these — and different root causes require different responses next quarter.

What did we hit, and was it because we were good or because the target was easy?

OKRs should be uncomfortable. Celebrating a KR you hit at 1.0 is only warranted if you honestly believe the target was as ambitious as it should have been. If you sandbagged, acknowledge it. Next quarter's targets should be harder.

What did we miss, and was it execution or planning?

Execution misses (we had the plan, the resources, the time — we just didn't execute well) have different solutions from planning misses (the assumptions were wrong). Be specific. "We assumed hiring 3 engineers in Q3 was realistic; we hired 1" is a planning miss. "The engineers were hired but the refactor took twice as long as estimated" is an execution miss.

What work happened that wasn't in our OKRs?

If significant work happened that wasn't in your OKRs, your OKRs didn't capture your actual priorities. Why? Reactive work that consumed bandwidth? Poor planning? Scope that expanded? The answer changes how you structure next quarter's OKRs.

Which assumptions turned out to be wrong?

Every OKR is built on assumptions: the market will behave this way, we'll hire those people, this product decision will drive that metric. Identifying the assumptions that failed is more valuable than dwelling on the KR miss — it tells you what to calibrate differently next quarter.

If we could go back to week 1, what would we have done differently?

This is the most practical retrospective question. It produces specific, actionable answers: "We would have started the SEO work in week 1 instead of week 4." "We would have set a lower initial target on KR3 until we understood the market better." "We would have killed objective 3 by week 5 instead of keeping it on life support."

How to use results for next quarter's planning

End-of-quarter results directly inform two things for the next quarter: target calibration and strategic priorities.

Target calibration: if you consistently score 0.9+ on KRs in a category, you're under-indexing ambition there. If you consistently score below 0.4, something is broken — either in planning, execution, or the measure itself. Use the score distribution to set more honest targets next quarter.

Strategic priorities: the question "what work happened that wasn't in our OKRs?" often reveals strategic priorities that should be in next quarter's OKRs. If the team spent 40% of the quarter on customer escalations that weren't planned, either next quarter's OKRs should include a KR for reducing escalations, or leadership needs to protect OKR time from reactive work.

The scoring meeting vs the retrospective meeting

These should be separate events. The scoring meeting (2 hours, all leads) should happen in the last week of the quarter when the data is in. The retrospective (1–2 hours, same group) happens a few days later, after everyone has processed the scores. Mixing scoring with retrospective creates a meeting that's simultaneously backward-looking and defensive — people can't have an honest conversation about what went wrong when they're simultaneously trying to make their scores look good.

What makes OKR reviews fail

Three failure modes are common. First, scoring without analysis — a spreadsheet with numbers and no conversation. Second, sandbagged scores — everyone rounds up to 0.8 regardless of reality. Third, blame without accountability — the retrospective surfaces that a KR missed because another team didn't deliver, and the conversation ends there with no action.

The antidote is a facilitator who isn't afraid to ask "what does that score actually mean?" and "what specifically are we doing differently next quarter?" Every end-of-quarter review should produce at least 3 specific decisions that change how next quarter's OKRs are planned. If the meeting ends with no decisions, it was a status meeting dressed up as a review.

Track OKR scores and velocity data in Okiar — free during beta.

Okiar is free during beta. Voice check-ins, AI projections, team health — live in minutes.

Start free →