🚀 Early Access: FREE full access to All Workflows and AI Prompt Systems! No credit card required.
Revenue leaders, RevOps teams, Sales directors, Sales operations managers, Finance partners
Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.
1. Copy the Workflow Prompt.
2. Paste it into your AI tool.
3. Replace the "Required Inputs"
4. Run the prompt.
Get access to this workflow and 1000+ others designed to save hours and get better results with AI.
You are a revenue operations consultant. Your task is to audit the accuracy and reliability of a sales revenue forecast.
### Required Input
- Forecast Period: [Example: "Q2 2026 monthly forecast"]
- Forecast Target: [Committed, best case, and target values if available]
- Actual Revenue Results: [Historical actuals compared with forecast. Example: "Forecast $900k, actual $720k"]
- Forecast Categories: [Example: "Commit, best case, pipeline, omitted"]
- Pipeline Data: [Opportunity value, stage, close date, owner, next step, age, and forecast category]
- Sales Process Stages: [Current stage names and qualification criteria]
- Historical Win Rates: [By stage, segment, source, or rep if available]
- Forecast Review Process: [How often forecast is reviewed and by whom]
- Known Issues: [Example: "Close dates move often, reps overcommit"]
- Business Context: [Seasonality, major launches, pricing changes, territory changes, or hiring changes]
### Input Validation
Review every required input before producing the final output. If anything is missing, unclear, contradictory, or too vague, ask specific clarification questions. Pause and wait for answers.
### Instructions
Separate forecast process issues from pipeline quality issues. Look for structural causes such as unclear stage definitions, weak exit criteria, stale opportunities, inconsistent forecast categories, unrealistic close dates, or missing inspection discipline.
Compare forecasts against actuals when historical data is provided. Identify over-forecasting, under-forecasting, or unpredictable variance. Explain what pattern the data suggests and what may be causing it.
Review whether each forecast category has clear evidence requirements. Assess whether commit and best case deals show buyer intent, next steps, stakeholder engagement, timeline, and commercial alignment.
Inspect stage weighting logic. If stage probabilities are used, check whether they reflect real conversion behaviour or CRM defaults. Highlight stages where conversion assumptions may inflate forecast confidence.
Analyse rep and manager behaviour. Look for common warning signs such as sandbagging, optimism bias, end-of-quarter pushes, close date recycling, low activity on commit deals, and large deals carrying too much forecast weight.
Turn the audit into process changes, CRM field improvements, forecast questions, manager routines, and reporting fixes.
### Output
Use this structure:
1. Forecast Accuracy Summary
- Forecast period reviewed
- Current reliability rating
- Main accuracy problem
- Expected business impact
2. Forecast Variance Review
Compare forecast versus actuals and identify patterns in overstatement, understatement, timing slippage, and segment variance.
3. Forecast Methodology Assessment
Evaluate categories, stage probabilities, close date discipline, inspection cadence, and ownership.
4. Pipeline Quality Findings
Identify stale opportunities, weak next steps, risky close dates, stage mismatch, deal concentration, and unsupported commit deals.
5. Rep and Manager Behaviour Signals
List observed behaviours, what they suggest, and how leadership should address them.
6. Forecast Risk Register
For each risk include evidence, severity, likely impact, and recommended control.
7. Forecast Improvement Roadmap
Create near-term, next-cycle, and long-term actions to improve reliability.
Include a forecast meeting agenda managers can use to inspect the riskiest deals.
An analysis of historical performance reveals a clear pattern of chronic overstatement and timing slippage:
Our audit of the current forecasting framework highlights major architectural vulnerabilities across four core components:
Reps currently assign categories like “Commit” and “Best Case” based on personal gut feel. There are no mandatory evidence requirements. A deal is routinely marked as “Commit” simply because the rep has a “good relationship” with the logistics manager, even if the corporate IT security team hasn’t yet received the technical gateway documentation.
The CRM uses rigid, out-of-the-box static percentages (e.g., Stage 2 = 50%, Stage 3 = 75%) to calculate weighted pipeline value. These probabilities do not reflect actual historical conversion trends. Our data shows that Stage 2 (Technical Demo) actually converts to won at only 22% due to feature-dumping friction. The current system drastically inflates mathematically weighted forecast expectations.
There is a complete absence of close date integrity. 60% of open opportunities feature close dates set to the final business day of the current month. This indicates that reps are treating the close date field as a loose administrative placeholder rather than a realistic, buyer-validated timeline.
Forecast reviews are currently run as passive “read-alouds” during weekly sales meetings. Frontline managers review deal lists line-by-line, asking reps for verbal status updates rather than deeply inspecting call intelligence data, talk-time metrics, or objective qualification fields.
A deep-dive data scrub of the active pipeline reveals severe data decay and underlying execution risks:
| Observed Behavior Pattern | What It Suggests (Root Cause) | Required Leadership Intervention |
|---|---|---|
| Close Date Recycling | Reps are kicking stagnant deals down the road by changing the month-end date without re-running active discovery. | Lock CRM editing fields for close dates that have been modified more than three times without director-level approval. |
| Sandbagging / Pipeline Hoarding | Reps intentionally hold back qualified early-stage deals from the CRM until late in the quarter to avoid manager inspection. | Audit cross-referencing call intelligence records against CRM opportunity creation dates to ensure transparency. |
| Manager Passivity | Frontline managers accept verbal rep assurances (“The buyer says we are looking good”) without checking for data alignment. | Mandate that managers verify that a Cost-of-Delay Ledger has been delivered before approving a deal for “Commit” status. |
Get access to all workflows, across every sector, with structured systems built for better results.