> For the complete documentation index, see [llms.txt](https://docs.phocassoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phocassoftware.com/budgets-and-forecasts/workforce-planning/overview-of-workforce-planning.md). # Overview of Workforce Planning {% hint style="info" %} **EARLY ACCESS**: The content on this page is temporary and subject to change. These changes are currently being rolled out, so you'll see them in your site soon. {% endhint %} Workforce Planning is a standalone planning tool for modeling employee costs and workforce changes over time. To use Workforce Planning, you need a Budgets & Forecasts license. ### How it works You set up a plan with the measures, dimensions, and benefits you need, add or import your employees, then forecast changes such as pay reviews, promotions, transfers, expansions or restructures. When you publish the plan, the salary and benefit values are projected into a dedicated Workforce database. From there, you can analyze workforce data on its own or bring it into a Budgets & Forecasts workbook to drive expense accounts. You enter costs into a workforce plan as annual values. When you publish the plan, the tool spreads these annualized values into daily transactions in the database.
### Getting started Before you use Workforce Planning, ensure you read and understand the following pages: * [Workforce Planning foundations](/budgets-and-forecasts/workforce-planning/overview-of-workforce-planning/workforce-planning-foundations.md): Understand perpetual plans, temporal cells, and annualized values before you build a workforce plan. * [Workforce Planning access and database permissions](/budgets-and-forecasts/workforce-planning/overview-of-workforce-planning/workforce-planning-access-and-database-permissions.md): Understand how database permissions and restrictions protect sensitive information in a workforce plan. * [Key differences from Headcount Planning](/budgets-and-forecasts/workforce-planning/overview-of-workforce-planning/key-differences-from-headcount-planning.md): If you use the Headcount tab in Budgets & Forecasts, compare the setup, data modeling, and workforce analysis to Workforce Planning. * [Workforce Planning FAQs](/budgets-and-forecasts/workforce-planning/overview-of-workforce-planning/workforce-planning-faq.md): Read through the answers to some common questions asked. You can then get to work: * [Take a tour of Workforce Planning](/budgets-and-forecasts/workforce-planning/take-a-tour-of-workforce-planning.md) * [Create a workforce plan](/budgets-and-forecasts/workforce-planning/create-a-workforce-plan.md) * [Add employees](/budgets-and-forecasts/workforce-planning/create-a-workforce-plan/add-employees.md) * [Manage employees](/budgets-and-forecasts/workforce-planning/create-a-workforce-plan/manage-employees.md) * [Model employees who don't receive an annual salary](/budgets-and-forecasts/workforce-planning/create-a-workforce-plan/model-employees-who-dont-receive-an-annual-salary.md) * [Publish a workforce plan](/budgets-and-forecasts/workforce-planning/create-a-workforce-plan/publish-a-workforce-plan.md) * [Use the workforce plan data](/budgets-and-forecasts/workforce-planning/use-the-workforce-plan-data.md) (includes export the plan) * [Analyze workforce data](/budgets-and-forecasts/contributor/analyze-workforce-data.md) * [Planning tab](/budgets-and-forecasts/owner-and-administrator/add-worksheet-tabs/planning-tab.md) * [Delete a workforce plan](/budgets-and-forecasts/workforce-planning/delete-a-workforce-plan.md) *** ### Limitations Workforce Planning is designed to replace the existing Headcount planning functionality and introduces several new capabilities, such as custom dimensions, measure and properties, and effective-dated changes. However, some functionality is still under development. #### Security and access Access is currently managed at the workforce plan level. You can control who can access a plan, but you cannot yet restrict users to specific employees, divisions, locations, or other subsets of workforce data. #### Workflow management Workforce Planning does not currently include workflow features such as: * Assigning employees or departments to specific users. * Approval workflows — review and sign-off processes. * Locking completed sections of a plan. Any user with permission to edit a plan can update its data. #### Employee costing The initial release is optimized for salaried employees. Support for more advanced workforce modeling, such as hourly employees, variable work schedules, and seasonal staffing patterns, is planned for a future release. #### Benefits configuration Benefits are currently defined at the plan level. Location-specific or region-specific calculations, such as different payroll tax rates by state or country, are not yet available. #### Resource planning Workforce Planning currently focuses on employee planning only. Additional planning models, such as fixed assets, leases, subscriptions, and capital expenditure, are planned as part of a broader resource planning roadmap. #### Cash vs accruals basis Published workforce plans currently generate accrual-based workforce costs. Cash-flow timing scenarios, such as monthly, weekly, or quarterly payment schedules, are planned for a future release. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.phocassoftware.com/budgets-and-forecasts/workforce-planning/overview-of-workforce-planning.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.