Roll-up reporting aggregates individual records upward through a hierarchy until they become a single summary number. Drill-down reporting travels the same hierarchy in reverse, starting at the summary and expanding it back into the records underneath. Both depend on the hierarchy being defined once and applied consistently.
A forecast number is a roll-up. Every rep commits deals, managers aggregate their teams, regions aggregate managers, and the company number falls out at the top. Asking why the company number moved is a drill-down.
The two directions in practice
| Roll-Up | Drill-Down | |
|---|---|---|
| Starts at | Individual records | A summary figure |
| Produces | One number | A list of contributors |
| Used for | Reporting a result | Diagnosing a result |
| Breaks when | Records have no parent | Filters differ between levels |
What a good drill path looks like
The path should follow the way accountability is structured, not the way the data happens to be stored. A revenue miss drills to segment, then to rep, then to the specific deals that moved. At the deal level the useful fields are stage, close date, and amount, because those are the fields whose changes signal something happened. ORM treats a change in stage, close date, or amount as meaningful activity on an opportunity.
That last level is where a coverage number turns into a decision. ORM's position is that pipeline coverage is an input and never the conclusion, because a company can hold 4x coverage and still miss when the pipeline is dependent on a few large deals or inflated by stale opportunities. Neither condition is visible in the rolled-up figure. All of them are visible one drill below it. We wrote about why the ratio alone misleads in the 3x pipeline coverage rule is wrong.
Keeping the two consistent
The failure mode is a roll-up total that does not reconcile to its own drill-down. Three checks catch most of it.
Confirm every child record has exactly one parent, because deals with a blank owner or an unmapped territory inflate the top total and disappear at every level below. Apply filters at the leaf level only, so a stage exclusion or a date range cannot behave differently at region than at rep. Convert currency at a single point in the chain rather than at each aggregation step.
When those hold, a win rate reported at the company level decomposes cleanly into segment and rep contributions, and a pipeline coverage ratio can be traced to the specific opportunities carrying it. When they do not hold, every review turns into an argument about whose number is right.
Frequently Asked Questions
What is the difference between drill-down and roll-up reporting?
Roll-up moves from detail to summary by aggregating records upward through a hierarchy such as rep to manager to region to company. Drill-down moves the other way, from a summary figure back to the individual records behind it. Same hierarchy, opposite direction.
How many levels should a drill-down path have?
Three levels covers most revenue questions: company to segment or region, segment to rep or account, rep to individual deal. More levels usually means the hierarchy is encoding two different dimensions at once, such as geography and product, which should be separate paths instead of one deeper one.
Why do roll-up numbers stop matching drill-down detail?
The usual causes are deals excluded by a filter at one level but not another, currency conversion applied at different points, and records that belong to no parent because an owner field is blank. Orphaned records are the most common. They appear in the company total and vanish when you drill into any region.
Does drill-down reporting require a data warehouse?
No. CRM reporting handles drill-down inside a single object well. A warehouse becomes necessary when the drill path crosses systems, such as moving from a revenue number down to the marketing campaigns that sourced the deals, because that join does not exist in the CRM.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like drill-down vs. roll-up reporting into prescriptive action for your team.
Schedule a Demo