Define the exact event that makes an opportunity closed won
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
One seller marks an opportunity won after a buyer says yes. Another waits for a signed order. A third waits for payment. The resulting report combines different commercial events under one stage name. A change in reported wins may reflect seller habits rather than a change in business.
Define closed won as the point when the required commercial commitment is complete, supporting evidence is available, and no designated sales-blocking condition remains unresolved. Then name the exact event for each approved sales motion. Individual sellers should not choose their own endpoint.
The practical test is whether two reviewers can use the same records to reach the same decision and completion date. The filled table and calibration exercise below turn that test into an operating practice. This defines a sales pipeline endpoint, not revenue recognition, contract interpretation, invoicing procedures, or delivery handoffs.
1. Choose an observable completion event
Confidence and completion answer different questions. A seller may be certain that a buyer will sign, while the required signature remains missing. Conversely, a completed order should not stay open merely because the seller worries about implementation.
Start with a sentence that makes the decision explicit:
For this sales motion, an opportunity becomes closed won when [observable event] occurs, supported by [required evidence], with [designated blockers] resolved.
Possible events include completion of an order document, valid seller acceptance of a purchase order, or receipt of a required initial payment. None is universally correct. Choose the event that represents completion of selling for the particular motion.
Test your choice against three questions:
- Can another person verify it? A dated record supports review; an undocumented recollection does not.
- Does it establish commercial completion? A scheduled kickoff is observable but may not establish the required commitment.
- Does it produce a repeatable decision? Phrases such as “substantially agreed” leave each seller to set a threshold.
If the event requires approval or acceptance, identify whose approval counts and what record establishes it. Otherwise, the definition simply replaces one ambiguous stage name with another.
2. Separate evidence, blockers, and later milestones
Evidence establishes what happened. It might be the completed order, a purchase order with a valid acceptance record, or confirmation of qualifying payment receipt. A stage-change comment saying “all agreed” does not replace the required evidence.
A blocker is an unfinished requirement that prevents commercial completion. Examples might include outstanding buyer approval, unresolved scope, or required seller acceptance. Name the specific condition and the evidence needed to resolve it. “Everything finished” is too broad to apply consistently.
A later milestone follows completion of selling. Kickoff, provisioning, training, and first use should not become hidden won criteria. If an acceptance step genuinely determines commercial completion, explicitly include it in the relevant motion rather than making all delivery activity a blocker.
Internal acceptance needs particular care. A decision about whether the seller accepts an order may belong in the closing rule. A downstream team's acknowledgment that it received the work generally serves a different purpose.
There is a trade-off: closing at order completion leaves later cancellations or payment failures to be tracked separately. Requiring payment can be appropriate for a prepaid motion, but adding that requirement to every sale changes the endpoint. Choose deliberately rather than moving the boundary to improve a reporting period.
3. Use a filled won-definition decision table
The table below is a reusable starting artifact. Replace its motion names, evidence requirements, and decision roles with your own approved choices before using it.
Hypothetical filled decision table: This fictional supplier uses signed-order, approved purchase-order, and prepaid motions. These are recommended operating choices, not Alactic customer results or claims about product controls.
| Sales motion or situation | Decision | Required evidence | Closing event | Blocker |
|---|---|---|---|---|
| Verbal commitment | Keep open. | Record the commitment and outstanding commercial step; neither establishes a win. | The qualifying event for the assigned signed-order, purchase-order, or prepaid motion. | The required order, acceptance, or payment event has not occurred. |
| Standard signed order | Close won when all requirements are complete. | Completed order document and dated confirmation that designated conditions are resolved. | The later of the final required signature and final designated blocker resolution. | Missing required signature or unresolved commercial condition. |
| Conditional signature | Keep open while the stated budget approval is outstanding. | Signed order, recorded condition, and dated confirmation of its resolution. | The later of the final required signature and final designated blocker resolution, as for the standard signed-order motion. | Outstanding budget approval or another designated condition. |
| Approved purchase-order motion | Close won only on valid seller acceptance after all required checks and designated blockers are cleared. | Motion eligibility, purchase order, scope and amount checks, blocker clearance, and dated acceptance by the designated reviewer. | Valid seller acceptance after every required check and designated blocker is complete. Premature acceptance does not qualify; record fresh acceptance after clearance. | Unapproved purchasing route, mismatch, unresolved condition, or missing valid acceptance. |
| Prepaid motion | Close won when order, payment, and blocker requirements are complete. | Completed order, authorized confirmation of qualifying payment receipt, and blocker-clearance evidence. | The latest of order completion, qualifying payment receipt, and final designated blocker resolution. | Missing order, missing qualifying payment, or unresolved condition. |
| Unresolved conditions in any motion | Keep open; separately assess whether the opportunity remains active. | Named condition, owner, and required resolution evidence. | Apply the assigned motion's rule after resolution. For purchase orders, obtain valid acceptance after all checks and blockers clear; premature acceptance must be recorded afresh. | The named condition remains unresolved. Another completion signal does not override it. |
The purchase-order rule deliberately requires acceptance after clearance, rather than using the later of an early acceptance and blocker resolution. Resolving a condition does not automatically validate an earlier acceptance.
The rows are intentionally asymmetric. Payment is essential for the prepaid motion but not the standard signed-order motion. That difference is workable when it is predefined and visible, rather than negotiated at reporting time.
4. Walk a borderline opportunity through the rule
Fictional worked example: An opportunity is assigned to the approved purchase-order motion. On Monday, the buyer's purchase order arrives. Its amount matches, but its scope includes an unresolved additional service. A seller records acceptance on Tuesday. The designated reviewer confirms the corrected scope on Wednesday and records fresh acceptance on Thursday.
Apply the table in sequence:
- Identify the motion. The approved purchase-order route applies, so receipt alone cannot close the opportunity.
- Check the evidence. Monday's document has an unresolved scope condition.
- Reject the premature event. Tuesday's acceptance occurred before clearance and does not qualify.
- Locate the qualifying event. Wednesday clears the blocker; Thursday supplies valid acceptance after clearance.
- Record the date. Thursday is the commercial completion date, even if the CRM update happens Friday.
A reusable completion record for this hypothetical case would read:
- Opportunity: Fictional supplier order P-17.
- Motion and rule: Approved purchase order; rule version Pilot A.
- Evidence: Corrected purchase order, scope-and-amount check, Wednesday clearance record, Thursday acceptance record.
- Blocker status: Additional-service scope resolved Wednesday; no other designated blockers outstanding.
- Qualifying event: Designated reviewer acceptance on Thursday, after clearance.
- Administrative update: Friday.
- Decision note: Tuesday acceptance excluded because it preceded required clearance.
This record explains the outcome without relying on the seller's confidence or requiring a reviewer to reconstruct the entire conversation.
5. Limit exceptions and preserve event dates
One rule for every opportunity can obscure genuinely different buying routes. Unlimited exceptions create the opposite problem: sellers can find a route to their preferred result.
For each permitted motion, document eligibility, required evidence, closing event, blockers, and the role authorized to confirm eligibility. Receiving a document labelled “purchase order” does not by itself establish eligibility for that motion.
Send an unfamiliar case to the designated decision owner. A reporting deadline, seller seniority, or opportunity size should not substitute for completion evidence. If an unusual case recurs, evaluate a defined motion instead of accumulating private exceptions.
Keep the event date distinct from the administrative entry date. For a signed order without blockers, use the final required signature date. For a conditional signed order, use the later qualifying date. For purchase orders under the table above, use valid acceptance after clearance.
If evidence cannot establish the date precisely, flag the uncertainty and apply an approved dating convention; do not invent a timestamp. Record the motion, rule version, evidence reference, decision owner, and any approved exception. These are recommended information requirements, not claims about available CRM fields or validation features.
6. Correct errors without hiding later changes
An opportunity incorrectly marked won differs from one that qualified and later suffered a cancellation or payment failure.
For an incorrect win, correct the stage and preserve the reason. Identify the missing requirement, restore the appropriate status, and retain enough history to explain the reporting change. An early stage update cannot serve as evidence that the event occurred.
For a later adverse event, preserve the original qualifying event and record what changed. Define how management reporting will show the subsequent outcome instead of silently rewriting the earlier decision. This keeps closing-discipline problems distinguishable from business changes after valid completion.
Review repeated corrections for patterns. Disputes about whether an approval is commercial or administrative suggest an unclear rule. Repeatedly missing documents suggest an evidence-availability problem. Those problems require different fixes.
7. Calibrate with independent decisions
Before routine adoption, have a seller and an operations reviewer independently classify the same recent records using the proposed rule and available evidence. Ask each to record won or not won, the applicable motion, the completion date if any, and the missing requirement if still open.
Hypothetical calibration exercise: In a fictional ten-record pilot, reviewers agree on eight stage decisions. One disagreement concerns premature purchase-order acceptance; the other concerns an unclear budget condition. They also choose different completion dates for one otherwise agreed win.
The pilot owner clarifies acceptance sequencing, defines the evidence that clears budget approval, and adds the event-date rule to the worksheet. Reviewers then reassess the disputed records independently and classify additional examples of the affected motions.
Track three observable outcomes:
- Decision agreement: Matching won-or-not-won classifications.
- Evidence completeness: Proposed wins containing all required evidence.
- Date agreement: Matching completion dates for records both reviewers classify as won.
Keep disagreements visible rather than resolving them through informal persuasion. Record which phrase, condition, or missing evidence produced each difference. A shared answer reached only after hearing the seller's explanation may still indicate an unusable written rule.
8. Approve a version, not an assumption
The pilot owner should explicitly approve the rule version, its effective date, and the sales motions covered. Approval should reference the decision table, evidence requirements, dating convention, and correction procedure.
Document any remaining ambiguous cases with an owner and the decision still needed. Withhold unresolved sales motions from routine application until their criteria are settled. Route affected opportunities through documented review rather than allowing sellers to improvise or treating ambiguity as evidence of a win.
A small pilot can reveal defects; it does not prove that a definition will handle every future opportunity. Revisit the rule when new purchasing routes or recurring disputes appear, and preserve version history so reviewers know which standard governed a decision.
Next action: Complete the definition sentence for your default motion, adapt the table, and assign a pilot owner. Ask independent reviewers to classify records before making that version the reporting standard.
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