The most useful pipeline review does not inspect every opportunity. It identifies the records that can materially change the forecast, confirms the next action and owner, and leaves Dynamics 365 more accurate than it was at the start of the meeting.
Before the meeting: prepare the view
- Filter opportunities to the period and team being reviewed.
- Separate open pipeline from committed or forecast categories used by your organization.
- Flag missing owners, close dates, stages, probabilities, and next actions.
- Identify overdue close dates and records with no meaningful recent update.
- Sort material risks by potential value and urgency.
Minutes 0–5: establish the forecast shape
- Compare current forecast and pipeline with target.
- Show value and opportunity count by stage or probability.
- Call out concentration in a small number of deals, owners, or segments.
- Review what materially changed since the previous meeting.
Avoid: treating aggregate pipeline as evidence that the target is covered. Ask how much of that value has timing and probability consistent with the current period.
Minutes 5–20: review material risk
Discuss only the opportunities that merit collective attention. For each selected record, answer:
- What changed since the last review?
- Is the close date supported by a buyer event or documented next step?
- Does the current stage match the work completed?
- What evidence supports the probability?
- What is the next action, who owns it, and when will it happen?
- Is there an external account event that changes timing or relevance?
Minutes 20–25: look for patterns
- Are deals stalling in the same stage?
- Are sales cycles lengthening for a particular segment?
- Do lost opportunities share a qualification or handoff issue?
- Does one rep need coaching, or does the process need redesign?
Use history to formulate a question. Small samples and inconsistent CRM data should not be treated as conclusive performance evidence.
Minutes 25–30: close the loop in Dynamics 365
- Update the close date, stage, probability, and forecast category where evidence changed.
- Record the next action and owner.
- Create follow-up tasks while the team is present.
- Remove clearly stale opportunities from the active forecast according to your process.
- Capture one coaching or process theme for follow-up outside the forecast meeting.
Minimum record fields for a useful review
| Field | Review question |
|---|---|
| Owner | Who is accountable for the next action? |
| Stage | What completed buyer or seller action supports this stage? |
| Probability or forecast category | What evidence supports the current confidence? |
| Estimated value | Is value current and is concentration creating forecast risk? |
| Close date | Which documented event supports this timing? |
| Next action | Is it specific, assigned, and dated? |
| Account context | Has an external company event changed relevance or urgency? |
Make the checklist repeatable
Build saved views that reflect this agenda, agree on field definitions, and review data-quality exceptions before the meeting. Automation should reduce preparation and direct attention; it should not replace manager judgment or rep context.
Prepare three saved views before the meeting
| View | Filter recipe | What to do |
|---|---|---|
| Overdue open opportunities | Status = Open AND Estimated Close Date before the review date | Sort estimated revenue descending. Confirm the next buyer milestone with each owner. |
| Upcoming closes | Status = Open AND Estimated Close Date on or after the review date AND before the start of the next reporting period | Check that the remaining work fits the available time. |
| Missing close dates | Status = Open AND Estimated Close Date does not contain data | Resolve timing gaps separately instead of omitting these records from the forecast conversation. |
Set the team scope explicitly and refresh fixed date cutoffs before every review. See the Dynamics 365 dashboard view setup for the views and filters to create first. Keep won/lost analysis separate and filter it by Actual Close Date.
Leave each reviewed deal with a specific action
Use this format in the opportunity’s notes and a related task: buyer milestone → next action → responsible owner → due date. For example: “Budget review Friday → send revised scope → account owner → Thursday noon.” Create the task against the opportunity, and confirm the owner and due date before ending the meeting.
At the next review, check whether the action happened and whether the buyer milestone changed. An edited CRM record is not, by itself, evidence that the customer progressed.
Primary source
Microsoft Learn: Explore forecasting, pipeline management, and analytics in Dynamics 365 Sales. Reviewed September 30, 2026.