HubSpot Forecasting: Tiers, Forecast Categories, Submissions, Goals and Setup

HubSpot's forecast tool records less forecaster judgment than its columns suggest. With Automate forecast categories on, a workflow writes each deal's category from its stage, overwriting a rep's hand edit at the next stage move, while the default Weighted amount counts every deal at its stage probability. A manager reading the Commit column as the reps' call is then reading pipeline configuration. The one forecast figure typed into the tool, the submission, is scored as the average of every submission for the period, measured against closed won. A rep who submits only on day 29 of a 30-day month can therefore outscore one who called the month within ten percent on day 1.

This article explains HubSpot forecasting as documented in October 2026. Tiers, seats and permissions come first, with the costs and returns they set, followed by forecast categories and their stage mapping, weighted and total amounts, submissions and goals, and the accuracy score on a sample team. The symptoms of a misconfigured tool lead into a setup procedure ending in verification, and the limits of the tool and of this evidence close it. The general methods are covered under revenue forecasting.

A forecast category is a deal's class of likelihood to close, held in the Forecast category deal property, whose default values are Not forecasted, Pipeline, Best case, Commit and Closed won. A forecast submission is the amount a rep or manager expects to close in one pipeline and period. The forecast deal amount values every deal in the tool, as Weighted amount, which is Amount multiplied by Deal probability, or as Total amount.

Tiers, Seats and Permissions

The forecast tool is included in Sales Hub and Service Hub Professional and Enterprise, and the Forecasting row of HubSpot's product and services catalog leaves Sales Hub Starter blank. The catalog reserves forecasting across team hierarchies for Enterprise, the only tier that can nest teams, so a Professional account, which includes ten teams, cannot roll reps up through managers to a director.

Using the tool requires an assigned Sales or Service Seat, Super Admins excepted. The same seat is needed to create, view or hold a forecast goal, and only a Super Admin can configure the tool. The permissions guide sets Forecast access to Forecast they own, which shows users their own forecast, or Forecast their team owns, which adds their teammates. Scheduled submission reminders reach only users with Edit access.

Costs and Returns of the Forecast Tool

The tool buys a forecast held beside the deals it describes: categories, submissions, goals, coverage and an accuracy history. Inside a Professional or Enterprise subscription it needs no licence beyond each forecaster's Sales or Service Seat, listed in the catalog at $100 a month on Professional and $150 on Enterprise. The other cost is data discipline: every figure derives from Deal stage, Amount, Close date and Deal probability, and a rep-owned category, set out below, adds a field someone must keep current.

The firm publishing this article implements HubSpot. The case is strongest for one level of teams forecasting new-business bookings by month or quarter from pipelines with enforced stage definitions. It is weakest for multi-level roll-ups on Professional, which need the team nesting that only Enterprise offers. For subscription revenue, a recurring revenue property in a custom forecast type lands on one date and does not recur, so the revenue schedule belongs in a model kept outside the tool. Fixed-lead accuracy, defined under the accuracy score below, is also computed outside the tool, taking from the History tab the submission standing at the lead.

Forecast Categories and Their Mapping to Deal Stages

Categories are mapped per pipeline on the Pipelines tab of Settings, Objects, Forecast, one category to each deal stage, and saving the mapping categorizes existing and new deals by stage. With the Automate forecast categories switch on, a workflow named Forecast Category Mapping for Pipeline applies the mapping, and HubSpot updates the Forecast category property whenever a deal changes stage. A category a rep sets by hand on the record stands until the next stage move overwrites it.

That design produces this article's finding, checkable in any portal. With automation on and the forecast deal amount at its default, Weighted amount, the Forecast category tab is a function of Deal stage and Amount alone. The stage picks the column, and its win probability sets how much of the amount counts. The exceptions are categories set by hand since a deal's last stage change and probabilities written by a manual update: a record edit, bulk edit, import, integration sync or API call. The forecast tool documentation presents categories as where a team adjusts the forecast on its knowledge of the deals. On those settings, that knowledge lasts until the next stage change, and the category tab is the deal stage tab regrouped.

The switch therefore decides what the category records. On, the category mirrors the stage, and the submission is the only figure that records the rep's call. Off, the documentation describes no update on later stage moves, so each deal keeps its category until a person changes it. The setup documentation lets a cloned workflow replace the default once the automation switch is turned off. A clone that writes a category only when the property is empty or the deal closes yields a rep-owned field. That field needs definitions tied to events on the record rather than to confidence, as the antipattern of forecast categories used as sentiment sets out.

Each option's position in the property, not its name, sets the definition shown in the settings, so Commit in second place reads as a low likelihood of closing. Position also drives the Deal change history report in the sales analytics suite, which counts any move down the list as Forecast Moved Forward. Only the last five options, beside Not forecasted and Closed won, can be mapped to stages.

Weighted and Total Amounts

Weighted amount is the default forecast deal amount for every user with Forecast permissions, and Total amount is the full Amount. Accounts created before 20 March 2024 also offer a legacy Forecast amount, driven by a Forecast probability set by hand or by workflow. Deal probability follows the stage, from 20% at Appointment scheduled to 90% at Contract sent in the default pipeline. A manual update sets it and stops it following the stage until the deal closes.

The setting decides what a category column means. A $60,000 Commit deal in Decision maker bought-in, at 80%, adds $48,000 to the Commit column on Weighted amount and $60,000 on Total amount. Closed won plus Commit therefore sums committed deals at full value only on Total amount.

Submissions, Goals and the Forecast Table

A submission is entered per pipeline and forecast period, optionally built from deals ticked in the Add to Forecast column. Every submission is kept, with a year of history, and a team submission replaces its reps' sum in the team row, per the forecast tool documentation.

Forecastable revenue goals appear only when their duration equals the forecast period, they cover one pipeline or all of them, and the forecast's filters match them. A user on several teams carries a target on one team only.

The documentation does not say whether Open pipeline follows the forecast deal amount setting.

The Accuracy Score and AI Projections

Tracking the accuracy of forecasts scores a user or team for a period as one minus the absolute gap between closed won and the submission average, as a share of closed won, floored at zero. The submission average is the mean of every submission made for the period; the formula is undefined when nothing closes, and the documentation does not say what the tool shows.

Averaging is the defect. A day-29 submission is made with every deal closed by day 29 already in Closed won, and forecast error grows with the horizon, as Hyndman and Athanasopoulos show in Forecasting: Principles and Practice. Averaging forecasts made at different horizons therefore rewards submitting only late and penalises early commitment, whatever the forecaster's skill. A fixed-lead score instead takes the submission standing at a set point, such as the end of day seven, which the History tab records; choosing the lead and the error measure is covered in measuring forecast accuracy.

Beside the category columns and the submission, the beta AI projections add a range projected from the past three months of closed-won deals and scored on the same formula, with no documented use of open deals.

Accuracy Scores on a Sample Team

The team below is sample data for recomputation and describes no client; each rep closes $100,000 in a monthly forecast period.

The tool ranks Rep C first and Rep B last, although Rep C submitted nothing until day 29. Scored on the submission standing at the end of day seven, Rep A is 10% out, Rep B is 30% out, and Rep C has no forecast, which a fixed-lead measure records as a missed submission.

Forecast Tool Symptoms and Their Causes

A deal a rep moved into Commit by hand returns to another category at its next stage move. The automation rewrote the property on the stage change; where the category should hold the rep's call, switch automation off or narrow a cloned workflow.

Categories no longer match the stages their deals have reached. Automation is off, so categories set when the mapping was saved never moved with the deals; switch it on, or make the category a field reps maintain.

The Commit column totals less than the committed deals' amounts added by hand. The forecast deal amount is Weighted amount, so switch to Total amount or read the sales analytics Forecast category report, which uses deal amount.

A manager given team visibility still sees no rows for the team's reps. The forecast tool lists only users with an assigned Sales or Service Seat, so check the reps' seats first. The permissions guide says Forecast their team owns shows teammates, while the forecast tool page says Team only shows the user's own forecast. Then test with the manager's login to settle the conflict, and confirm the reps sit on the manager's team.

Setup and Verification Procedure

1. Confirm Sales Hub or Service Hub Professional or Enterprise, a Sales or Service Seat for every forecaster and goal holder, and a Super Admin. Seat planning by role is set out in Sales Hub onboarding.
2. Set Forecast permissions, Forecast they own for reps and Forecast their team owns for managers, and make each rep a main member of the team whose goal they carry.
3. In Settings, Objects, Forecast, choose the forecast period first, since a later change resets goals and submissions, then the forecast deal amount.
4. On the Pipelines tab, map stages to categories and set the automation switch: on for a stage view, off or a cloned workflow for a rep-owned category.
5. In Edit forecast categories, order the options so that position matches meaning.
6. In Settings, Objects, Forecast, Forecast submissions, select the Forecast submission status indicator: it flags forecasts not updated within eight days, a default editable up to 31.
7. Create Forecastable Revenue goals from Sales, Forecast, with the forecast period as their duration and one pipeline or all.
8. Under Actions, Set submission schedule, set a due time and reminders. The accuracy score still averages every submission, so the due time sets a lead only for a fixed-lead score kept outside the tool.
9. In one rep's drill-down, add Deal stage and Forecast category through Edit columns and confirm each deal carries its stage's category. Then set a test deal's category by hand, move it one stage, and read the property history to see which value stands.
10. Filter the forecast to each goal's pipeline and period to confirm the goal appears. Sign in as a rep and as a manager to confirm each sees what their permissions state. The setup is accepted when these checks match the decisions taken in steps 2 to 4.

Limits of the Tool and of This Evidence

Beyond the tier gates above, the tool applies one period length to every pipeline and maps each stage to one category per pipeline. The documentation describes no forecast by product or line item and no fixed-lead accuracy score.

This article covers the native tool as documented in October 2026, and HubSpot's knowledge base governs wherever the two differ. Revenue recognition, the custom report builder and other vendors' forecasting tools are out of scope. Every behaviour described comes from documentation rather than a test portal; the overwrite of a hand-set category follows from the documented update rule, and step 9 tests it. The sample team is constructed, and nothing here measures whether any setting improves real forecasts.

In Summary

HubSpot's forecast tool values deals at Weighted amount by default, groups them into categories mapped from deal stages, and adds submissions, goals, an accuracy score and a beta AI projection. On Sales Hub and Service Hub Professional and Enterprise it costs nothing beyond a Sales or Service Seat per forecaster, and it is weakest for multi-level roll-ups on Professional, recurring revenue and fixed-lead accuracy. With automation on, the category view is the stage view regrouped, and the accuracy score rewards the rep who submits only late.

The decision to take at setup is which figure records the rep's call: the submission, scored at a fixed lead from its history, or a rep-owned category defined by events on the record and read at Total amount. A portal that takes neither route labels a stage view as a forecast and scores submission timing as accuracy.