A goal review meeting is the end-of-cycle session where you score each goal, work out what actually drove the result, write down what you learned, and decide what carries forward. For a small team it takes 45 to 60 minutes. It looks backward — which is exactly what makes it different from your weekly check-in.
This is the meeting most small teams skip, and skipping it is why the same misjudgements repeat every quarter. Below: a timed agenda, the four questions to ask about each goal, and the failure modes that turn a review into theatre. For the weekly counterpart, see the goal check-in template →
Review vs check-in — don’t merge them
Both look at goals; they do opposite jobs. Running them as one meeting reliably kills whichever half is less urgent — and that’s always the learning half.
Weekly check-in — forward
Fifteen minutes, every week, in flight. Asks: where’s the number, what’s blocking it, what’s next? Its output is unblocked work.
Cycle review — backward
Forty-five minutes, once a cycle, after the fact. Asks: what did we achieve, why, and what did we learn? Its output is scores and lessons.
The agenda
Five blocks, about 55 minutes including prep. The order matters more than the timings — especially scoring before discussing.
Prep the numbers first — before the meeting (15 min, solo)
Every owner fills in the final value and a proposed score ahead of time. Reviewing while hunting for data is how a 45-minute meeting becomes two hours.
Score every goal before discussing any (10 min)
Go around and lock in the results — hit, partial, missed, or a 0.0–1.0 score. No debate about why yet. Scoring first keeps the narrative from shaping the number.
Discuss the surprises, not the whole list (15 min)
Spend the time on goals that landed far from expectations, in either direction. A goal that hit exactly as planned teaches you very little.
Write down what you learned (10 min)
Capture one lesson per surprising goal, in plain words, where you’ll actually see it next quarter. Unwritten lessons don’t survive the week.
Decide what carries forward — then stop (5 min)
For each goal: keep, reshape, or drop. That list is the input to planning, and the meeting ends there. Do not start setting next cycle’s goals now.
If you run OKRs, step two is where the 0.0–1.0 scores get set — the mechanics of that, including how to roll key results into an objective, are in OKR grading & scoring →
The four questions to ask about every goal
Same four questions, every goal, in this order. The order is the whole trick: the result gets settled before the story gets told.
Did we hit it?
The plain result first — hit, partial, or missed, with the final number. Settle the score before anyone explains anything, or the explaining will bend the score.
What actually drove it?
The real cause, not the tidy story. Sometimes a hit was luck and a miss was good work against bad conditions — say so out loud.
What did we learn?
One transferable lesson: about the customer, the estimate, or the team. A cycle with no lesson written down was a cycle you paid for twice.
Does it carry forward?
Keep, reshape, or drop. An unfinished goal is not automatically next cycle’s goal — it has to earn the slot again.
Who’s in the room, and for how long
Keep it to the goal owners and whoever leads the team — people who can speak to a result and decide what happens to it. Every extra spectator shifts the tone from examining numbers to defending them. For three to five goals, 45 to 60 minutes is right; if you need longer, you’re gathering data live or you’ve drifted into planning.
Keep it honest, not comfortable
A review is only worth the hour if people say true things in it. Two habits do most of the work: score before you discuss, so the narrative can’t bend the number, and ask “what would have made this easier?” instead of “why didn’t you hit it?” — the first invites a real answer, the second invites a defence.
Praise an honest miss more warmly than a sandbagged win. Teams learn very fast what gets rewarded in that room — and whatever it is, that’s what next cycle’s numbers will be shaped to produce.
What goes wrong
Four patterns account for nearly every review that stops being useful.
Skipping it entirely
The most common one. The cycle just fades and the next starts from memory instead of reality — so the same estimate mistakes repeat forever.
Letting it become planning
Twenty minutes in, everyone’s excitedly designing next quarter and the review is abandoned. Separate meetings, or the backward-looking half always loses.
Rubber-stamping
Everything reported green, nodded through in ten minutes, no lessons. A review where nothing surprising is ever said isn’t a review — it’s a ceremony.
Turning it into a performance review
The moment scores affect standing, people optimise for looking good and the data stops being true. Keep grading and appraisal in separate rooms.
Hand off to the next cycle
The review’s real product is a short list: what to keep, what to reshape, what to drop, and the lessons behind each. That list is the first input to your next planning session — which is a different meeting, ideally on a different day. Done properly, the next quarter starts from what actually happened instead of from optimism. See quarterly planning for small teams for the other half of the loop, and progress tracking for teams → for what happens in between.
Celorly’s Settle screen is this meeting, prepared for you: every goal in the closing cycle with its final number, ready to score — outcomes for SMART goals, 0.0–1.0 for OKRs with the objective rolled up automatically. Close the cycle and the results stay attached to it, so when you open the next one, last cycle’s reality is right there instead of in someone’s memory.
Goal review meetings — quick answers
What is a goal review meeting?+
It’s the session at the end of a cycle where a team scores each goal, works out what actually drove the result, records what it learned, and decides which goals carry into the next cycle. It’s backward-looking — unlike a weekly check-in, which is about unblocking work in flight.
How do you run a goal review meeting?+
Have owners prep final numbers beforehand, score every goal before discussing any, then spend the time on the goals that landed far from expectations. Write down one lesson per surprise, decide keep/reshape/drop for each goal, and stop there — planning is a separate meeting.
How long should a goal review take?+
About 45 to 60 minutes for a small team with three to five goals, plus 15 minutes of solo prep per owner beforehand. If it runs much longer, you’re either gathering data live or drifting into planning next cycle.
Who should attend a goal review?+
The goal owners and whoever leads the team — the people who can speak to results and decide what carries forward. Keep spectators out: the more people watching, the more the conversation drifts toward defending numbers instead of examining them.
What’s the difference between a goal review and a check-in?+
A check-in is short, weekly, and forward-looking: what’s blocking us and what’s next. A goal review happens once per cycle, is backward-looking, and produces scores plus lessons. Merging them means you either stop unblocking work or stop learning from it.
How do you keep a goal review honest?+
Score before discussing, ask “what would have made this easier?” rather than “why didn’t you?”, and keep the outcome away from pay and ratings. Praising an accurate miss more than a sandbagged win is what makes honesty safe next time.