Mid-Quarter OKR Check-In: How to Run One That Actually Changes Your Quarter

The mid-quarter OKR check-in is the most underused lever in the entire OKR system. Most teams either skip it entirely or run it as a status meeting where everyone says "on track" and nothing changes. Done well, the mid-quarter check-in is the moment you can still intervene — there's enough time to course-correct, enough runway to reallocate resources, and enough data to make a real decision rather than a guess. Here's how to run it so that something actually changes as a result.

Published May 2026 · OKIAR Editorial

When to run it and who needs to attend

Week 6 of a 13-week quarter. Not week 7 (too late to make major changes), not week 5 (not enough data). Week 6 is the moment where you have roughly half the quarter's check-in data, early velocity signals are visible, and you have seven weeks left to do something about problems.

Who attends: the leadership team plus team leads. Individual contributors don't need to be in this meeting — it's a decision-making session, not a status report. If all you're doing is listening to reports, you can do that asynchronously. The mid-quarter check-in earns its spot on the calendar only if decisions are actually made in the room.

The agenda that works

15 min

Projection review

Not status — projection. For each company-level OKR, the facilitator shows the current velocity data and the projected quarter-end landing. "At current pace, KR2 (pipeline coverage) will land at 2.8x vs a target of 3.5x. KR1 is on track." This requires having a tool that calculates projections — or doing the math manually. It cannot be self-reported status.

30 min

At-risk KR deep dives

For each KR that projects to miss, the team lead presents: the root cause (one sentence), what has been tried, and the specific intervention they propose. No whining, no excuses. Just: "Here is why it's behind, here is what we're doing, here is what we need from this room."

20 min

Resource decisions

If a KR is behind and the proposed intervention requires resources, headcount, or priority changes from another team — this is where that conversation happens. Not in a separate meeting scheduled later. Here, now, with the decision-makers present.

10 min

OKR modifications (rare)

The bar for modifying an OKR mid-quarter is high. "We're behind" is not a reason to lower the target. Legitimate reasons: external market change (key customer went bankrupt, competitor folded, acquisition announced), internal resource change (unexpected hiring freeze, key person left), or the OKR was fundamentally miscalibrated from the start. If you modify, document the reason.

5 min

Decisions recap

Summarize every decision made in the meeting. Who owns what, by when. Send to all attendees immediately after. This is what converts a status meeting into an action-generating meeting.

The "everything is on track" problem

If you run a mid-quarter check-in and everything is on track, one of three things is true: (1) your targets were too easy, (2) self-reporting is biased, or (3) the quarter is genuinely going unusually well. Option 3 is possible but rare.

The solution to options 1 and 2 is to use projection data rather than self-reported status. "On track" is a judgment. "At current velocity, this KR will land at 87%" is math. When teams see the projection rather than the status badge, the conversation changes. KRs that feel "on track" reveal that they're trending toward 78%. KRs marked "at risk" sometimes have a projection of 91% — meaning the pessimism isn't data-backed.

What to do when a KR is genuinely behind

Week 6 behind doesn't mean the KR is lost — but the options narrow quickly. A KR that's at 30% of target with 7 weeks left needs either an intervention or a realistic conversation about what "done" looks like. The three options:

Intervene with resources — add headcount, reallocate from another initiative, remove a blocker that requires leadership authority. This is the right response if the miss is execution-constrained (the team would hit it with more resources) and the KR genuinely matters.
Accept the miss, learn for next quarter — if the KR was genuinely over-indexed (conditions changed, assumptions were wrong), the right call is to document why and use that insight for Q4 planning. Don't pretend a KR that will land at 45% is "on track."
Change the KR target — only if the original target was miscalibrated from the start. This requires a high bar of evidence and public acknowledgment. If you change targets whenever you're behind, the OKR system loses all accountability value.

The mid-quarter check-in as a cultural signal

How leadership runs the mid-quarter check-in sends a cultural signal about what OKRs are for. If every behind KR gets defended without consequence and the meeting ends with no changes, teams learn that OKRs are performance theater. If every miss is punished regardless of circumstances, teams learn to sandbag and never set ambitious targets.

The right signal: misses are expected (ambitious OKRs should miss sometimes), surprises are not (we should have seen this coming in week 6 data), and decisions happen when intervention is possible. The mid-quarter check-in is the moment where that culture is made or broken every quarter.

Get mid-quarter projection data automatically in Okiar — free during beta.

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

Start free →