> 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/owner-and-administrator/add-worksheet-tabs/planning-tab.md).

# Planning tab

Add a Planning tab in your financial budget workbook to drive expense accounts that depend on employee costs or headcount.

{% hint style="info" %}
User permissions: Budgets & Forecasts and Manage Budgets & Forecasts
{% endhint %}

The Planning tab brings published workforce plan data into your financial budget. Use employee-related costs, such as wages, commissions, and benefits, and reference properties such as FTE and headcount, to drive accounts in the Main tab.

{% hint style="info" %}
**Prerequisite**: [Publish the workforce plan](/budgets-and-forecasts/workforce-planning/create-a-workforce-plan/publish-a-workforce-plan.md) in Workforce Planning.
{% endhint %}

1. Either click the **Budget** menu > **Add tab** or click the **Add tab** button (at the bottom of the workbook), then select the **Planning** tab type.
2. On the **Configuration** tab, complete each of the following:
   1. Enter a **name** for the tab. For example, *Salaries*.
   2. Select the **Workforce** **database**.
   3. Select the **stream** that contains the workforce plan data.
   4. Select the **measures** you want to use to drive accounts in the Main tab.
   5. Select the **reference properties** you want to include, such as FTE or headcount, then select how to aggregate each one.
      * **FTE** defaults to **Average**. Other options are **Period start**, **Period end**, and **Count**.
      * **Headcount** defaults to **Count**, which returns the number of active employees.
   6. Select how you want to map the measures to accounts:
      1. **Measure only**: Map each measure to one account. For example, map Salary to one salary account for all employees.
      2. **Measure and dimension**: Map each measure to different accounts based on a dimension. For example, map Salary to different accounts for each trading entity.
3. Click **Next**.
4. On the **Mapping Account** tab, select an account for each measure or dimension-measure combination.
5. Click **Save and finish**.

The **Planning** tab is added to the workbook and displays the workforce plan data at the mapped dimension levels.

Also, a sum row is added to the **Main** tab containing the mapped plan values.

#### About the sum row

The plan-driven values are added to the Main tab in a sum row rather than directly replacing existing values. This allows you to combine workforce plan values with other budget values.

For example, to include an ad-hoc adjustment, add another sum row.

The final value in the Main tab is the total of the plan-driven sum row and any additional sum rows.

#### Sync updates from the workforce plan

The data in a Planning tab is a point-in-time snapshot and doesn't automatically update when the workforce plan changes. Republish the workforce plan, then sync the Planning tab to bring in the latest values.

1. In Workforce Planning, make the changes and republish the plan.
2. In the Budgets & Forecasts workbook, open the budget and open the **Planning** tab.
3. Click the **Tab** menu, then click **Sync planning data**.

If there are no updates to bring through, a message displays indicating that no changes were made.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.phocassoftware.com/budgets-and-forecasts/owner-and-administrator/add-worksheet-tabs/planning-tab.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.