Your forecast can keep changing even after you've adjusted it, because Assembled recalculates forecasts automatically. If you need a forecast to hold steady for scheduling or reporting, you can request a forecast lock from Assembled support.
Why does my forecast change after I've already adjusted it?
Adjustments you make on the Manage forecasts page do apply to the Support Volume page and other reports. Once saved, an adjustment overrides the base forecast for those intervals.
The base forecast underneath your adjustment can still change, though. Saving an adjustment triggers an automatic forecast regeneration (this happens by default, since forecast auto-generation is normally turned on), and forecasts also regenerate on their own once a day. Either kind of regeneration recalculates the base forecast, and your adjustment is then applied on top of that new base, which can shift the final total even though your adjustment itself hasn't changed.
Keep in mind: Outliers don't stack directly with your adjustments. Marking an interval as an outlier excludes that historical data from model training, which can change the base forecast your adjustment is layered on top of.
How do I confirm my adjustments are still in place?
- Go to Forecasts > Manage forecasts.
- Select the channel and queue, then choose your date range.
- Open the Adjust tab. Your adjustments for that channel, queue, and date range are listed there.
If your adjustments are showing up and the forecast hasn't regenerated since you made them, they're in effect.
How do I lock a forecast so it stops changing?
A forecast lock stabilizes a forecast for a chosen period so it stops updating automatically. Locking isn't self-serve today — request it from Assembled support at support@assembledhq.com, or through your account manager or CSM if you have one, with the channels, queues, and date range you want locked.
Important: A lock stops automatic daily regeneration, but it doesn't block manual changes. Any new adjustments, outliers, totals, model changes, or saved reforecasts you make for the locked dates will still overwrite the locked forecast.
What's the difference between the forecast lock preview and an actual lock?
The Forecast lock preview slider on Forecasts > Management is a simulation: it shows how accurate your models would have been at a given lead time. It doesn't freeze your live forecast. To actually stop a forecast from updating, request a lock from Assembled support as described above.
How does the rolling lock window work?
A forecast lock is a rolling window measured from today, not a fixed date range. For example, a 120-day lock covers the next 120 days from whenever you check it: if it covers January through April this month, it will cover February through May next month, and so on. The length of the window stays the same, but the dates it covers shift forward over time. If you need the window's length changed, ask Assembled support to update it.
Should I lock a long period, or a shorter one?
This depends on your forecast model and how much accuracy you're willing to trade for stability.
With a rolling-average model (for example, one based on the most recent 4 weeks of data), a long lock means later months in the locked period are still based on that same original window of data, without picking up newer trends or seasonal changes. The further out you go, the more the forecast can drift from what's actually happening.
A shorter lock (for example, 4–6 weeks), rolled forward periodically, usually keeps a better balance between stability and accuracy for models like this. A longer lock, like a full quarter, favors stability and is a reasonable choice if your team tracks and adjusts volume manually and doesn't need the model to pick up new trends during the locked period.
Note: Let Assembled support know which trade-off you'd prefer when you request a lock, and they can walk through the specifics for your model before setting it.
Questions? Contact support@assembledhq.com and we'll be glad to help.
Comments
0 comments
Article is closed for comments.