Help / Deals / Forecast: commit, best case, excluded

Forecast: commit, best case, excluded

Concept2 min
In one sentenceEvery open deal sits in Commit, Best case or Excluded by rule, from its status - not from anyone's optimism - and each bucket says why.

How a deal is placed

The Forecast reads the status the loop already gave each open deal. Moving, Due and Ready deals are Commit - "moving or due - counted in your number". Held deals are Best case - "play running - counted at best case only" - until every move on the hold is ticked. Overdue deals are Excluded - "nobody has explained these yet - out of the number until someone does". The three buckets together are your whole open pipeline at full value; won and lost deals are in none of them. Under each deal a line says why it is where it is.

An Excluded deal needs a person, not a stage change. Press Why is this fine? on the row (or drag it into Commit), say what they told you under "What did they say?" and give a "Good until" date - at most 30 days out unless an admin changed the limit, and never past the deal's close date. Press Count it and the deal returns to Commit until that date, then falls out on its own. Commit shows how much of its total is "accounted for by hand"; Take it back out undoes it, and so does placing a hold or advancing.

Attainment

The strip at the top shows Closed won against the workspace quota, and Commit + won - the number if commit lands. The Attainment panel groups the same book By rep or By team (teams are set under Admin › Teams): percent of quota won, commit, coverage, what is still to go, open deals, and movement in commit since last week once a second week has been captured. A rep with no quota reads "no quota set", never 0%.

Did this answer it? Not quite - tell us