That makes the push count a better forecast input than the close date itself. The date tells you what the rep hopes. The number of times it has moved tells you how reliable that hope has been.
Reading the count
| Pushes | What the record is telling you |
|---|---|
| Zero | Date still holds, treat the stage probability as valid |
| One, with a named buyer event | Normal on long cycles, keep the forecast category |
| One, with no reason recorded | Date was set to a quarter boundary, not to the buying process |
| Two or more | Downgrade the category and require new evidence to restore it |
| Two or more with no field changes between | The deal has decayed, work it as a fresh opportunity or close it |
The signal underneath the pushes
The earliest warning is quieter than a push. ORM points to the lack of any signal as the first indicator: no activity on the record, no data changing, no notes. From the seller's side the same pattern shows up as a buyer who stops returning email and stops picking up the phone. The pushes come afterward, once the rep has to explain the gap in the forecast.
That ordering is useful. If you are only reacting to close date changes, you are catching the deal at the second warning rather than the first.
What to do with a repeatedly pushed deal
Reset it instead of redating it. Ask what event will cause the buyer to sign, confirm that event exists on the buyer's calendar, and set the close date to it. If nobody can name the event, the deal leaves the forecast and stays in the pipeline as an open opportunity with no period assigned.
Applied consistently this pulls a meaningful amount of value out of the current quarter, which is uncomfortable and correct. ORM data shows that of the pipeline carrying close dates inside a quarter on day one of that quarter, roughly 20% closes in the quarter, so 80% of the value sitting in the period is not realized there. Counting pushes early is how you find out which 80% before the quarter ends.
For the mechanics of building a forecast that survives this correction, see how to create a sales forecast and the definition of deal slippage. The same discipline is what keeps forecast accuracy stable across the quarter instead of collapsing in the final weeks.
Frequently Asked Questions
Is one close date push a problem?
A single push on a long enterprise cycle is normal, especially when it tracks a procurement or budget event the rep can name. It becomes a problem when the push has no documented reason attached. A date that moved because the quarter ended is a different event from a date that moved because legal review was scheduled for the following month.
How do you count pushes in a CRM?
Use field history on the close date. Count each forward move of the date on an open opportunity, and record the size of each move alongside the count. Two small moves inside a month mean something different from two moves that each jump a full quarter.
What should happen after the second push?
Downgrade the forecast category and require new evidence to move it back. ORM finds that a deal slipping from one quarter into the next is less likely to close even when it sits in commit, so a twice-pushed deal that stays in commit is carrying a probability the history does not support.
Do repeated pushes mean the rep is wrong about the deal?
Not always about the deal, but almost always about the date. Repeated pushes usually mean nobody has confirmed a decision event with the buyer, so the rep is estimating from their own pipeline pressure. The fix is asking what has to be true for the new date to hold, not asking whether the deal is still alive.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like how many times does a deal push before it closes? into prescriptive action for your team.
Schedule a Demo