What Days Since Last Activity Measures
Days since last activity counts the elapsed time since the most recent recorded event on an open opportunity. It is the most common trigger in pipeline hygiene automation and the most commonly misconfigured, because activity means different things in different CRMs.The definition you pick decides whether the metric is useful. Logged calls, emails, and meetings are easy to generate and easy to fake. Field changes are harder to fake and closer to the truth. ORM counts a change in stage, close date, or amount as meaningful activity. A deal with twenty logged emails and no field change in four months is quiet, whatever the activity counter reports.
Silence is the earliest risk signal
The strongest early warning on a deal is the absence of a signal. No stage change, no data moving, no notes. Reps recognize the same pattern from the buyer's side, where emails go unanswered and calls go to voicemail. The CRM version of that silence is a last-activity date that keeps getting older while the close date sits untouched.
That combination, a static close date paired with a growing silence window, is worse than a close date that moves. A rep who pushes a date is still engaged with the deal. See deal slippage for what the push itself predicts.
Setting thresholds that hold up
Derive the window from the expected cycle for that deal type. ORM predicts a close curve per opportunity group, with curves running from 1 to 80 weeks and most closing expectation before week 12. A group whose curve peaks at week 8 cannot tolerate a 60-day silence. A group whose curve peaks at week 40 can.
Start with bands like these and reset them against your own closed-won silence history:
| Silence window vs expected cycle | Read | Action |
|---|---|---|
| Under 10% of expected cycle | Normal | No action |
| 10% to 25% | Cooling | Rep confirms a next step with the buyer |
| 25% to 50% | At risk | Remove from commit until confirmed |
| Over 50% | Treat as dead until proven otherwise | Re-qualify or close lost |
How to use the metric
- Pair it with the close date. Silence alone is noisy. Silence on a deal carrying an in-quarter close date is a forecast problem, and only 20% of pipeline holding an in-quarter close date on day one of the quarter actually closes in that quarter across ORM's customer base. - Report it by value, not by count. Ranking reps on how many quiet deals they own encourages record deletion. Ranking the dollars behind the silence directs attention to the deals that decide the number. - Flag, do not auto-close. Automation surfaces the deal. A manager decides the outcome. That split keeps reps honest without making the CRM feel adversarial. - Feed it back into calibration. Compare closed-won deals against their silence history each quarter to learn the real threshold, then reset the bands. This is how the metric stops being a guess and starts improving forecast accuracy.
Frequently Asked Questions
What should count as activity on an opportunity?
Field changes carry far more signal than logged touches. ORM counts a change in stage, close date, or amount as meaningful activity. Logged calls, emails, and meetings are easy to generate and easy to inflate, so a deal with twenty logged touches and no field change in four months is quiet regardless of what the activity counter says.
How many days without activity should trigger a review?
Set the window from the deal's own expected cycle rather than a round number. A segment where most deals close inside 12 weeks needs a much shorter silence window than one where the cycle runs a year. A single company-wide threshold flags the wrong deals in both directions.
Is silence worse than a pushed close date?
Often yes. A rep who moves a close date is still engaged with reality. A deal where nothing changes at all, no stage movement, no data edits, no notes, is usually further gone. The earliest warning on a deal is the absence of a signal rather than a bad one.
Can activity tracking be automated?
Yes, and it should be. Automate the flag rather than the removal. Let the system surface deals that cross the silence window and let a manager decide the outcome during pipeline review, because automatic deletion destroys rep trust in the system faster than any reporting gain justifies.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like days since last activity into prescriptive action for your team.
Schedule a Demo