What Is the Difference Between a Pipeline Review and a Pipeline Inspection?
A pipeline review is a coaching conversation about deals. A pipeline inspection is a data audit of records. The review asks what a rep should do next on a live opportunity. The inspection asks whether the opportunity should be counted as pipeline in the first place.The terms get used interchangeably, and the cost of blurring them is a book that looks healthy in every meeting and disappoints every quarter. Reviews are forward-looking and rep-centric. Inspections are backward-looking and record-centric. A team can run flawless weekly reviews and still carry a book where more than ten percent of pipeline has gone untouched for twelve months, because a review only touches the deals a rep chooses to bring, and no rep volunteers the opportunity they stopped working four months ago.
What Happens in a Pipeline Review?
A pipeline review works live deals forward with the rep who owns them. The manager and rep walk a subset of the book, usually the opportunities with in-quarter or next-quarter close dates, and build the next action for each.The questions are about buyers. Who is the economic buyer and has the rep been in a room with them. What is the compelling event and did the buyer articulate it. What is the agreed next step, on what date, with whom. Where is the deal exposed, and what would need to be true for it to close a month earlier.
The output is a work list. Introductions to chase, business cases to build, procurement steps to start early. A pipeline review is management labor applied to deals that are still moveable, and its value depends entirely on the manager knowing the deals well enough to challenge the rep's story.
What Happens in a Pipeline Inspection?
A pipeline inspection tests every record in the book against rules, and it does not require the rep to be present. The output is an exception list.The checks are mechanical. Time since last meaningful change, where meaningful means a change in stage, close date, or amount. Close dates that have already passed. Opportunities with no scheduled next step. Stage assignments not supported by the required evidence for that stage. Amounts far above the historical closed-won average for that segment. Duplicate records against the same account.
None of that requires judgment, which is why inspection scales and review does not. A manager with eight reps cannot review two thousand open opportunities, but a query can flag the four hundred that fail at least one rule, and the manager can then spend review time on the ones that matter.
How Do Review and Inspection Compare Side by Side?
A review works the deals a rep brings, and an inspection tests every record whether the rep brings it or not.| Dimension | Pipeline Review | Pipeline Inspection |
|---|---|---|
| Subject | Deals a rep is working | Every record in the book |
| Question | What is the next action? | Should this count as pipeline? |
| Run by | First-line sales manager | RevOps, largely automated |
| Rep present | Yes, required | No, not needed |
| Output | Actions per deal | An exception list to clear |
| Cadence | Weekly to biweekly | Continuous checks, monthly clearing |
| What it catches | Weak champions, missing next steps | Stale records, stage inflation, bad dates |
| What it misses | Deals the rep does not raise | Deal quality that data cannot see |
Why Does Stale Pipeline Matter So Much?
Stale pipeline matters because it inflates coverage, and inflated coverage produces false comfort at exactly the moment a team should be building. Across ORM customers, more than ten percent of pipeline has sat untouched for twelve months.The arithmetic is unforgiving. A team carrying four times coverage where a tenth is dead is really carrying 3.6x, and the dead portion is usually concentrated in the older, larger, more optimistic opportunities that nobody wanted to close lost. That skews the average deal size upward too, which then feeds a forecast that expects more revenue per win than the business has ever produced.
Composition is the real issue, not the ratio. A pipeline can hold plenty of coverage and still fail because it is concentrated in a few large deals, sitting in the wrong stage, owned by the wrong reps, or built on close dates that keep moving. That is the case laid out in the 3x pipeline coverage rule is wrong, and inspection is the mechanism that keeps pipeline coverage connected to something real.
What Aging Rule Should Trigger an Inspection Flag?
Use a twelve-month rule as the outer boundary and set tighter thresholds by expected cycle length. At ORM, most customers apply a twelve month rule, with meaningful activity defined as a change in stage, close date, or amount.Twelve months is a floor rather than a target. If deals in a segment typically close inside twelve weeks, an opportunity untouched for six weeks is already a problem and should flag well before the annual boundary. Grouping opportunities by expected duration and setting an aging threshold per group is more useful than one global number, because a ninety-day mid-market deal and a nine-month enterprise deal fail on different timelines.
The other threshold worth setting is close-date churn. Count how many times a close date has moved. A deal on its third push is behaving differently from one on its first, and that count is a cleaner deal slippage signal than any probability field.
Who Should Own Each One?
Managers own reviews and RevOps owns inspections. The split matters because it changes the conversation.When a manager runs the inspection themselves, the session becomes an argument about whether the pipeline is clean, and reps defend their numbers. When RevOps produces the exception list, the manager arrives with specific records that failed specific rules and the conversation is about what to do with each one. Reps engage with a list. They resist a verdict.
The clearing cadence should be monthly, with a full scrub two weeks before the quarter closes. That timing is deliberate. Next quarter's coverage baseline gets set on the first day of the period, and every capacity and pipeline generation decision made in the first two weeks flows from it. Starting a quarter with inflated inventory means those decisions are wrong before anyone has made a call.
Frequently Asked Questions
Is a pipeline review the same as a pipeline inspection?
No. A pipeline review is a coaching conversation about specific deals with the rep who owns them. A pipeline inspection is a data audit of the whole book that runs with or without the rep in the room. The review works deals forward. The inspection finds records that should not be counted as pipeline at all. Most teams run reviews and skip inspections, which is why coverage numbers drift away from reality.
What does a pipeline inspection actually check?
Opportunity age since last meaningful change, close dates in the past, deals with no next step, stage assignments that do not match the evidence, amounts that differ sharply from historical closed-won values in the same segment, and duplicate records. These are data conditions rather than judgment calls, which is why an inspection can be automated and a review cannot.
How much of a typical pipeline is stale?
Across ORM customers, more than ten percent of pipeline has gone untouched for twelve months. It varies by customer, but the pattern holds. That inventory sits in coverage calculations and makes a thin quarter look adequately covered, which is the practical reason inspection matters more than most teams treat it.
Who should run a pipeline inspection?
RevOps should own the inspection and produce the exception list. The manager then works the exceptions with the rep. Splitting it this way removes the argument, because the manager arrives with a list of specific records that failed specific rules rather than a general complaint about pipeline hygiene. Reps engage with a list. They defend against an accusation.
How often should you inspect the pipeline?
Run the automated checks continuously and the exception-clearing session monthly, with a full scrub two weeks before the quarter ends. The pre-quarter timing matters because next quarter's coverage baseline gets set on day one, and starting a period with inflated pipeline means every decision made from it is wrong.
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