Skip to main content

Salesforce Collaborative Forecasts: Rollups and Quotas

Updated Add a comment
💬 In plain words: Salesforce Collaborative Forecasts rolls Opportunity revenue or quantities up your sales hierarchy into a single grid organized by time period and Forecast Category (Pipeline, Best Case, Commit, and Closed). Sales managers can apply judgment adjustments directly on the grid without overwriting the rep's underlying Opportunity records, while Quota tracking sits alongside the rollup to show real-time target attainment.
📌 Illustrative scenario: An account executive has three late-stage deals closing this quarter totaling ₹30,00,000 in the Commit category against a ₹40,00,000 quarterly quota. During the weekly pipeline review, the regional sales manager learns that one ₹5,00,000 contract is delayed in procurement. Instead of forcing the rep to falsify the Opportunity Amount or StageName, the manager enters a forecast adjustment on the Forecasts tab, lowering the rep's committed rollup to ₹25,00,000. Both the original ₹30,00,000 rollup and the manager's ₹25,00,000 adjusted figure remain visible with a clear indicator icon.

🔑 Key Points

  • Three architectural decisions define every forecast: When configuring Collaborative Forecasts, an administrator must decide what measure rolls up (the Forecast Type, such as Opportunity Amount, Quantity, Product Family, Opportunity Splits, or Schedules), which hierarchy governs the rollup (the User Role Hierarchy or the Enterprise Territory Management hierarchy), and how time periods and categories are displayed (monthly vs. quarterly, single category vs. cumulative rollup).
  • Forecast Categories bridge deals to the forecast grid: Collaborative Forecasts does not group deals by Opportunity Stage names directly. Instead, each StageName maps to a ForecastCategoryName value (Pipeline, Best Case, Commit, Omitted, or Closed), which determines the column where the deal's value lands.
  • Adjustments are non-destructive overlays: Manager adjustments and owner adjustments (when enabled in Setup) are stored as separate forecast adjustment records (ForecastingAdjustment or ForecastingOwnerAdjustment). They never overwrite the Amount field on the underlying Opportunity unless a user explicitly edits the Opportunity record list in the lower pane.
  • The Forecast Hierarchy is distinct from record sharing: Although a role-based Forecast Hierarchy is generated automatically from your org's User Role Hierarchy, an admin must explicitly enable users and assign a designated Forecast Manager at each manager node in Setup (Forecasts Hierarchy) for subordinate numbers to roll up cleanly.

⚙️ Concept: How Collaborative Forecasts Aggregates Pipeline

Standard Opportunity reports and dashboards are great for slicing pipeline by industry or lead source, but they struggle to capture the human side of sales management: quota attainment per period and top-down executive judgment. When managers export Salesforce reports into private spreadsheets just to apply their own "haircut" to an overly optimistic rep's pipeline, leadership loses a single source of truth. Collaborative Forecasts is Salesforce's native Sales Cloud solution for structured, hierarchical revenue projection.

To understand how a deal moves from a rep's screen into the VP of Sales' quarterly commit number, let's trace the four building blocks of Collaborative Forecasts:

  1. Forecast Types (ForecastingType): A Forecast Type defines the data source and measure for a specific forecast view. Out of the box, organizations commonly start with Opportunity Revenue (rolling up the standard Amount field) or Opportunity Quantity. For complex selling models, you can activate multiple Forecast Types simultaneously—such as forecasting by Product Family (to separate Hardware vs. SaaS targets), Opportunity Revenue Splits or Overlay Splits (when multiple reps share credit on one deal), Line Item Schedules (when revenue is recognized across future delivery months), or a Custom Currency/Number Field on the Opportunity (such as Annual Recurring Revenue, ARR__c).
  2. Rollup Display (Single Category vs. Cumulative Rollups): In Forecasts Settings, admins choose how the category columns behave. Under Single Category Rollups, each column shows only the total of deals sitting in that exact category (Pipeline, Best Case, Commit, Closed). Under Cumulative Forecast Rollups, columns aggregate progressively so leadership doesn't have to do mental math: the Commit Forecast column automatically sums Closed + Commit deals, the Best Case Forecast column sums Closed + Commit + Best Case, and the Open Pipeline column sums all open categories.
  3. Hierarchy Basis (Role vs. Territory): By default, Collaborative Forecasts aggregates numbers upward along the Role-Based Forecast Hierarchy. Every Opportunity's value rolls up from the Opportunity Owner (or Split Owner) to the user designated as the Forecast Manager for their parent role. Alternatively, if your organization uses Enterprise Territory Management (ETM) and sells across matrixed geographic or industry pods rather than strict HR management lines, you can create a Territory-based Forecast Type that rolls Opportunity amounts up the active Territory Hierarchy instead.
  4. Quotas (ForecastingQuota) and Adjustments: Enabling Show Quotas in Forecasts Settings lets admins or managers load target revenue or quantity goals per user (or per territory), per Forecast Type, and per fiscal period. Alongside quotas, admins can enable Manager Adjustments (allowing a Forecast Manager to adjust a direct subordinate's category total) and Owner Adjustments (allowing a rep or manager to adjust their own summary number) with optional adjustment notes for auditability.
Diagram illustrating how Salesforce Collaborative Forecasts rolls up Opportunity amounts by Forecast Category across the Role or Territory Hierarchy alongside Quotas and Manager Adjustments
🧠 Core Rule: Collaborative Forecasts = Opportunity measures rolled up a Role or Territory Hierarchy by Forecast Category and Date Period, paired with Quotas and visible Manager Adjustments.
🧭 360 Card — Collaborative Forecasts

Rule: Deal amounts (or quantities/schedules) roll up the Forecast Hierarchy into period buckets sorted by Forecast Category, producing one authoritative projection per period.
Benefit: Replaces disconnected manager spreadsheets with a live grid where executive overrides are visibly tracked next to the raw bottom-up pipeline.
Tradeoff: The forecast grid is only as accurate as your underlying metadata. A single Opportunity Stage mapped to the wrong Forecast Category, an unpopulated CloseDate, or a missing Forecast Manager assignment in the hierarchy will skew the rollup.
Boundaries: You can activate up to four Forecast Types in standard orgs (check your specific edition's limits in Setup). Quotas must be loaded per Forecast Type, per user/territory, and per period. Manager adjustments apply to the summary category cell in the forecast grid rather than changing individual Opportunity field values.
Volume & Hierarchy Design: Because role-based forecasts follow the User Role tree, an overly deep or fragmented Role Hierarchy creates extra clicks for executives drilling down into deals and increases recalculation overhead when users change roles mid-quarter.

🛠️ Worked Example: Auditing Missing Deals and Loading Quotas via SOQL & Apex

📋 Illustrative Implementation & Troubleshooting: Imagine you enable an Opportunity Revenue Forecast Type for Q3. A regional sales director opens the Forecasts tab and reports two issues: first, her team's Commit rollup is missing ₹15,00,000 from a rep who recently transferred into her division; second, the "Quota Attainment %" column is blank for her entire team. Let's walk through how to diagnose the hierarchy and category gap, and how to load ForecastingQuota records programmatically or via Data Loader.

Part 1: Diagnosing why a deal is missing from a manager's Forecast rollup

When an Opportunity's amount fails to appear in the expected manager's Forecast Category column, run through these four diagnostic checks (you can execute the read-only SOQL queries below in Developer Console or Salesforce Inspector by substituting your own record IDs):

-- 1. Inspect the Opportunity's date, stage, forecast category, and owner role
SELECT Id, Name, Amount, CloseDate, StageName, ForecastCategory, ForecastCategoryName,
       OwnerId, Owner.Name, Owner.UserRole.Name, Owner.ForecastEnabled
FROM Opportunity
WHERE Id = '006XXXXXXXXXXXXAAA'

-- 2. Check active Forecast Types in the org
SELECT Id, DeveloperName, MasterLabel, IsActive, IsAmount, IsQuantity, DateType
FROM ForecastingType
WHERE IsActive = true
  • Check 1 — Owner.ForecastEnabled ("Allow Forecasting" checkbox): Even if a sales rep owns open Opportunities and sits in the right Role, their deals will not roll up properly in Collaborative Forecasts—and they cannot view the Forecasts tab—unless the Allow Forecasting checkbox (ForecastEnabled = true) is checked on their User record in Setup.
  • Check 2 — Forecast Hierarchy Manager Assignment: In Setup under Forecasts Hierarchy, each manager role requires a designated Forecast Manager user. If the regional director's role node does not have her User selected as the Forecast Manager, subordinate role numbers cannot aggregate into her personal forecast view.
  • Check 3 — Date Type Mismatch: A Forecast Type can bucket revenue by CloseDate, ProductDate (Opportunity Product Service Date), or ScheduleDate. If the Forecast Type uses Product Date and the rep left ServiceDate blank or in next quarter, the deal rolls into a different period than its CloseDate.
  • Check 4 — Custom Forecast Filters: In Forecasts Settings, admins can add custom filter criteria to a Forecast Type (for example, RecordType.Name = 'New Business'). Any Opportunity that fails the filter is excluded from that Forecast Type's rollup.

Part 2: Loading Quotas via ForecastingQuota

Once Show Quotas is enabled in Forecasts Settings and the running user has the Manage Quotas and View All Forecasts permissions, you can load quotas either via the native Forecasts Quotas setup page in Lightning or in bulk via API / Data Loader / Apex using the ForecastingQuota object.

The illustrative Apex snippet below shows how ForecastingQuota connects a ForecastingTypeId, a QuotaOwnerId, and a StartDate matching the exact start date of an active fiscal period in your org. Note that this snippet is an excerpt that was not executed in a live org during drafting; test it in a Sandbox after enabling Collaborative Forecasts and Quotas:

// 1. Query the active Opportunity Revenue Forecast Type
ForecastingType revType = [
    SELECT Id 
    FROM ForecastingType 
    WHERE DeveloperName = 'OpportunityRevenue' 
      AND IsActive = true 
    LIMIT 1
];

// 2. Upsert or insert a Quota for a specific Forecast-enabled User
// StartDate MUST match the exact first day of a valid forecast period (month or quarter)
ForecastingQuota q3Quota = new ForecastingQuota(
    ForecastingTypeId = revType.Id,
    QuotaOwnerId = '005XXXXXXXXXXXXAAA', // Replace with active Sales Rep UserId
    StartDate = Date.newInstance(2026, 10, 1), // First day of the fiscal period
    QuotaAmount = 4000000.00 // ₹40L target (set CurrencyIsoCode if multi-currency is enabled)
);
insert q3Quota;

Validation steps: After inserting the ForecastingQuota record in a Sandbox, open the Forecasts tab, select the Opportunity Revenue Forecast Type from the top dropdown, navigate to the October 2026 (or Q4) period for that user, and verify that the Quota column displays 4,000,000.00 and the Quota % progress bar dynamically calculates attainment against their Closed and Commit columns.

⚠ Common Mistake & Interview Trap: A very common misconception is that adding a user to a Manager Role in the standard User Role Hierarchy automatically makes them the Forecast Manager for everyone below them. In Salesforce, you must also check Allow Forecasting on the user's record and verify in Setup → Forecasts Hierarchy that the manager is explicitly assigned as the role's Forecast Manager. Without that assignment, the branch appears unassigned on the Forecasts Hierarchy tree and subordinate numbers fail to roll up to that manager's view.

❓ Core Questions and Scenario-Based Answers

Q: Set up forecasting so managers see their team's pipeline weighted by category with quotas. What are the key choices?
🎯 Say this first: Enable Collaborative Forecasts, configure the Forecast Hierarchy (Role or Territory) and enable users with "Allow Forecasting," create and activate the appropriate Forecast Type (such as Opportunity Revenue), verify Stage-to-Forecast Category mappings and Cumulative vs. Single rollup settings, and enable Quotas and Manager Adjustments.

Walk through these five architectural and setup steps to deliver a complete manager forecasting view:

  1. Enable Collaborative Forecasts & Define Period Display: In Setup, go to Forecasts Settings and turn on Collaborative Forecasts. Configure the default forecast period display (Monthly or Quarterly, and how many periods forward and backward users can view) to match your org's fiscal calendar.
  2. Select the Hierarchy Basis and Assign Forecast Managers: Decide whether revenue rolls up the standard Role Hierarchy or an active Enterprise Territory Management model. Check the Allow Forecasting box on every participating rep and manager User record, and assign the designated Forecast Manager for each management node under Setup → Forecasts Hierarchy.
  3. Create and Activate Forecast Types: Choose what measure you are forecasting. Start with Opportunity Revenue (Amount) for standard deal tracking, or create additional Forecast Types for Product Families, Opportunity Splits, Line Item Schedules, or custom currency/number fields if your business measures ARR or multi-year installments.
  4. Align Forecast Categories and Rollup Style: Audit your Opportunity StageName picklist values to confirm each stage maps to the right Forecast Category (Pipeline, Best Case, Commit, Omitted, or Closed). Decide whether leadership wants Single Category Rollups (each bucket isolated) or Cumulative Forecast Rollups (where the Commit column automatically includes Closed + Commit).
  5. Configure Quotas and Adjustment Governance: Enable Show Quotas in Forecasts Settings and load user targets via the Forecasts Quotas setup UI or Data Loader (ForecastingQuota). Finally, decide whether Forecast Managers can adjust subordinates' forecasts and whether reps can adjust their own summary numbers.
Q1: Forecast numbers look wrong — deals aren't in the expected category. Where do you look?

When a sales leader reports that deals are missing from a forecast column or the rollup total doesn't match their pipeline report, troubleshoot in this order:

  • 1. Stage-to-Forecast Category Mapping & Manual Overrides: Check the Opportunity's StageName definition in Object Manager. If a late stage is mapped to Pipeline instead of Commit, every deal in that stage lands in the wrong column. Also check if reps have edit access to the Forecast Category field on the Opportunity layout and manually overrode the category on specific records.
  • 2. Forecast Hierarchy & "Allow Forecasting" Status: Verify that the Opportunity Owner sits in the expected child role beneath the manager, that the owner has Allow Forecasting enabled on their User record, and that the manager is assigned as the Forecast Manager in the Forecasts Hierarchy.
  • 3. Date Field and Fiscal Period Alignment: Confirm which date field the active Forecast Type uses (CloseDate, ProductDate, or ScheduleDate). A deal closing on October 1st will not appear in a Q3 forecast view ending September 30th.
  • 4. Forecast Type Filters & Split Percentages: If the Forecast Type uses custom Opportunity filters or rolls up based on Opportunity Splits, check whether the deal meets the filter criteria and whether the rep's OpportunitySplit percentage is less than 100%.
  • 5. Active Manager or Owner Adjustments: Look for the adjustment icon next to the summary number on the Forecasts grid. If a manager previously typed a manual override into the Commit cell, the grid displays the adjusted amount until the adjustment is recalculated or removed, even as underlying Opportunities change.
Q2: The company sells via territories, not a strict management hierarchy. How does forecasting adapt?

When sales coverage is organized by geography, named accounts, or industry verticals rather than HR reporting lines—for example, a rep reports to a Commercial Sales Director for HR purposes but closes deals inside both the "India North" and "Middle East" territories—role-based forecasting rolls all of that rep's deals up to one HR manager. To align the forecast with actual market territories, enable Territory Forecasts using Enterprise Territory Management (ETM):

  • Activate an ETM Model: Build your territory tree in Setup under Territory Models (for example, APAC → India → India North), configure assignment rules to assign Accounts and Opportunities to territories, and set the Territory Model state to Active.
  • Assign Forecast Managers to Territories: Inside the active Territory Hierarchy, assign a specific user as the Forecast Manager on each parent territory node where you want rollups and manager adjustments to occur. Users assigned to a leaf territory without a Forecast Manager roll their territory deals directly into the territory total.
  • Create a Territory-Based Forecast Type: In Forecasts Settings, create a new Forecast Type and select Territory as the hierarchy basis (available for Opportunity Revenue, Opportunity Quantity, and Product Family measures).
  • How deals roll up: An Opportunity rolls into a territory's forecast based on the Territory2Id field stamped on the Opportunity record, completely decoupling regional revenue projections from the org's User Role chart.

🔗 Next Concept & Self-Check

📝 Self-Check Question: A sales rep owns a ₹10,00,000 Opportunity in the Negotiation/Review stage (mapped to Commit). Her sales manager thinks the buyer will negotiate a 20% discount before signing, so the manager uses the Forecasts tab to adjust the rep's Commit summary cell down by ₹2,00,000. What happens to the Amount field on the underlying Opportunity record, and what does the VP of Sales (one level higher in the Forecast Hierarchy) see?

Answer & Explanation: The Amount field on the underlying Opportunity record remains unchanged at ₹10,00,000. Manager adjustments on the Forecasts grid are stored separately on the forecast adjustment object and never overwrite Opportunity record data. However, when the forecast rolls up to the VP of Sales one level higher in the Forecast Hierarchy, the VP's rollup total incorporates the manager's adjusted figure (reflecting the ₹2,00,000 reduction) while displaying an indicator icon so the VP can inspect both the raw unadjusted pipeline and the manager's adjustment note.
Follow-Up Question: What if two sales reps collaborate on a single ₹50,00,000 Opportunity and need to split the forecast credit 60/40 across two different managers?

By default, a standard Opportunity Revenue forecast gives 100% of the deal's forecast credit to the single OwnerId on the Opportunity. When multiple sellers share revenue credit on the same deal, enable Opportunity Teams and Opportunity Splits in Setup. Salesforce provides two built-in split types: Revenue Splits (which must always total exactly 100% across the team members on the deal—such as 60% for the primary AE and 40% for a specialist AE) and Overlay Splits (which can total any percentage above or below 100% for solution engineers or channel managers). Once you create a Forecast Type based on Opportunity Revenue Splits, ₹30,00,000 (60%) rolls up to the primary rep's Forecast Manager and ₹20,00,000 (40%) rolls up to the specialist rep's Forecast Manager automatically, without duplicating the Opportunity record.

Was this article helpful?

Have a question or spotted a mistake? Ask here about this article

Found this guide useful? Buy me a coffee (opens in a new tab)

Comments

Questions, corrections and your own experience are all welcome.