Require Evidence Before a Pipeline Stage Changes

Replace adjectives with events. "Solution fit confirmed" is not observable. "Buyer confirmed the integration works in their sandbox and named the technical approver" is. The second version tells a reviewer what to look for and tells the representative what to complete.

Write the criteria with the sales team, not for them. Representatives will follow a rule they helped design, especially when the rule removes ambiguity about when to ask for the next commitment. The criteria should be demanding enough to mean something and simple enough to remember.

Keep one page per stage. Each page should list the entry criteria, the exit criteria, the evidence object, the approver, and the common exception. If the criteria need a flowchart, they are too complicated for daily use.

Evidence must be a thing, not a feeling. A signed order form, a security review completion notice, a mutual action plan with dates, a recorded technical validation, or a written confirmation from the buyer all qualify. A note that says "buyer is excited" does not.

Attach the evidence to the opportunity as a link or a document, not as a description. A reviewer should be able to open the object and compare it with the stage claim. If the evidence lives in an email, save it to the opportunity record so it survives the representative's inbox.

Not every deal needs the same evidence. A small transactional deal may close on a written confirmation, while an enterprise deal needs the security review and the signed order. Define the evidence by segment rather than applying the enterprise standard to every sale.

Deals move backward, and that is healthy when it reflects new information. The problem is the silent backward move that happens during a forecast call to avoid a hard conversation. Make regression a visible event with a reason and an approver.

Require a reason code for every backward move: budget lost, champion left, requirements changed, timeline slipped, or competitive loss. The reason should be recorded in the stage history, not just discussed on the call. Patterns in regression reasons are one of the best sources of product and qualification feedback.

Decide who can move a deal backward. The representative can usually request it, while the sales manager approves it above a value threshold. The approval should not be so heavy that people avoid the correct action, but it should leave a trace.

The stage history should capture the previous stage, the new stage, the timestamp, the actor, the reason, and the evidence link. Store it as an append-only record. The current stage is a field; the history is the explanation.

This is the same discipline that makes the pipeline stage evidence rules usable in daily work. The NIST Cybersecurity Framework 2.0 frames governance and risk as continuous activities, and pipeline governance follows the same logic: the record of decisions matters as much as the decision.

Include the forecast category in the history when it changes with the stage. A deal that moves from pipeline to best case without new evidence is a forecast change disguised as a stage change. Separating the two makes the review honest.

A close date that moves three times is telling you something. Track the number of close date changes, the total days moved, and the reason. Do not allow a stage change to reset the close date history.

Set a threshold for review. Two changes may be normal in a complex deal. Five changes usually means the buyer has not committed to a date, or the representative is avoiding a loss. The review should ask what event will cause the deal to close, not why the date moved.

Keep the original close date and the current close date visible. The difference is a useful measure of forecast quality, and it is much harder to argue with than a narrative about pipeline health.

Pull a sample of deals that changed stage last month and check the evidence. Twenty deals across representatives is enough to see whether the standard is being followed. For each deal, open the evidence object and confirm it supports the stage claim.

Record the result as pass, missing evidence, or evidence does not support the stage. Share the aggregate with the team and the examples without attribution. The point is to improve the standard, not to catch individuals.

If one transition fails repeatedly, the criterion is probably unclear or the evidence is too hard to obtain. Fix the criterion before adding another reminder. A stage gate that everyone works around is worse than no gate, because it creates false confidence.

Sales support can prepare the evidence pack, check completeness, and route exceptions. It should not decide the forecast category, approve a discount, or confirm that a buyer has authority. Those are commercial judgments with accountable owners.

Write the boundary into the role description. The support specialist may say "the evidence for this stage is missing" and return the deal. The sales manager decides whether the stage stands. This separation protects both the specialist and the forecast.

When the forecast category and the stage evidence disagree, book a free consultation before the next review. Review the boundary whenever a new stage or forecast category is introduced. Administrative convenience has a way of expanding into decisions that belong to sales leadership.