Overview

Forecast Command is the drill-down behind the FORECAST tile on the Revenue Engine masthead. It shows where the period is projected to land, the range around that figure, how confident Summit53 is in it, and the inputs you can check it against. Use it before a forecast call to understand the number, not just read it.

Opening Forecast Command

Open Revenue Engine from the sidebar.
Check the period in the dropdown next to the REVENUE ENGINE label. Forecast Command always shows the selected period; see Sales Periods.
Click the FORECAST tile in the masthead. A panel headed Forecast Command (ML projection · confidence · trend) slides in from the right.
Close it with Close, the × button, Esc or a click on the dimmed page.

The Forecast Overview card

Forecast Range

Under FORECAST RANGE you see three figures and a bar that places them on one scale:

Most Likely: the projected landing for the period (explained below). It is the same figure as the FORECAST tile and the headline.
Low and High: the confidence range applied to Most Likely. Together they are the same landing zone the Forecast Rail shows.

Beside the heading, a trend label reads Improving, Decliningor Stable. Any figure that hasn’t been calculated yet reads Pending.

The confidence badge

The badge pairs the forecast confidence percentage with a label. Hover the ? icon for a plain-English explanation.

High Confidence: 80% or more.
Medium Confidence: 60% to 79%.
Low Confidence: below 60%.
Confidence pending: the full forecast is still being calculated, so the percentage shows a dash rather than a number.

A one-line summary follows the badge, for example “Likely to hit forecast with focused execution”. When confidence is below 60%, the summary appears as a red alert with a View At-Risk Deals link instead.

View Forecast Components

Expand View Forecast Components to see the inputs beside Most Likely:

ML Forecast (next month): the model’s prediction for next month’s bookings only. It is an input to compare against, not a forecast for the whole period.
Manual Commit: the value of open deals your CRM puts in the Commit forecast category for the period. It is bottoms-up and not risk-adjusted.
Execution Score: the average health score of your open deals that have been scored. It reads Pending when none have been scored yet.
View Pipeline Intelligence: opens Flow, the Pipeline Explorer. See Pipeline Explorer: The Flow Schematic.
Execution-Adjusted Forecast: expand it to see the Base Forecast, the Execution-Adjusted figure and the Adjustment between them. If it can’t load, it reads Unable to load execution forecast.

What Most Likely is

Most Likely is your sellers’ forecast call, not a model output. Summit53 works it out like this:

It takes each quota-carrying seller for the period: active members with a quota above zero, excluding top leadership.
For each seller it uses their most recent forecast call from the last 14 days: the manager’s commit if there is one, otherwise the rep’s commit, otherwise the model’s prediction.
It converts each call into your reporting currency and adds them up.
The total is never lower than the revenue already closed-won in the period.

If fewer than 70% of sellers have a recent call, or nobody carries a quota for the period, Most Likely falls back to closed-won revenue plus probability-weighted open deals closing in the period. Open deals with no probability add nothing.

Forecast Command doesn’t say which method is in use. Check the line under the large figure in the Forecast Rail: projected landing · rep forecast calls or projected landing · closed-won + weighted pipeline.

How it relates to the Forecast Rail

The Forecast Rail, on the Revenue Engine home screen, shows the same forecast in a compact form. Use it for a quick read and Forecast Command for the detail.

The rail’s large figure is Most Likely.
The rail’s LANDING ZONE is Low to High, and its confidence percentage matches the badge.
Under FORECAST INPUTS, the rail adds WEIGHTED PIPELINE (pipeline says) when Most Likely comes from your sellers’ calls, so you can compare the two.

For every part of the rail, see Revenue Engine Masthead: Forecast Call, KPIs & Drill-downs.

View At-Risk Deals opens Risk Signals, which you can also reach from Deals in the sidebar. See Risk Signals.
Quota Settings: quotas decide who counts as a quota-carrying seller.
Forecast Settings: where each person’s forecast figures are entered, edited and imported.
ML/AI Configuration: train the model behind ML Forecast (next month).
Reporting Currency & Exchange Rates: how amounts are converted.

The older Forecast Command Center is a legacy page with no navigation entry; use this drill-down instead.

Best practices

Plan around the Low to High range, not just Most Likely.
Compare Most Likely with WEIGHTED PIPELINE on the rail. A large gap between what reps say and what the pipeline says is worth a conversation.
Treat ML Forecast (next month) as a sense check on the near term, not as the period forecast.
When confidence drops below 60%, follow View At-Risk Deals before the forecast call.

Troubleshooting

Figures read Pending or the badge says Confidence pending. The full forecast is still calculating. Give it a moment, or press Refresh on the masthead.
Most Likely doesn’t match ML Forecast (next month). That’s expected: Most Likely is the sellers’ call for the period, and the ML figure covers next month only.
The rail says closed-won + weighted pipeline. Fewer than 70% of quota-carrying sellers have a forecast call from the last 14 days, or no one carries a quota for the period. Ask sellers to update their forecast figures (see Forecast Settings), and check quotas in Quota Settings.
There’s no View At-Risk Deals link. It appears only when confidence is below 60%. Open Risk Signals from Deals in the sidebar at any time.
View Pipeline Intelligence opened Flow. That’s where the link now leads.
The figures didn’t change when you expected them to. Check the period dropdown on the masthead, then press Refresh.

Forecast Command: Most Likely, Range & Confidence