Splitting the jobs fixes it. Four separate rhythms, each with one question and one output.
The four rhythms
| Rhythm | Question | Output |
|---|---|---|
| Weekly, manager and rep | What changed since last week | Deals flagged for silence or date movement |
| Monthly, manager and rep | What should not be here | Deals reset, moved to nurture, or closed lost |
| Day one of the quarter, leadership | What shape is this quarter | A committed number and a snapshot of the starting position |
| After the quarter, RevOps and leadership | What did we get wrong | Recalibrated thresholds and assumptions |
The quarter-start review is the one that pays
The day-one review decides the quarter. It is the only point where a shortfall can still be closed by building pipeline, pulling deals forward, or changing where the team spends its time. A forecast produced in week eleven is a report, not a forecast.
That review needs a decomposition rather than a coverage ratio. What will close from pipeline that already exists, what has to be created and closed inside the quarter, and what might be pulled forward from a later period. See how to create a sales forecast for the build, and sales forecasting best practices for the standing disciplines around it.
Calibrate against seasonality, not against last quarter
The post-period review is where thresholds get corrected. Compare what closed against what the day-one snapshot said would close, then adjust. Seasonality has to be part of that comparison. Q2 and Q4 usually run stronger than Q1 and Q3, and the third month of a quarter runs stronger than the first two, so a team measuring this quarter against the last one will read a seasonal pattern as a performance change. That mistake shows up later as a correction nobody can explain, and it quietly degrades forecast accuracy alongside the deal slippage it gets blamed on.
For the full walkthrough, see the deep dive on this topic.
Frequently Asked Questions
How often should pipeline be reviewed?
Weekly for deal movement, monthly for cleanup, and once at the start of every quarter for the forecast build. Teams that run a single weekly meeting covering everything end up coaching deals and never removing any, because removal is the least comfortable item on the agenda and it always loses to the others.
What belongs in the weekly pipeline review?
What changed since last week. Stage movement, close date movement, amount movement, and deals that went silent. Anything that did not move is either fine or a problem, and the review exists to sort those two piles. Strategy on individual deals belongs in a separate coaching conversation.
Why does the day-one review of a quarter matter most?
Because it is the only review that can still change the outcome. ORM customer data shows only 20% of pipeline carrying an in-quarter close date on day one closes inside that quarter. Knowing the likely shape of the quarter at the start is what makes a forecast useful. Getting the number right in the final week does not help anyone.
Should reps or managers own the review?
Managers own the meeting and reps own the records. The manager's job is to enforce the standard and force decisions on deals that fail it. When the rep runs the agenda, the review becomes a narrated tour of the deals the rep feels best about.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like pipeline review cadence into prescriptive action for your team.
Schedule a Demo