Stage Forecast Category Null Review

Preserve missing forecast-category mappings instead of inventing a default forecast bucket. Preparation only, not an account action.

What to provide

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

How it works

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.

The output

opportunity | stage | category_value | config_version | enabled_evidence | mapping_status | owner

Worked fictional example

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.

Checks and limits

Keep source versions and original values. Unknowns stay unknown. Use qualified review for regulated, legal or hiring decisions. No live account compatibility test, send, share, schedule, ledger change or payment is authorized.

More sales workflows · How-to guides

Method: reviewed source. Demand lead: 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. Checked October 8, 2026.