Collaborative Forecasting Types and Adjustments

Why This Topic Matters
Collaborative Forecasting sits inside the Advanced Cloud Applications domain of the Salesforce Advanced Administrator exam, and it is one of the most heavily tested Sales Cloud configuration areas. Sales leaders depend on forecasts to predict revenue, manage pipeline risk, and plan hiring and spend. An administrator who misconfigures forecast types, rollups, or adjustments can wipe out months of manager judgment calls or produce numbers nobody trusts. The exam tests whether you understand the design decisions (which forecast type, which measurement, which date, which rollup method) and the operational consequences (what happens to adjustments when settings or the hierarchy change). Expect scenario questions that describe what a VP of Sales wants to see, and ask you to pick the configuration that delivers it.

What Collaborative Forecasting Is
Collaborative Forecasts is the modern forecasting tool in Sales Cloud (the older Customizable Forecasting has been retired). It projects sales by rolling up opportunity data through a hierarchy, grouped into forecast categories over a defined period. Key building blocks you must know:
• Forecast hierarchy - By default it mirrors the user role hierarchy. Each role can have a designated forecast manager who sees and can adjust the forecasts of everyone beneath them. With Enterprise Territory Management you can instead forecast by the territory hierarchy.
• Forecast users - Users must have the Allow Forecasting permission and be enabled in the forecast hierarchy to appear in forecasts.
• Forecast period and range - Monthly or quarterly periods, using standard or custom fiscal years. You set how many periods back and forward to display (for example, 3 months in the past through 7 months ahead).
• Forecast categories - Pipeline, Best Case, Commit, Omitted, and Closed. Each opportunity stage maps to one category (set on the Stage picklist values). Users with field access can override the category on an individual opportunity.
• Quotas - Optional targets per user per period, loaded through the UI, Data Loader (ForecastingQuota object), or API, so the forecast page can show quota attainment.

Forecast Types
A forecast type defines what is being forecast, how it is measured, and which date places it in a period. You can have up to four active forecast types at once, and users switch between them on the forecasts page. The main options:
• Opportunities - Forecast on the opportunity Amount (revenue) or on Quantity. The most common type.
• Opportunity Splits - Requires Opportunity Teams and Opportunity Splits to be enabled. Forecasts revenue split types (where percentages must total 100 percent) so each rep is credited with their share of a deal. Overlay splits can also be forecast so overlay roles such as sales engineers get credit without double counting the main pipeline.
• Product Families - Rolls up opportunity line items by product family, measured in revenue or quantity. Requires Products and Product Schedules considerations to be understood; the product family picklist must be populated.
• Opportunity Products / Line Items - Forecast at the line item level, useful when products have different dates from the opportunity close date.
• Custom currency field - Forecast on a custom currency field on the opportunity (for example, Annual Contract Value or Margin) instead of Amount.
• Custom measure - Forecast on a custom number or currency field for non-standard measures.
• Territory forecasts - When Enterprise Territory Management is enabled, forecast types can roll up by territory instead of role.

Each type also has a date type: Close Date (default), Product Date (for line items), or Schedule Date (for product revenue or quantity schedules). A single forecast type uses one measurement, one date, and one hierarchy. If a business needs revenue and quantity for the same object, that is two forecast types.

Rollup Methods: Individual vs Cumulative
This is heavily tested. You choose one rollup method per org.
• Individual Forecast Category Rollups - Each column shows only its own category. Commit shows only deals in Commit, Best Case shows only Best Case, and so on.
• Cumulative Forecast Rollups - Columns accumulate from most likely to least likely: Closed Only = Closed; Commit Forecast = Closed + Commit; Best Case Forecast = Closed + Commit + Best Case; Open Pipeline = Pipeline + Best Case + Commit. Managers like this view because the Commit Forecast column answers the question what will we actually book this period without adding columns together.
Remember: switching rollup methods purges existing adjustments.

Forecast Adjustments
Adjustments let people apply judgment to the numbers without touching the underlying opportunities. There are two settings in Forecasts Settings:
• Manager adjustments (Enable forecast adjustments) - A forecast manager can adjust the forecast amount of any direct subordinate, and can also adjust their own total. Managers above them can adjust further.
• Owner adjustments (Enable owner adjustments) - Every forecast user can adjust their own forecast amounts.
Important behaviors to memorize:
• Adjustments change the forecast number only. Opportunity records are never modified, and the original rolled-up amount is retained and visible on hover.
• Adjusted cells show a visual indicator (an edit icon). Hovering reveals the amount without adjustments, the adjusted amount, who adjusted it, and an optional note explaining why.
• Adjustments are made to open categories such as Best Case and Commit (and Pipeline or Open Pipeline depending on your rollup settings). The Closed or Closed Only column can never be adjusted because it reflects booked revenue.
• If both an owner adjustment and a manager adjustment exist for the same cell, the manager adjustment takes precedence in the manager's view and in rollups above the manager. The owner still sees their own adjustment on their own page.
• Adjustments are specific to a forecast type, period, and category. Adjusting Commit for a Revenue type does not adjust the Quantity type.
• Adjustments roll up. If a manager adjusts a rep from 100,000 to 120,000, the manager's own total and every level above reflects 120,000 (unless someone higher adjusts again).

When Adjustments Are Purged
Exam writers love this because it has real consequences. Adjustments are deleted when you:
• Disable manager adjustments or owner adjustments (the corresponding adjustments are purged).
• Change the forecast hierarchy - moving a user to a different role or changing the forecast manager purges adjustments for the affected users.
• Change or delete a forecast type, or change its measurement (revenue to quantity) or date type.
• Change the forecast period (monthly to quarterly or vice versa) - this also affects quotas.
• Switch between individual and cumulative rollups.
• Change the forecast category mapping of stages? No - remapping stages changes underlying amounts but does not itself purge adjustments; however, totals shift under the adjustments, so warn users.
Best practice: communicate changes, make them at period boundaries, and export Forecasting Items report data first.

Visibility, Sharing, and Reporting
• Forecast managers see their own forecasts and everyone below them. Users with the View All Forecasts permission can view any user's forecasts.
• In Lightning, a forecast manager can share their forecast page with other users (for example, a sales operations analyst) without changing the hierarchy.
• Use the Forecasting Items and Forecasting Quotas custom report types. Forecasting Items exposes fields like Forecast Amount, Amount Without Adjustments, Amount Without Manager Adjustment, and Owner Only Amount, so you can audit who adjusted what.
• Forecasts are only as good as the stage-to-category mapping and close date hygiene; validation rules and opportunity list views are common supporting recommendations.

How It Works End to End
1. Enable Collaborative Forecasts in Setup and grant Allow Forecasting to users via profile or permission set.
2. Define up to four forecast types, each with object, measurement, and date type.
3. Choose the rollup method, forecast period, and display range.
4. Decide on adjustments (manager, owner, or both) and whether to show quotas.
5. Build the forecast hierarchy by assigning forecast managers to roles (or configure territory forecasts).
6. Verify stage-to-forecast-category mappings on the Opportunity Stage field.
7. Load quotas and add the Forecasts tab to the Sales app.
8. Train managers to review, adjust with notes, and use reports to reconcile.

Exam Tips: Answering Questions on Collaborative Forecasting Types and Adjustments
• Count the requirements. If a scenario needs revenue and quantity, or opportunity revenue and product family revenue, it needs multiple forecast types. Remember the limit of four active types.
• Splits means Opportunity Splits must be enabled first. Any question about crediting multiple reps or overlay roles points to the Opportunity Splits forecast type with Opportunity Teams and Splits enabled.
• Product-based questions - Forecasting by product line or category means the Product Family type; dates that differ from the opportunity close date point to Product Date or Schedule Date.
• Custom financial metric (ACV, margin, bookings) - Choose a forecast type based on a custom currency or custom measure field, not a formula hack on Amount.
• Cumulative keywords - If a manager wants one column that includes Closed plus Commit, answer Cumulative Forecast Rollups. If they want each category shown separately, answer Individual Forecast Category Rollups.
• Adjustments never change opportunities. Any answer suggesting adjustments update the Amount field or the stage is wrong. Adjusting a forecast and editing an opportunity are different actions.
• Who can adjust - Managers adjusting subordinates requires manager adjustments enabled; reps changing their own numbers requires owner adjustments enabled. Both can be on at once; the manager's adjustment wins in rollups.
• Closed is not adjustable. If a choice says adjust the Closed column, eliminate it.
• Adjustments disappeared - When a scenario says adjustments vanished after a change, look for a hierarchy change, forecast type change, period change, rollup change, or adjustments being disabled. The answer is almost always that the configuration change purged them, not a bug or a permission issue.
• Someone cannot see a forecast - Check that the user has Allow Forecasting, is enabled in the hierarchy, or needs View All Forecasts or a shared forecast page.
• Numbers look wrong - Think stage-to-forecast-category mapping, opportunities with close dates outside the range, or users not in the hierarchy before suspecting the forecast engine.
• Auditing adjustments - The correct answer is a report built on the Forecasting Items report type, not an opportunity report.
• Read for the keyword hierarchy: role-based hierarchy is default; territory-based forecasting requires Enterprise Territory Management.
• Eliminate retired features. Any answer referencing Customizable Forecasting is a distractor.

Quick Recap
Forecast types define what, how, and when you forecast (object, revenue or quantity, date type), with up to four active at once. Rollups are individual or cumulative. Adjustments let managers and owners apply judgment without altering opportunity data, are visible with notes and original amounts, cannot touch the Closed column, and are purged when hierarchy, type, period, rollup, or adjustment settings change. Master these rules and you will handle any Collaborative Forecasting scenario the exam presents.