How to run a sales pipeline review
Run a sales pipeline review from a dated opportunity export. Check stages, stale follow-up, overdue closes, and the actions owners should take next.
Free app. Runs on your Mac with the Claude or Codex plan you already have.
What sales pipeline review is
A sales pipeline review is a structured look at open opportunities on a stated date. Its purpose is to decide which deals need attention, what each owner should do, and which entries need better evidence before a manager can judge them. Use a dated opportunity snapshot, a copy of the pipeline at one point in time, so everyone can trace a flag back to the same source.
A useful review produces a weekly pipeline report and a sales action queue. The report shows what was included, how open deals are distributed across stages, and where key fields are missing. The queue translates specific evidence into proposed owner decisions. For example, a deal can have an overdue close date and no recorded next step. The owner can check the buyer's current plan and bring back the agreed date or update the record once the facts are clear.
What it does for the business
- Use the review meeting for decisionsSend the readout ahead and use meeting time to resolve the cases on the action queue. Owners can bring evidence about why a date needs attention and leave with a specific confirmation or follow-up to get.
- Find records that need repairA list of unknown owners, conflicting IDs, and missing activity dates shows sales operations where to investigate. Fixing repeated gaps at the source can make the next review easier to run and interpret.
- Direct time toward useful follow-upA rep can check the next agreed milestone on a deal with an expired close date or clarify whether a key action still has an owner. The manager can use the same list to decide which cases need coaching or help from another team.
- Give planning teams comparable inputsStage counts and subtotals let teams discuss the pipeline on a consistent basis. Keep the evidence limits with the figures so managers can decide what needs confirmation before using them in forecast or resource planning.
Sales pipeline review, step by step
Define the snapshot and its fields
A pipeline figure needs a date, a population, and a definition.
What to do
- Find the authorized opportunity export and record its explicit as-of date. Preserve the source so the same cut can be reviewed later.
- Read headers and representative rows. Check whether each row represents an opportunity or whether a deal can have several rows because of products, installments, or another source structure.
- Identify the stable opportunity ID. Agree which statuses mean open, won, or lost and how stage and status differ in your records.
- Identify the amount basis, such as total contract value or annual recurring value, and the currency. Document which dates represent stage entry, meaningful activity, and expected close.
Why
A pipeline health check can start with counts even if some financial fields are unavailable. Its usefulness depends on shared definitions. If two reviewers use different dates or one counts product rows as deals, they can disagree about apparent risk without disagreeing about any actual opportunity.
Reconcile the records before counting
Every source row should have an explainable place in the review.
What to do
- Keep a source row reference and the raw values alongside the fields you standardize. Use explicit status rules so a new or unfamiliar label stays unknown.
- Check duplicates after establishing what a row represents. Record exact duplicate exclusions and set conflicting records for the same ID aside for investigation.
- Flag invalid activity and stage-entry dates, including any dated after the snapshot. Treat missing and invalid dates as unknown for age calculations.
- Reconcile input rows to included, closed, exact duplicate, and quarantined rows. Report distinct IDs separately and explain any gap between rows and opportunities.
Why
A tidy summary can hide the records that made it hard to produce. Reconciliation gives owners and sales operations a way to check whether a deal disappeared because it closed, was repeated, or had data that needed investigation. Keep those reasons available alongside the summary so they can be corrected at the source.
Calculate the readout and make an action queue
A flag should lead to a question the owner can answer.
What to do
- Calculate stage age as days since the recorded entry into the current stage. Calculate inactivity separately from the last meaningful activity using your team's definition of meaningful.
- Flag an overdue close date when the expected close precedes the snapshot date. Check the proposed or agreed inactivity threshold and make the boundary explicit.
- Group open counts and financial subtotals by stage. Within each stage, keep currencies and amount bases distinct and show where amounts are unknown.
- Record each flag with its source evidence. Propose one decision per deal so a rep with overlapping flags has a clear first action, such as confirming the next buyer milestone.
- Use an authorized event history with stated coverage for any movement analysis. Keep observed transitions separate from the dated snapshot summary.
Why
Stage age and inactivity answer different questions. A deal can have been in review for a long time while the buyer is still actively working through it. The flags focus attention and let the owner supply context that a dated record alone cannot capture. An older activity date indicates the need to check follow-up, without establishing the buyer's intentions.
Verify the figures and hand off decisions
The meeting should end with an owner decision that can be checked at the next review.
What to do
- Reproduce the calculations from the retained source. Check the population, grouping, dates, and threshold rules against the report and action rows.
- Open the evidence behind the actions and check what each proposes. If a deal owner or next step remains unknown, leave it visible and assign someone to resolve the record.
- Lead the readout with the finding that changes this week's decisions. Give owners the evidence and the proposed action so they can confirm it or explain what changed.
- Document scope limits and separate data repairs from deal decisions. Keep the output as a draft for the sales manager or qualified forecast owner to review before any forecast commitment.
Why
A sales review is useful when the owner can respond to a specific reason for attention. It also needs to be repeatable so the next meeting can distinguish changes in the source from changes in definitions. A review of the actual evidence catches issues that a clean-looking table can hide.
Common mistakes
- Using today's date for an old exportAnchor age and overdue flags to the explicit date of the opportunity snapshot.
- Counting line items as opportunitiesEstablish what a row represents and check the unique opportunity key before adding rows together.
- Using record updates as buyer activityUse the last date that supports meaningful activity and leave the field unknown when the source lacks it.
- Adding incompatible valuesKeep subtotals separate when the currency or amount basis differs.
- Reporting movement from a single snapshotUse dated event records with stated coverage to describe any observed stage transitions.
What a good result looks like
- A named as-of date and clear opportunity, status, and amount definitions.
- Every source row reconciled, with exclusions and conflicting IDs recoverable.
- Separate stage age and inactivity calculations, with unknowns visible.
- Counts and comparable subtotals that reproduce from the retained inputs.
- One proposed decision per included opportunity with supporting flags available.
And then what? Using the result
- Give each owner the actions for their opportunities and ask for the evidence needed to confirm a date, decision, or reported gap.
- Use the review meeting to resolve decisions that require manager help, such as assigning support to validate a buyer milestone.
- Send recurring data gaps to sales operations with the row references so the source can be corrected.
- Save the dated review for comparison and request a covered event export if the team needs to understand stage movement.
When to run it
- Before the weekly deal meetingPrepare the queue so owners can arrive with answers about overdue dates, stale deals, and missing next steps.
- After a territory or ownership changeUse the review to find gaps in ownership and establish which open opportunities need a handoff first.
- Before preparing a forecastCheck the pipeline population and value definitions first. Take the evidence and open questions to the person responsible for the actual forecast.
Questions people ask
How do you run a sales pipeline review?
Start from a dated opportunity export, validate the included deals, and turn evidence about age, close dates, and next steps into proposed owner decisions. Rebuild the figures from the retained data and record unresolved fields so owners know what to confirm.
What goes in a weekly pipeline report?
Include the snapshot date, included and excluded records, open counts by stage, comparable subtotals, and the actions that need attention. Give owners the rule and evidence behind each flag. Show where missing inputs limit the conclusions.
How do you identify stale deals?
Compare the last meaningful activity date to the snapshot date using an explicit inactivity threshold. Keep deals without a usable activity date visible as unknown. Check the flagged deals with their owners before deciding how to follow up.
Can a pipeline snapshot show stage movement?
A single snapshot shows current stage and can show how long a deal has been there when the entry date is known. Use a dated event history with stated coverage to see actual transitions. Keep the conclusions within the period and deals the history covers.
How should you handle deals in different currencies?
Show separate subtotals for each currency and amount basis. Add a combined value only when you have comparable amount definitions and an agreed, dated conversion basis. Label unknown amounts separately from recorded zeros.
Can you predict which deals will close from the review?
The snapshot supports an attention queue for the recorded opportunities. An overdue date or missing action tells the owner what to check. A forecast calls for additional evidence and a review by the person responsible for forecast decisions.
More jobs in Sales & outbound
Sales pipeline review with AI, on your own Mac.Free app. Runs on your Mac with the Claude or Codex plan you already have. Your files stay on your computer.
Download for Mac