This is the most visible form of pipeline decay, and it is the easiest to fix. Unlike qualification problems, which need judgment, a past-due date is an unambiguous data error that any RevOps team can list in one query.
Why past-due deals accumulate
Reps set close dates against internal reporting boundaries instead of buyer events. When the quarter ends and the deal has not closed, updating the date requires admitting the deal slipped, so the record sits untouched. The date going stale is a side effect of avoiding the conversation.
ORM counts meaningful activity on an opportunity as a change in stage, close date, or amount. A deal that has gone past due without any of those changes is a deal nobody is working, and ORM data shows more than 10% of a typical customer's pipeline has gone untouched for 12 months.
The report that surfaces them
| Slice | What it tells you |
|---|---|
| Count and value of open deals with close date before today | The size of the correction waiting in your forecast |
| Days past due, bucketed | Separates a one week lag from a dead opportunity |
| Past-due value by rep | Shows whether the problem is systemic or concentrated |
| Past-due deals sitting in commit | The highest risk group in the entire pipeline |
Fixing it without gaming the field
The rule that works is a standing review gate. Any deal that goes past due gets a new date backed by a buyer event or gets closed with a reason code, and that decision happens in the weekly pipeline review rather than in the CRM at midnight.
Clearing past-due dates changes what your coverage number means. A pipeline that looks like 4x can drop to 3x once expired deals are pushed into their real periods, which is exactly why coverage on its own should never be read as the forecast. Tracking the past-due list alongside deal slippage gives you the two numbers that predict a miss before the quarter is decided, and both feed forecast accuracy directly.
Frequently Asked Questions
What does a past-due close date mean in a CRM?
It means the opportunity is still open but the date the rep committed to has already come and gone without a decision. The record is now carrying a date that describes the past, so any report that groups pipeline by close date is placing that deal in a period it cannot close in.
How many past-due deals is too many?
Any past-due deal older than a few days is a hygiene failure, because the rep either knows the new date and has not entered it or does not know it and should not be forecasting the deal. Track the count and the dollar value weekly, and treat a rising trend as a signal that forecast discipline is slipping ahead of the numbers showing it.
Should past-due deals be closed lost automatically?
No. Automatic closure destroys the audit trail that makes slippage analysis possible and pushes reps into gaming the date field. The better rule is a forced review. A past-due deal cannot stay open past the weekly pipeline review without a new date backed by a buyer event or a documented close lost reason.
Do past-due close dates affect forecast accuracy?
Yes, in both directions. They inflate the current period when a report counts them as still due, and they hide real revenue when the deal actually closes in a later period that nobody planned for. Either way the forecast is describing a quarter that will not happen.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like past-due close date into prescriptive action for your team.
Schedule a Demo