> 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/contributor/analyze-workforce-data.md).
# Analyze workforce data
Analyze workforce data to support business decisions about employee costs and benefits.
After you publish a workforce plan, you can analyze its data in the Workforce database using [Flex Modes](https://docs.phocassoftware.com/flex-modes/). Each plan is published as a separate stream named to match the plan.
If you have access to the Workforce database, it displays in the list of databases under Flex Modes in the Phocas navigation menu.
1. In the Phocas navigation menu, open **Flex Modes** and click **Workforce**.
2. If several workforce plans have been published, select the required plan from the **Stream** menu. The plan's data displays in the grid.
{% hint style="info" %}
If you're not familiar with Flex Modes, see [Take a tour of Flex Modes](/flex-modes/take-a-tour-of-flex-modes.md) for an overview.
{% endhint %}
### How the data is structured
When you publish a workforce plan, its employee information, measures, and other data are structured in the Workforce database as follows.
#### Employee data
Each employee is published as an entity in the **Employee** dimension, with their unique employee ID as the **Code**. The employee name is published as a property of the **Employee** dimension.
Employee dimension view of the workforce plan data
#### Remuneration data (measures)
Each remuneration measure, such as **Salary**, **Bonus**, **Commission**, and **Pension**, is published as an individual measure. A **Total** measure is also published to display the sum of all remuneration measures.
Measures menu
The measures are also published as entities in the **Measure** dimension, giving you additional flexibility when analyzing the data.
Measure dimension view of the workforce plan data
{% hint style="success" %}
The **Measure** dimension uses system-generated codes. When you view this dimension, to make the data easier to read, use the **Properties** menu to hide **Code** and show **Name** instead.
{% endhint %}
#### Custom data
Custom properties from the workforce plan are published as transaction properties in the Workforce database. You can view them in transaction view only.
### Analysis examples
Because measures are published both as individual measures and as entities in the **Measure** dimension, you have two ways to drill down into the data.
#### View measures vertically
This view is useful for analyzing the components of each employee's remuneration across time.
1. Drag the **Employee** and **Measure** dimensions into the [**Nest view**](/flex-modes/customize-the-grid/create-a-nested-view.md) dropzone.
2. Select the **Total** measure from the **Measures** menu.
3. Expand an employee row in the grid. Each remuneration component and each benefit displays as a row, so you can see exactly what makes up total remuneration for each employee.
Nested view of employee and remuneration data
#### View measures side-by-side
This view is useful for comparing specific measures across employees or other dimensions. Don't include the **Total** measure, as this would double-count the values.
1. Use the **Measures** menu to select the measures you want to view in the grid.
2. Click the **Employee** dimension.
---
# 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/contributor/analyze-workforce-data.md?ask=&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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)