Revenue decision guide · Slipped deals
Slipped deals: learn why the quarter moved
Track every close-date movement, record the reason and distinguish a genuine timing change from a deal that was never ready.
The operating question
A new close date records where the deal went, not why it moved.
It's 28 March. A deal expected to close on Monday moves to 30 April. The Seller updates the close date, the pipeline report refreshes and the quarter loses the value. By Tuesday, every current view is internally consistent. The CRM says April. The forecast excludes the deal. The old date and the moment the decision changed are already difficult to reconstruct.
In April the security review takes longer than expected and the deal moves to June. The same field changes again. When the team reviews the loss of the original quarter, one person remembers procurement, another remembers security and a third says the deal was always really a June deal. The current record supports all three stories because it contains the destination, not the journey.
A slip isn't just a changed date. It's a commercial event that needs a reason, an owner and the evidence available when the move was made.
- 31 MarOriginal close dateBudget expected
- 30 AprFirst slipProcurement not started
- 30 JunSecond slipSecurity review incomplete
Flagging a changed date isn't enough
The obvious response is to alert the Manager whenever a close date changes. That is useful. It tells somebody that movement happened while there may still be time to act.
It doesn't explain the movement. A procurement delay, an unapproved budget, a missing security requirement and a weak business case can all push the same date into the next quarter. Counting them as identical slips creates activity without learning. The alert needs the previous date, the new date, who changed it, why they changed it and what evidence supported the reason.
The second slip is a different event from the first
A first move can be a real scheduling change. A second move says the revised date was also unsupported, or that a new condition appeared after the first decision. Those are different failures and the response should be different.
Most systems can't tell them apart because each update replaces the last value. That turns repeated uncertainty into one clean future date. The record looks current precisely because the history that would challenge it has gone.
Treat every slip as a decision record
Keep the before and after dates, the forecast category before and after, the reason given at the time, the person who made the change and the supporting source. If the reason isn't known, record that rather than forcing a convenient code.
Then connect the event to the next action. Procurement not started may need an owner and a meeting. Security requirements unknown may need technical discovery. A business case that never became urgent may require the deal to be qualified out rather than moved again.
The external evidence is directional, not a diagnosis
Ebsta and Pavilion report a clear relationship between the duration of slippage and win rate in their 2025 GTM Benchmarks sales-efficiency digest. Across 655,000 opportunities worth $48 billion from 387 companies, the reported win-rate curve moves from 18% after a one-week slip to 13% after one month, 8% after three months, 5% after six months and 3% beyond six months. Read the Ebsta and Pavilion digest.
That doesn't prove that the slip caused the lower win rate. Weaker deals may be more likely to slip in the first place. It does show why repeated movement deserves inspection rather than another date change.
Where slip analysis goes wrong
A longer dropdown isn't a better explanation. If the person updating the date has to choose one reason from a list, allow a short account of what changed and retain the source behind it. Otherwise the code becomes another clean label applied to a messy decision.
Don't use repeated slips as a Seller leaderboard. Look first at deal stage, forecast category, segment, approval path and the timing of missing evidence. The purpose is to find where the operating process allowed an unsupported date to survive.
The distinction worth keeping
The close date is the current destination. The slip event is the decision that moved it. You need both.
Once the events survive, the team can separate genuine timing changes from deals that were never ready, see which reasons recur and learn whether the action taken after the first slip prevented the second.
How PROOF approaches it
Keep the evidence, decision and action connected.
PROOF keeps the source, timing and accountable decision together so the team can act while the outcome can still change and learn from what happened afterwards.
See the working product