The delta is the agenda
Week over week forecast movement is the deal level difference between two consecutive forecast snapshots, sorted by the kind of change that produced it. A forecast that moved from 4.2 million to 4.25 million looks quiet. Underneath it, two deals may have slipped out of the period while three were upgraded into commit, which is a loud week reported as a calm one.The report requires stored snapshots. Without them the CRM only knows the current state, and last week's forecast is gone.
Six movement types worth separating
- Added. New opportunities created with close dates inside the period. - Closed won. Value that converted, moving out of forecast and into actuals. - Upgraded. Deals promoted to a higher category, such as best case into commit. - Downgraded. Deals demoted, which is the same event read in reverse and usually the more honest signal. - Slipped. Close dates pushed beyond the period boundary. - Lost or omitted. Deals removed from the period through a loss or a disqualification.
Each type has a different owner and a different follow up. Slippage belongs to deal inspection. A run of additions with in-period close dates belongs to pipeline generation. Upgrades landing heavily in the final two weeks belong to whoever set the category criteria.
Read close date changes first
ORM identifies a rep changing the close date as the best available signal of deal slippage, and finds that a deal slipping from one quarter to the next becomes less likely to close even when it stays in commit. That makes close date movement the first section of the report rather than a footnote.
ORM also points at the opposite pattern, where the earliest warning is the absence of any signal. No stage change, no amount change, no close date change, and no activity. ORM treats a change in stage, close date, or amount as the marker of meaningful movement, so a deal that produced none of them for several consecutive weeks deserves a look even though it never appears in the movement totals.
Movement is an early warning, not a scoreboard
Use the report to shorten the forecast call, not to litigate individual rep behavior in front of a group. The productive version opens with the largest four movements by dollar value, asks what changed at the account, and ends with a named next step for each.
Over a full period the movement history also becomes a training set for the next one. Teams that keep it can answer how much value typically slips out of week ten, which is a far more useful planning input than a single accuracy percentage. For the wider practice, see sales forecasting and sales forecasting best practices.
Frequently Asked Questions
How do you build a week over week forecast movement report?
Store a snapshot of every open opportunity at the same hour each week, then diff consecutive snapshots at the deal level. Group each difference into a movement type and sum the dollar impact of each type. The report is the six or so totals plus the deals behind them.
Why does a flat forecast still need a movement report?
Because a flat number can hide a 400,000 dollar downgrade offset by a 400,000 dollar upgrade. Those are two different events with two different follow ups, and the net figure erases both.
What movement should worry you most?
Close dates moving out. A rep pushing a close date is the strongest available warning that a deal is in trouble, and it usually appears before the deal changes category.
Should the movement report replace the forecast call agenda?
It should set the agenda. Spending the call on deals that did not move is how teams review the same twelve opportunities every week and learn nothing new from any of them.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like week over week forecast movement into prescriptive action for your team.
Schedule a Demo