The Forecast Risk Diagnostic
A self-audit for CROs, RevOps leaders, and board-facing revenue teams
By Tom George, Vitelis
Why this audit exists
Most forecast misses do not start at commit. They start earlier, when a deal is allowed to stay in the pipeline with weak buyer evidence and a confident story.
This audit is for revenue leaders who need a sharper read before board reviews, CEO check-ins, or QBRs. It helps you identify which opportunities are carrying forecast risk because the underlying evidence is thin: the pain is unverified, the trigger is absent, the value case is soft, the stakeholder map is incomplete, or the next step is not real enough to support the close date.
Use it to answer a simple question: Which deals are real, which are still hypotheses, and which should be requalified now?
How to use this guide
This is a scored self-assessment that removes subjectivity in evaluating the validity of deals.
For each deal, answer the checks in the scorecard using the strongest evidence you can find in the CRM, call notes, email trail, mutual action plan, and account research. Then total the points and apply the result band.
How to read the result
- Low risk means the deal has enough buyer evidence to stay in forecast with discipline.
- Medium risk means the deal may be real, but one or two core proof points are weak.
- High risk means the deal is being carried on seller narrative more than buyer evidence.
- Remove or requalify means the opportunity should not be forecasted as-is.
Part 1: Audit dimensions
This audit measures seven dimensions that drive forecast confidence. Each dimension matters because it tells you whether the opportunity is anchored in buyer reality or just pipeline motion.
| Dimension | Why it matters | What’s being tested |
|---|---|---|
| 1. Pain verified | If the buyer has not confirmed a real problem, the deal is usually a story, not a budgetable opportunity. | Has the buyer described the issue in their words, with examples or operational impact? |
| 2. Urgency or external trigger | A deal without a reason to act now tends to slip, stall, or get reprioritized. | Did something change, break, expire, get mandated, or become visible? |
| 3. Solution fit | If the fit is generic, the deal can survive in pipeline while never becoming a decision. | Is there a credible link between the account’s problem and what you sell? |
| 4. Competition or status quo | You need to know what you are displacing, including doing nothing. | Are we up against another vendor, an internal workaround, or no action? |
| 5. Business case | If value is not quantified or at least tied to a concrete outcome, close dates float. | Can someone explain the economic logic of the deal? |
| 6. Buying committee | If the stakeholders are unclear, the deal is usually one approval away from surprise. | Do we know who matters, who is blocking, and who can say yes? |
| 7. Decision process | If the next step is vague, the forecast is based on seller optimism, not execution. | Do we know the path to signature, procurement, legal, security, or board approval if needed? |
Part 2: Scoring rubric
Score each dimension using the evidence you actually have, not the level of confidence in the seller’s story.
Scoring scale for each dimension
| Score | Evidence standard |
|---|---|
| 0 | No buyer-confirmed evidence, only seller assumption or generic discovery notes |
| 1 | Weak or indirect evidence, not yet validated by the buyer or a decision maker |
| 2 | Some evidence, but incomplete, outdated, or not tied to a specific buying reason |
| 3 | Strong evidence, confirmed by the buyer and usable in a forecast review |
Maximum score: 21 points
Questions or checks by dimension
1) Pain verified
Score based on the quality of buyer evidence, not how serious the pain sounds.
| Question / check | 0 | 1 | 2 | 3 |
|---|---|---|---|---|
| Can the buyer state the problem in their own words, with a current example? | No | Indirect | Partial | Clear and specific |
| Is the pain tied to a real operational, financial, or strategic consequence? | No | Weak | Some linkage | Confirmed consequence |
| Has the buyer acknowledged why this matters now, not just in general? | No | Vague | Some timing | Explicit timing |
Worked example
Account: Meridian Services
Stage: Commit
Amount: $240,000
The seller says the account has “strong interest” in reducing manual work. The buyer has never confirmed the cost of the current process, named the team affected, or said what breaks if nothing changes.
Score: 1
Interpretation: Pain is not verified. This should not sit in commit until the buyer can describe the problem concretely.
2) Urgency or external trigger
This dimension checks whether there is a real reason to move now.
| Question / check | 0 | 1 | 2 | 3 |
|---|---|---|---|---|
| Is there a trigger such as hiring, regulation, reorg, contract renewal, incident, budget cycle, or executive mandate? | No | Weak guess | Some evidence | Confirmed trigger |
| Does the trigger create a deadline or decision window? | No | Unclear | Soft window | Clear decision window |
| Has the buyer acknowledged the cost of delay? | No | Indirect | Partial | Explicit |
Worked example
Account: Apex Manufacturing
Stage: Proposal
Amount: $410,000
The rep has a strong demo response, but no external event explains why the deal should close this quarter. The buyer is “reviewing options,” which is not a trigger.
Score: 0 or 1
Interpretation: Without a trigger, this is often a next-quarter slip disguised as momentum.
3) Solution fit
This checks whether the opportunity matches the problem and the buying context.
| Question / check | 0 | 1 | 2 | 3 |
|---|---|---|---|---|
| Is the use case clearly within your product’s core value zone? | No | Stretch | Reasonable | Clear fit |
| Can you link the product to the buyer’s pain without a generic pitch? | No | Weak | Partial | Direct |
| Is there evidence the buyer sees the fit, not just the seller? | No | Some | Mostly | Yes |
Worked example
Account: Verity Advisory
Stage: Discovery
Amount: $95,000
The buyer likes the platform, but the rep is forcing a broad enterprise use case when the real issue is one narrow workflow. The fit is too loose.
Score: 1
Interpretation: Fit is likely overextended. Narrow the use case or remove the deal from forecast.
4) Competition or status quo
A deal is at risk if you do not know what you are displacing.
| Question / check | 0 | 1 | 2 | 3 |
|---|---|---|---|---|
| Do you know the real alternative, including doing nothing? | No | Guess | Partly known | Clear |
| Has the buyer named another vendor, internal solution, or manual process? | No | Maybe | Some evidence | Yes |
| Can you explain why your approach wins against the current state? | No | Weak | Partial | Clear |
Worked example
Account: Summit Logistics
Stage: Negotiation
Amount: $330,000
The team assumes the deal is against a competitor. In reality, the account is still trying to force an internal process to work.
Score: 1
Interpretation: If the real competitor is the status quo, the forecast should be discounted until the buyer says otherwise.
5) Business case
This dimension measures whether the deal has economic weight.
| Question / check | 0 | 1 | 2 | 3 |
|---|---|---|---|---|
| Is there quantified value, even directional, tied to the buyer’s outcome? | No | Informal | Partial | Clear |
| Can the value case survive board, finance, or procurement scrutiny? | No | Weak | Some support | Yes |
| Is the buyer using the business case to justify the deal internally? | No | Not yet | Some use | Yes |
Worked example
Account: Orion Retail
Stage: Commit
Amount: $600,000
The rep has talked about “efficiency” but has not tied the deal to headcount, revenue, risk reduction, or cycle time. Finance has no reason to prioritize it.
Score: 1
Interpretation: Weak business case is one of the most common causes of late-stage slippage.
6) Buying committee
This dimension checks whether you know who must move.
| Question / check | 0 | 1 | 2 | 3 |
|---|---|---|---|---|
| Do you know the economic buyer, champion, blockers, and likely approvers? | No | Partial | Mostly | Clear |
| Have the key stakeholders been engaged directly or through validated influence? | No | One person | Some | Multiple |
| Is there evidence of stakeholder alignment, not just access? | No | Weak | Some | Strong |
Worked example
Account: Redwood Insurance
Stage: Proposal
Amount: $275,000
The opportunity has one enthusiastic operator and no named executive sponsor. The seller assumes the chain of approval will work itself out.
Score: 1
Interpretation: Deals with unclear committees often look healthy until the final 10 days.
7) Decision process
This checks whether the path to a decision is real.
| Question / check | 0 | 1 | 2 | 3 |
|---|---|---|---|---|
| Is there a defined decision process, including steps, owners, and timing? | No | Vague | Partially defined | Clear |
| Is the next step buyer-owned and meaningful? | No | Seller-led | Some buyer input | Buyer-owned |
| Do you know what must happen before the deal can close? | No | Some idea | Mostly | Clearly mapped |
Worked example
Account: Helix Pharma
Stage: Commit
Amount: $150,000
The next step is “follow up next week.” There is no mutual action plan, no date for legal review, and no confirmation that procurement has started.
Score: 0
Interpretation: This is not a decision process. It is a calendar placeholder.
Part 3: Result bands
Total the score across all seven dimensions.
| Total score | Risk band | What it means |
|---|---|---|
| 18 to 21 | Low risk | The deal has enough buyer evidence to stay in forecast, with normal monitoring |
| 13 to 17 | Medium risk | The opportunity is plausible, but one or two proof points are thin |
| 8 to 12 | High risk | The deal is materially under-supported and should not be forecasted as clean |
| 0 to 7 | Remove or requalify | The opportunity is mostly seller narrative and should be re-scoped or removed |
Score interpretation by pattern
Total score is useful, but the pattern matters more.
- Low total with one score of 0: one missing pillar can still break the deal.
- Medium total with low buying committee and weak decision process: likely late-stage risk.
- High total with weak pain and no trigger: usually not a real opportunity, regardless of enthusiasm.
- Any deal with 0 in pain verified or decision process: treat as high risk until proven otherwise.
Part 4: Priority recommendations
Use this matrix to decide what happens next. Do not keep every deal in the same handling lane.
Priority matrix
| Risk tier | Gap | Action |
|---|---|---|
| Low risk | Minor evidence gap in one dimension | Keep in forecast, but require one strengthening action before the next review |
| Medium risk | Two dimensions are under-supported | Run a requalification meeting and close the evidence gap within 7 days |
| High risk | Pain, business case, or decision process is weak | Remove from commit, re-stage, or reset the close date |
| Remove or requalify | No verified buyer evidence | Pull out of forecast and rebuild around a real pain or alternate use case |
What to do by gap
If pain is unverified
Action: Re-open the conversation around the buyer’s language, not the seller’s pitch.
Ask: “What is breaking, costing money, or putting targets at risk right now?”
Exit criterion: The buyer states the problem in specific operational terms and confirms impact.
If there is no external trigger
Action: Look for a real event. If none exists, stop assuming urgency.
Ask: “What changed that makes this a priority this quarter?”
Exit criterion: A deadline, event, or business change is documented.
If the value case is weak
Action: Build a narrow business case tied to one measurable outcome.
Ask: “If this solves the problem, what improves, by how much, and for whom?”
Exit criterion: The deal has a credible economic or operational rationale.
If the buying committee is unclear
Action: Map who must approve, block, or influence the decision.
Ask: “Who else needs to believe this is worth doing?”
Exit criterion: The key roles are known and at least partially engaged.
If the decision process is vague
Action: Replace open-ended follow-up with a mutual plan.
Ask: “What are the steps between here and signature?”
Exit criterion: You have a buyer-owned next step, a date, and a decision path.
If the solution fit is generic
Action: Narrow the use case or move the opportunity out of forecast.
Ask: “Which specific problem does this solve better than the current approach?”
Exit criterion: The fit is specific enough to survive scrutiny.
If competition or status quo is unknown
Action: Surface the real alternative.
Ask: “What happens if you do nothing, and what are you comparing us against?”
Exit criterion: You know the actual alternative and why your path wins.
Part 5: How to use the audit in a live forecast review
Run this in your forecast meeting the same way you would run a pipeline inspection.
A practical workflow
- Pick the top 10 forecasted opportunities by amount or slip risk.
- Score each one across the seven dimensions.
- Flag any deal with: - Pain score under 2 - Decision process score under 2 - Business case score under 2
- Compare the rep’s forecast status to the audit score.
- Resolve every mismatch with one of three outcomes: - Keep - Requalify - Remove
A simple rule for board-facing confidence
If a deal cannot show buyer-confirmed pain, a real trigger, and a named decision path, it is not board-safe no matter how good the demo looked.
Close: Implementation, pitfalls, and next actions
Implementation
Use this diagnostic on the deals that matter most, not every record in the CRM. The value is in exposing false confidence early, before the number is carried into commit, board review, or quarter-end pressure.
Start with:
- Top 10 deals in forecast
- Any late-stage deal with no executive sponsor
- Any deal with a slip history
- Any opportunity that depends on one enthusiastic contact
Common pitfalls
- Confusing activity with evidence: Meetings, emails, and follow-ups are not buyer proof on their own.
- Letting stage inflate confidence: A proposal in CRM is not the same as a proposal the buyer is ready to act on.
- Treating enthusiasm as urgency: Positive sentiment does not equal a compelling event.
- Ignoring the committee: One champion is not a decision process.
- Overweighting the seller story: If the buyer has not confirmed the pain, the deal should be scored lower.
Next actions
If you want this to be usable in one sitting, turn the audit into a simple spreadsheet:
Suggested columns
- Account
- Stage
- Amount
- Close date
- Pain verified
- Urgency or trigger
- Solution fit
- Competition or status quo
- Business case
- Buying committee
- Decision process
- Total score
- Risk tier
- Action owner
- Due date
Operating rule
Any deal that lands in High risk or Remove or requalify should leave the forecast review with an owner, a due date, and one evidence requirement. If it cannot, it should not remain forecasted.