1. Sales Forecasting
  2. Features
  3. Management rollups
Feature · Management rollups

Management rollups

Follow rep submissions up the management chain and keep leadership overlays separately explained.

OverviewLeadership Rollups
Sales Forecasting · Management rollups

Leadership Rollups

Forecast rollups

New
PeriodScopeOwnerChild submission countTotal commitTotal best case
FP-7465Team40130880
FP-9707Region850190
FP-6005Org4450390
FP-9646Team15670660
FP-1118Region16740650
6 of 6 records
FP-7465Forecast rollups · FR-38844
Team
Child submission count40
Total commit130
Total best case880
Total pipeline710
Total closed180
Example screen with sample data

What you can do

See where the leadership number comes from

A reviewed forecast needs a clear path from the rep’s call to the leadership discussion. Submission status changes trigger rollup recomputation through the user management chain. Team, Region and Org scopes identify the owner and level of the resulting forecast, with child submission counts and commit, best-case, pipeline and closed totals.

Sales Manager, Sales Director and VP Sales can record their own adjustments alongside those derived totals. Each adjustment retains its type, amount, category, period and reason. Keeping the overlay as its own record lets the next reviewer distinguish the child submissions from leadership judgment.

How the work is organized

  • Management chain. The rep’s manager relationship determines the team handoff, and successive manager relationships identify regional and organization ownership. Admin and Sales Operations check that chain before relying on the rollups.
  • Derived totals. Recalculation updates the rollup for the same period, scope and owner. The child count helps a leader ask whether the expected submissions are represented in the current result.
  • Leadership overlay. An adjustment records an addition, removal or manual overlay with its reason. The leader retains the decision separately so changes to the base call remain explainable.

What to agree during setup

Review the actual reporting structure with the people who own the forecast. A regional label alone does not establish the user-to-manager chain. Check that each pilot rep reaches the intended Sales Manager, Sales Director and VP Sales through those relationships.

Agree which submission states contribute to a formal leadership call and how a reopened call is handled in the review discussion. Rehearse an amount correction through that procedure and check the rollup’s recomputation time and totals afterward. Keep the submission currency and revenue or bookings basis consistent before combining amounts.

Define who can make an overlay at each scope and what reason is required. The adjustment type should make its intended effect understandable. Agree how the team presents the derived total and the overlay together, and how repeated recalculation preserves the recorded leadership judgment without applying it again accidentally.

Check the handoff on an actual case

Use pilot reps under the same manager and submit their calls for the same period. Recompute the team rollup and compare its child count and category totals with the contributing submissions. Follow the same reporting chain to the regional and organization owners and verify the amounts at each level.

Have Sales Manager record a reasoned adjustment to the team call. The underlying rep submission should retain its original amount, while the adjustment shows its author and intended category effect. Repeat rollup recomputation and check that it updates the existing period-scope-owner record rather than adding another rollup. Ask Sales Director to explain the final leadership view from its child totals and the separate overlay evidence.

What your team sees

  • Leadership Rollups — Period totals by management scope and owner, with child counts and recomputation time.
  • My Forecast Adjustments — The current leader’s overlays with amount, type and reason.
  • Manager Review Inbox — Submitted child calls that still need a manager decision.

Follow the work through

Use Submit and review the forecast for the decision and rollup rehearsal, then Inspect forecast risk for changes that may affect the next call.

What it keeps track of

Data model
Forecast rollups
Derived per owner per period totals summed up the management hierarchy from Team to Region to Org.
Forecast submissions
Per rep per period forecast submission carrying the commit, best-case and pipeline call to the manager.
Submission lines
One line per forecast category and revenue type on a submission, holding the rep number and the system auto amount.
Adjustments
Manual numeric overlays by manager, director or VP on top of rolled-up child submissions, kept separate for audit.
Forecast categories
The category taxonomy reps use to classify open opportunities: Closed, Commit, most likely, best case, Pipeline, Omitted.
Forecast periods
US fiscal forecast periods on a calendar-year basis (Week, Month, Quarter) with submission deadlines and open/lock/close lifecycle.
Users
Users
Forecast notes
Rep and manager commentary attached to a forecast submission.

Who uses it

Permissions
Sales Manager
Owns the team call.
Sales Director
And VP Sales review their respective scopes and explain adjustments.
Sales Operations
Checks recomputation, Admin maintains the hierarchy, and Finance Analyst reviews the amount basis.

Set up Sales Forecasting your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started