Weekly Review vs Monthly Review: Which Numbers Go Where?

Why this matters

An owner builds a weekly review, throws every number they can find onto the agenda, and the meeting runs long, covers ground that has not changed since last week, and still misses the slow-moving trend that needed a month of data to show itself. The opposite mistake is just as common: a number that swings daily gets buried in a once-a-month review, so a real problem runs for weeks before anyone notices. This tree sorts an individual number into the cadence that actually fits it, so the weekly review stays fast and the monthly review stays meaningful.

Start here: what does this number actually measure

Before sorting a number into a cadence, name what kind of thing it is. That single question decides almost everything else.

• Does it move meaningfully within a few days? (jobs booked this week, cash collected, today's coverage) - candidate for weekly.
• Does it only mean something once enough time has passed to smooth out normal day-to-day swings? (average ticket, close rate, repeat-customer share) - candidate for monthly.
• Is it both, at different resolutions? Some numbers belong in both places in different forms; see the last section.

If the number is volatile day to day, put it on the weekly review

A number that naturally jumps around from one day to the next tells you almost nothing read in isolation on any single day, but a week of it read together is exactly the right window to catch a real problem early.

• Test: would looking at this number every single day be noisy and exhausting, but looking at a week of it be genuinely informative? That is the signature of a weekly-cadence number.
• Typical examples: jobs completed, same-day cancellations, callbacks opened, cash coming in, whether the coming week is fully staffed.
• The weekly review question for these numbers is always the same shape: did this week look normal, and is next week already showing a problem?

If the number only makes sense over a longer window, put it on the monthly review

Some numbers are built from enough individual events that a single week is too small a sample to read honestly. Reading them weekly just shows you noise dressed up as a trend.

• Test: does one unusually good or bad week swing this number by an amount that would embarrass you if you acted on it? If yes, it needs a longer window before it means anything.
• Typical examples: average ticket, sales-close rate, first-time-fix rate, repeat-customer share, days to get paid measured as an average.
• The monthly review question for these is different in kind from the weekly one: is the underlying business getting better, staying flat, or getting worse, and does that change a decision this month?

If a single bad week just happened, resist moving a monthly number to the weekly list

The moment a monthly-cadence number takes a bad month, the instinct is to start watching it every week so it does not happen again. Do this rarely and on purpose, not by default. Watching a slow-moving number on a fast clock mostly produces false alarms, because normal week-to-week noise in a small sample looks exactly like a real problem until enough time passes to tell them apart. If a monthly number needs closer attention after a bad reading, prefer breaking it into a faster proxy (a leading indicator that moves with it) over just checking the slow number more often. See related: Leading Indicators vs Lagging Indicators in a Service Business.

If a number is genuinely useful at both cadences, split it into two versions

A handful of numbers earn a place on both reviews, but they should not be the identical figure read twice. Give the weekly version a different job than the monthly version.

• Cash position weekly is "what is in the account and what clears this week." Monthly it is "is our collections cycle getting faster or slower on average."
• Bookings weekly is "is the coming week full." Monthly it is "is booked volume trending up or down against the same month last year."

If you cannot describe a distinct question each cadence answers, you are duplicating effort rather than covering two real needs. Pick the one cadence that matters more and drop the other.

If a number keeps showing up as a surprise at the monthly review, it belongs on the weekly one

This is the most common real miss. A problem that has clearly been building for a while gets caught at the monthly review, and in hindsight the weekly numbers would have shown it two or three weeks earlier if anyone had been tracking a fast proxy for it. When a monthly review surfaces a problem that was not a surprise in hindsight, that is the signal to promote a related, faster-moving number to the weekly list, not to just resolve to "pay closer attention" next month.

Quick recap

1. Ask whether the number is meaningful within a few days or only over a longer window.
2. Volatile, meaningful-within-days numbers go weekly, answering "is this week normal and is next week already off."
3. Numbers that need volume to mean anything go monthly, answering "is the trend improving, flat, or worsening."
4. Do not chase a slow number onto a fast clock after one bad reading; find its faster proxy instead.
5. A number worth reviewing at both cadences needs a genuinely different question at each one, or it should only live in one place.
6. A monthly surprise that was actually building for weeks is a cue to promote a leading number to weekly, not to just watch harder next month.

References

• U.S. Small Business Administration (SBA), small business performance measurement
• Trade-standard practice for tiered business review cadence
• See related: The Daily, Weekly, Monthly, Quarterly Operating Cadence; Reading a Trend Line Instead of a Single Week's Snapshot; Leading Indicators vs Lagging Indicators in a Service Business