What Is the Difference Between a Pipeline Scrub and a Pipeline Review?
A pipeline review works live deals forward. A pipeline scrub decides which records deserve to stay in the pipeline at all. The review is a recurring management rhythm. The scrub is a periodic cleanup event with a definition of done.The two get conflated because both involve a manager, a rep, and a list of opportunities. The difference is what happens to a deal nobody wants to discuss. In a review, that deal gets skipped, because reviews cover the opportunities a rep chooses to bring. In a scrub, every open record gets a decision, and skipping is not one of the options.
That single rule is why scrubs work. Pipeline does not rot because managers fail to coach. It rots because no forum forces a verdict on the opportunity that stopped moving in March and that everyone has quietly agreed not to mention.
What Happens in a Pipeline Review?
A pipeline review builds the next action for deals that are still moving. Weekly or biweekly, manager and rep, focused on in-quarter and next-quarter close dates.The conversation is forward-looking. What is the agreed next step and on what date. Who else needs to be in the buying group. What has the buyer committed to in writing. Where is the risk and what would need to change to pull the deal in a month.
Reviews assume the opportunity is real. That assumption is reasonable for a deal that moved stage last week and unreasonable for one that has not changed since two quarters ago, which is precisely why a review cannot substitute for a scrub. The meeting is built to advance deals, and advancing a dead deal produces a next step that nobody performs.
What Happens in a Pipeline Scrub?
A scrub applies a disposition rule to every open opportunity and closes the loop on each one. Time-boxed, usually a half day per team, run against a pre-built exception list.Four dispositions cover almost everything. Keep the record as it stands. Re-date it to a defensible close date with a reason. Re-stage it to match the evidence that actually exists. Close it lost with a loss reason. The rule that makes the session work is that no record leaves the meeting without one of those four applied.
The exception list should be built before anyone sits down. Opportunities with close dates in the past. Records with no change in stage, close date, or amount for longer than the typical cycle in that segment. Deals whose stage claims a level of buyer engagement the activity history does not support. Amounts well above what the segment has ever closed. Duplicates against the same account.
Preparation is what separates a scrub from a longer review. Walking into the room without the list means spending the session finding problems rather than resolving them.
How Do Scrubs and Reviews Compare Side by Side?
One is a rhythm, the other is an event with an end state.| Dimension | Pipeline Review | Pipeline Scrub |
|---|---|---|
| Purpose | Advance live deals | Decide what stays in pipeline |
| Coverage | Deals the rep raises | Every open record |
| Frequency | Weekly or biweekly | Quarterly, before period close |
| Prepared by | Manager, from the CRM view | RevOps, as an exception list |
| Decision rights | Rep proposes next steps | Manager approves a disposition |
| Definition of done | Every raised deal has an action | Every open record has a verdict |
| Typical duration | 30 to 60 minutes | Half a day per team |
| Effect on coverage | Little to none | Coverage drops, quality rises |
How Much Junk Is Actually Sitting in the Pipeline?
More than ten percent of pipeline across ORM customers has gone untouched for twelve months. That is inventory sitting inside every coverage calculation the business runs.The second number is harder to hear. Of the pipeline value carrying an in-quarter close date on the first day of a quarter, roughly twenty percent closes in that quarter. Eighty percent of the value that appears to be in the period does not land in the period. That is less a data problem than a pattern ORM sees repeatedly across its customer base, and a forecast that ignores it will tend to run optimistic.
Both facts point the same direction. A team at three and a half times coverage carrying ten percent dead inventory is really at about three times, and the dead portion is the part most likely to sit in older records no rep wanted to mark closed lost, which is why it can skew the average deal size upward and inflate any weighted pipeline calculation built on top of it.
When Should Each One Run?
Reviews run on a fixed weekly or biweekly slot. Scrubs run two to three weeks before the quarter ends.The scrub timing is deliberate. Next quarter's coverage baseline gets set on day one of the period, and the capacity, territory, and pipeline generation decisions made in the first two weeks all flow from that baseline. A team that opens a quarter with inflated inventory makes those calls wrong before anyone has taken a customer meeting.
Scrubbing after the quarter starts is better than not scrubbing, but it means the plan was built on a number that was never real. Scrubbing in the last week of a quarter is theater, because the quarter has already happened by then.
What Should Happen After a Scrub?
Convert the findings into standing rules so the same records do not come back. A scrub that ends with a cleaner CRM and no rule changes guarantees an identical scrub next quarter.Three rules do most of the work. Set an aging threshold per segment rather than one global number, because a ninety-day mid-market deal and a nine-month enterprise deal go stale on different timelines. Require a scheduled next step with a date on any opportunity in a late stage. Require a written reason on any close-date change, which also gives you the push count per deal that predicts slippage better than a probability field.
Then track what the scrub changed. Coverage before and after, the count of records closed lost, and the movement in forecast accuracy over the following two quarters. Teams that measure this stop treating the scrub as an administrative chore, because the change in pipeline coverage and in forecast accuracy becomes visible in their own tracking.
Frequently Asked Questions
What is the difference between a pipeline scrub and a pipeline review?
A pipeline review is a recurring working session about deals a rep is actively pursuing. A pipeline scrub is a time-boxed cleanup event where every open opportunity gets a disposition decision, including the ones nobody has touched in months. The review moves deals forward. The scrub decides which records still belong in the pipeline at all.
How often should you run a pipeline scrub?
Quarterly, timed two to three weeks before the period ends so the next quarter opens on a clean baseline. Some teams add a lighter mid-quarter pass. Running a scrub monthly is usually a sign that daily hygiene rules are missing, because a well-governed pipeline should not accumulate enough junk to justify a monthly cleanup.
What counts as a stale opportunity?
An opportunity with no meaningful change for a period longer than your typical sales cycle, where meaningful means a change in stage, close date, or amount. A twelve-month rule works as an outer boundary. Across ORM customers, more than ten percent of pipeline has sat untouched for twelve months, and that inventory is still being counted in coverage math.
Who runs a pipeline scrub?
RevOps builds the exception list and sets the disposition rules. Managers and reps make the calls record by record. The separation matters, because a scrub run entirely by sales turns into a negotiation about whether a deal is really dead, and a scrub run entirely by RevOps closes deals that were quietly alive.
Does scrubbing the pipeline hurt forecast accuracy?
It improves it. Removing dead inventory lowers the coverage ratio and raises the quality of what remains, which means the ratio starts tracking outcomes again. Across ORM customers, only twenty percent of the value carrying an in-quarter close date on day one of the quarter actually closes in that quarter, so a pipeline that has never been scrubbed is producing a number that has almost no relationship to the revenue that lands.
See how ORM turns these insights into action
ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.
Schedule a Demo