TL;DR: A good OKR check-in template captures four things: current status, what moved last week, what's blocked, and what's happening next. The format matters less than the cadence: a simple template done consistently beats a sophisticated one done quarterly. The best check-in system is one that updates automatically, without anyone filling out a form.

Key Takeaways

• A check-in is not a status report. It's a decision trigger: is this goal on track, and if not, what needs to change?

• Async beats sync. A 10-minute weekly async update is more sustainable than a 30-minute meeting that gets cancelled when things get busy.

• Owner + confidence score are the two most important fields. If you don't know who owns a goal and how confident they are, you don't know anything useful.

• 90% of US enterprises miss their annual goals: usually because the check-in cadence breaks down by week 6. The check-in format is the last line of defense.

• The best check-in is one nobody has to do. Brev's Goal Agents pull status from the tools teams already use: no form, no reminder, no manual update required.

Why most OKR check-ins fail

Before the template, the honest diagnosis:

1. The form is too long. If the check-in asks for more than 5–7 fields, people skip it. Every additional field is friction that compounds across 40 goals per quarter.

2. No one reads the output. If the leadership team doesn't look at check-in data before the WBR, the people filling it out know it: and stop.

3. The cadence breaks in busy weeks. Check-ins submitted inconsistently are worse than no check-in at all, because stale data looks current.

4. There's no escalation path for red goals. If a goal is at risk and nothing happens, submitting the check-in feels pointless.

A good check-in template fixes problems 1 and 4. Leadership behavior (reading the output, acting on red flags) fixes problems 2 and 3.

The OKR check-in template

Copy this into Notion, Google Sheets, or your OKR tool. The weekly version is for teams moving fast; the bi-weekly version is for goals with longer feedback loops.

Weekly check-in template

Filled-in example

The bi-weekly variant

For goals with longer feedback loops (headcount, brand, infrastructure):

When to use async vs. sync check-ins

Async (recommended for most teams):

• Weekly, in writing, submitted by EOD Friday

• Leadership reviews over the weekend or Monday morning

• WBR starts with exceptions (off-track and at-risk goals), not status recaps

• Time investment: 5–10 min per owner per week

Sync (for complex or at-risk goals only):

• When a goal has been off track for 2+ consecutive check-ins

• When there's a dependency that requires a real-time conversation to unblock

• When confidence has dropped significantly (e.g., 4 → 1 in one week)

Don't run a weekly OKR check-in meeting to discuss every goal. That's a WBR. Check-ins are async data collection; the WBR is where you act on the data.

How to handle red goals

An off-track status should trigger an automatic escalation, not just a note in a doc.

When a goal goes off track:

1. The owner flags it with the "Blockers" field

2. The CoS / VP Ops sees it flagged in the dashboard before the WBR

3. The WBR agenda includes it as a discussion item, not a status update

4. A recovery plan (owner + deadline + resources needed) is agreed within 5 business days

5. If the goal can't recover this quarter, it gets officially deprioritized: not left in a zombie state

The worst outcome isn't a goal that goes red. It's a goal that goes red, nobody acts on it, and the team submits check-ins through the end of the quarter anyway because it's on the list.

What to automate

The check-in template above assumes someone fills it in. In 2026, that's increasingly optional.

Brev's Goal Agents pull progress automatically from the tools teams already use:

• GitHub and Linear for engineering goals (PR merges, issue closure, deployment frequency)

• Salesforce and HubSpot for revenue goals (pipeline, closed-won, NRR)

• Jira and Asana for project milestones

• Slack conversations for blockers and commitments

When a check-in happens automatically: pulled from actual work outputs, not manual form submissions: the data is more current, more accurate, and available in real time. The CoS doesn't chase 40 people for updates on Friday afternoon. The WBR starts with a pre-built view of what's red and why.

The template is useful. The system is better.

See also

• KPI vs OKR: what's the difference and which should you use?

• OKR examples for operations teams

Written by Chris Pitchford, Co-founder of Brev | Former VP Sales, Ally.io (acquired by Microsoft as Viva Goals)