PeerLab Book a call Start free
Team/Manager Guide Free

Pipeline Review Cadence Design Guide: Weekly to QBR

A complete operating system for pipeline review across four layers, from weekly rep 1:1 to quarterly board, with exact agendas, inspection questions, and rules for what belongs where. Stops review meetings cannibalising each other and turns your cadence into a genuine management tool rather than a reporting ritual.

How to use it

Read the four layer blueprints in order, then compare your current cadence against the failure modes section to find where you are losing signal. Implement one layer at a time, starting with the weekly 1:1, before changing your team call or monthly forecast meeting.

What's inside

  • Four complete meeting blueprints: frequency, duration, attendees, and agenda for each layer
  • Specific inspection questions for each layer, written as exact questions to ask in the room
  • A decision table for when to escalate a deal from one layer to the next
  • Named failure modes for each layer with concrete symptoms and fixes
  • A "what lives where" reference table so managers stop duplicating questions across meetings
  • Rules for separating coaching from inspection within the same review structure
  • Guidance on which pipeline metrics to track at each layer and at what threshold
  • A note on when NOT to run a formal pipeline review at all

A pipeline review cadence is an operating system. Each layer should answer different questions, involve different people, and produce different outputs. When layers blur together, the weekly team call becomes a QBR and the QBR inspects corpses. This guide gives you the architecture to prevent that.


The Four Layers at a Glance

LayerFrequencyDurationWho AttendsPrimary Output
Rep 1:1Weekly30 minManager + repDeal-level coaching actions
Team Pipeline CallWeekly45 minFull team + managerRisk flags, shared blockers, forecast call
Monthly Forecast ReviewMonthly60 minManager + senior leaderCommit accuracy, gap to target, resource decisions
QBRQuarterlyHalf dayFull commercial leadershipStrategic adjustments, capability gaps, quarter plan

Layer 1: Weekly Rep 1:1

Frequency: Every week, same slot, non-negotiable. Duration: 30 minutes. If it regularly runs over, you are doing coaching and pipeline review in the same meeting without a structure for either. Attendees: Manager and rep only.

Agenda

  1. Rep self-reports on the three deals most likely to move this week (5 min)
  2. Manager runs inspection questions on those deals (15 min)
  3. Coaching on one named skill or behaviour observed that week (8 min)
  4. Actions logged before the meeting ends (2 min)

Inspection Questions for Layer 1

  • Who is the economic buyer and when did you last speak to them directly?
  • What is the agreed next step and who owns it?
  • What has changed since we last reviewed this deal?
  • What is the specific reason this deal will close in the forecast period, not the one after?
  • What would cause this deal to slip and what have you done about that risk?
  • Is there a competitor in this deal? What do you know about their position?

What Does NOT Belong Here

Forecast numbers. Aggregate pipeline coverage. Team performance comparisons. Those belong in Layers 2 or 3. The 1:1 is deal-level and rep-specific.

Failure Mode: The 1:1 That Becomes a Status Update

Symptom: The rep talks, the manager listens, nothing changes. No challenge, no coaching, no actions. Fix: Manager speaks less than 40% of the time. Every 1:1 ends with a written action the rep owns. If the same deal appears three weeks running without movement, escalate or close it out.


Layer 2: Weekly Team Pipeline Call

Frequency: Weekly, separate from the 1:1 cycle. Duration: 45 minutes hard stop. Attendees: Full team plus manager. No senior leaders unless there is a specific deal requiring executive involvement.

Agenda

  1. Manager states the team's current forecast position versus target (5 min)
  2. Each rep names their one biggest deal risk this week and what they need to unblock it (15 min, strict time-boxing at 2-3 min per rep)
  3. Shared blockers and cross-team patterns discussed (10 min)
  4. Any deals requiring escalation flagged (5 min)
  5. Actions and owners confirmed (10 min)

Inspection Questions for Layer 2

  • What is the team's coverage ratio today and is it moving in the right direction?
  • Which deals in commit are we least confident in and why?
  • Are there blockers multiple reps share that point to a product, pricing, or process problem?
  • Which deals moved forward this week? Which stalled?
  • Do we have enough pipeline to cover the gap if our bottom-third commit deals slip?

What Does NOT Belong Here

Individual coaching. Deal-level interrogation of a single rep in front of the group. That belongs in the 1:1. The team call is about pattern recognition and collective accountability, not public performance management.

Failure Mode: The Storytelling Session

Symptom: Reps give long, narrative updates on individual deals. The meeting runs 90 minutes. The manager has not looked at the CRM before the call. Fix: Pre-read the pipeline in the CRM before the call, every week. Set a strict 2-minute cap per rep on deal updates. The call surfaces flags, it does not replace the 1:1.


Layer 3: Monthly Forecast Review

Frequency: Once per month, ideally in the first week of the month reviewing the prior month close and current month position. Duration: 60 minutes. Attendees: Sales manager plus direct reporting leader (VP, Head of Sales, or equivalent). Finance optional but useful.

Agenda

  1. Prior month actuals versus commit and versus pipeline call (10 min)
  2. Current month commit, best case, and pipeline coverage (15 min)
  3. Quarter-to-date position and projection to end of quarter (15 min)
  4. Gap analysis: what needs to happen to hit target and is it realistic? (15 min)
  5. Resource or support decisions required (5 min)

Inspection Questions for Layer 3

  • How accurate was our commit forecast last month and what drove the variance?
  • What is our pipeline coverage ratio for the current quarter at this point in time?
  • Which deals in this month's commit have not had a qualified conversation with the economic buyer in the past 14 days?
  • If our bottom 20% of commit deals slip, do we still hit target?
  • Are there systemic reasons deals are slipping (product gaps, pricing issues, contracting delays)?
  • What actions are we taking this month that will affect next quarter's pipeline?

What Does NOT Belong Here

Individual rep performance management. That belongs in 1:1s and separate performance conversations. The forecast review is about numbers and decisions, not people.

Failure Mode: The Forecast Review That Sandbaggs

Symptom: Managers consistently undercommit to protect themselves. Senior leaders adjust upward based on gut feel. Neither side trusts the numbers. Fix: Track commit accuracy over rolling three months for every manager. Name the gap between commit and actual every single month. Accurate forecasting, not optimistic forecasting, is what gets rewarded in how you run the room.


Layer 4: Quarterly Business Review (QBR)

Frequency: Once per quarter, within the first two weeks of the new quarter. Duration: Half day (3-4 hours). Full day if headcount exceeds 20 or you are including territory and hiring reviews. Attendees: Full commercial leadership team. Reps present their own sections in many formats, but the QBR is not a rep training session.

Agenda

  1. Quarter actuals: revenue, win rate, average deal size, cycle length (30 min)
  2. Pipeline entering the new quarter: coverage, quality, and distribution by rep and segment (45 min)
  3. What worked and what did not, with evidence (30 min)
  4. Capability gaps identified through the quarter's inspection (30 min)
  5. Strategic adjustments for the new quarter: territory, focus, activity targets (45 min)
  6. Commitments and owners for the quarter (30 min)

Inspection Questions for Layer 4

  • Did we hit our number? If not, was it a pipeline problem, a conversion problem, or a deal-size problem?
  • What does win rate by stage tell us about where we are losing deals?
  • Which reps have pipeline entering this quarter that is genuinely qualified versus carried over and stale?
  • What do we need to stop doing that is consuming time without producing revenue?
  • Where are our capability gaps and what will we do about them this quarter?
  • Is our ideal customer profile still accurate based on the deals we won and lost?

What Does NOT Belong Here

Deals that have not moved in 90 days. If a deal is in your QBR pipeline review and nobody has spoken to the buyer in three months, remove it before the meeting. The QBR inspects the living pipeline, not the wishlist.

Failure Mode: The QBR That Reviews Dead Deals

Symptom: 40% of the deals reviewed are stale, the meeting runs long, and nothing strategic gets decided because the room is stuck on individual opportunities. Fix: Enforce a pipeline hygiene rule before the QBR: any deal with no buyer-side activity in 60+ days is either closed lost or moved to a nurture status and removed from active pipeline before the QBR pack is built.


Deal Escalation Decision Table

Use this to decide which meeting a deal needs to appear in.

SituationEscalate To
Deal stalled for 2+ weeks with no next stepWeekly 1:1, manager coaching
Rep unable to access economic buyerWeekly 1:1 and team call if pattern is widespread
Deal in commit with no buyer contact in 14 daysMonthly forecast review, flag as at-risk
Deal requires executive sponsor or procurement supportMonthly forecast review, action assigned to leader
Deal has been in pipeline for 2+ quarters without progressingQBR, decision to close or resource differently
Systemic win rate drop below [your threshold, e.g. 25%] at a specific stageQBR, strategic agenda item

What Lives Where: Quick Reference

Topic1:1Team CallForecast ReviewQBR
Individual deal coachingYesNoNoNo
Deal risk flagsYesYesNoNo
Forecast accuracyNoYes (team level)YesYes (quarter review)
Coverage ratioNoYesYesYes
Win rate trendsNoNoNoYes
Rep performance managementYesNoNoNo
Strategic territory decisionsNoNoNoYes
Shared blockersNoYesOccasionallyNo

When NOT to Run a Formal Pipeline Review

  • When CRM data is not current. Running a review off stale data trains reps to ignore CRM hygiene. Fix the data first.
  • When the team is mid-close on a quarter-end push. Replace the team call with a brief standup. Inspection kills momentum in the last 72 hours of a quarter.
  • When the manager has not read the pipeline before the meeting. Cancelling and rescheduling is better than running an uninformed review. It signals that preparation is non-negotiable.

Get the next Sales Leadership & GTM Strategy resource by email

A short note when something new lands in Sales Leadership & GTM Strategy. We email you once to confirm first; nothing else arrives until you click it. One click to stop.

This page's topic is already selected. Add others if you like.