Peak Command · Guide · Monthly review
The monthly review
in 90 minutes.
An agenda for 90 minutes: numbers against plan, goal check-ins, decisions due and three priorities for next month. Put together your questions for the month here.
What should your next monthly review settle?
2 questions in the plan. First question: Which three numbers show whether the month was good?
The month in four blocks
Numbers. Goals. Decisions.
Which three numbers show whether the month was good?
The month is for deviations, not for reports.
A monthly review where everyone reads out their numbers costs time and changes nothing. Prepare the numbers, discuss only deviations above your threshold and close with three priorities. Peak Command builds the monthly agenda from goals, check-ins, plan and decision reviews that are due; sources without data are shown as missing.
From reading to doing
Your monthly questions. For the next meeting.
The next month.
2 questions selected
- Which three numbers show whether the month was good?
E.g. revenue, contribution margin, cash at month end.
- From which deviation do you discuss a number?
A fixed threshold prevents debates about rounding errors.
What makes a monthly review
useful.
A few numbers with plan and source, an explanation for every larger deviation, and a decision or a conscious “we wait”.
Which three numbers show whether the month was good?
E.g. revenue, contribution margin, cash at month end.
Fresh numbersEach number with its date. A three-week-old number is a hint, not a fact.
A deviation thresholdOnly from e.g. ±5% is a deviation discussed.
Reviews dueDecisions whose review date falls in the month come to the table.
The playbook
90 minutes, three blocks.
Compare, explain,
commit.
Plan → Actual → Explanation → Decision
- 01
Numbers against plan.
Put plan and actual side by side, with source and date. Mark only what is above your threshold. The rest isn't discussed.
Example · October (fictional)Revenue €182,000 (plan €200,000), margin 41% (plan 40%).
Only revenue is above the ±5% threshold. - 02
Explain before acting.
For each deviation, ask for the cause first. A delay isn't a slump. An explanation without evidence stays an open question.
Explain a deviation
“Two large orders (€21,000 together) slip into November.”“Revenue was weak.” - 03
Review, decide, commit.
Look at decisions whose review date is due and record the outcome. At the end there are three priorities for next month, each with an owner.
Outcome of the meetingA review due: “price increase of 6%” (August).
Keep it, repeat the review in January.
Your quality check
Is your monthly review prepared?
Tick what you have checked. Your selection stays in this view only.
0 of 4 points checked
What this article is based on.
Editorial guide with a fictional example and made-up numbers. Monthly agenda, goal check-ins, decision reviews that are due and sources marked as missing exist in Peak Command today.
- Evidence pending
Editorial guide with fictional companies and numbers. No customer data, no measured values, no customer results.
Prepare next month in Command.
Sign in and open the monthly agenda. Without an account, the demo shows the same structure.
Frequently asked questions
How is it different from the weekly review?
The week asks what is blocked. The month asks whether the plan still matches reality and what you change.
Where do plan and reality come from?
From Peak Year and the connected apps. Peak Command shows plan, forecast and reality side by side.
What if numbers are missing?
Name the gap. Peak Command shows missing sources as not available, never as 0.