These two processes get conflated into a single weekly call all the time. That's exactly why both end up doing their jobs poorly.
The weekly forecast call is one of the most universal rituals in sales. Manager pulls up Salesforce, rep walks through deals, a number gets called. The whole thing takes an hour. Somewhere in there, both inspection and forecasting are supposed to happen.
They don't, because they're structurally different processes that need different data, different participants, and different outcomes. Running them together means doing both poorly.
What each process is for
| Pipeline inspection | Forecasting | |
|---|---|---|
| Core question | Why are these deals in the pipeline, and what evidence supports their probability? | What are we going to close this quarter, and what number are we calling? |
| Primary input | Objective activity data: engagement signals, stage age, stakeholder coverage, deal velocity | Qualified pipeline, stage probability, rep judgment, and AI-adjusted scores |
| Who runs it | Manager and RevOps, often without the rep present for the data review phase | Manager and rep together, with the CRO or VP reviewing the rollup |
| Output | A set of actions: re-engage, escalate, move back a stage, remove from pipeline | A number: what we're committing to, what's best case, what's the conservative view |
| Frequency | Weekly for in-quarter pipeline, monthly for next-quarter view | Weekly call, daily updates for at-risk deals in the final weeks of the quarter |
| What it is not | A forecast call, a status update, or a rep-driven narrative review | An inspection, an audit, or a coaching conversation |
Why conflating them produces worse outcomes for both
When inspection and forecasting happen in the same conversation, inspection almost always loses. The forecast call has a specific deliverable: the number. Inspection doesn't produce a number. It produces questions and actions. Under time pressure, the numbers always win.
The result: the forecast call turns into a status report. Reps walk through deals. Numbers get called. Risk doesn't get systematically surfaced because the process isn't built to surface it. It's built to produce a rollup.
Meanwhile, inspection never really happens. Individual deals get discussed when they come up, but there's no systematic comparison of every deal against objective criteria. Problems that should have been caught in week four show up in week eleven.
How to run inspection and forecasting as separate processes
Pipeline inspection: before the forecast call. Inspection should happen before the forecast call, not during it. Pull objective data for every in-quarter deal: stage, age, last activity date, buyer engagement recency, stakeholder count, close date movement history, before any rep conversation. Flag anomalies: deals older than 1.5x average for stage, no buyer engagement in 14+ days, single-threaded above value threshold, close date moved twice. Form a hypothesis for each flagged deal, not a conclusion: "This deal looks stalled based on engagement signals. I want to understand why." Have specific, data-grounded conversations with reps about flagged deals only, not a full pipeline walkthrough. Assign specific actions with owners and due dates. If nothing changes after inspection, the inspection failed.
Forecasting: informed by inspection. The forecast call happens after inspection, informed by what was found. Deals inspection flagged as at-risk get discounted or flagged. Deals that passed inspection carry more weight. The number the manager calls is grounded in data, not just rep submissions. The forecast call itself should run 30 minutes or less if inspection happened correctly. The work of understanding pipeline quality was already done. The call confirms the number and flags anything that's changed since inspection ran.
The most common mistake: using the forecast call as an inspection substitute
Organizations running forecasting and inspection as a single weekly call aren't doing inspection. They're doing forecast calls that occasionally surface risk. The deals that get caught are the ones reps happen to mention. The deals that stay hidden are the ones where the rep is still defending the number.
Separate processes force a different standard. Inspection is systematic: every deal gets reviewed against objective criteria, not just the ones reps surface. The forecast call is then built on a foundation that's already been validated, rather than one assembled in real time from rep narratives.
Summary
Pipeline inspection and forecasting are different processes answering different questions. Inspection asks whether the pipeline is real. Forecasting asks what number to call. When they happen together, inspection gets crowded out by the urgency of the number.
The fix is structural: run inspection before the forecast call, on objective data, without the rep narrative driving the conversation. Then build the forecast on what inspection found. The result is a number that reflects the actual state of the pipeline, not the story reps told about it.
See how Backstory separates inspection data from forecast submissions, and connects them correctly. See the Pipeline Health solution →
Related resources
Deal Execution & Revenue Intelligence hub →
Deal Risk: How to Spot It Early →
See Backstory in action,
no meeting required
See the platform for yourself, or get the guide to help you evaluate it.