A sales forecast built once at the start of a quarter and checked again twelve weeks later functions as a guess with a report date attached to it. A forecast that holds up under real conditions runs on a defined weekly rhythm: five specific activities, one assigned to each business day, that move deals through validation, coaching, and reporting in a fixed order every week for the life of the quarter.
Monday is deal-level review. Tuesday is pipeline aggregation. Wednesday is coaching. Thursday is the CRO forecast call. Friday is the board report. Skip any one of the five and the numbers reported the following week stop reflecting what is happening in the pipeline.
The Forecast Cadence assigns one specific task to each weekday, from Monday’s deal-by-deal scoring through Friday’s board report of Commit, Projected, and Upside as three separately calculated numbers. A quarter run on this rhythm produces a forecast that moves in small, visible increments every week, while a quarter run without it produces nothing new until the final number misses.
The Five-Day Rhythm
The cadence runs the same five days, in the same order, every week of the quarter, regardless of how the previous week went.
| Day | What happens | Who runs it |
|---|---|---|
| Monday | Every deal gets scored against the 5 C’s and BID. Deals that gained a condition this week get documented. Deals that lost one get flagged. Deals with no movement in fourteen days get inspected for a Kill decision. | First-line managers and reps |
| Tuesday | Sales leadership aggregates the week’s movement into a new Commit number: which deals migrated up, which migrated down, and which were killed. | Sales leadership |
| Wednesday | A deal that lost a condition on Monday, or one that has sat flat for two weeks, gets the manager’s direct attention: a specific conversation about what changed on that deal and what the rep needs to do next. | Manager, rep, sometimes enablement |
| Thursday | The CRO reviews whether Commit is rising fast enough to hit target, whether Projected is still tracking to historical maturation rates, and where the largest risk sits in the weeks ahead. | CRO |
| Friday | Commit, Projected, and Upside are packaged into a report along with the week’s deltas and any material changes, and sent to leadership and the board. | CRO and leadership |
Wednesday’s step is what turns scoring into improvement. A deal that lost ground gets real coaching in the same week the gap was found, worked against the live deal that surfaced it, while the details are still fresh enough for the rep to apply the correction on the next call.
What Gets Reported to the Board Every Friday
The Friday report is the same five items every week, in the same order, so leadership and the board are reading the same structure quarter after quarter:
- Commit: the dollar total, the change from last week, and how many deals matured to a fully verified state to produce that change
- Projected: the dollar total, and whether it held stable or shifted based on a change in pipeline composition
- The Forecast, which is Commit plus Projected: the combined total against the quarter’s target
- Upside: the dollar total from early-stage pipeline, reported as headroom and never counted toward the plan
- Material changes: any deal that lost a verified condition, any Kill decisions, and any new high-value deal that entered the pipeline
That structure depends on the same standard behind every deal in it: a deal only counts toward Commit once every one of five buyer-confirmed conditions holds, and a deal only counts toward Projected once three or four of them do. Neither category is a rep’s confidence level. Both are counts of deals that cleared a specific, buyer-verified bar.
What a Healthy Commit Curve Looks Like
A quarter run on this rhythm should show Commit rising in a specific, trackable pattern. A representative healthy quarter against a $10 million target looks like this:
| Week | Commit | % of target |
|---|---|---|
| Week 1 | $3.2M | 32% |
| Week 3 | $4.1M | 41% |
| Week 5 | $5.4M | 54% |
| Week 7 | $7.2M | 72% |
| Week 9 | $8.5M | 85% |
| Week 11 | $9.4M | 94% |
| Week 12 | $10.1M | 101% |
The curve matters as much as the final number. In this example, Commit does not clear target until week 12, the final week of the quarter. A quarter where Commit clears target by week 10 instead is a healthier quarter than this one, even though both end above 100%, because clearing target two weeks early leaves margin to absorb a slipped deal or a stakeholder change without missing plan. A quarter where Commit only clears target in the final week has no such margin: one deal that loses a condition in week 12 turns a hit into a miss with no time left to recover.
Flatness is the other signal worth watching for. A Commit number that sits unchanged for two or three weeks in a row is a diagnostic trigger. Either reps have stopped verifying conditions, managers have stopped inspecting deals closely, or deals genuinely are not maturing on schedule, and each of those points to a different fix. A number that jumps sharply, for example from 32% to 90% of target between weeks one and four, deserves the same scrutiny in the other direction: either the pipeline is unusually strong, or conditions are being marked verified more loosely than the standard allows.
Why the Rhythm Matters More Than the Categories
Commit, Projected, and Upside are defined by what percentage of five buyer-confirmed conditions each deal has cleared and by the historical close rate attached to that state. What the cadence adds is the mechanism that keeps those numbers current instead of stale. A deal with all five conditions verified on Monday and one lost by Wednesday should already show up as a lower Commit figure by Thursday’s CRO call. Waiting until the deal fails to close weeks later to notice the change means someone has to explain, after the fact, why a verified deal didn’t hold.
This five-day structure, worked through in Gap Revenue Performance, is what keeps a validated forecast from drifting back into a guess between board meetings. Skip the Monday review, skip the Friday report, or let a single week pass without the aggregate refresh, and the categories stop tracking reality even if the underlying scoring rules never changed.
Gartner’s research found that fewer than half of sales leaders and sellers have high confidence in their own organization’s forecast accuracy, and a forecast that only gets checked once a month is a direct contributor to that number. Confidence in a forecast comes from watching it move in small, explainable steps every week of the quarter.
What Most Organizations Do Instead
A long-haul flight crew keeps up regular check-ins with air traffic control, monitors instruments continuously, and makes small corrections to altitude, heading, and fuel burn throughout the flight, so no single correction at the end has to be large enough for a passenger to notice.
Most sales forecasts run the opposite pattern. A number gets set at the start of the quarter, updated once a month if that, and the organization scrambles in the final two weeks to close the gap between the number it announced and the number the pipeline can produce. That pattern looks fine for eleven weeks and collapses in the twelfth. The weekly rhythm exists to replace one large correction at quarter-end with a dozen small ones nobody has to explain after the fact.
“The cadence is the discipline that keeps the forecast honest. Without it, the criteria are just words.”
Frequently Asked Questions
What is the Forecast Cadence in sales forecasting?
The Forecast Cadence is a fixed five-day weekly rhythm that runs the same way every week of a quarter: Monday deal-level scoring against buyer-verified readiness conditions, Tuesday pipeline aggregation into a new Commit figure, Wednesday targeted coaching on deals that lost ground, Thursday a CRO-level trajectory review, and Friday a board report of Commit, Projected, and Upside as three separate numbers.
How often should a sales forecast be updated?
At minimum, weekly, broken into distinct activities assigned to distinct days. A monthly or quarterly touch-up cannot catch a deal that loses a verified condition mid-week, which means the reported number is already out of date by the time anyone looks at it again.
What three numbers get reported to the board under this cadence?
Commit, the total value of deals with every readiness condition verified; Projected, the total value of deals at three or four of five conditions verified; and Upside, early-stage pipeline reported as headroom and never counted toward the plan. The number a CRO takes to the board as the forecast is Commit plus Projected only.
What does a healthy Commit number look like across a quarter?
It rises steadily week over week and clears the quarter’s target before the final week rather than in it. A quarter where Commit hits target two weeks before close carries more margin to absorb a late setback than one that reaches the same number on the last possible day, even though both technically hit plan.
What happens if an organization skips the Monday review or the Friday board report?
The forecast categories stop reflecting current pipeline reality. A deal can lose a verified condition on a Tuesday and still be counted in Commit two weeks later if nobody re-scores it, which means the number reported to the board is no longer the number the scoring rules would produce.
Is the Forecast Cadence the same thing as a weekly pipeline review meeting?
No. A single weekly pipeline meeting typically covers one function reviewing deals together. The Forecast Cadence assigns five distinct activities to five distinct days, run by different people for different purposes: managers scoring deals, leadership aggregating the results, managers coaching the gaps that scoring surfaced, the CRO reviewing trajectory, and the board receiving a structured report, in that order, every week.
Does a flat Commit number always mean something is wrong?
A Commit number that holds steady for two or three consecutive weeks is a signal worth investigating, since deals should be maturing through the pipeline continuously in a healthy quarter. The cause is usually one of three things: reps have stopped verifying conditions, managers have stopped inspecting deals closely enough to catch changes, or deals genuinely are not progressing on schedule, and each of those requires a different response.
0 Comments