Pipeline Review Prep: What Your Assistant Should Have Ready

A good pipeline review takes an hour and changes what the team does this week. A bad one takes two hours and changes nothing. The difference is usually preparation. When the data is clean and the exceptions are surfaced in advance, the meeting can focus on the deals that need attention. This is the prep checklist we use.

48 hours before: data hygiene

Run the weekly CRM hygiene checklist first. In particular:

• Past-due close dates updated or deals closed out
• Every open deal has a future-dated next step
• Stages reflect exit criteria
• Amounts and products populated
• Activity from the past week logged

Send reps a short list of their records that need attention, with a deadline.

24 hours before: build the pack

1. Pipeline summary

• Total pipeline by stage and close month
• Week-over-week changes: new, advanced, pushed, won, lost
• Coverage ratio against the period's target (pipeline ÷ remaining quota), if your team tracks it

2. Forecast view

• Commit, best case and pipeline categories by rep
• Changes in forecast category since last week
• Gap to target

3. Exceptions list

The most valuable page in the pack. Flag:

• Deals pushed more than once in 30 days
• Deals with no activity in 14+ days
• Large deals with no economic buyer identified
• Deals in late stages without a mutual plan or next meeting
• Amount changes greater than an agreed threshold

4. Deal briefs for top opportunities

For the five to ten largest or most important deals:

• Stage, amount, close date and history of pushes
• Last three activities
• Key contacts and their roles
• Open risks and next steps
• Link to the CRM record

Meeting day: logistics

• Agenda sent, with the pack linked
• Video link and recording settings confirmed
• Notes template ready
• Time-boxed agenda: summary (10 min), exceptions (25 min), top deals (20 min), actions (5 min)

After the meeting: follow-through

• Notes and action items distributed within two hours
• Action items assigned owners and due dates
• CRM updated with any changes agreed in the meeting
• Next week's exceptions list pre-seeded with open items

Who does what

The split matters. Reps should spend time on facts only they know. Everything else should be prepared for them.

Report templates that save time

Build three saved reports once:

1. Pipeline by stage and close month
2. Week-over-week changes (using historical trending or snapshots)
3. Exceptions (filters for each exception rule)

Both Salesforce and HubSpot support saved reports and dashboards that make this a refresh rather than a rebuild.

Measuring whether prep is working

• Meeting length trending down
• Fewer "let me check and get back to you" moments
• Forecast accuracy improving over time against actual results
• Actions completed by the next meeting

Track these informally at first; the trend is what matters.

Common mistakes

1. Prepping the night before. Reps need time to update records.
2. Too many slides. One summary, one exceptions list, a handful of deal briefs.
3. Re-reviewing every deal. Focus on exceptions and top deals.
4. No follow-through. Actions without owners and dates don't happen.

A worked example: the Friday-to-Monday prep cycle

For a sales team that holds pipeline review on Monday at 10 a.m., here is how an assistant might run the prep. The leader's own time drops to about 20 minutes of reading.

The one-page team summary

Coverage is a common planning number. Many teams aim for roughly three times remaining quota, but the right ratio depends on your historical win rate, so calculate yours from the last four quarters.

Questions the leader should be able to ask, with answers in the pack

• Which deals over a set size (say $25,000) changed close date this week, and why?
• Which commit deals have no meeting scheduled in the next 10 days?
• Which deals have a single contact and no economic buyer identified?
• What did we lose last week, and what reason was logged?

If the pack answers these before the meeting, the meeting becomes coaching rather than data gathering.

Checklist: definitions to agree on before you start

• What each stage means, with entry criteria a rep can check
• What "commit" means at your company (for example, verbal yes plus agreed paperwork timeline)
• Required fields per stage: amount, close date, next step, next-step date, decision maker
• How weighted pipeline is calculated (stage probability or forecast category)
• Who can change a deal's forecast category

Without shared definitions, the assistant's report is only as consistent as the most optimistic rep.

Running the meeting itself

A prepared pack changes what the meeting can be. A simple 45-minute agenda for a team of six to eight reps:

1. Five minutes: the numbers. The leader walks through the team summary. No deal discussion yet.
2. Twenty-five minutes: the deals that matter. Three to five deals flagged in advance. For each one: what changed, what's the next step, what help is needed.
3. Ten minutes: risks and slips. Every deal that pushed its close date gets one sentence.
4. Five minutes: actions. The assistant reads back the actions captured, with owners and dates.

Keep rep-by-rep walkthroughs for one-on-ones. When the whole team listens to every deal, attention fades and the review turns into reporting rather than decisions.

Keeping a history

Ask the assistant to keep the weekly snapshots in one sheet, one tab per week. After a quarter you'll have the data to measure slippage rates, stage conversion and forecast accuracy. Those are hard to rebuild after the fact, and they make next quarter's forecast more honest.

The bottom line

Pipeline reviews improve dramatically with a 48-hour prep routine: hygiene first, then a concise pack with an exceptions list and deal briefs, then disciplined follow-through. It's a few hours of work a week — and it's work an assistant can own.

See ExecWing Revenue & Sales Assistants and the SaaS industry page.

Sources

• Salesforce Help and HubSpot Knowledge Base for reporting features.