Litware's Forecast and Goal Alignment
Litware's fiscal year runs July through June. The company has six sales territories, a manager hierarchy, and annual quotas. Managers use forecast categories such as Pipeline, Best Case, Committed, Won, and Lost. Symptoms: forecast rollups are off by 10-15%; parent goals do not aggregate child goals; goal rollups are late; some opportunities do not appear in the forecast. Constraints: no custom code; use out-of-box forecast configuration and goal management; managers need historical snapshots; quotas must be visible by territory and by manager. The sales team uses the Opportunity entity with estimated revenue, estimated close date, and a territory field. The forecast must align to the fiscal year, not the calendar year, and must support manager review.
1. Configure the forecast to align with the fiscal year, territories, and manager hierarchy.
Read the worked answer
Reasoning: Forecast configuration starts with the fiscal year settings, which must be set to July-June before the forecast is created. Choose a forecast that uses the Opportunity entity, includes the estimated revenue and estimated close date, and uses forecast categories that match the business labels. Add the territory as a forecast dimension so managers can review by territory, and use the manager hierarchy for rollups. Historical snapshots should be enabled so managers can compare previous forecasts. Opportunities may be missing because the forecast category is blank, the estimated close date falls outside the forecast period, or the territory is not populated. Check those fields and the forecast's security settings. Recalculate the forecast after changes.
2. Configure goal metrics and parent-child goals so that quotas aggregate by territory and manager.
Read the worked answer
Reasoning: Create a goal metric with the amount data type and a rollup field that points to opportunity estimated revenue. Set the goal period to the fiscal year and assign goals to the appropriate salespeople or teams. For parent goals, use the goal hierarchy and a rollup query that includes child goals. Parent goals aggregate only when the child goals are linked and the rollup job runs. Goal rollups are asynchronous, so late aggregation may be a timing issue rather than a configuration error. Verify that the goal's target and actual values use the same metric and that the rollup field is correct. Test with one territory and its manager.
3. Troubleshoot why forecast rollups are off by 10-15% and why some opportunities do not appear.
Read the worked answer
Reasoning: Start by comparing the forecast total with a view of open opportunities for the same period. Look for opportunities with blank estimated revenue, missing territory, or a forecast category that is not included in the forecast. Check whether the forecast period matches the opportunity close date and whether the opportunity is closed as Won or Lost. Also verify that the forecast hierarchy includes the managers and that the forecast is recalculated. A 10-15% gap often comes from opportunities owned by users outside the forecast hierarchy or from duplicate opportunities counted twice. Use the forecast snapshot to compare historical values and confirm whether the gap is constant or intermittent.