Playbook . 6 min read

How to Run Weekly Goal Check-ins

In short

A weekly check-in is the short, recurring update where goal owners record progress, confidence, and blockers. It is what keeps goals alive in the long middle between planning and review, and it is where a stall first becomes visible. This playbook covers how to run check-ins that people actually keep doing and that surface risk early instead of flattering it.

Goals do not fail at the planning offsite or the quarterly review. They fail in the quiet weeks between, when attention drifts and nobody notices a goal has stalled until the score comes in low. The weekly check-in is the cheap insurance against that, but only if it survives contact with busy people. That means keeping it short and protecting its honesty. This playbook does both.

The steps

01
Keep it to a few minutes per owner

A check-in that feels like a report will be skipped within a month. Hold it to a progress number, a confidence rating, what changed, and what is blocked. The discipline of brevity is what makes it sustainable week after week.

02
Tie confidence to the work, not the mood

Confidence ratings drift to green because amber invites questions. Counter it by anchoring confidence in something observable, the actual work moving beneath the goal, so the rating reflects reality rather than optimism. A grounded amber beats a reflexive green.

03
Make the blocked line mandatory

Every check-in should name what is blocked or what help is needed, even if the answer is sometimes nothing. A blocker field that is empty every single week is a sign the check-in has become a formality people fill in without thinking.

04
Read check-ins before the team meeting

Collect check-ins asynchronously and read them before you meet, so the meeting is spent removing blockers, not collecting status. A team meeting that exists to hear updates one by one is the most expensive way to read a document.

05
Act on the reds, every time

The whole point of weekly check-ins is early action. If a red or a blocker surfaces and nothing happens, owners learn that flagging risk is pointless and revert to green. Visibly responding to the first honest red is what keeps the signal trustworthy.

Frequently asked questions

Are weekly check-ins too frequent?

For active quarterly goals, weekly is the right rhythm: frequent enough to catch a stall early, rare enough not to become noise. Steady-state KPIs can be reviewed less often.

Should check-ins be a meeting or async?

Async for the updates themselves, then a short live meeting to act on the blockers. Using meeting time to read out status one person at a time is the most common way check-ins waste everyone's time.

Try Vindaris free

Run this playbook on goals connected to real work

Vindaris connects every goal to the traceable work moving it, so the cadence in this playbook runs on real progress instead of hand-typed status. Start free, no credit card.

Sign Up for Free