Forecast Settings: Submit, Bulk Edit & Import Forecasts

By Summit53 Team

Overview

The Forecast Settings page is where your team manages revenue forecasts and predictions. You review a summary of pipeline and commit, edit forecasts in bulk, and import or export forecast data. This is the configuration and data-entry surface for forecasting โ€” the leadership-facing roll-up lives in the Unified Forecast & Command Center.

Getting there

Open the Forecasts card from the Settings hub, or go to /revenue-intelligence/settings/forecasts.

Choosing a period

Use the period toggle to view forecasts by Weekly, Monthly, Quarterly, or Annual. The summary and table update to the selected period.

Forecast Summary

The summary panel totals the key numbers for the period: Total Pipeline, Total Best Case, Total Commit, and Coverage(pipeline relative to target). Use it to sanity-check the roll-up before sharing numbers upward.

Forecast categories

Forecasts are organised into standard categories โ€” typically Pipeline, Best Case, and Commit. The in-page Forecast Settings Help explains what each category means, how to use the systemโ€™s suggestions, and best practices for keeping a forecast honest.

Toolbar actions

  • Bulk Edit โ€” open the bulk editor to set Pipeline, Best Case, and Commit values across many rows at once.
  • Import โ€” load forecast figures from a file.
  • Export โ€” download the current forecast for sharing or offline review.

Bulk-editing forecasts

  1. Select the period you want to forecast for.
  2. Choose Bulk Edit to reveal editable fields.
  3. Enter Pipeline, Best Case, and Commit amounts as needed.
  4. Save, then confirm the Forecast Summary totals reflect your changes.

Troubleshooting

  • Coverage looks thin: coverage compares pipeline to target โ€” check the period and confirm quotas/targets are set.
  • Numbers donโ€™t match the Command Center: this page is for entry and the per-period roll-up; the Unified Forecast view may aggregate differently. Confirm both use the same period.
  • Import didnโ€™t apply: re-check the file matches the expected columns and that you imported into the intended period.