A sales weekly business review should change decisions, not collect updates that already exist in the CRM. The meeting is useful when it identifies material exceptions, tests forecast assumptions, allocates help and closes with named actions. It becomes expensive theatre when every seller narrates every opportunity, managers reward optimistic numbers and nobody records what was decided.
This guide provides a copyable 60-minute template, calculation rules, an exception log and a meeting-quality audit. It is designed for a first-line sales manager or Head of Sales, but the structure can be adapted to a region, segment or small commercial team. Use only data the team is authorised to share, and keep customer and employee information inside approved systems.
Direct answer: what belongs in a sales WBR?
A practical sales WBR has six parts: outcome and prior actions; target and actual movement; pipeline exceptions; forecast changes; coaching and capacity; and decisions with owners. It reviews changes since the previous meeting rather than repeating the whole pipeline. The core output is an action and decision log, not a slide deck.
The meeting should answer five questions:
- What changed materially?
- Why did it change?
- Which assumption is weakest?
- What decision or help is needed now?
- Who will do what by when, and how will we know?
If a topic cannot influence action this week, move it to a different forum.
Before the meeting: define the operating contract
Write a one-page WBR contract before creating a dashboard. Include purpose, scope, participants, inputs, decision rights, confidentiality and outputs.
Purpose: improve near-term revenue judgment and remove execution constraints.
Scope: one team, named period and agreed revenue definition. State whether renewals, partners, consumption revenue or services are included.
Participants: the smallest group able to provide evidence or make decisions. Sellers need not attend every section if the review covers sensitive people decisions.
Inputs: CRM snapshot, target, recent conversion, ageing, forecast categories, major risks and prior actions. Freeze the reporting cut-off so late edits do not rewrite history.
Authority: specify who can change forecast categories, approve discounts, reallocate support or escalate delivery constraints.
Output: a decision log, action log, changed forecast narrative and issues assigned to other forums.
This contract prevents a common failure: expecting one meeting to serve pipeline inspection, performance review, strategy, coaching and executive reporting simultaneously.
The 60-minute agenda
| Time | Segment | Required question | Output |
|---|---|---|---|
| 0–5 min | Outcome and prior actions | Which prior commitments closed or slipped? | Closed actions and exceptions |
| 5–12 min | Target and movement | What changed in actual, pipeline and forecast? | Agreed variance statement |
| 12–30 min | Pipeline exceptions | Which opportunities need a decision, evidence or help? | Opportunity actions or removal |
| 30–42 min | Forecast judgment | What moved, why and with what confidence? | Updated range and risk narrative |
| 42–52 min | Coaching and capacity | Which recurring constraint needs practice or reallocation? | Coaching or capacity action |
| 52–60 min | Decisions and close | Who owns each action and review date? | Final decision and action log |
The agenda is a default. A transactional team may review shorter cycles; an enterprise team may need more time on a few complex opportunities. Preserve the logic even when the timing changes.
Section 1: prior actions before new discussion
Begin with the last action log. Mark each item complete, changed, overdue or cancelled. Do not accept “in progress” without a next observable event. If actions regularly roll forward, the team has a capacity, authority or meeting-design problem.
Use this table:
| Action ID | Decision or issue | Owner | Due date | Evidence of completion | Status | Next decision |
|---|---|---|---|---|---|---|
| WBR-042 | Confirm security review path for Acme | Jordan | 18 Sep | Buyer email naming reviewer and date | Complete | Keep close date |
| WBR-043 | Reprice Beta proposal | Priya | 18 Sep | Approved margin scenario | Overdue | Escalate pricing approval |
The evidence column matters. “Spoke to customer” is activity. “Customer confirmed procurement review on 24 September” is a verifiable state change.
Section 2: target and movement
Show only the measures needed to orient the meeting:
- period target and actual closed revenue;
- current forecast range;
- qualified pipeline created and removed since the last cut;
- stage conversion and ageing relative to a relevant baseline;
- concentration in the largest opportunities;
- one customer-quality or margin signal where relevant.
Avoid a wall of metrics. A measure belongs when it changes a decision. Define every term in a metric dictionary, including currency, period, booking rule and treatment of renewals or services.
Core calculations
Unweighted pipeline coverage equals open qualified pipeline divided by the remaining target.
If the remaining target is €500,000 and qualified pipeline is €1,500,000, coverage is 3.0x. This is not a probability of success. It is an exposure ratio that must be interpreted with conversion, quality and time.
Stage-weighted pipeline equals the sum of opportunity amount multiplied by a documented stage probability. If historical performance does not support the weights, label the result a convention rather than a forecast.
Forecast error for a completed period can be calculated as absolute forecast minus actual, divided by actual. Track direction as well as absolute error. A manager who is always optimistic and one who is always conservative create different planning problems.
Concentration equals the value of the largest few opportunities divided by the total forecast. A €1 million forecast with €650,000 in one unverified deal is not equivalent to a diversified forecast.
Section 3: pipeline exceptions, not pipeline narration
Create rules that select which opportunities enter the meeting. Example triggers include:
- close date moved more than once;
- no verified next event;
- stage age exceeds the team threshold;
- amount changed materially;
- decision process or economic buyer is unconfirmed;
- critical technical, legal, security or procurement dependency is unresolved;
- margin or discount crosses a tolerance;
- forecast category conflicts with stage evidence;
- opportunity is material to the period outcome.
The threshold should reflect the sales motion. Do not copy a 30-day ageing rule into a market where procurement normally lasts six months. Use historical distributions and judgement.
For each selected opportunity, require a compact evidence card:
| Field | Example |
|---|---|
| Customer outcome | Reduce manual reconciliation before year-end close |
| Verified event | Finance workshop booked for 23 Sep |
| Decision participants | CFO sponsor; controller evaluator; IT security reviewer |
| Current evidence | Workshop accepted; data sample received |
| Weakest assumption | Security review can finish in ten working days |
| Next decision | Allocate security architect or move forecast |
| Owner and date | Manager by 19 Sep |
The manager should not rewrite the deal in the meeting. Ask one question that tests the weakest assumption. If the seller cannot supply evidence, change the category or define the next test.
Section 4: forecast as a judgment with a range
Separate the forecast from the pipeline. Pipeline describes possible work at stages. Forecast expresses a time-bounded judgment about expected outcomes under stated assumptions.
Use three views:
- Committed evidence: opportunities with agreed category criteria and no unresolved material contradiction.
- Expected range: downside and upside based on named risks, not arbitrary percentages.
- Management actions: decisions that can still change the result.
A forecast narrative should explain movements. For example: “The base case fell from €820,000 to €740,000 because two procurement events moved beyond the period. Upside remains €900,000 if the Gamma security review closes by 25 September. Concentration is high: 38% of base case depends on Delta. We request an executive reference call and will revise the category if no date is confirmed by Friday.”
This paragraph is more useful than a green dashboard because it exposes evidence, uncertainty and requested action.
Section 5: coaching and capacity without public humiliation
The WBR can reveal patterns, but it should not become a public performance hearing. Discuss shared process gaps in the group. Move sensitive individual feedback, pay, health, conduct and formal performance decisions to the appropriate private process.
Look for recurring system signals:
- multiple sellers lack verified decision criteria;
- discovery notes describe product features but not customer outcomes;
- legal review repeatedly starts too late;
- one solution engineer blocks several deals;
- close dates cluster at period end without buyer events;
- discount requests arrive without a value case.
Translate a pattern into either coaching, process repair or capacity action. Coaching fits when a behaviour can be observed and practised. Process repair fits when the stage definition, handoff or approval is unclear. Capacity action fits when a scarce resource cannot serve demand.
Use a coaching card:
| Behaviour | Evidence | Practice | Success signal | Review |
|---|---|---|---|---|
| Confirm buyer decision process | 4 of 7 late-stage records lack named steps | Role-play decision-process questions; review two calls | 90% of stage-three records include participants, criteria and date | Next WBR |
Do not infer personality from pipeline data. Diagnose observable work.
The copyable WBR template
Header
- Team and period:
- Data cut-off and source:
- Meeting owner:
- Decision authority present:
- Confidentiality classification:
1. Prior actions
- Completed:
- Overdue and reason:
- Decision needed:
2. Business movement
- Target / actual / remaining:
- Current base / downside / upside:
- Pipeline created / removed:
- Material conversion or ageing change:
- Concentration or margin warning:
3. Pipeline exceptions
For each: opportunity, trigger, evidence, weakest assumption, requested decision, owner, deadline.
4. Forecast changes
- Movement since prior cut:
- Cause:
- Assumption:
- Confidence or range:
- Action that can change outcome:
5. Coaching and capacity
- Shared capability pattern:
- Process or handoff defect:
- Scarce resource:
- Private follow-up required:
6. Decisions and actions
- Decision:
- Owner:
- Due date:
- Evidence of completion:
- Escalation trigger:
- Review date:
A worked example
A six-person B2B team has a €900,000 quarterly target and €300,000 closed. The remaining target is €600,000. Qualified open pipeline is €1.8 million, apparently 3.0x coverage. The dashboard looks healthy.
The exception rules reveal a different picture. Two opportunities worth €700,000 have no confirmed procurement date. Another €250,000 opportunity depends on a security review that has not started. Three smaller opportunities have verified buyer events within two weeks. The stage-weighted total is €920,000, but the weights are inherited defaults and have not been calibrated.
The team sets a base range of €520,000–€680,000 for the remaining period instead of reporting €920,000 as expected revenue. It requests one security resource for the material review, assigns sellers to confirm procurement events by Thursday and removes one record whose buyer postponed the project. A coaching pattern also appears: several sellers document champions but not decision criteria. The manager schedules a private call review and a group practice session.
At the next WBR, procurement dates are confirmed for one large opportunity and rejected for another. The forecast becomes narrower. The meeting did not manufacture certainty; it improved calibration and released capacity from a deal that no longer belonged in the period.
WBR-12: audit the meeting itself
Score each statement zero for no, one for partly and two for yes. A strong review scores at least 20 of 24 without a zero on decision or confidentiality controls.
- Purpose and period are explicit.
- Data source and cut-off are fixed.
- Metric definitions are documented.
- Prior actions are reviewed first.
- Exceptions select discussion topics.
- Opportunity evidence is separated from opinion.
- Forecast is separated from pipeline.
- Uncertainty and concentration are visible.
- Requested decisions have authorised participants.
- Sensitive coaching stays in the correct forum.
- Every action has owner, date and completion evidence.
- The meeting ends on time with a distributed log.
Scores below 14 indicate a reporting meeting rather than a decision system. Repair the lowest control first. Do not add more slides.
Common failure modes and repairs
Every opportunity is reviewed
Failure: the meeting expands while high-risk items receive little attention.
Repair: define exception triggers and rotate deep dives outside the WBR.
Managers demand one number
Failure: uncertainty is hidden inside optimistic categories.
Repair: require base, downside, upside and the assumption separating them.
CRM hygiene becomes public blame
Failure: people protect themselves by entering low-quality data or delaying updates.
Repair: separate system defects, training and individual accountability. Use private coaching where appropriate.
Actions have no evidence
Failure: “follow up” repeats for weeks.
Repair: state the customer or internal event that proves completion.
Dashboards replace judgment
Failure: stage weights and colours are treated as facts.
Repair: test historical calibration and require a narrative for material movement.
The wrong authority attends
Failure: the team identifies blockers but cannot resolve them.
Repair: either invite the authorised decider for a bounded segment or route a documented escalation immediately.
Adapting the template
For a high-volume transactional team, shorten opportunity review and emphasise conversion, response time, lead quality and capacity. For enterprise sales, review fewer accounts and deepen decision process, multi-party alignment, security, legal and delivery evidence. For a partner-led model, include partner commitment and attribution rules. For renewals, replace new-pipeline coverage with adoption, health, risk and commercial-renewal signals.
Keep one principle: the meeting must connect evidence to a decision. A metric that does not change action belongs in analysis, not necessarily in the room.
Responsible AI in the WBR
AI can summarise approved notes, flag missing fields or draft questions. It should not invent buyer evidence, make employment decisions or send customer commitments without accountable review. Define permitted inputs, retention, verification and final authority. A generated summary is a draft. The source record and the manager remain authoritative.
Monitor false positives. A tool may label an opportunity risky because a field is blank when the evidence exists in an approved system it cannot access. Conversely, fluent summaries can hide an unsupported claim. Require source links or record references for material statements.
Your next WBR
Before the next meeting, do three things. First, publish five exception triggers. Second, replace the slide deck’s final page with the decision and action log. Third, measure whether the meeting closed prior actions and changed any decision. After four cycles, review forecast calibration, overdue actions and participant time.
A useful WBR is not energetic because the manager speaks more. It is disciplined because the team discusses fewer items, exposes weaker assumptions and leaves with authorised action.
Managers who want structured practice across pipeline inspection, forecasting, coaching, performance cadence and responsible use of sales data can review MTF Institute's Professional Certificate in Sales Management. Check the current curriculum and enrolment terms directly, then compare its assignments with the WBR artifacts in this guide. A course should support application; it does not replace local authority, customer evidence or fair people processes.
Conclusion
The weekly business review should be the control loop for sales execution. The 60-minute template connects target movement, pipeline exceptions, forecast judgment, coaching and capacity to recorded decisions. The calculations help orient the discussion, but they do not replace evidence. The WBR-12 audit keeps the forum honest.
Start with one team and one period. Preserve the history of forecasts and actions. When the meeting repeatedly surfaces the same problem, stop reviewing it and redesign the process that creates it.