Back to all articlesLoss analysis

Set Dormant Review Dates Around Buyer Events, Not Arbitrary Intervals

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A dormant opportunity reaches its review date. Nothing has changed on the buyer’s side, so the owner moves the date forward again. The record looks maintained, but the team still cannot explain what would make the opportunity worth reconsidering.

Set the review around the condition that could restore the buyer’s ability to decide: budget becoming available, a project restarting, or a funding decision being made. Where no reliable event exists, use a bounded uncertainty review with an explicit decision at the end. Do not substitute another arbitrary interval for missing evidence.

The practical distinction is simple: the event explains why a review is useful; the date tells the team when to inspect the evidence. Neither the arrival of the date nor the occurrence of the event automatically makes the opportunity active.

1. Start with the blocker, not the next available date

Before choosing a review date, write one sentence explaining why the buyer cannot currently advance the decision. Make it specific enough that another person could recognise whether the situation has changed.

In a hypothetical opportunity, “budget issue” is too broad. “The department cannot commit spend until its approved allocation is released” describes a testable condition. Likewise, “project delayed” leaves too much ambiguity; “the implementation project is suspended until the buyer assigns a replacement project lead” identifies what must change.

Useful dormant sales opportunity review criteria answer four questions:

  • Blocker: What currently prevents the decision from progressing?
  • Change condition: What observable change could remove that blocker?
  • Evidence: What would establish that the change actually happened?
  • Disposition: What will the owner decide if the condition remains unmet?

If the blocker is only the seller’s interpretation, label it as an inference. A buyer-confirmed constraint and an internal guess should not carry the same weight when selecting a review date.

This is a status-review method, not an outreach schedule. A review may consist of assessing evidence already held. It does not necessarily require a new message, meeting, or reactivation attempt.

2. Separate a buyer event from a calendar assumption

A useful event must be relevant to this decision. A new quarter, a company announcement, or a general planning season is not sufficient on its own. The event matters only if it could change the specific constraint recorded against the opportunity.

Consider a hypothetical buyer whose budget becomes available at the start of a financial period. The calendar boundary may be relevant, but it is not proof that this purchase has funding. The stronger review condition is confirmation that the relevant allocation has been released and remains available for the project.

Use three tests before treating an event as the basis for a review:

  1. Causal relevance: Would the event materially change the buyer’s ability to consider this purchase?
  2. Identifiable evidence: Could the owner distinguish occurrence from rumour or expectation?
  3. Timing confidence: Is there a credible date or window, and is its source recorded?

An event can pass the first two tests without passing the third. Funding approval may clearly matter while its timing remains unknown. That is a reason to use an uncertainty review, not to invent an approval date.

Also distinguish a necessary condition from a sufficient one. A project restart may remove one blocker while procurement capacity or decision ownership remains unresolved. Record those remaining dependencies rather than treating the headline event as permission to restore active status.

3. Give every review an event condition and a fallback

A date-only record loses the reasoning behind the review. An event-only record can remain dormant indefinitely because nobody knows when to assess it. Pair the two.

For an event with credible timing, set the review for when evidence should reasonably be available—not automatically on the event’s expected start date. If an internal buyer decision is expected during a stated week, a review after that window may be more useful than one on its opening day. Any allowance for evidence availability is a planning assumption, not a promised response time.

For uncertain timing, set a bounded review horizon chosen by the team. Its purpose is to decide whether retaining the opportunity as dormant remains justified. It is not a prediction that the buyer will be ready by then.

Each record should contain a primary owner and a default decision if the expected event does not occur. The default might be closure under the team’s status definitions, or a single extension supported by new evidence. “Move the date forward” is not a complete default decision.

Keep this information in an opportunity record or a shared worksheet. The method does not depend on a particular CRM control. The important requirement is that the next reviewer can reconstruct why the date was chosen.

4. Filled worksheet: four fictional dormant opportunities

Fictional worked example: All organisations, evidence summaries, dates, roles and decision rules below are hypothetical. The worksheet is assumed to have been prepared on 4 March 2027. Its review horizons illustrate choices, not recommended universal intervals.

Opportunity A: budget release

  • Recorded blocker: The buyer has an approved departmental allocation but cannot commit it until finance releases the funds.
  • Evidence held: A buyer finance contact confirmed the approval and an expected release on 1 April 2027. The release itself has not been confirmed.
  • Review condition: Evidence that the allocation has been released and still covers this project.
  • Review date: 6 April 2027, allowing time after the expected release for evidence to become available.
  • Owner: Account owner; sales manager decides any exception to the fallback.
  • Decision at review: If release is confirmed, reassess remaining blockers and whether a current decision process exists. Do not reactivate on the calendar date alone.
  • If the event does not occur: Retain dormant status only if there is a revised, buyer-supported release date and the project remains funded. Without that evidence, close under the team’s unfunded or deferred reason.

Opportunity B: project restart

  • Recorded blocker: The buyer suspended implementation planning while appointing a new project lead.
  • Evidence held: The sponsor identified a planned restart meeting for 19 April 2027 and said the incoming lead would determine the revised scope.
  • Review condition: Confirmation that the meeting occurred, a lead accepted ownership, and the project received a current remit.
  • Review date: 22 April 2027.
  • Owner: Opportunity owner; account lead reviews any material scope change.
  • Decision at review: Assess whether the original opportunity still represents the buyer’s project. Requalify changed scope rather than restoring the old assumptions.
  • If the event does not occur: Permit one revised review only if a replacement meeting and responsible project lead are identified. If the project remains suspended without either, close as deferred or cancelled under local definitions.

Opportunity C: unresolved funding

  • Recorded blocker: The project depends on additional funding that has not been approved.
  • Evidence held: The sponsor confirmed that a funding request exists but could not identify a decision date or a scheduled decision forum.
  • Review condition: Evidence of a funding decision, or a credible decision milestone with an accountable buyer-side owner.
  • Review date: 31 March 2027, an uncertainty boundary rather than a forecast approval date.
  • Owner: Opportunity owner; sales manager approves any evidence-based extension.
  • Decision at review: If funding is approved, reassess the purchase decision. If it is rejected, close as unfunded.
  • If uncertainty remains: Close as funding unresolved unless new evidence establishes a specific decision milestone. A repeated statement that funding is being pursued is not enough to reset the date.

Opportunity D: unspecified pause

  • Recorded blocker: The buyer requested a pause without explaining what would allow the decision to resume.
  • Evidence held: A buyer message confirms the pause. There is no supported budget, staffing, timing, or project-restart explanation.
  • Review condition: A credible reason to retain the opportunity: an identified blocker, a relevant change condition, and evidence that the project still exists.
  • Review date: 18 March 2027, a short uncertainty boundary selected for this hypothetical case.
  • Owner: Opportunity owner.
  • Decision at review: Replace the unspecified pause with an evidence-based condition if one becomes available.
  • If no explanation emerges: Close as paused with timing unknown. Do not relabel the pause as a budget problem or invent a future restart date.

The final two entries deliberately lack a reliable buyer-event date. Their dates govern the seller’s decision about continued dormant status; they do not describe when the buyer is expected to resume.

5. Use the review to choose a disposition, not renew the hold

At the review, compare the recorded condition with the evidence now available. Keep the result distinct from the event itself.

  • Condition met, decision process viable: Reconsider active status using the team’s qualification requirements.
  • Condition met, another blocker remains: Record that blocker and assess whether a new dormant condition is justified.
  • Event moved, credible new evidence exists: Revise the condition and date, preserving the original expectation and reason for the change.
  • Event failed or uncertainty persists: Apply the recorded fallback instead of silently extending the hold.

Closure here means the record no longer merits dormant opportunity status under the team’s rules. It need not mean that future interest is impossible. A later material change can support a fresh assessment without pretending that the old opportunity remained decision-ready throughout the pause.

Preserve the original blocker when adding a new one. Otherwise, a sequence of changing explanations can make a repeatedly stalled opportunity appear to have one continuous, well-understood delay.

6. Handle weak signals and missed events explicitly

The main trade-off is between waiting for useful evidence and allowing uncertainty to persist indefinitely. Requiring perfect certainty can lead to premature closure. Accepting every hopeful signal can make dormant status permanent.

Separate occurrence from expectation. A hypothetical sponsor’s statement that a restart is likely is evidence of an expectation, not evidence that the project restarted. A hypothetical public funding announcement may concern the organisation without establishing an allocation for this purchase.

If a review date passes without a completed assessment, mark the review as overdue. Do not move the date simply to clear the overdue state. Record the assessment when it happens and retain the missed date so the team can distinguish review discipline from buyer delay.

If a buyer changes the expected event date repeatedly, ask what new evidence supports each revision. A date change alone is not necessarily a stronger basis for retaining the opportunity. Where owners disagree, have the designated decision-maker apply the recorded fallback or document a specific exception.

7. Test the method on a bounded set of records

Start with a small batch rather than redesigning every dormant record at once. As a hypothetical pilot, a manager could select ten opportunities with the nearest review dates and rewrite them using the worksheet fields above.

For each record, capture whether it has a specific blocker, an evidence-backed event or explicit uncertainty boundary, an accountable owner, and a decision if nothing changes. Count completed fields before and after the exercise. These are checks on review quality, not measures of likely sales success.

At the next review cycle, count how many completed reviews produced an explicit disposition and how many were extended without new evidence. Inspect the latter individually: the problem may be a vague condition, an unsupported timing assumption, or reluctance to apply the fallback.

The immediate next action: take the next dormant opportunity due for review and finish this sentence: “We will reconsider dormant status when this condition is evidenced; if it remains unverified by this date, this owner will make this decision.” If the sentence cannot be completed honestly, use a bounded uncertainty review rather than another arbitrary interval.

Sales operationsDormant opportunitiesPipeline managementOpportunity reviews

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