# HubSpot’s Forecast Tool: What It Counts, Where the Rep’s Number Comes In, and the Monday Check

https://salesbond.app/blog/hubspot-forecast-tool/
Published: 2026-10-22 · Updated: 2026-10-26

The HubSpot forecast tool is a view built on top of your deals, and a deal appears in it only when three things line up: its Close date falls inside the period you are looking at, it sits in the pipeline you selected, and its owner is inside the team you are reviewing. Inside that view HubSpot can group deals by deal stage or by forecast category, and the two are different instruments. A stage records where the deal is in your process. A forecast category records how confident the rep is that the deal closes this period, and it is meant to be set by a person. Let HubSpot map one onto the other automatically and you get one number wearing two labels. The tool earns its place when the two stay apart and a manager compares them, every Monday, against the number the rep submitted.

## What the HubSpot forecast tool counts

The tool lives under Sales > Forecast in Sales Hub and Service Hub Professional and Enterprise, and using it takes an assigned Sales or Service seat ( [HubSpot: use the forecast tool](https://knowledge.hubspot.com/forecast/use-the-forecast-tool)). Its settings sit in Settings > Objects > Forecast and need Super Admin permissions ( [HubSpot: set up the forecast tool](https://knowledge.hubspot.com/forecast/set-up-the-forecast-tool)).

Three filters decide what you see. Dropdowns at the top pick the pipeline and the close date, and you review a team by clicking its name ( [HubSpot: use the forecast tool](https://knowledge.hubspot.com/forecast/use-the-forecast-tool)). The consultancy man.digital calls these three locked criteria, close date, pipeline and owner, with rollups following the team hierarchy ( [man.digital: HubSpot forecasting](https://www.man.digital/blog/hubspot-forecasting)). We’d put it more bluntly. The forecast tool never looks at your whole pipeline. It looks at a slice, and the slice is cut by a date field reps edit by hand.

The amounts in that slice are weighted by default: Amount multiplied by Deal probability ( [HubSpot: set up the forecast tool](https://knowledge.hubspot.com/forecast/set-up-the-forecast-tool)). So every number in the tool inherits your stage probabilities, and we wrote up how to get those from your own win rates in [HubSpot deal stages and probabilities](https://salesbond.app/blog/hubspot-deal-stage-probability-forecast/). Here we take them as given.

## Deal stage is not a forecast category

A forecast category is the rep’s confidence that a deal closes this period; a deal stage is its position in the process. HubSpot’s own wording: categories let the team adjust the forecast based on what they know about the deals without losing track of where each deal is in the sales process ( [HubSpot: use the forecast tool](https://knowledge.hubspot.com/forecast/use-the-forecast-tool)). That’s why the Deal stage and Forecast category tabs sit side by side.

Categories are set up per pipeline. In Settings > Objects > Forecast, on the Pipelines tab, you pick a pipeline and sort its stages into Not forecasted, Pipeline (low likelihood of closing), Best case (moderate likelihood), Commit (high likelihood, committed to the forecast) and Closed won. A rep can change one deal’s category by hand from the deal record ( [HubSpot: set up the forecast tool](https://knowledge.hubspot.com/forecast/set-up-the-forecast-tool)).

Then there is the switch. Automate forecast categories, on the same tab, creates a workflow and updates the category automatically whenever a deal moves to a different stage ( [HubSpot: set up the forecast tool](https://knowledge.hubspot.com/forecast/set-up-the-forecast-tool)). Read that from the rep’s side. She looks at a deal in Contract sent, knows the champion just went quiet, and sets it to Best case. The next stage move puts it back wherever the mapping says. man.digital makes the same point, that auto-mapping overwrites manual picks when stages change, and recommends turning it off ( [man.digital: HubSpot forecasting](https://www.man.digital/blog/hubspot-forecasting)).

We agree and our reason is simpler than accuracy. With the switch on, the Forecast category tab is the Deal stage tab with fewer columns, and you’re paying attention to two views of one number. A category is only worth a column when a human can disagree with the stage and have it stick. Reps won’t do that well until the team shares a definition of commit, so we wrote one down in [commit vs best case](https://salesbond.app/blog/commit-vs-best-case-forecast/).

## Where a rep’s own number comes in

Categories are set deal by deal. The submission is one number for the period, and its the only place in the tool where a rep says what she expects to close rather than tagging deals.

She clicks Submit in the Forecast Submission column, picks the pipeline and period, enters an amount and a note. When a manager submits for a user, the panel also lists the deals with Add to Forecast checkboxes, and the amount fills in with the sum of the ticked deals ( [HubSpot: use the forecast tool](https://knowledge.hubspot.com/forecast/use-the-forecast-tool)). So the number starts life as a deal sum and can be typed over. That’s the right design: the gap between the ticked deals and the typed amount is the rep’s judgment, written down.

Past submissions stay: the History tab goes back up to one year ( [HubSpot: use the forecast tool](https://knowledge.hubspot.com/forecast/use-the-forecast-tool)). That’s the record you need when a rep says in April that she “always said” March was soft.

To keep the numbers fresh, a Super Admin can set a submission schedule with reminders, and the forecast submission status indicator flags anyone who hasn’t updated in a set number of days ( [HubSpot: set up the forecast tool](https://knowledge.hubspot.com/forecast/set-up-the-forecast-tool)). We set the indicator to seven. Weekly submission, weekly review, one calendar.

And treat the note as mandatory, even though HubSpot doesn’t. A number without a note is a guess. A number with “Acme slipped to May, Beta signed Friday” is a forecast somebody can argue with. If you want a coverage number next to the submission, see how [HubSpot pipeline coverage](https://salesbond.app/blog/pipeline-coverage-ratio-hubspot/) divides open pipeline by the gap to goal.

## The Monday check: three numbers that should agree

![Diagram: one rep's Submitted, Commit and Closed won numbers, with arrows to compare submitted against each of the other two](https://salesbond.app/wp-content/uploads/2026/10/hubspot-forecast-tool-2.png)

Every Monday we open the forecast for the current period and go rep by rep; for a team of five it takes about ten minutes. The first number is the submission, read from the rep’s row in the Forecast Submission column together with its note, because that’s the figure she put her name on. The second is her Commit total on the Forecast category tab, same pipeline and same close date range, which is what her deal tagging says. The third is her Closed Won for the previous month or quarter, which you get by moving the Close date dropdown back one period. Then click her name and look at the deals behind the numbers: a green or red dot under a deal stage means the stage moved forward or back within the selected range ( [HubSpot: use the forecast tool](https://knowledge.hubspot.com/forecast/use-the-forecast-tool)). Whatever you agree goes into the Next step field on that same screen, which fills the deal’s Next step property, so the one-on-one lands on the record and not in a chat.

A made-up example of how the comparison reads. Maria submitted $60k. Her Commit tab shows $85k. Last month she closed $35k. The first gap says she tagged $25k of deals as commit that she does not believe in, or the auto-map tagged them for her; either way, those are the deals to open first. The second gap says she expects nearly double her last month, which is fine if the note explains it and a problem if it doesn’t.

Three numbers, two questions. The one-on-one has an agenda before anyone speaks.

When the three agree you’re done with that rep in a minute. When they disagree in the same direction for three Mondays running, the problem is a definition, not a deal, and that’s a team conversation. We make the broader case for small teams in [sales forecast accuracy for small teams](https://salesbond.app/blog/sales-forecast-accuracy-small-teams/).

What the three numbers can’t tell you is whether a commit deal is still alive. A deal in Commit with a close date on the 30th and no activity since the 2nd passes every filter in the tool. We build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive, and SalesBond works with HubSpot too. Its Deal Health checks every deal against more than 20 rules and explains what’s wrong with each one and what to do about it. If you want that list next to the forecast on Monday, [check your CRM with SalesBond](https://salesbond.app/).

## Why a deal is missing from the forecast

Nearly every “the forecast is wrong” message we get is really “a deal I expected is not in the view,” and the three filters explain almost all of it.

Close date is the first suspect. The tool shows deals whose close date sits in the selected period, so a deal tagged Commit with a close date on the first of next month is in nobody’s number this month. man.digital calls this the hidden deal problem and the top source of forecast confusion they see ( [man.digital: HubSpot forecasting](https://www.man.digital/blog/hubspot-forecasting)). The fix is a deal filter, Forecast category is Commit and Close date is outside the current period, run before the Monday check.

Pipeline is the second. The dropdown shows one pipeline at a time, and the tool only shows goals tied to one pipeline or to all of them, with filters that match the goal’s date and pipeline ( [HubSpot: use the forecast tool](https://knowledge.hubspot.com/forecast/use-the-forecast-tool), [HubSpot: set up the forecast tool](https://knowledge.hubspot.com/forecast/set-up-the-forecast-tool)). A renewal pipeline with its own stages is a separate forecast, and a deal created in the the wrong pipeline stays invisible until somebody moves it. How we set the goals themselves is in [HubSpot goals and rep targets](https://salesbond.app/blog/hubspot-goals-rep-targets/).

Owner is the third, and the subtlest. Rollups follow teams, so a rep who isn’t assigned to a team is missing from the team’s number. And if your Forecast view permission is Team only, you see your own goals and forecast in the team view, not your teammates’ ( [HubSpot: use the forecast tool](https://knowledge.hubspot.com/forecast/use-the-forecast-tool)).

One more isn’t a filter at all. Any stage mapped to Not forecasted keeps its deals in the pipeline for the period but out of the forecast ( [HubSpot: set up the forecast tool](https://knowledge.hubspot.com/forecast/set-up-the-forecast-tool)), so a missing deal is sometimes a mapping problem, not a deal problem.

## FAQ

**Can I export forecast data from HubSpot?** Yes, through reports rather than the forecast tool itself. In Reporting > Reports, open Sales, then Forecast & revenue, pick a report such as Forecast category, and choose Actions > Export unsummarized data; the download link arrives by email and in the notification center ( [HubSpot: use the forecast tool](https://knowledge.hubspot.com/forecast/use-the-forecast-tool)).

**Where are HubSpot forecast reports?** Not under Sales > Forecast, where people look first. They live in Reporting > Reports under Sales > Forecast & revenue, and the submission history opens in Sales analytics through View submissions over time in the submission panel ( [HubSpot: use the forecast tool](https://knowledge.hubspot.com/forecast/use-the-forecast-tool)).