Structure decides whose judgment counts
A forecast roll-up hierarchy is the aggregation chain the forecast travels through, plus the rules for what each level may change on the way up. The structure is not administrative detail. It determines whose judgment lands in the company number and whether anyone can reconstruct how that number was built.The chain usually runs rep, front-line manager, region or segment leader, company. Each level should submit its own figure rather than inheriting the sum below it. The difference between a level and the sum beneath it is that leader's applied judgment, which is exactly the thing worth measuring over time.
Reconcilability is the design constraint
Every level must be traceable to the deals underneath it. If a regional number cannot be walked back to opportunities, the roll-up has stopped being a forecast and become an estimate wearing a forecast's clothes.
Two practices keep that property intact. First, capture each level's submission separately instead of overwriting a single field. Second, require a written reason for any variance a leader introduces. A leader who takes ten percent out of a region is often right, and the reason is the part worth keeping.
The double-count problem
Aggregation is where the same revenue quietly appears twice. Watch for four sources:
- Overlay roles. Solutions consultants, partner managers, and specialists are attached to deals owned by someone else. They belong in a credit hierarchy, not the revenue roll-up. - Split opportunities. Splits need an ownership rule that sums to the full amount, and reporting has to respect it. - Multi-product deals recorded as separate opportunities against a single contract. - Renewal and expansion overlap, where a customer success team and an account executive both forecast the same expansion.
A roll-up that totals more than the company can actually book will still look internally consistent at every level, which is why the check has to happen deliberately.
Hierarchy changes break history
Territory changes, segment reorganizations, and manager moves reassign deals and rewrite the comparison base. Reporting that reads the current org chart will show last quarter's numbers under this quarter's structure, and accuracy by manager becomes meaningless.
Store the hierarchy as it stood at each submission. That way a manager's accuracy record follows the deals they actually called. This matters more than it sounds: ORM notes that territory changes distract reps and hurt execution even when pipeline coverage still looks healthy, so the quarter after a reorganization is exactly when clean historical comparison is most useful.
Get the hierarchy right and the roll-up becomes an auditable chain of judgments. Get it wrong and leadership plans against a total nobody can explain, which is a large share of what goes wrong in sales forecasting.
Frequently Asked Questions
What is a forecast roll-up hierarchy?
It is the chain the forecast aggregates through and the rules attached to each link. A typical chain runs rep, front-line manager, region or segment leader, then company. Each level submits its own number, and the difference between a level and the sum of the level below it is that leader's judgment, applied on the record.
Should managers be able to change a rep's number?
Yes, as long as the change is visible. A manager who quietly edits deal categories destroys the rep's accuracy record and their own. A manager who submits a different total and logs the reason keeps both records intact and creates something the team can learn from later.
How do you handle overlays and split credit?
Decide which hierarchy carries the revenue and which carries only credit. Overlay roles such as solutions consultants and partner managers should not add to the revenue roll-up, or the same dollar will appear twice. Split opportunities need an ownership rule that sums to one hundred percent of the amount.
What happens when the hierarchy changes mid-quarter?
Historical comparability breaks unless you preserve the old structure alongside the new one. Territory moves and reorganizations reassign deals, so last quarter's numbers by manager stop matching this quarter's. Store the hierarchy as of each submission rather than reading the current org chart when you report.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like forecast roll-up hierarchy into prescriptive action for your team.
Schedule a Demo