# Commit vs best case: how to split a small team’s forecast without the drama

https://salesbond.app/blog/commit-vs-best-case-forecast/
Published: 2026-09-29 · Updated: 2026-10-26

Commit is the part of your forecast you would bet on: deals with a confirmed buyer, a date and a next step. Best case is commit plus the deals that could close if things go right. The gap between the two is how much of the period is still undecided, and on a small team that gap is where most of the manager’s week should go.

That’s the whole definition. The hard part is getting five reps to mean the same thing when they say “commit,” in a CRM like Pipedrive, where we haven’t found forecast categories as a built-in feature. This post is about that part.

## Where the two words come from, and why a five-person team should borrow them

The vocabulary comes from bigger sales orgs and the forecasting tools built for them. Salesloft’s guide (originally on the Clari blog, [published December 2021](https://www.salesloft.com/resources/blog/defining-sales-forecast-categories-to-drive-reliable-revenue)) lays out a ladder: Pipeline, Best Case, Commit, Closed and Omitted. That guide sets a high bar for commit, expecting reps to close about 90% of what they put there. Before a deal moves in, the rep is supposed to ask whether the contact can actually sign, whether the timeline is confirmed and whether a [mutual action plan](https://salesbond.app/blog/mutual-action-plan-small-teams/) exists.

Why would a team of five need enterprise vocabulary? Because the alternative is worse. Without categories, a small team forecasts one of two ways. Either the manager asks each rep “what’s closing this month?” and writes down whatever confidence sounds like on a Monday, or the team leans entirely on stage math. Stage math has its place, and we covered its blind spots in [how a weighted pipeline forecast works and where stage percentages lie](https://salesbond.app/blog/weighted-pipeline-forecast/). A weighted forecast multiplies each deal by the probability attached to its stage, unless a rep has [typed a probability on the deal itself](https://salesbond.app/blog/pipedrive-deal-probability-vs-stage-probability/). It never asks a person to say “this one I’d stake my number on.” Categories ask exactly that. Use them next to weighting; they answer a different question.

There’s also plain language. If someone on your team came from a larger company, they already use these words. Better to pin down what they mean in your shop than let each rep carry a private definition.

## Commit vs best case, side by side

Commit sits inside best case: commit is the floor of your forecast, best case is the ceiling, and every commit deal also counts toward best case. ORM Tech puts it the same way, calling the pair [the floor and the ceiling of the same forecast](https://orm-tech.com/blog/commit-vs-best-case-forecast/), nested rather than competing. Here is how we’d set up the three buckets for a small team.

| | Pipeline | Best case | Commit |
| --- | --- | --- | --- |
| Entry rule | Qualified, open, amount entered | Real buyer engaged, close date inside the period, at least one open question | All four commit rules below are true, checked in the CRM |
| Who decides | Rep | Rep | Rep proposes, manager can veto in the weekly review |
| Who sees the number | Rep and manager | Manager, used for coaching | Manager and whoever you report revenue to |
| What it’s for | Finding deals to work next | Deciding where to spend effort this week | The number you promise |

Two choices in that table are deliberate. First, commit is the only bucket the manager can veto. Letting the manager push deals *into* commit turns it into the manager’s forecast, and the rep stops owning it. Second, best case stays inside the team. It’s a coaching number. Report it upward and people start planning around your ceiling.

On percentages: vendors publish different thresholds for each category, and we haven’t found one source worth repeating as a standard. Set your own after a quarter or two. Look back at what share of your committed deals actually closed. If it’s far below what you’d want, your entry rules are too loose. If you keep the forecast in a template, here is [which column in the forecast template is commit and which is best case](https://salesbond.app/blog/sales-forecast-template-crm-fields/).

## Entry rules a rep can check in ten seconds

Here is the trap with categories. They’re an opinion. A rep who feels good about a call will move a deal to commit, and a rep who got burned last month won’t commit anything. Neither is lying; both are guessing.

So tie entry to what’s on the deal record. Our starting rule for commit has four parts, and each one takes a glance. There’s a scheduled next activity with a date inside the period. At least two people from the buyer’s side are on the deal, because one champion is a single point of failure. The amount came from the buyer; a number the rep estimated doesn’t count. And the close date has moved no more than once. If the buyer still works with another vendor, also check [when their current contract ends](https://salesbond.app/blog/incumbent-contract-end-date-pipedrive/). In the last quarter of the year, add one check to the commit rule: [whether the budget expires on December 31](https://salesbond.app/blog/year-end-budget-deadline-deals-pipedrive/) or rolls over.

We wrote separately about [what counts as a next activity](https://salesbond.app/blog/pipedrive-next-activity/) in Pipedrive and what is only a placeholder.

Four is plenty. You’ll be tempted to add “legal has the contract” or “budget approved.” Add them only if your deals actually go through those steps, otherwise nothing ever qualifies for commit and the category dies quietly.

Best case needs just one rule: the deal could close this period if one named thing goes right. Make the rep write that thing down. “Waiting on their CFO” is a best case deal. “They seemed keen” is pipeline.

The same line separates a buyer’s action from a rep’s mood: only the first counts as one of the [buying signals](https://salesbond.app/blog/buying-signals-pipedrive-deals/) worth logging on the deal.

## What the gap between commit and best case tells you

A hypothetical makes it concrete. A five-rep team has a monthly target of $160,000. Two weeks in, commit adds up to $120,000 and best case to $175,000, so $55,000 sits in best case without being committed. Commit covers three quarters of the target. To hit the number, the team needs $40,000 of that $55,000 to land, nearly three of every four best case dollars. That’s a stretch. The difference is you know it on day fifteen instead of day thirty.

So treat the gap as a list of decisions. Each best case deal has that one named thing standing between it and commit, and the manager’s job in the weekly review is to go down the the list and ask what happens to that thing before next Monday. A small gap with the target already covered means reps can start pushing next month’s deals. A large gap with a thin commit means every hour this week goes to those few deals, and you tell whoever you report to now, not on the last day.

Commit can look healthy and still hang on one card, so add a second line: the [forecast without the biggest deal](https://salesbond.app/blog/one-big-deal-forecast-pipedrive/).

Over time the gap says something about the pipeline too. If best case is barely above commit month after month, reps may be sandbagging, holding deals back until they’re certain. If it’s always double commit and the extra rarely closes, best case has turned into a wish list. Fix the entry rule before you blame the reps. Pair this with your [pipeline coverage ratio](https://salesbond.app/blog/pipeline-coverage-ratio/): coverage tells you if there’s enough in the funnel at all, the commit and best case split tells you how much of it is real this period.

For telling the two habits apart, see our piece on [sandbagging vs happy ears](https://salesbond.app/blog/sandbagging-vs-happy-ears/).

![Manager reviewing the sales forecast data with team members.](https://salesbond.app/wp-content/uploads/2026/09/commit-vs-best-case-forecast-2.png)

## Deals that jump into commit in the last week

Every manager has seen this. On the 25th, commit looks thin. On the 28th, three deals appear in it that were never in best case. Sometimes that’s a genuinely fast buyer. More often it’s a rep closing the gap in the spreadsheet while the customer hasn’t moved. The same thing happens in Pipedrive when someone ends the month by [dragging a deal to a later column](https://salesbond.app/blog/pipedrive-forecast-view-dragging-deal-date/).

Our rule: a deal that lands in commit in the final week without having spent time in best case gets one question in the review. What changed on the record? A new meeting booked, a second contact added, a confirmed amount. If the answer is visible, keep it. If the answer is “I have a good feeling,” it goes back to best case and nobody makes a scene about it.

Track these jumps for a couple of months. A rep whose late jumps close is reading thier buyers well. One whose late jumps slip keeps needing the question. That pattern is also a decent input for a [deal health score](https://salesbond.app/blog/deal-health-score/) if you’re building one.

## Setting it up in Pipedrive without a new tool

You don’t need a forecasting add-on to try this. Start with a custom deal field of the **single option** type called “Forecast category,” with three values: Pipeline, Best case, Commit. Pipedrive’s [guide to custom field types](https://support.pipedrive.com/en/article/what-types-of-custom-fields-are-there) describes single option as a list of predefined options where only one can be selected, which is exactly the constraint you want. A deal lives in one bucket at a time.

Next to it add a **date** field called “Committed on” that the rep fills the day a deal enters commit. That one field makes late jumps visible without anyone digging through the deal’s history. For best case deals, a short text field, “What must happen,” holds the one named thing the rep wrote down.

Then give it a rhythm. Filter the deal list to close dates inside the current period, add Forecast category as a column, and go through the list with the team once a week. Same day, same order: commit first, then best case, then anything that jumped. After two full periods, compare what was committed with what actually closed and tighten or loosen the entry rules.

Check how your account is configured before you add fields. Some teams already have a half-used “probability” or “confidence” field, and it should be retired first, or you’ll end up with two opinions on every deal.

Categories won’t turn reps into better forecasters on their own. What they do is make the guessing visible, and once calling something commit means pointing at a scheduled meeting and a second contact, the Monday conversation shifts from confidence to the record. So pick one review day this month, add the field, and run two periods before you touch the rules. When that’s working, look at the [leading indicators behind these numbers](https://salesbond.app/blog/leading-vs-lagging-sales-metrics/), which show trouble while there’s still time to act.