Use your pipeline review to decide what happens next.

Decide which opportunities need help, a different next step, a revised expectation or a pause. Send routine updates before the meeting so colleagues can use the time together to resolve questions the owner cannot settle alone.

Agree which opportunities to review and the period the review covers. You might review active quotes awaiting a technical decision, opportunities whose expected decision date has passed, or a small set requiring resources from another team. Record the inclusion rule so a cleaner-looking pipeline cannot be achieved simply by leaving difficult cases out.

Cross-account priorities belong in the account prioritisation guide. This review examines what the buyer needs to decide within each opportunity. Forecast reporting may use the same records, but a forecast category should not substitute for explaining what the buyer has agreed.

Prepare six fields for each opportunity: the specific customer need; evidence supporting its current stage; the next customer decision; the missing commitment or answer; the responsible person; and the date or event that justifies the next review. Add a link to the latest meaningful change so a new reader can distinguish today’s situation from last week’s.

A statement such as “procurement reviewing” needs a source. Was this said in a conversation, inferred from a sent quote, or copied from an earlier update? Keep the date and the speaker’s role with the statement. Use checked call notes when a meeting produced the evidence, and quote follow-up when the decision concerns a particular revision.

Use the stages your business actually needs. Salesforce’s opportunity guidance notes that sales stages differ between companies and describes contact roles alongside the opportunity. Neither a stage name nor the presence of a contact establishes that the next purchase decision is agreed.

Let the owner state the customer decision in one sentence, then show the supporting record. Ask what is uncertain and what would change the proposed action. This order makes disagreement useful: a colleague can challenge the evidence or offer a way to resolve the gap without debating an unexplained confidence percentage.

End each discussion with an action, an owner and a review trigger. Where customer participation is needed, record who will ask and how the request fits the relationship. “Involve finance” is incomplete. “Ask the customer sponsor whether finance needs the total-cost comparison before approval” describes work someone can carry out.

An owner may need help from a technical reviewer, service team or another account colleague. The deal stakeholder map keeps those roles connected to the decision. Avoid turning every uncertainty into another customer meeting when an internal record can answer it first.

A record can be stale because the owner failed to enter a recent conversation. It can also be accurate while the customer waits for a genuine dependency. Check which problem you have before using age to escalate, close or contact the customer. A moved close date should include the reason and its source.

Use a small set of explicit review outcomes: continue with an agreed action, resolve an internal dependency, confirm customer timing, pause with a restart condition, or close with the evidence available. Preserve “unknown” when a loss reason is not known. An orderly queue should not create certainty that the team does not possess.

If no action remains justified, the team can stop carrying the opportunity as active. Record who made that judgement and what new information would warrant reconsideration. Keep any relationship or contact exclusions attached to the account when the opportunity changes state.

Trial the review on five opportunities. Ask a colleague outside those deals to identify the current customer decision, its evidence and the next action. Note the missing context. Then inspect the following review: did the assigned action produce an answer, reveal another dependency or merely create another task?

Keep process measures separate from commercial outcomes. Fewer unassigned records or clearer next steps can show that the process is better organised; they do not establish that the review caused revenue. Use the measurement guide for outcome comparisons and the monthly commercial review to decide what the wider system needs.

A standalone pipeline view or review workflow has its own scope and quote. Within a Build campaign, agree which opportunity context and qualification decisions return to the campaign operator, and who acts on the replies. Your team, ClarityRev or both can handle the agreed work. Build includes operation and improvement during its agreed period; Run is optional continuation afterwards. Your sales team retains responsibility for sales calls, prices and closing.