Forecasting fails at the manager level. Not at the rep level.

A rep puts a deal in commit because they are optimistic. The manager rolls it up to leadership without challenge. Leadership uses the number for capacity planning, hiring, and financial commitment. The quarter closes 35% short. The post-mortem says "the pipeline was not as strong as it appeared."

The pipeline was exactly as weak as it appeared. The manager did not look closely enough to see it.

Forecast discipline is not a CRM field. It is a management judgment process that requires the manager to override rep optimism with independent evaluation of evidence.

The five forecast categories

The manager should define and enforce five forecast categories with clear evidence requirements:

Commit. The deal has a signed or verbal agreement pending only administrative steps. There is a specific close date, a named economic buyer who has confirmed budget and timeline, a complete stakeholder map, a completed evaluation, and a known next step that is the last step before signature. Commit without evidence is optimism.

Best case. The deal has a strong champion, a clear business case, a reasonable timeline, and no identified blockers. The manager's judgment is that this deal is more likely to close than the historical average, but there is one or more open question that makes commit inappropriate. Best case without evidence is hope.

Pipeline. The deal has qualified interest, a real buyer, and a next step. But there is an open commercial, technical, or competitive question that has not been resolved. The manager cannot say with confidence when this deal will close or at what probability. Pipeline without a clear path to close is a hope inventory.

Downgrade watch. The deal has risk. A competitor is active, the timeline has slipped, the champion has changed, the business case is weak, or the technical evaluation is unresolved. The manager has identified a specific risk that is not yet a blocker. Downgrade watch means the deal is still open but needs management intervention.

Closed lost. The deal is gone. The manager requires a reason code: price, competition, timing, no budget, no champion, no decision, or not a fit. Reason codes are the only way to turn closed lost into learning.

What the manager must inspect for each deal

The manager should not take the rep's forecast category at face value. For every deal in commit and best case, the manager must independently evaluate:

Timing risk. Is the close date based on the buyer's stated timeline or the rep's need to show progress? The buyer's timeline should be supported by buyer evidence — a mutual plan, procurement date, executive commitment, or direct confirmation — not only the rep's confidence.

Value risk. Has the deal been scoped correctly? Are there expansion or contraction risks? Is the deal still at the originally quoted value or has discounting reduced it?

Stakeholder risk. Is the champion still in place? Have there been organizational changes that could affect the buying process? Is the economic buyer still engaged?

Technical risk. Has the evaluation been completed successfully? Is there an unresolved technical blocker? Is there a proof of concept that has not been completed?

Competitive risk. Is a competitor actively in the deal? Has the competitor been given an advantage in a demo, a pricing proposal, or a reference call? What is the rep's competitive positioning?

Process risk. Is the buyer's process on track? Are there procurement or legal steps that could introduce delay? Is there a budget cycle that could affect timing?

Seller execution risk. Has the rep done everything they should have done by this stage? Is there a missed call, a missing proof, a delayed follow-up that could affect the outcome?

The manager's forecast conversation

The manager should run a structured forecast conversation with each rep weekly, not in the last hour before the forecast call.

The conversation structure:

  • For each deal in commit: what is the one thing that could prevent this deal from closing on the committed date? What is your plan if that happens?
  • For each deal in best case: what is the one question that, if answered favorably, would allow you to move this to commit? What is the evidence that question will be answered in your favor?
  • For each deal in pipeline: what needs to happen in the next two weeks to move this deal forward? Who needs to do it?
  • For each deal in downgrade watch: what is the specific intervention required? Who should do it? When?
  • For each deal closed lost: what is the reason code? What did we learn? What would we do differently?

Downgrade discipline

The most important management skill in forecasting is downgrade discipline.

Most managers wait too long to downgrade. They wait until the deal shows a clear problem before moving it. But a good manager downgrades when the risk is identified, not when the outcome is certain.

The downgrade trigger: if the manager can identify a specific risk that the rep cannot fully mitigate, the deal should be moved to a lower category, even if the rep disagrees. The manager's judgment overrides rep optimism when the evidence does not support the optimistic category.

This is not being pessimistic. It is being accurate. A manager who downgrades a deal that subsequently closes does no harm. A manager who holds an optimistic commit that misses costs the company real planning capacity.

The test: would you be comfortable presenting this forecast to your CFO as the basis for a hiring decision? If not, the forecast is too optimistic.

The forecast call as a management tool

The forecast call is not a reporting meeting. It is a management decision meeting.

The manager should come to the forecast call with two things: a revised forecast that reflects management judgment, and a specific action plan for every deal in downgrade watch. The forecast call should produce two outputs: an updated number, and a list of interventions with owners and dates.

If the forecast call is only a number update, the manager is using it as a reporting ritual, not a management tool.

The artifact: manager forecast inspection model

For each deal in commit and best case, complete this before the forecast call:

Deal name and rep:

Committed value:

Committed close date:

Stage:

Evidence for commit: (What specific buyer evidence exists?)

One thing that could prevent close: (Specific, not vague.)

Rep's current confidence: (1-5)

Manager's independent confidence: (1-5)

Gap analysis: (If manager confidence is lower, why?)

Intervention required: (What must change? Who does it? By when?)

Recommended forecast category: (Based on evidence, not optimism.)