Plan requirement
| Subscription | Any plan |
| Also required | Workforce Management |
| Access | Admin |
The limits that shape what you can build: teams, schedules, history and forecast horizon.
Where limits apply
- Teams and locations, how many you can define.
- History, how far back the data goes.
- Forecast horizon, how far ahead you can plan.
- Schedule length, the period one schedule covers.
- Intervals, the granularity of forecasts.
The exact figures are shown in the product and depend on your arrangement.
History is the one that bites first
Forecasting works from past volume. A new deployment has none, so early forecasts are poor, and that is expected rather than a fault.
Importing historical volume shortens that period considerably.
Interval granularity matters more than horizon
Half-hourly intervals show the Monday morning peak; daily totals hide it entirely. Since the peak is the reason to forecast at all, granularity is where the value sits.
Teams are a design decision, not a limit
Long before you reach any cap, a structure with twenty teams becomes unmanageable. Build teams around how you actually schedule people.
Plan the horizon around your rota
If schedules are published a month ahead, the forecast must reach at least that far with confidence. Check that before promising a publishing rhythm.
Ask before committing
If somebody expects year-ahead planning or minute-level tracking, confirm what is possible first. Contact pluscloud support and we will check it against your setup.
Comments
0 comments
Article is closed for comments.