Sales pipeline review template:agenda, questions, stages and the sheets to run it.

Forecasting is where weak pipeline reviews show up first. Gartner's State of Sales Operations survey found that only 45% of sales leaders and sellers had high confidence in their organization's forecasting accuracy, and tied the problem partly to data: 47% of respondents believed their organization had high-quality data, while 13% described their data quality as poor (Gartner, via WebWire). A weekly review cannot fix a CRM on its own, but it is the one place every week where bad data, optimistic close dates and missing next steps get noticed by someone other than the rep.

A sales pipeline review template fixes three things that drift when a team runs the meeting from memory: the order of the agenda (numbers before stories), the questions asked of each deal (evidence before opinion), and the definitions everyone uses (what a stage means, what counts as commit). The template below is built around those three. It is different from the sales and marketing SLA template, which governs how leads are handed over, and from the CRM data dictionary template, which defines the fields the review depends on.

The CSV files are saved as UTF-8 with a byte order mark, which Microsoft's support documentation says lets Excel open a UTF-8 CSV normally, so ₹ and other symbols display correctly (Microsoft Support). In Google Sheets, use File, then Import; Google lists .csv and .txt among the supported import types (Google Docs Editors Help). The deal sheet carries its own stage lookup table in columns W to Z, so changing a probability there updates every weighted amount.

The movement block borrows from how CRMs already report change. Salesforce's Pipeline Inspection, for example, groups changes into new, won, increased, moved in, moved out, decreased, lost and overdue, and its waterfall view shows which of those explains a drop in open pipeline (Salesforce Trailhead). If your CRM has no such view, the deal sheet's close-date-moves column and a weekly export give you the same answer by hand.

Keep the weekly review for deals and the monthly one for patterns. A weekly pipeline review that discusses conversion rates runs over; pattern questions belong in the monthly session, where they can be compared with B2B funnel conversion benchmarks and with your own last three months. If pipeline speed is the issue, the pipeline velocity guide and the pipeline velocity calculator break it into deals, value, win rate and cycle length.

These deal inspection questions follow the logic of qualification frameworks rather than any one of them. MEDDPICC, which its maintainers trace back to MEDDIC created at PTC in the 1990s, lists metrics, economic buyer, decision criteria, decision process, paper process, implicated pain, champion and competition (MEDDICC).

The question that does the most work is the simplest: is there a dated next step that the buyer agreed to? A deal with no next step in the buyer's calendar is a hope, whatever its stage. The deal sheet flags these as NO NEXT STEP or OVERDUE before the meeting, so the review can spend its minutes on why, not on discovering it. For competitor questions, use the sales battlecard template.

CRMs store the probability for you, but not the evidence. In HubSpot, each deal stage carries a probability that drives the weighted amount on the board view, and the pipeline must include both a Won and a Lost stage for sales reports to work; HubSpot can also show and require specific properties when a deal enters a stage (HubSpot Knowledge Base). Zoho CRM maps each stage to a probability, and calculates expected revenue from the stage and amount automatically, so it cannot be typed in (Zoho CRM Help). Use required stage properties for the exit criteria you can capture as fields (economic buyer, close date, amount, loss reason) and the review for the ones you cannot.

Do not keep vendor default probabilities. Replace each one with the share of deals that reached that stage in the last four quarters and went on to close won. The same goes for the maximum days in stage: set it near the median time deals that eventually won spent there. HubSpot's stage calculated properties (date entered, date exited, latest and cumulative time in each stage) give you those durations on Professional and Enterprise plans, but they are off by default for new pipelines and stages (HubSpot Knowledge Base). The Zoho CRM, HubSpot CRM and Salesforce service pages cover the setup itself.

The commonly quoted pipeline coverage ratio of 3x is not a law; it is what a one-in-three win rate implies. Teams with a 20% win rate need 5x, and teams that close half their qualified deals need 2x. The template therefore asks for your own historical win rate from the same stage and calculates the coverage you need from it, alongside the coverage you have and the gap in money.

Two rules keep the number honest. First, count only deals with a close date inside the period; a deal dated next quarter is next quarter's coverage. Second, measure win rate on the same definition you use for pipeline: if pipeline starts at Qualified, win rate is won ÷ (won + lost) for deals that reached Qualified. Setting the targets that feed this calculation is covered in how to set marketing pipeline targets, and quota maths in the sales quota calculator.

Slippage is invisible unless you keep a starting snapshot, because a CRM shows today's close date, not last month's. The coverage sheet has a slippage block (deals forecast, won, lost, pushed) and a commit accuracy block (commit value at the start of the period vs value closed from it), plus a six-period trend table. Use forecast categories with fixed meanings: HubSpot's forecast tool, available on Sales Hub Professional and Enterprise, defines pipeline as low likelihood, best case as moderate likelihood, and commit as high likelihood and committed to the forecast (HubSpot Knowledge Base). The template uses Commit, Best case, Pipeline and Omitted with written definitions so they mean the same in every CRM.

A rising slippage rate with stable win rates usually means close dates are set by the seller rather than confirmed by the buyer. A falling commit accuracy usually means commit is being used for deals that lack an economic buyer; the deal sheet counts those automatically. If slippage comes from long legal and procurement steps, the contract redline duration predictor and the sales cycle length forecaster help set realistic close dates. When the cause is leads that were never qualified, the fix sits upstream in the MQL to SQL handoff.

One practical sign that a review has become trustworthy is that sales and marketing stop arguing about the numbers. In the HR tech RevOps case study, a joint MQL definition and lead scoring raised MQL to SQL conversion from 8% to 23%, and a weekly pipeline review was set up with marketing and sales reading the same HubSpot report. A broader look at whether the CRM, stages and reporting can support this kind of review is what the RevOps audit and the HubSpot portal audit cover.