Tag: forecast accuracy

  • Forecast Categories Explained: Commit, Best Case, Pipeline

    Forecast categories are labels your CRM uses to sort open deals by how confident a rep is that each one will close in a given period. The five standard labels (used by Salesforce and mirrored by most other CRMs) are Pipeline, Best Case, Commit, Closed, and Omitted. They’re related to the deal’s sales stage, but they aren’t the same thing.

    If you’ve ever opened a forecast report and seen a deal sitting in “Qualification” stage but tagged as “Commit,” you’ve probably wondered what’s going on. That’s not necessarily a bug. Stage and forecast category measure two different things, and mixing them up is one of the most common reasons forecasts go sideways.

    This post breaks down what each category means, how they roll up into a number leadership actually trusts, and how to set definitions your whole team can agree on.

    What is a forecast category, exactly?

    A forecast category is a classification tag attached to an opportunity that signals how likely the rep thinks it is to close within the current forecast period, usually a month or a quarter. Salesforce, which popularized this model, uses categories to group opportunities by confidence of closing. Most other CRMs, including HubSpot, use some version of the same idea, though the labels can differ slightly, so check your own naming.

    Here’s the distinction that trips up most new reps and managers. A pipeline stage (like “Proposal Sent” or “Negotiation”) describes where a deal sits in your sales process. A forecast category describes how sure you are it will close on time.

    The two are connected, though. In Salesforce, each stage maps to a default forecast category, and that mapping drives how opportunities roll up into a rep’s or manager’s forecast. Admins can also allow users to override the category on a deal. So a deal in a late stage can still be tagged Pipeline if the rep isn’t confident, and a deal in an early stage can be tagged Best Case if the rep has unusually strong conviction. The override is where judgment enters the forecast, which is also where most of the trouble starts.

    Stage (example) Default category (example)
    Discovery Pipeline
    Qualification Pipeline
    Demo Best Case
    Proposal Best Case
    Negotiation Commit
    Closed Won Closed
    Closed Lost Omitted

    That mapping is an illustration, not a recommendation. Yours will differ. One useful check: make sure every active stage maps to a category, because an unmapped stage defaults to Pipeline, which can quietly understate late-stage deals.

    What does each category mean?

    Pipeline is the broadest, lowest-confidence category. These are opportunities that are actively being worked but haven’t earned a stronger label yet. They might close this period, next period, or not at all. In most CRM configurations, every new opportunity starts here by default. Think of it as the “still in progress, don’t bank on it yet” bucket. It’s useful for understanding total potential revenue, but it typically gets excluded from the number you’d present as a committed forecast.

    Best Case sits one notch up. These are opportunities with real interest and a plausible path to closing this period, but still some risk. It’s also the category most prone to inflation, and that tracks with what most RevOps teams will tell you: it requires less evidence than Commit and feels better to report than Pipeline, so reps lean on it. Writing down what specifically disqualifies a deal from Commit keeps Best Case from becoming a dumping ground for hopeful deals.

    Commit is the rep’s public promise. These are opportunities the rep is telling their manager, in effect, “this one is closing this period, you can count on it.” In cumulative rollups, the Commit total usually becomes the floor that leadership plans around, because it includes Commit plus anything already Closed. Commit is better understood as an accountability signal than a probability estimate, which is exactly why it needs the strictest bar of any category.

    Closed covers deals already won in the period. There’s no projection involved. It’s the booked outcome. In the standard setup, Closed means Closed Won only.

    Omitted covers opportunities excluded from the forecast. That’s typically where Closed Lost deals land, along with deals that are on hold, stalled, or pushed to a future period. Some Salesforce orgs also enable an optional “Most Likely” category between Commit and Best Case, so check whether yours does before you compare numbers across teams.

    Define categories by evidence, not by percentage

    Different reps calibrate confidence differently, so one rep’s 80% might be another’s 55%. Defining a category by required evidence makes the label mean the same thing no matter who fills it in. Here’s an illustrative starting point:

    Category Example evidence required Example disqualifiers
    Pipeline Qualified need and an identified contact None, this is the default
    Best Case Confirmed need, budget discussed, a proposed timeline, a next meeting booked No buyer contact in the last two weeks; no identified approver
    Commit A mutual close plan, confirmed budget, known approvals and signers, and a dated next step Dependency on an unconfirmed event; legal or procurement not yet engaged

    Pro tip: don’t let a close date inside the quarter be the only reason a deal reaches Commit. The date is a hope. The evidence is what turns it into a commitment.

    How do forecast categories roll up into a number?

    Most CRMs let you view totals by category in two ways. A single rollup shows only the deals in each category. A cumulative rollup shows each category plus everything more certain than it. Here’s an illustrative example with made-up numbers:

    Category Single rollup Cumulative rollup
    Closed $400K $400K
    Commit $600K $1.0M (Commit + Closed)
    Best Case $1.1M $2.1M (Best Case + Commit + Closed)
    Pipeline $2.3M Open pipeline: $4.0M (Pipeline + Best Case + Commit)

    Leadership can compare a conservative scenario (Commit, cumulative) against an optimistic one (Best Case, cumulative). Definitions of “open pipeline” vary, with some setups excluding Closed and some including it, so check which version your report uses before you compare numbers across teams or periods. A cumulative total and a single-category total can look very different for the same pipeline.

    Weighted pipeline is a related but different idea: instead of sorting deals into buckets, it multiplies each deal’s value by a probability to produce a blended number. Teams often use both, and it’s worth understanding how weighted pipeline works alongside forecast categories.

    Check whether the labels are earning their meaning

    A label is only useful if it predicts something. One simple measure compares your Day One Commit forecast with what actually closed by the end of the period. If you started the quarter with $1.0M in cumulative Commit and $900K closed, that’s a 10% miss. Track it every quarter, along with how often Commit deals closed and how often Best Case deals closed. Here’s an illustrative history:

    Quarter Commit deals that closed Best Case deals that closed
    Q1 85% 35%
    Q2 71% 40%
    Q3 64% 28%

    A declining Commit close rate like the one above suggests the definition is loosening, not that reps got worse at selling. Tighten the evidence requirements before you coach individuals. Decide on a target close rate for each category and review the numbers in your forecast meeting.

    Warning signs in your categories

    • A Commit total that sits on a thin Best Case and shallow pipeline. A healthy-looking Commit with little behind it is a fragile forecast.
    • Deals jumping from Pipeline straight to Commit. That’s worth a second look in review.
    • A growing Omitted bucket. It can mean deals are slipping or qualification is breaking down.
    • Pipeline padded with stale deals whose close dates keep sliding forward each month.
    • Overrides nobody explains. If categories change without a note, the label stops carrying information.

    Five questions for a Commit review

    1. What has the buyer actually done in the last seven days?
    2. Who signs, and have we spoken to them?
    3. Is budget confirmed, and by whom?
    4. What is the next step, and when is it scheduled?
    5. What could still stop this deal from closing this period?

    If a rep can’t answer three of these, the deal probably belongs in Best Case. These questions draw on the same logic as qualification frameworks like BANT and MEDDIC, and a poorly qualified deal will fool even the best category definitions.

    A simple checklist for defining your own categories

    1. Write a one-sentence definition for each category your team uses (Pipeline, Best Case, and Commit at minimum).
    2. List the specific, observable evidence required to qualify for each one. Avoid relying on probability percentages alone.
    3. List disqualifying conditions, especially for Best Case and Commit (stale buyer contact, no confirmed budget, dependency on an unconfirmed event).
    4. Map every active stage to a default category, and decide whether reps may override it.
    5. Decide whether your forecast rollup will be cumulative or single-category, and make sure everyone reading the report knows which.
    6. Review quarterly how often Commit deals and Best Case deals actually closed. If the numbers are way off from what the labels imply, your definitions need tightening, not your reps.

    If you’re still getting oriented on forecasting basics, our beginner’s guide to sales forecasting is a good place to start.

    Summary

    Forecast categories sort open deals by how confident a rep is that each will close in the current period. The five standard categories are Pipeline (early and uncertain), Best Case (real interest with some risk), Commit (the rep’s public promise), Closed (won deals), and Omitted (excluded, usually including lost deals). They differ from sales stage, which describes where a deal sits in the process, although in many CRMs each stage maps to a default category that reps may or may not be allowed to override.

    Define each category by observable evidence rather than a probability, check whether your rollup is single or cumulative, and track how often Commit and Best Case deals actually close. When Commit close rates slip, tighten the definition before coaching individuals. Watch for deals jumping straight to Commit, a growing Omitted bucket, and unexplained overrides.

    FAQ

    Is a forecast category the same as a sales stage?

    No. Stage tracks where a deal sits in your sales process. Forecast category tracks how confident the rep is that it will close on time. They often correlate, since stages map to default categories, but they’re separate fields and shouldn’t be treated as interchangeable.

    What are the five standard forecast categories?

    Pipeline, Best Case, Commit, Closed, and Omitted. These are the standard categories Salesforce ships with, and most other CRMs use a similar structure even if some of the naming differs.

    Where do lost deals go?

    Typically into Omitted. Closed usually means Closed Won only, so lost deals are removed from the forecast by mapping Closed Lost to Omitted.

    Can a deal skip categories, like jumping straight from Pipeline to Commit?

    Technically yes, if overrides are allowed. Whether that’s a good idea is a different question. A deal that jumps straight to Commit without passing through Best Case is usually worth a second look in your forecast review.

    Why does Best Case get inflated so often?

    Because it requires less evidence than Commit but still feels more credible to report than plain Pipeline. Tight, written disqualification criteria are the best fix we’ve seen for this.

    Do I need all five categories, or can I use fewer?

    Some teams run a functional forecast with just Pipeline, Best Case, Commit, and Omitted, treating Closed separately since it’s an outcome rather than a projection. What matters more than the count is that every rep and manager applies the same definition consistently.

    Do forecast categories replace probability weighting?

    Not necessarily. Categories group deals by confidence, while weighted pipeline multiplies each deal’s value by a probability. Many teams use both, using categories for the call and weighting as a cross-check.

    Who should own the category definitions?

    Usually sales leadership and RevOps together. Sales owns the judgment about what evidence is meaningful, and RevOps owns the configuration, the stage mapping, and the tracking that shows whether the labels are working.

  • What Is Deal Slippage? Causes and How to Prevent It

    Deal slippage is when a sales opportunity that was forecasted to close in a specific period (say, this quarter) doesn’t close on time and gets pushed to a later date. The deal isn’t dead. It’s still open. But it’s no longer where your forecast said it would be, and that gap is where revenue predictability goes to die.

    If you’ve ever walked into a quarterly business review with a pipeline that looked great on paper, only to watch half your “committed” deals quietly move to next quarter, you already know this problem. It’s one of the most common and most avoidable issues in sales pipeline management, yet most teams don’t even track it as its own metric.

    What is deal slippage, exactly?

    Deal slippage describes opportunities that were forecasted to close within a specific time period but fail to do so and get pushed into a future date. It’s different from a lost deal. A lost deal is closed and gone. A slipped deal is still alive, still in your pipeline, just not where you said it would be.

    This matters because slipped deals quietly distort your numbers. Unlike lost deals, slipped deals remain in the pipeline but introduce uncertainty in revenue forecasting and pipeline accuracy. You can have a pipeline that looks perfectly healthy in total dollar value while hiding a forecast that’s falling apart underneath.

    Slippage shows up most in B2B sales, where long sales cycles, multiple stakeholders, and complex approvals often delay decision-making. If you’re selling into mid-market or enterprise accounts with procurement, legal, and multiple approvers, some slippage is just part of the territory. The question is how much, and whether it’s getting worse.

    Why slippage hurts more than a single missed date

    It’s tempting to treat a slipped deal as a minor scheduling issue, since the deal is technically still alive. The damage shows up in three places at once. First, your forecast for the current period just lost revenue it was counting on, which means someone has to explain the gap to leadership. Second, next period’s forecast just inherited a deal it didn’t plan for, which can crowd out new pipeline that would have closed on its own schedule. Third, the deal itself is now less likely to close at all, because the momentum that existed when the close date was set has already started to fade.

    That third point is the one teams underestimate most. A slipped deal doesn’t sit frozen in time waiting patiently for the buyer. Priorities shift, champions change roles, budgets get reallocated, and a competitor gets a second look. Every week a deal drifts past its original date is another week for something to change that wasn’t in your forecast.

    How do you measure a deal slippage rate?

    You calculate it with a simple formula: divide the number (or value) of slipped deals by the total number (or value) of deals forecasted to close in that period, then multiply by 100. For example, if your team forecasts 40 deals to close in Q3 and 12 of them push to Q4, your slippage rate for that quarter is 30%.

    There’s no single universal benchmark, since the right number depends on your industry, deal size, and typical sales cycle length. That said, most high-performing sales organizations target a slippage rate below 20% on committed pipeline, and rates consistently above 30% usually point to deeper problems with qualification, forecast discipline, or rep coaching rather than a few unlucky deals.

    Worth noting: slippage has been trending the wrong way across the industry. Deal slippage has nearly doubled in recent years, rising from 12% to 22%, largely driven by more stakeholders like CFOs and procurement officers getting involved later in the deal cycle. More separate research found win rates plummet by 113% once deals extend beyond two months past their expected close, which tells you slippage isn’t a neutral delay. It actively kills deals the longer it drags on.

    Measure it both ways if you can, by deal count and by deal value. Count-based slippage tells you how reliable your reps’ close dates are in general, while value-based slippage tells you whether the biggest deals are the ones slipping, which usually matters more for the forecast. A team can look fine on count and still be in trouble if the three largest deals of the quarter are the ones that moved.

    Why does deal slippage happen?

    Slippage usually isn’t one big dramatic event. It’s a handful of small gaps that compound. The most common causes include:

    • No compelling event. A large share of slipping deals lack a clear reason for the buyer to act now, so there’s nothing forcing a decision by any particular date.
    • Weak qualification. Reps pursue opportunities without confirming real budget, timeline, or fit, so the “close date” in the CRM was more of a guess than a commitment.
    • Missing stakeholder engagement. If the economic buyer or final approver hasn’t been identified and looped in, the deal stalls in internal review.
    • Reactive selling. Some reps wait for the buyer to drive the process instead of proactively pushing it forward, and momentum just evaporates.
    • Stale CRM data. Sometimes a deal already slipped weeks ago in reality, but nobody updated the close date, so it looks like a surprise in this week’s pipeline review when it’s actually old news.

    Honestly, most slippage I’ve seen traced back to qualification, not closing skill. Reps get excited about pipeline volume and let deals sit in the forecast that never should have been there in the first place. Low-performing reps are 217% more likely to experience slippage than top performers, which tells you this is a coachable, process problem rather than bad luck.

    What are the early warning signs of a deal about to slip?

    Because most pipeline reporting looks backward, by the time a close date moves, the warning signs have usually been visible for weeks. A few patterns are worth building into your weekly deal review:

    • No next meeting on the calendar. A late-stage deal with no scheduled next step is drifting, whatever the CRM stage says.
    • Single-threaded contact. If the rep only talks to one person at the account, any delay on that person’s side stalls the whole deal.
    • Legal or procurement not yet involved. A deal forecast to close in three weeks that hasn’t touched contracts or procurement is almost certainly going to slip.
    • Vague language from the rep. Phrases like “they’re just busy” or “should be soon” usually mean the rep doesn’t have a specific buyer action to point to.
    • Close date already moved once. A deal that has slipped before is statistically more likely to slip again than one that hasn’t.

    None of these signs prove a deal will slip, but each one is a reason to ask a direct question during review rather than accepting the close date at face value.

    How do you prevent deal slippage?

    You can’t eliminate slippage entirely, especially in longer enterprise cycles, but you can catch it early and shrink it. Here’s a practical sequence:

    1. Define a real close date, not a wish date. A close date should be tied to a specific buyer action (contract signed, PO issued), not just “end of quarter” because that’s when your fiscal period ends.
    2. Require a compelling event before a deal enters forecast. If the rep can’t name why the buyer needs to act by that date, it shouldn’t count as committed.
    3. Map the full buying committee early. Identify the economic buyer, legal, procurement, and any other approver before the deal reaches late stage, not after it stalls there.
    4. Track slippage rate as its own metric, by rep and by stage. Don’t bury it inside win rate. A rep with a great win rate but high slippage is still a forecasting risk.
    5. Review stalled deals weekly, not just at quarter-end. Deals that sit too long in one stage usually show warning signs (no next meeting booked, no recent activity) well before the close date actually moves.
    6. Keep CRM close dates current. Make updating a close date part of the deal review ritual, not an afterthought reps do only when asked.

    Pro tip: if a deal has pushed its close date more than once, stop trusting the new date at face value. Ask the rep to walk through the actual next buyer action and who owns it. If they can’t answer specifically, that deal probably needs to come out of your committed forecast entirely.

    Getting this right connects directly to [TODO LINK: How to accurately forecast revenue] your overall forecasting accuracy. If you’re still fuzzy on how forecasting and pipeline fit together, it helps to start with sales forecasting basics, and if you’re not sure how pipeline differs from a funnel in the first place, our post on sales pipeline vs. sales funnel breaks that down. Understanding your weighted pipeline also helps, since slipped deals often inflate weighted totals long after they should have been discounted.

    At Revlyn, we see this come up constantly in RevOps conversations: teams have plenty of pipeline data but no clean way to separate “deal is genuinely progressing” from “deal is just sitting there waiting to slip.” Fixing that distinction is usually a bigger forecast-accuracy win than adding more top-of-funnel volume.

    Summary

    Deal slippage happens when a deal forecasted to close in one period moves to a later one without being lost. It distorts forecasts, crowds the next period’s pipeline, and lowers the odds the deal ever closes, since momentum fades with every week past the original date. The slippage rate is simple to calculate: slipped deals divided by deals forecasted to close in the period. Many strong teams aim for under 20% on committed pipeline, while consistently above 30% usually signals a qualification or forecast-discipline problem.

    Most slippage traces back to a short list of causes: no compelling event, weak qualification, missing stakeholders, reactive selling, and stale CRM data. Prevention comes down to setting close dates tied to real buyer actions, requiring a compelling event before a deal enters the forecast, mapping the buying committee early, tracking slippage as its own metric, reviewing stalled deals weekly, and keeping close dates current. A deal that has already slipped once should never be trusted at its new date without a specific next buyer action behind it.

    FAQ

    Is deal slippage the same as a lost deal?

    No. A lost deal is closed and done. A slipped deal is still open, it just didn’t close in the period it was forecasted for and got pushed to a later date.

    What’s a healthy deal slippage rate?

    There’s no single number that applies to everyone, since it depends on deal size and sales cycle length. As a general guide, many high-performing teams aim to keep slippage under 20% of committed pipeline, and anything consistently above 30% is worth investigating.

    Does deal slippage always mean the deal will eventually close?

    Not necessarily. Repeated slippage often signals poor qualification, internal delays, or customer misalignment, and every slip increases the chance of churn, reprioritization, or a competitor stepping in before the deal ever closes.

    How is deal slippage different from pipeline leakage?

    Pipeline leakage is when prospects drop out of your pipeline entirely without buying. Slippage is different: the deal stays in your pipeline, it just takes longer to close than expected.

    Can CRM data alone catch slippage early?

    Not reliably on its own. Most pipeline tools report stage, velocity, and conversion rates, which are retrospective, so you also need to watch for behavioral warning signs like missing stakeholder engagement or stalled next steps well before the close date actually moves.

    Should slipped deals stay in the committed forecast?

    Only if the rep can name a specific next buyer action, who owns it, and when it will happen. A deal that has slipped once with no concrete path to the new date is better moved to a lower forecast category until the evidence supports it.