Commit is a claim about a period, so the clock is short
A deal should stay in commit only for as long as the period it was committed to still has days left in it. Commit is not a quality rating. It is a statement that this deal closes inside this period, and the label expires with the period regardless of how the deal looks.That framing gives a simple test. If a deal has held commit across two period boundaries, it has been wrong at least twice, and the right response is to strip the label and re-qualify rather than to move the date again.
The signals that a commit deal has gone stale
ORM treats a change in stage, close date, or amount as the marker of meaningful activity on an opportunity. A commit deal producing none of those for several weeks is the pattern worth acting on, and ORM describes the earliest slippage warning as the absence of any signal at all, with no data changing on the record and no buyer returning calls or email.
ORM also identifies a rep moving the close date as the strongest single indicator of deal slippage, and finds that once a deal slips from one quarter to the next it becomes less likely to close even while it stays in commit. A deal with two close date changes and a commit label is not a forecast entry, it is a follow up.
For aging more broadly, ORM applies a 12 month rule for most customers and reports that 10 percent or more of a typical pipeline has gone untouched for a year.
What to do with a deal that already slipped
Take the label off first, then decide. Three checks make the call quick.
- Has anything material changed since the last commit? A new decision maker, a revised legal timeline, or a confirmed budget line counts. A promise to follow up does not. - Does the amount still hold? ORM notes most deals close for less than the value carried in the CRM, so a slipped deal often needs its amount corrected as well as its date. - Is the buyer still engaged? Silence on email and calls is the earliest and cheapest signal available.
Track dwell time as a metric
Median days in commit before close is a standing pipeline metric worth reporting. Compare it against days in commit for deals that slipped or were lost. When the two distributions look the same, the commit criteria are not separating anything and the category has become a habit.
ORM reports that roughly 20 percent of pipeline carrying in-quarter close dates on day one of the quarter actually closes in that quarter, which is a useful reminder of how much dated pipeline moves. For related context, see forecast accuracy and sales forecasting best practices.
Frequently Asked Questions
How long is too long for a deal to sit in commit?
Past the close date it was committed to. Commit is a statement about a specific period, so the moment that period ends the label has been proven wrong and the deal needs to be re-qualified rather than carried forward with its old status attached.
Should a deal be re-committed after it slips?
Only after it clears the entry criteria again with new evidence, such as a revised signature path or a confirmed budget approval. Re-committing on the same evidence that already failed once repeats the error with a later date on it.
What is a reasonable commit dwell time to target?
Shorter than the remaining days in the period, and shrinking over time as criteria tighten. Track the median days a deal spends in commit before closing and compare it against deals that ended up slipping.
Does a long commit dwell time always mean trouble?
Not for long cycle enterprise deals committed early with a signed procurement timeline. It does mean trouble when nothing about the deal has changed while it sat there, since a static deal is not progressing toward a signature.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like how long should a deal stay in commit into prescriptive action for your team.
Schedule a Demo