FAQs

Pipeline review questions, answered

Pipeline reviews are where forecast accuracy is won or lost, yet most of them collapse into status readouts that no one can act on. This hub consolidates factual answers to the recurring questions revenue leaders ask about running a disciplined weekly inspection, from meeting structure and the right questions to ask, to how slipped deals and forecast categories should be handled. Each answer links to a deeper explainer and to the Strkr surfaces where the practice runs week over week.

Pipeline review FAQs

Frequently asked questions.

What is a pipeline review?

A pipeline review is a recurring working session in which managers and sellers inspect every open opportunity against a shared standard, decide which deals are real, and agree on the next buyer-side action for each one. It is not a status update, a forecast call, or a 1:1 in disguise. The output of a good review is a shorter, cleaner pipeline and a shared operating picture of risk. Reviews that produce the same list of deals week after week without new buyer evidence are the signal that the standard is not being enforced.

Read the full answer →

What is deal inspection?

Deal inspection is the act of pressure-testing a single opportunity against observable criteria: a confirmed economic buyer, a defensible success metric, a committed next step, and a close date that reflects the buying process rather than the quarter calendar. Inspection questions are specific and testable, not open-ended. A deal that cannot survive five minutes of inspection is not a forecastable deal, it is an aspiration. Teams that formalize inspection into a short, written checklist raise forecast accuracy faster than teams that rely on manager intuition alone.

Read the full answer →

How often should pipeline reviews happen?

Most high-performing revenue teams run a weekly pipeline review by segment or pod, a biweekly or monthly inspection at the leadership level, and a quarterly recalibration of stages and criteria. Weekly cadence catches stalled deals while there is still time to act and keeps hygiene expectations from decaying. Slower cadence lets rot accumulate between touchpoints. Faster cadence tends to produce meeting fatigue without improving forecast quality. The right rhythm matches the sales cycle: short-cycle motions can tolerate more frequent inspection, long-cycle motions should not confuse activity with progress.

What should a weekly pipeline meeting cover?

A disciplined weekly review covers four things in order: changes since last week, new deals entering the forecast, deals at risk of slipping, and deals that should be removed or demoted. Each deal gets the same inspection: what moved on the buyer side, what is the next committed step, and what is the specific risk. The agenda is not a reading of the CRM. Everyone arrives having updated their records, and the meeting is reserved for decisions that cannot be made asynchronously. Thirty to sixty minutes is usually enough when the agenda is enforced.

What makes a good pipeline review template?

A durable template surfaces the fields that drive decisions and hides the rest. Core columns include deal, stage, value, close date, change since last review, next step with date, forecast category, and a one-line risk note. Templates that try to display every field produce noise. Templates that enforce updates before the meeting produce action. The best templates are built into the CRM view that managers and sellers already use day to day, so the review is a shared screen rather than a parallel spreadsheet that drifts out of sync within a week.

What is pipeline hygiene?

Pipeline hygiene is the ongoing practice of keeping deal records accurate, current, and testable. It includes close dates that reflect reality, next steps that are specific and dated, stage placement that matches exit criteria, and loss reasons coded against a stable list. Hygiene is the precondition for every other pipeline metric: coverage, velocity, and win rate all collapse without it. Teams that formalize hygiene into a short, visible checklist and inspect against it in every review see the fastest gains in forecast accuracy and the biggest reduction in end-of-quarter surprises.

Read the full answer →

What is a forecast category?

A forecast category is the judgment label attached to a deal to signal how confident the seller and manager are in it closing in the current period. Common categories include Commit, Best Case, Pipeline, and Omitted. Categories are distinct from stage: a late-stage deal with no committed next step can still be Best Case rather than Commit. Categories are the layer where management overrides live, and they are the number finance uses to roll up the call. Reviews that reconcile stage, probability, and category each week produce the cleanest forecast.

Read the full answer →

What is a slipped deal?

A slipped deal is one whose close date has moved out of the committed period into a later one. Slippage is a leading indicator, not just an outcome: it points to a weakness in qualification, a missing economic buyer, or a competing internal priority that was never fully surfaced. Reviews should track slip count and slip age by rep and by segment, not just revenue slipped. A deal that has slipped twice is almost always a loss in waiting. Treating slippage as a diagnostic question rather than a reporting metric is where cycle-time improvement starts.

Read the full answer →

What is pipeline coverage?

Pipeline coverage is the ratio of open pipeline value to the quota or target it is expected to produce for a period. A coverage ratio of three means a team is carrying three times its goal in open opportunities. The right ratio depends on segment, average win rate, and sales cycle length, so a benchmark that works in mid-market may be thin for enterprise. Coverage is a leading indicator, not a guarantee, and should be read inside the review alongside hygiene and stage mix. Teams that treat coverage as a target rather than a diagnostic tend to inflate pipeline rather than build it.

Read the full answer →

What questions should managers ask in a deal review?

Strong deal reviews run on a short, repeating set of questions: who is the economic buyer and have they confirmed the project in writing, what is the quantified success metric the buyer owns, what is the next buyer-side action and its date, which competitor or status quo is in the deal, and what has changed since last review. Each question is answerable or it is not. Managers who ask the same questions every week train the behavior they want. Managers who freelance the agenda train sellers to improvise answers, which is where forecast noise originates.

What is stage conversion?

Stage conversion is the share of deals that advance from one stage to the next within a defined window. Measuring it by stage reveals where the pipeline actually leaks: a healthy early funnel with weak Proposal to Negotiation conversion is a very different problem from a weak Discovery to Proposal step. Conversion rates become the benchmark that reviews are run against, since a deal lingering in a stage past its typical dwell time is a specific, testable risk. Teams that publish stage conversion by segment and rep give reviews a factual spine instead of a vibe check.

Read the full answer →

How is a pipeline review different from a forecast call?

A pipeline review is deal-by-deal inspection focused on hygiene, next steps, and risk. A forecast call is a roll-up conversation focused on the number the team will commit to for the period. The review feeds the forecast, but the two should not be collapsed into one meeting. Collapsing them tends to shortcut inspection in favor of defending a number, which is how pipeline rot accumulates. Separating them, running the review first and the forecast call second, with a day or two between, produces more honest numbers and faster corrective action when a deal falls out.

See it in Strkr

Related product surfaces.

Forecasting in Strkr Strkr CRM Strkr platform features

Run a pipeline review your team will actually look forward to

See how Strkr turns stage criteria, hygiene checks, and forecast categories into a weekly inspection rhythm that produces decisions instead of status updates.

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.