Skip down to the research record

Weekly pipeline review: 3 items before the call

Quota Forecast Editorial Team · Published · 11 min read

A weekly pipeline review covers three items: open deals and risk flags, the next 30 days of the forecast, and coaching needs.

Key takeaways

  • Flag deals with unresolved questions.
  • Build the forecast from the deals reviewed.
  • Record coaching needs with a clear follow-up.

Why the weekly pipeline review comes before the forecast call

It is the meeting where you look at the deals that will shape the forecast before anyone commits to a number, and it gives you time to act on those problems before the number is set. If you wait until the forecast call to look at the pipeline, you are mostly reporting on what has already happened.

Xactly explains why tracking sales performance matters. In its words, "Tracking sales performance helps businesses spot strengths, fix gaps in their sales process, coach reps, and forecast revenue more accurately." (Xactly) That one sentence names four jobs, and a weekly pipeline review can cover several of them at once. You can see which deals are strong, which parts of the sales process are slowing things down, which reps need help, and what the forecast should reflect.

Xactly also describes what good sales performance looks like: "Good sales performance is clear when you see it: reps hit quotas, revenue is gained, and pipelines are healthy and moving." (Xactly) For a revenue leader, the pipeline is where you can check that last part before the quarter's numbers arrive. A review that asks whether the pipeline is healthy and moving is a direct way to look.

This article covers three items to put on the agenda. Each one follows the weekly practice that Salesforce describes in its advice on scaling a sales team: reviewing open deals and flagging risk, forecasting the next 30 days, and using the meeting to spot coaching needs early. (Salesforce)

Item 1: Review open deals and flag the at-risk ones

Review every open deal in the pipeline and flag the opportunities that look at risk. Salesforce describes regular pipeline reviews as "Weekly check-ins where the team reviews open deals, flags at-risk opportunities, and forecasts the next 30 days." (Salesforce) The first two parts of that description are about individual deals. Before the team can talk about the forecast, it needs to know which deals are in trouble.

Start with the deals that are closing soonest, since they affect the near-term forecast the most. For each one, ask the deal owner three simple questions. What changed since the last review? What is the next step, and when is it booked? Who on the buyer's side is involved and engaged? If the answers are vague or missing, flag the deal and write down what would clear the flag.

It helps to agree on a short list of flag reasons before the meeting so everyone uses the same language. Examples include no next step on the calendar, a buyer who has gone quiet, a close date that has moved more than once, or a deal that is waiting on an internal approval nobody has confirmed. Using shared reasons makes it easier to compare deals across reps and to see patterns from one week to the next.

Keep a few rules for how flags are handled:

  • Each flagged deal gets one owner and one date for the next action.
  • A flag stays on the list until someone can name the action that clears it.
  • The meeting spends most of its time on flagged deals, not on deals that are on track.
  • Anyone who changes a deal's stage or close date says why in the record.

For date changes, use a close date change log.

These rules keep the review focused. Without them, the meeting can drift into a long walk through every deal, and the deals that need attention get the same few minutes as the ones that do not.

Before the meeting, send each rep the list of their open deals and ask them to mark any that have changed since the last review. A rep who arrives with a short note on each deal leaves more of the meeting for the decisions that matter.

Item 2: Forecast the next 30 days

Forecast the next 30 days as part of the same weekly check-in, not as a separate exercise. (Salesforce) The forecast should be built from the deal review you just completed, using the flags from item one.

Walk the forecast from the deals on the table. Put each deal in the forecast category your team already uses, and make sure the category matches what the deal owner said in the review. For help distinguishing categories, see forecast category rules. Then compare the total with the forecast you gave last week. Write down what moved and why. A change with no clear reason is worth a question in the meeting, because it may point to a deal that has been counted too early or too late.

Ask a direct question about the flagged deals: if these slipped out of the window, would the forecast still hold? This does not require a precise model. It asks the team to think about how much of the number depends on a small set of deals with open questions. If the answer is that most of the forecast rests on flagged deals, that is a finding to report on the forecast call.

Use the same 30-day window every week. When the window stays fixed, you can compare one week's forecast with the next and see whether deals are moving into the window, out of it, or staying where they are. Changing the window from week to week makes those comparisons harder to read.

When you take the forecast to the forecast call, bring the list of changes with it. A forecast that comes with the reasons for each move is easier to discuss than a single number. Say which deals moved into or out of the window, which flags are still open, and which deals the team is least sure about. That gives the forecast call something specific to test.

Illustrative example: Check dependence on flagged deals

Suppose an illustrative forecast includes 10 deals in the next 30 days, with 3 flagged because their next steps are missing. Review what would happen if those deals slipped outside the window. Deal counts alone do not show how much of the forecast is at risk; check the amounts attached to the flagged deals before discussing the total.

Item 3: Use the review to spot coaching needs before quotas slip

Use the review to spot coaching opportunities before they become missed quotas. Salesforce says weekly pipeline reviews, "even 30 minutes," also "keep the team aligned on priorities and help managers spot coaching opportunities before they become missed quotas." (Salesforce) The review is a natural place to notice coaching needs, because the same deal data that shows risk also shows where a rep is stuck.

Salesforce also says that "Effective sales coaching can increase sales performance by up to 8%." (Salesforce) That is a useful reason to treat coaching as part of the pipeline work, not as something separate that happens later. An increase of up to 8% is an upper bound, not a guaranteed result for your team.

In practice, the link between a deal and a coaching need can be easy to see. If a rep's deals keep stalling at the same stage, or the same objection keeps appearing in notes, that is a coaching question as well as a deal question. Record it as a coaching item with an owner and a date, and keep the list short. One or two concrete follow-ups each week are easier to track than a long list.

Separate the deal from the person when you write the note. "This deal stalled at pricing" describes the deal. "The rep keeps stalling at pricing" describes a pattern that may need coaching. Both can be true, and both are worth recording, but the coaching note should say what the rep will work on and how the manager will check progress.

How long the review can be

Salesforce's wording suggests that a short review can still do its job. That is a useful point for a busy revenue leader, because the review does not have to be a long meeting to be worth holding.

If your current review runs longer than you want, the three items above give you an order for cutting. Keep open deals and flags first, since they cover the risk side of the review. Keep the forecast second, since it depends on the deal review. Move coaching to the end, and if time runs short, make sure each coaching item still gets an owner and a date before the meeting closes.

Choose a time that does not move every week. A review that keeps a fixed slot is easier for the team to plan around, and it gives the forecast call a predictable input. If the review is regularly rescheduled, the forecast call may end up working from stale information.

Keep the team on the same CRM view

A shared view of the deal data makes the review easier to run. Salesforce cites the latest Small and Medium Business Trends Report, which says that "76% of SMB customers say their teams operate off the same CRM view." (Salesforce) That figure describes SMB customers in that report, not your company, but it points to the same practical question you face: does everyone in the review work from the same records?

Before the meeting, agree on where deal stages, close dates, and next steps are recorded. Decide who is responsible for keeping each field current, and check the fields before the review starts rather than fixing them during the meeting. When the data is current, the time in the room goes to decisions. When it is not, the meeting turns into a search for the right number.

It also helps to decide what the team sees. If reps and managers look at different versions of the pipeline, the same deal can be described in two different ways. A single view that everyone can open before the review keeps the discussion on the same facts.

Weekly habits that support the review

Salesforce lists three weekly habits: "CRM hygiene checks, manager 1:1s grounded in real data, dashboards visible to the whole team." (Salesforce) Each one supports the pipeline review in a different way.

CRM hygiene checks are the routine work of making sure deal records are accurate and complete before the review starts. A quick pass through the open deals, looking for missing next steps or out-of-date close dates, saves time in the meeting itself.

Manager 1:1s grounded in real data mean that the one-on-one conversations use the same numbers as the pipeline review. If a rep's flagged deal comes up in the review, the same deal should come up in the one-on-one, with the same notes and the same next step. This keeps coaching tied to what is actually happening in the pipeline.

Dashboards visible to the whole team give everyone the same starting point. When reps can see the team's pipeline, they know what the review will cover, and managers can point to the same view when they talk about priorities.

A simple agenda you can reuse

A simple agenda follows the three items in order: open deals and flags, then the next 30 days, then coaching follow-ups. Use the same order each week so the team knows what to expect.

Close the meeting by reading back the actions, owners, and dates. A list of actions that everyone heard and nobody wrote down is hard to follow up on. Send the notes to the team soon after the review, so the next week's review starts from the same list.

If the review runs over time, do not drop the flags to make room. Move the coaching follow-ups to a short message after the meeting instead. The flags and the forecast feed directly into the forecast call, so they are the parts to protect first.

Mistakes to avoid in the review

A review can fail by turning into a status report with no decisions. Each deal discussed should end with a next step, an owner, or a flag, and the forecast should end with a clear view of what could change it. If the meeting finishes with only updates, the review has not done its job.

A flag list that only grows tells the team nothing new each week. Set a habit of checking each flag at the start of the next review and either clearing it or escalating it.

Take the next step today

Open your current pipeline and check the deals closing soonest for missing next steps before your next review.

Common questions

Does a risk flag mean a deal is lost?

No: a risk flag marks an unresolved question about an open deal. Record what would clear it before relying on that deal in the forecast.

Is the pipeline review the forecast call?

The pipeline review comes before the forecast call. It gives the team time to examine deal risks before committing to a number.

Sources