Clear exit criteria turn pipeline stages into measurable systems
Set exit criteria as the observable events that must happen before a deal leaves a pipeline stage.
Key takeaways for how to set exit criteria for sales pipeline stages
- Stage definition: Without exit criteria, stages become fuzz, and reps move deals based on instinct, turning your pipeline into a list of vibes rather than a measurable system, according to Close.
- Activity threshold: Any active deal with no logged calls, emails, or meetings in 14 days is being neglected, as defined in Designing your sales pipeline.
- Field requirement: If any stage has required columns, you must fill in the columns on those stages before you save the form or move to a new stage, from Business process flows overview.
- Stage count: Below 3 stages, you lose the ability to track meaningful progress, reported by Close.
- Time tracking: Stage calculated properties show the amount of time records spend in each stage of a pipeline, published by HubSpot.
According to Close, your sales pipeline is the structure that turns qualified leads into closed deals. Without exit criteria, stages become fuzz; reps move deals based on instinct, and your pipeline becomes a list of vibes rather than a measurable system. This lack of definition prevents managers from standardizing how deals move through stages to ensure accurate coaching and forecasting.
A deal advances to the next stage when specific, observable things have happened, as reported by Close. These observable markers create a measurable system for both reps and managers. When progress is defined by observable events rather than intuition, the pipeline reflects actual deal health.
Opportunity Statuses describe each stage a pending deal can go through within a specific Pipeline, according to Close. By defining these statuses clearly, you establish the structural rules that govern deal movement.
To build this measurable system, replace vague stage descriptions with concrete, observable progress markers. This approach ensures that every deal in your pipeline has met the same structural requirements, allowing for consistent coaching and accurate forecasting.
A filled reference table of stage rules by publisher
The table below lists the 5 structural and behavioral checks for standardizing pipeline stages. Each row names the publisher that documents the specific rule or configuration limit. Use this reference to verify your current setup against documented behaviors before adjusting your team’s workflow.
| Publisher | Stage Rule | Specific Constraint or Behavior | Source Document |
|---|---|---|---|
| Close | Neglect detection | Any active deal with no logged calls, emails, or meetings in 14 days is being neglected. | Close |
| Microsoft | Mandatory fields | If any stage, including the current stage, has required columns (except hidden columns), you must fill in the columns on those stages before you save the form or move to a new stage. | Microsoft |
| Close | Stage count limits | Below 3, you lose the ability to track meaningful progress. | Close |
| HubSpot | Time tracking | Stage calculated properties for contacts, companies, deals, tickets, services, projects, leads, and custom objects show the amount of time these records spend in each stage of a pipeline. | HubSpot |
| HubSpot | Stagnation filters | Create a saved view to identify deals that have spent more than two weeks in a given stage. | HubSpot |
Defining observable progress markers for each stage
Replace instinct-based deal movement with specific, observable events that must occur before a deal advances. This rule shifts stage progression from subjective judgment to verifiable actions. When a manager cannot point to a concrete event that triggered a stage change, the pipeline lacks measurable structure. Observable markers create a consistent standard for reps and managers alike, ensuring that every deal moves forward for the same documented reasons.
To implement this, identify the exact event that defines the completion of each current stage. For example, if a stage represents initial contact, the observable marker might be a logged call or a sent proposal. If a stage represents negotiation, the marker might be a signed term sheet or a scheduled legal review. These markers must be visible in your CRM record, not just in a rep’s memory. The stage description serves as the baseline for what the stage represents. Your exit criteria must align with this description. If the stage description says "Qualified," the observable marker must prove qualification, such as a confirmed budget or a named decision-maker.
Avoid vague markers like "good relationship" or "interested." These terms are not observable. An observable marker is a binary state: it either happened or it did not. Ask yourself: can I see this event in the activity log or the deal record? If the answer is no, the marker is not observable. Use the stage description as your anchor. Ensure that your chosen observable marker directly supports that description. If the description is "Proposal Sent," the marker is the timestamp of the proposal email. If the description is "Negotiation," the marker is the date of the first negotiation call.
Weekly stage reviews can follow Deal stage progress: 7 checks for weekly coaching.
Setting activity and time-based hygiene rules
Pipeline hygiene depends on tracking whether reps actively work deals or let them sit idle. You can identify neglected opportunities by monitoring logged activity and time spent in each stage. Close defines neglect specifically: any active deal with no logged calls, emails, or meetings in 14 days is being neglected, as reported by Close. This rule gives you a clear, observable threshold to flag deals that have stalled due to inactivity.
HubSpot provides tools to measure how long records remain in specific pipeline stages. According to HubSpot, stage calculated properties for contacts, companies, deals, tickets, services, projects, leads, and custom objects show the amount of time these records spend in each stage of a pipeline. These properties allow you to quantify stagnation objectively rather than relying on subjective estimates.
To act on this data, HubSpot suggests creating a saved view to identify deals that have spent more than two weeks in a given stage, as reported by HubSpot. This saved view serves as a practical filter to surface deals that exceed your defined time limit. By combining Close’s activity-based neglect definition with HubSpot’s time-tracking capabilities, you can build a two-part hygiene check: first, verify recent contact attempts, and second, confirm the deal has not exceeded a reasonable duration in its current stage.
Stalled deals can also be sorted with Track 8 lead filter checks for stalled deal reviews.
When implementing these rules, focus on consistency. Ensure your team logs all calls, emails, and meetings so the 14-day neglect metric remains accurate. Simultaneously, configure your CRM to track stage duration so you can generate the saved view for stalled deals. This approach shifts pipeline management from intuition to data-driven oversight. If a deal triggers either the activity neglect flag or the time-in-stage alert, review it immediately to determine if it requires escalation, re-engagement, or closure.
Configuring mandatory fields and workflow triggers
Standardizing how deals move requires enforcing data completeness and automating transitions. You can configure these controls using the rules documented in the Business process flows overview - Power Automate | Microsoft Learn guide.
Mandatory field enforcement Microsoft states that if any stage, including the current stage, has required columns (except hidden columns), you must fill in the columns on those stages before you save the form or move to a new stage Microsoft. This rule applies to the specific product configuration described in that source. It does not apply universally to every CRM platform or every business model. When you set up your pipeline, identify which columns are critical for a stage to be considered "complete." For example, if a "Proposal Sent" stage requires a "Proposal Date" and a "Buyer Contact" field, the system will block the deal from advancing until those specific fields are populated. This prevents reps from moving deals forward with incomplete data, which often leads to inaccurate forecasting.
Workflow trigger setup To automate actions when a deal moves, Microsoft describes a specific configuration where S1 connects to S2, with a workflow on stage S2 and sets the trigger to Stage Exit Microsoft. This trigger type is specific to the platform documented in the source. Not all CRM systems support a "Stage Exit" trigger in the same way. You should verify your specific platform's capabilities before assuming this exact configuration is available.
Practical application When configuring your pipeline, map out which stages require specific data and which stages should trigger automated workflows. For instance, you might require a "Competitor Identified" field before a deal can move from "Qualification" to "Discovery." You might also set a workflow to trigger when a deal exits "Discovery," automatically sending a notification to your sales operations team. These settings turn your pipeline stages into measurable systems by ensuring that every deal has the necessary data and that key events are captured automatically.
Reviewing stage counts and pipeline scope limits
When defining your pipeline structure, the number of stages you create directly impacts your ability to monitor deal health. You must balance the need for granular tracking against the risk of creating a process that is too complex to manage effectively.
Close states that if a pipeline has fewer than three stages, you lose the ability to track meaningful progress. According to Close, this lower bound is necessary to maintain visibility into where deals stand. If your current setup has only two stages, such as "Open" and "Closed," you cannot distinguish between early discovery and late-stage negotiation. This lack of granularity prevents you from identifying which specific phase is causing delays. You should review your current stage count to ensure it meets this minimum threshold for effective tracking.
Managers who coach from stage rules can also read Sales call library: Coaching rules from 5 publishers.
Freshsales states there is no upper limit on the number of stages in a pipeline. While you are not technically restricted by the software, adding stages without a clear purpose can clutter your view. Each additional stage requires its own set of exit criteria and coaching focus. If you add a stage, you must be prepared to define exactly what observable event moves a deal into it and out of it.
Illustrative example of applying the checks
A small team runs 1 pipeline with 4 stages. The first deal has no logged call, email, or meeting for 14 days, so the team treats it as neglected and reviews it today. The second deal has stayed in 1 stage long enough to appear on a saved view of stalled deals. The team will not advance either deal until the required fields on that stage are filled. They keep at least 3 stages so early conversations and late talks stay separate. For each stage they name 1 observable event, such as a logged meeting, and they confirm that event in the record before the deal moves. These round figures show how the checks work together on a normal afternoon.
Action step: Open your CRM and set up a saved view that flags deals with no logged activity in 14 days or deals that have remained in their current stage for more than two weeks.
FAQ: how to set exit criteria for sales pipeline stages
What makes a pipeline stage definition vague?
According to Close, without exit criteria, stages become fuzz.
How can I identify deals that are being neglected in a stage?
Reported by Close, any active deal with no logged calls, emails, or meetings in 14 days is being neglected. You can identify these stalled opportunities by checking activity logs for this specific gap. This rule helps you spot deals that have lost momentum in the current stage.
Do I need to fill in specific columns before moving a deal to a new stage?
Published by Microsoft, if any stage, including the current stage, has required columns, you must fill in the columns on those stages before you save the form or move to a new stage. Hidden columns are the exception to this requirement. This enforces data completeness before the deal advances.
Can I have an unlimited number of stages in a single pipeline?
Yes, stage count can keep rising, so add a stage only when you can name the observable event that moves a deal in and out.
How do stage calculated properties help with coaching?
Reported by HubSpot, stage calculated properties for contacts, companies, deals, tickets, services, projects, leads, and custom objects show the amount of time these records spend in each stage of a pipeline. Use this data to coach reps on time management and stage progression.