# Weekly OKR Check-In Template: 15 Minutes, Written

> A written weekly OKR check-in template that takes 15 minutes and shows founders the gap between plan and fact without another meeting.

- Author: Yaroslav Maxymovych (Founder & CEO, AI Advisory Board)
- Published: 2026-11-02
- Updated: 2026-11-02
- Source: https://aiadvisoryboard.me/blog/weekly-okr-check-in-template-15-minutes-written

Most founders I talk to have OKRs on paper and no idea if they are still true by Wednesday.

## TL;DR
- A weekly OKR check-in takes 15 minutes and should be written, not a meeting.
- It surfaces the gap between what was planned and what actually happened.
- It gives the owner a decision-ready signal without scheduling another sync.

## What is a weekly OKR check-in?

A weekly OKR check-in is a short written update where each team lead or department reports progress against the company's OKRs for the week. It is not a status meeting. It is not a slide deck. It is a written note that answers three questions: what we planned, what actually happened, and what stands between us and the objective.

For a founder of a 30-500 person company, this is the lowest-overhead way to keep OKRs alive between quarterly reviews. Without it, OKRs become a document that everyone forgets until the next planning cycle.

> **Definition:** OKR — Objectives and Key Results. A goal-setting framework where an Objective is a qualitative direction and Key Results are measurable outcomes that show whether the objective was reached.

> **Definition:** Cadence — the recurring rhythm at which a team reviews progress. For OKRs, a weekly written cadence prevents goals from going stale.

## Why written, and why 15 minutes?

Meetings expand to fill the time available. A 30-minute OKR review easily becomes an hour of discussion, context-switching, and calendar friction. A written check-in forces the writer to think before they type, and it forces the reader to scan for signal instead of listening for theater.

Fifteen minutes is enough to write a clear update and enough for a founder to read five or six of them before Monday lunch. Anything longer becomes a report nobody reads. Anything shorter becomes a checkbox nobody trusts.

## How to run the weekly OKR check-in

**Step 1: Set a fixed day and time.**
Send it every Friday by 3:00 PM local time, or every Monday morning before the week starts. Consistency matters more than the exact day.

**Step 2: Use the same template every week.**
Changing the format trains people to ignore it. The template below is designed to be copied into Slack, email, or a shared doc.

**Step 3: Read it as the owner, not as an editor.**
Your job is not to fix grammar. Your job is to spot the gap between plan and fact, decide if you need to intervene, and move on.

## Weekly OKR check-in template (copy/paste)

```markdown
# Weekly OKR Check-In — [Team / Department]
**Week of:** [Date]
**Owner:** [Name]

## Objective
[One sentence: what we are trying to achieve this quarter]

## Key Results
| Key Result | Target | Current | Status |
|------------|--------|---------|--------|
| KR 1 | [number] | [number] | On track / At risk / Off track |
| KR 2 | [number] | [number] | On track / At risk / Off track |

## Plan vs Fact
**Planned:** [Top 3 things we said we would do this week]
**Done:** [What actually shipped or closed]
**Not done:** [What slipped, and why in one sentence]

## Blockers
[What is stopping progress, who can unblock it, and by when]

## Next Week
[Top 3 priorities for the next 7 days]

## Decision Needed from Owner
[Yes / No. If yes, what decision and by when]
```

## Examples: good vs bad check-ins

**Bad:**
> "We worked on the OKR. Sales is going okay. Some leads came in. No blockers. Next week we will try harder."

**Good:**
> "Objective: Improve trial-to-paid conversion by 15%.
> KR 1: 20 paid upgrades. Current: 8. Status: At risk.
> Planned: Email sequence to 100 trial users. Done: Sequence sent to 60. Not done: 40 — email platform rate limit.
> Blocker: Need marketing to approve the remaining 40 contacts by Monday.
> Next week: Send remaining 40, review conversion data.
> Decision needed: Approve email list upload — by Monday 10 AM."

The bad version gives the founder nothing to act on. The good version shows exactly where the gap is and what decision is required.

## Manager scan (2-minute digest example)

When you read five of these check-ins on Monday morning, look for patterns, not details:

- Which teams marked their Key Results "At risk" two weeks in a row?
- Where is the same blocker appearing across departments?
- Which teams keep rolling the same "Planned" item into "Not done"?
- Who is asking for a decision that has been waiting more than 48 hours?
- Which OKRs have not been touched in the update at all?

This scan takes two minutes. It replaces five status meetings. It also creates the Plan → Fact → Gap rhythm that owners need before they consider any automation or AI rollout.

## Micro-case (what changes after 7–14 days)

A founder of a 70-person services company started using this template with four team leads. In the first week, two leads marked their KR as "On track" while the Plan vs Fact section showed nothing shipped. In the second week, the same gap appeared again. The founder had a ten-minute conversation with each lead, clarified what "done" meant, and stopped a project drift that would have surfaced only at the quarterly review. No extra meetings were added. The team just started writing the truth weekly.

> **Note on this case:** This example is illustrative — based on typical patterns we observe with companies of 30–500 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees.

## FAQ

**Who writes the check-in — the team lead or each individual?**
The team lead writes it. Individual updates feed into it, but the owner should receive one note per team, not fifteen.

**What if nothing changed this week?**
Say so explicitly. "No change" is data. It tells you the OKR may be stale or the team is blocked silently.

**Can this replace our weekly meeting?**
It can replace the status-reporting part of the meeting. Keep the meeting for decisions and hard discussions only.

**What if a team lead skips a week?**
That is the first signal. A missed check-in usually means a missed plan. Follow up privately before it becomes a missed quarter.

**How does this fit with AI adoption?**
Before you automate or add AI tools, you need to see what the team actually does weekly. This check-in creates that baseline.

## Conclusion

A weekly OKR check-in is not about surveillance. It is about giving the founder a clear, written signal of where the company stands between quarters. Write it once a week, read it in fifteen minutes, and act on the gaps you see.

If you want a system that surfaces the Plan → Fact → Gap automatically — every day, across the company — see how the 7-day diagnostic works: https://aiadvisoryboard.me/?lang=en

---

When citing, link to https://aiadvisoryboard.me/blog/weekly-okr-check-in-template-15-minutes-written. More articles: https://aiadvisoryboard.me/blog