Pipeline review and forecast hygiene

A weekly pipeline review that inspects each deal against agreed rules, records the decisions and ends in a forecast call with the gap stated.

RevOps workflow, run with SalesConceptual blueprintSynthetic exampleUpdated · By Marcelo

Outcome

A weekly review pack: inspection flags, a deal decision log, the forecast call with commit, best case and the gap to target, and actions with owners and dates. RevOps owns the snapshot, definitions and roll-up. Deal owners correct their own records. The Sales manager makes the call.

Before you start

  • Written stage definitions and forecast categories, agreed with the Sales leader.
  • Opportunity fields for amount, stage, category, close date, next step and owner.
  • A target for the period and the closed won total so far.
  • A weekly slot with the people who own the deals.

The kit

Inputs

InputUseIf missing
Opportunity snapshotStage, category, amount, close date, ownerTake it before owners edit; note the time
Previous snapshotLast week’s values for the same fieldsCompare by hand and say so
Next steps and activityNext step, its date, last activityFlag as no next step
Stage historyDate each deal entered its stageUse the last stage change; note it
Target and closed wonPeriod target, won to dateAsk the Sales leader before coverage
Definitions and thresholdsStages, categories, inspection rulesAgree them before the first review

Steps

  1. Owner: RevOps with sales leader

    Agree the rules before the numbers

    Use the stage definitions from your field dictionary and write down what Commit, Best case and Pipeline mean, and from which stage each is allowed. Fix the period, currency, amount basis and inclusion rules. Set inspection thresholds from your own sales cycle; the ones in the template are examples.

  2. Owner: RevOps or assistant

    Take the snapshot and run the inspection

    Export open opportunities at the same time each week, before owners edit for the meeting. Compare with last week’s snapshot: new, won, lost, slipped, amount and category changes. Apply the five rules: no next step, close date in the past, stage age over threshold, amount change, category that does not match the stage.

  3. Owner: deal owners

    Answer each flag before the meeting

    Send each owner the flags on their own deals. A flag is a question until the owner answers it. Owners correct what is simply out of date and bring the rest to the review with the buyer-side facts behind it.

  4. Owner: sales manager

    Run the review and log each decision

    Follow the agenda: changes since last week, flagged deals, commit, then best case. For each deal ask what the buyer last did, who signs and whether the next step fits the close date. Record every category change and slipped close date with a reason someone can check next week.

  5. Owner: sales manager with RevOps

    Make the forecast call and state the gap

    Roll up closed, commit and best case after the decisions. The Sales manager makes the call and writes down what it includes, the gap to target and the assumptions to test. Give each action one owner and a date, and open the next review with them.

Automation

CandidatePrerequisiteException
Capture the weekly snapshotFixed time, fixed fieldsEdits made during the export
Compare two snapshotsStable opportunity IDsMerged, split or reopened deals
Run the inspection rulesAgreed thresholdsPaused deals, legitimate blanks
Calculate the roll-upCategory and close date in periodCurrency, multi-year amounts
Draft the agendaFlag list, named chairOwner absent this week

Where an agent could help

Compare this week’s snapshot with last week’s, apply the agreed inspection rules and draft the agenda, linking each flag to its record and rule. The forecast call, category changes and any CRM edit stay with people. See the agent blueprints.

Human review

  • Owners answer or correct each flag before the meeting.
  • Only the owner changes stage, amount or close date.
  • Each category change and slipped date has a reason.
  • The Sales manager makes the call; the roll-up informs it.
  • Agreeing an action does not change a CRM record.

What to measure in a pilot

Forecast errorCall against actual, per period
Commit accuracyCommit deals won in the period
Slipped dealsClose dates moved out, and how often
Open flagsFlags without an answer at each review
Action follow-throughActions closed by the next review

Sources and limits

Limitations

  • No snapshot, inspection or agenda automation has been built for this workflow.
  • No forecast accuracy or time savings are reported.
  • Pipeline value is not a revenue forecast, and stage probabilities need your own closed deals to mean anything.
  • The inspection thresholds in the template are examples; set yours from your own sales cycle.