Set an Expiry Rule for Opportunity Probabilities
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
An opportunity can retain a high probability even after the decision date has passed and the person supporting that estimate has left the buying process. The percentage still looks precise, but its justification no longer describes the deal.
Update a stale sales forecast probability when a material supporting assumption expires, is contradicted, or can no longer be verified—not simply because the opportunity is older. Review the evidence first. Then retain the estimate with a renewed justification, revise it to reflect changed conditions, or move it out of the main forecast until it is supportable.
The practical control is an expiry rule attached to the estimate: what evidence supports it, when that evidence needs review, which events invalidate it, and who decides what happens next. The filled hypothetical checklist below shows how to apply that rule without turning elapsed time into an automatic penalty.
1. Make the probability claim explicit
Before setting an expiry rule, establish what the percentage means. A probability of winning eventually is not the same as a probability of closing within the forecast period. A delayed purchase can remain plausible while becoming unlikely to contribute to this period's revenue.
For this workflow, define the working estimate as the probability of a closed-won outcome within the named forecast period. If your organisation uses a different definition, record it explicitly and assess timing separately. Do not silently switch definitions during a review.
A usable probability statement includes:
- The outcome and period: what must happen, and by when.
- The supporting buyer evidence: a dated confirmation or observable purchasing step.
- The material assumptions: conditions that must remain true for the estimate to hold.
- The next review trigger: a date or event that requires reassessment.
Stage labels alone do not supply this justification. An opportunity can remain in the same sales stage while its budget, authority, or purchasing timetable changes. Likewise, a recent seller note does not make old buyer evidence fresh.
2. Expire the justification, not the opportunity
An expiry rule should stop an unsupported probability from carrying forward unexamined. It should not automatically declare the opportunity lost.
Use this operating rule: when a material assumption reaches its review date or is invalidated by an event, the estimate requires a new decision before it can be treated as current. A review may preserve the percentage, but only with an updated rationale.
Set the review point around the evidence's expected life. A decision-date confirmation should be reviewed when that date passes without the expected outcome. A confirmation about requirements may remain useful longer, provided nothing material has changed. Approval tied to a named sponsor needs review if that sponsor leaves or loses authority.
Elapsed time matters because it can weaken the relevance of evidence. It does not reveal the size of the probability change by itself. A scheduled purchasing pause supported by an authorised buyer is different from an unexplained delay. Applying the same reduction to both would conceal that difference.
A periodic backstop review can catch assumptions that have no obvious event trigger. Treat that interval as a local operating choice, not a universal decay curve. Reaching it prompts examination; it does not prescribe a percentage reduction.
3. Separate invalidation from missing information
Evidence can become unusable in several ways, and each calls for a different response.
- Contradicted: the buyer confirms that funding is no longer available. The old funding assumption is invalid, so retaining the estimate requires a different justification.
- Overtaken: the confirmed decision date passes without a decision. The old schedule no longer supports a close in the original period, even if purchase intent remains.
- Disconnected from authority: the contact who described the approval path is no longer involved. Their earlier statement may remain historically accurate, but it does not establish who can approve now.
- Unverified: no current information establishes whether the assumption still holds. This is uncertainty, not proof of rejection.
- Reconfirmed: a buyer with relevant responsibility supplies new evidence that supports the assumption. This can renew the justification, but only for what that person actually confirmed.
The distinction prevents two mistakes: treating silence as a definite loss and treating the absence of bad news as continued support for a high probability. Neither is a sound substitute for current evidence.
4. Filled hypothetical probability-expiry checklist
Fictional worked example: all names, dates, amounts, and percentages in this example are hypothetical. The percentages illustrate review decisions; they are not calibrated recommendations or customer results.
Harbour Supply has an opportunity valued at £60,000. Its recorded probability was 80% for a close by 30 September. The estimate relied on a buyer-confirmed decision date of 12 September, an operations sponsor coordinating approval, unchanged requirements, and an expected purchasing review. The forecast review takes place on 18 September.
Estimate being reviewed
- Claim: 80% probability of closing by 30 September.
- Last supporting evidence: the operations sponsor's confirmation on 3 September that approval was expected on 12 September.
- Review owner: opportunity owner, with the forecast manager deciding forecast inclusion.
- Expiry rule: review when the decision date passes without approval, the sponsor's role changes, or the purchasing route changes.
Check A: Has the decision date elapsed?
- Finding: yes. The 12 September decision date passed without approval.
- What expires: the schedule supporting the original September estimate.
- What does not follow: that the buyer has rejected the purchase.
- Action: mark the original timing justification as expired. Do not preserve 80% by moving the close date alone.
Check B: Is the buyer contact still present and authoritative?
- Finding: the operations sponsor is on leave and will not participate for the remainder of September. No replacement sponsor has been confirmed.
- What expires: the assumption that this sponsor can coordinate the remaining approval steps during the period.
- What remains unknown: who now owns business approval and whether that person supports the purchase.
- Action: treat approval ownership as unresolved. An internal account-team belief that someone else will take over is not replacement buyer evidence.
Check C: Are the requirements unchanged?
- Finding: on 17 September, the buyer's technical evaluator confirmed that the agreed scope and requirements remain unchanged.
- What remains supported: the proposed solution still addresses the stated requirements.
- What this does not establish: budget authority, business approval, or a September purchase date.
- Action: retain this evidence as current, without using it to renew unrelated assumptions.
Check D: Is there newly confirmed purchasing evidence?
- Finding: on 18 September, the procurement lead confirmed receipt of the revised quotation, identified the remaining approval steps, and stated that the earliest purchasing review would be 7 October. Funding still requires business-owner approval.
- What improves: the purchasing route is now clearer and supported by a responsible buyer participant.
- What changes: the stated route no longer supports the original September close.
- Action: use the new evidence to reassess an October estimate, not to rescue the September percentage.
Recorded decision
Remove the opportunity from the September main forecast. Keep it open with the prior 80% retained in the change history, not presented as a current estimate. Record the next-period estimate as pending review because business approval ownership and funding remain unresolved.
Reassess when the responsible business approver is confirmed, with a backstop review on 8 October if no earlier material event occurs. Record both the renewed purchasing evidence and the unresolved approval conditions so the next reviewer does not mistake progress for completion.
5. Choose between retaining, downgrading, and excluding
The checklist should lead to a decision, not just a stale flag. Use three distinct outcomes.
Retain with renewed justification when fresh evidence supports the original outcome and period. For example, in a hypothetical variation, an authorised replacement approver confirms that approval is complete and the remaining purchase step still fits within September. Retaining the estimate may be reasonable, but the record needs the new basis and next expiry trigger.
Downgrade when the outcome remains assessable but the evidence is weaker. In another hypothetical variation, the replacement approver supports the purchase but adds a funding review before a still-feasible September close. A team might revise 80% to 55% under its own documented probability bands. That number is illustrative; it should not become a default penalty for a delay.
Exclude from the main forecast when the period is no longer supported or material unknowns make a numeric estimate misleading. Preserve visibility in a separate pending-review or scenario view. Exclusion is a forecasting treatment, not a lost-opportunity declaration.
If reporting requires a numeric field, agree how unresolved estimates will be represented and excluded from the main calculation. Do not use a zero that readers could mistake for a confirmed loss, or retain an old high value where it will still be counted.
6. Keep positive evidence within its proper scope
New evidence is not automatically strong evidence for every forecast assumption. A technical confirmation can renew confidence in fit without saying anything about purchasing authority. Procurement activity can establish a process without establishing that funding is approved.
For each new fact, ask: which specific uncertainty does this resolve? Then update that part of the rationale. In the worked example, the procurement lead's confirmation improves understanding of the buying route while weakening the September timing case. Both effects belong in the same review.
This approach also avoids excessive pessimism. If the buyer confirms an unchanged scope and a credible later purchasing step, retain those facts. Do not erase valid evidence merely because another assumption failed. The estimate should reflect the combination of supported and unresolved conditions.
7. Prevent expiry reviews from becoming cosmetic updates
The most common failure is to refresh the record without refreshing its basis. Changing the review date, editing a note, or shifting the close date can make a record look current while leaving the same unsupported probability in place.
- Require a decision reason: identify the evidence that changed, remained valid, or is missing.
- Preserve the previous claim: retain the old probability, period, and rationale in the review history rather than overwriting the reasoning.
- Name the unresolved condition: avoid vague statuses such as waiting on buyer when the actual issue is unconfirmed budget authority.
- Assign an inclusion decision: someone must decide whether the estimate belongs in the main forecast while review is pending.
There is a trade-off. Very short review intervals create administrative work without necessarily improving evidence. Very long intervals allow unsupported assumptions to persist. Start with event-based triggers for material assumptions, then use a backstop interval where events are difficult to observe.
If a stale estimate has already carried through several forecast cycles, recover by reviewing its current basis—not by inventing a retrospective sequence of percentage reductions. Record the gap, make the present inclusion decision, and establish a new expiry rule.
8. Test the rule in the next forecast review
Use a small, explicitly defined sample before extending the process. A hypothetical pilot could review ten high-probability opportunities whose decision dates have passed or whose approval contacts have changed.
- Write the outcome and forecast period behind each percentage.
- Identify the material supporting evidence and its date.
- Mark each assumption as current, contradicted, expired, or unverified.
- Choose retain, downgrade, or exclude, with a named decision owner.
- Record the next event trigger and backstop review date.
Measure how many sampled estimates have a documented current basis before and after the review, how many lack a period-specific purchasing path, and how many pending-review estimates still enter the main forecast. These are observable checks on the process, not proof that forecast accuracy has improved.
The immediate target is straightforward: every reviewed probability should have a defensible basis, a clear inclusion decision, and an explicit point at which its assumptions must be examined again.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications