Independent study lab
This is an independent, free, learning-only student project. It respects every company and vendor. Trademarks belong to their owners. It is not affiliated with or endorsed by Amazon Web Services, Cisco, Genesys, Salesforce, Twilio, or any other company. If you have a concern, the page will be removed or corrected promptly through the contact form. Nothing here is sold. There are no ads. The author is happy to volunteer for any organization.
Hiring plans and scheduling plans — Learn it in 5 minutes
About five minutes of reading
A hiring plan and a scheduling plan do not read the same forecasts.
A capacity plan turns forecasts and a scenario into staffing targets. A Hiring plan estimates long-term full-time equivalents, up to 64 weeks, and needs both a long-term and a short-term forecast. The capacity page recommends at least 4 weeks of overlap and requires at least 1 day.
A Scheduling plan needs only a published short-term forecast. It returns headcount in 15- or 30-minute intervals, matching that forecast, and the plan dates must sit inside the forecast dates. Plan override is not available for a Scheduling plan.
- Create a scenario before you create the plan.
- Shrinkage and available full-time equivalents can be imported. Hiring plans use day-level files. Scheduling plans use interval-level files.
- Task and email plans can start from an automatic backlog when you use an average time to complete.
- The getting-started list ends with review, then publish. Override and re-run are for hiring plans.
Number on this page: Hiring 64 weeks. Long-term full-time equivalent estimates
Sources and go deeper
- Capacity planning in Connect Customer - Amazon Connect Customer AWS docs. last checked 2026-10
- Forecasting in Connect Customer - Amazon Connect Customer AWS docs. last checked 2026-10
- Forecasting & agent scheduling in Connect Customer - Amazon Connect Customer AWS docs. last checked 2026-10