# Stage Forecast Category Null Review

Preserve missing forecast-category mappings instead of inventing a default forecast bucket.

## Scope
Preparation and review only. No account action or professional decision.

## Inputs
Stage IDs and forecast-category export; forecasting-enabled status; opportunity stage roster; owner bucket policy.

## Workflow
1. Match stages to a dated configuration export.
2. Separate explicit category, null category and absent stage row.
3. Explain that the documented stage default may be null when forecasting is not enabled; verify supplied status.
4. List opportunities with unresolved mapping and the configuration owner; never assign a category by probability.

## Output contract
opportunity | stage | category_value | config_version | enabled_evidence | mapping_status | owner

## Fictional acceptance test
Fictional stage S 1 has probability 50% but category null. Hold its forecast bucket; do not turn 50% into Best Case. S 2 absent from the export is a different missing-row exception.

## Review gates
Keep original values, source IDs and version dates. Unknown facts stay held. Use qualified review for hiring, legal and accounting conclusions. No send, share, sign-in, scheduling, ledger change or payment. Fictional contract review is not a live account compatibility test.

## Method source
https://developer.salesforce.com/docs/atlas.en-us.uiapi.meta/uiapi/ui_api_responses_opportunity_stage_picklist_values.htm

Checked October 8, 2026. Oct8 live GSC through Oct5: marketing copilot 37 impressions, Planable/Claude 33 and Planable/ChatGPT 23, campaign brief 12 and reports 11. Marketing/social topics follow these parent-query leads; other professions follow method-source workflow needs, not exact query measurements. Exact monthly volume is unmeasured.