Allow users to schedule forecast model changes to take effect at a specific future date, rather than applying immediately.
C
Connie
Current Behavior:
When a user selects “Set as current model,” the change takes effect immediately for all future forecasts, regardless of the date range selected in the Forecast Review page. The date range currently only affects what’s displayed for comparison, not when the model becomes active.
Requested Behavior:
Enable users to specify an effective date for activating a forecast model (e.g., switch to the Seasonal model starting December 1, 2025). This would allow teams to plan and automate seasonal or event-based model changes without needing manual intervention.
Example Use Case:
A team wants to:
- Use the 8-week average model through November
- Automatically switch to the Seasonal model for December
Currently, this requires a manual change on Dec 1. Scheduling it in advance would save time and prevent human error.