A goal check-in template is a short, repeatable format for updating each goal: where the number is now, whether you’re on pace, what’s in the way, and what happens next. Four fields, about two minutes per goal. Copy the format below, drop in your numbers, and you have a check-in that fits in fifteen minutes.
Most teams don’t need a better tracking system — they need the same four questions asked the same way every week. This page has three formats to steal: a per-goal block, a 15-minute meeting agenda, and an async version for Slack. Want the habit behind them first? See how to track goals →
The per-goal check-in template
One block per goal. Same fields every week, so you can compare this week to last at a glance.
Goal: [name] — owner: [name]. Now: [current] of [target]. Status: on track / at risk / behind. Blocker: [what’s in the way, or “none”]. Next: [the one thing before the next check-in].
Filled in: “Goal: qualified demos — owner: Ben. Now: 18 of 25 per month. Status: at risk. Blocker: two of four outbound sequences still unwritten. Next: finish both sequences by Thursday.” Anyone reading that knows the number, the risk, the cause, and the fix — in one line. Rolling several of these into a single team picture is covered in progress tracking for teams →
The four questions every check-in answers
Whatever format you use, a check-in that doesn’t answer these four isn’t worth the meeting.
Where is the number now?
The current value against the target — “340 of 400.” One number, not a paragraph. If nobody can state it, the goal isn’t really being tracked.
Are we on pace?
On track, at risk, or behind. Pace matters more than the total: 60% done in week 3 is great, in week 11 it’s trouble.
What’s in the way?
One blocker, or “none.” This is the question that earns the meeting — it’s where the team can actually help each other.
What’s next?
The one thing the owner will do before the next check-in. It turns a status update into a commitment.
The 15-minute team check-in agenda
For a small team with three to five goals, the whole thing fits in a quarter of an hour — if you run it in this order.
Collect the numbers before the meeting
Each owner fills in their current value and status ahead of time. Gathering data live is what turns a 15-minute check-in into an hour.
Read the board, don’t recite it
Everyone can see the updates, so don’t read them aloud. Skim the list together and note which goals are amber or red.
Spend the time only on what’s slipping
Green goals get no airtime — a nod and move on. The whole meeting exists for the at-risk and behind ones.
Name the next step and who owns it
Every amber or red goal leaves with one concrete action and one name. No action means nothing changes before next week.
End on time, every time
Fifteen minutes, hard stop. A check-in that reliably ends on time is a check-in people keep showing up to.
The async check-in template
No meeting needed. Each owner posts the same block in a thread on the same day each week, and you only pull people together for the goals in trouble.
🎯 [goal name] · [current] of [target] · [🟢 on track / 🟡 at risk / 🔴 behind] · Blocker: [one line or “none”] · Next: [one action].
Async works especially well for distributed teams and for goals whose numbers only move slowly. The rule that makes it work: the same day, the same format, every week. Miss either and it decays into silence.
Weekly or biweekly?
Pick one cadence and hold it. The wrong rhythm quietly kills the habit.
Weekly — the safe default
Best for fast-moving goals and full-quarter pushes. Catches a drifting goal within days, and the habit sticks precisely because it’s frequent enough to remember.
Biweekly — when progress is slow
Better when the numbers barely move week to week and updates would just repeat. Anything slower than biweekly and problems hide until it’s too late to fix them.
Whichever you pick, anchor it to your cycle — see quarterly planning for small teams →
What a check-in is not
A check-in is short, frequent, and forward-looking: what’s blocking us, what’s next. It is not a status report to management, not a performance conversation, and not the end-of-cycle review where you score what you achieved — that’s a separate, backward-looking meeting. Merge the two and people start defending their numbers instead of asking for help, which is exactly the behaviour that makes goals fail quietly. For scoring at the close, see OKR grading & scoring →
Celorly is this template, built in: each goal already has an owner, a current value against its target, and a status — so a check-in is updating a number and a line, not rebuilding a doc. The Monitor screen puts the at-risk and behind goals at the top, which is the only part of the agenda that needs your fifteen minutes. Weighing up tools? See what to look for in goal-tracking software →
Goal check-ins — quick answers
What is a goal check-in template?+
It’s a short, repeatable format for updating a goal — the current number, a status (on track, at risk, or behind), one blocker, and the next step. Using the same four fields every time keeps updates comparable and takes about two minutes per goal.
What should a goal check-in include?+
Four things: where the number is now against the target, whether you’re on pace, what’s blocking it, and the one thing you’ll do before the next check-in. Anything beyond that belongs in a doc, not a check-in.
How long should a goal check-in take?+
About 15 minutes for a small team, or two minutes per goal if you run it async. If it regularly runs longer, you’re either discussing green goals or solving problems that deserve their own meeting.
Should goal check-ins be weekly or biweekly?+
Weekly for fast-moving goals or a full quarter of work; biweekly when progress is naturally slower and weekly updates would just repeat. Weekly is the safer default — monthly is too slow to catch a goal drifting.
Can you run goal check-ins async?+
Yes, and many small teams should. Each owner posts the same four fields in a thread on the same day each week, and you only call a live conversation for the goals that are at risk or behind.
What’s the difference between a check-in and a goal review?+
A check-in is short, frequent, and forward-looking — it asks what’s blocking us and what’s next. A goal review happens at the end of the cycle, is backward-looking, and scores what you actually achieved. Don’t merge them: the weekly meeting is for unblocking, not judging.