> 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/create-a-workforce-plan/model-employees-who-dont-receive-an-annual-salary.md).

# Model employees who don't receive an annual salary

Workforce Planning currently supports only [annualized measure values](/budgets-and-forecasts/workforce-planning/overview-of-workforce-planning/workforce-planning-foundations.md#annualized-values-and-spreading). To model hourly paid employees, store the hourly rate and hours worked in custom properties, then use a calculated static measure to derive an annualized salary.

### Set up the columns

In the plan setup, add the following [columns](/budgets-and-forecasts/workforce-planning/create-a-workforce-plan.md#set-up-the-columns):

* A custom property **Hourly rate**. For example, $35 per hour.
* A custom property **Number of hours**. For example, 40 hours per week.
* A static measure with a formula that calculates the annualized salary. For example, Hourly rate × Number of hours × 52 weeks per year.

Use a static measure (rather than an effective-dated measure) for the formula. Formulas work best when they don't change over time.

Change the underlying properties (Hourly rate and Number of hours) over time to reflect changes; the formula recalculates automatically.

If you need to model varying weeks per year, add a third custom property (for example, Weeks per year) and reference it in the formula. This lets you increase the number of paid weeks in some years to reflect your business calendar.

### Enter hourly employee data

When you [add or import employees](/budgets-and-forecasts/workforce-planning/create-a-workforce-plan/add-employees.md), enter values for the **Hourly rate** and **Number of hours** columns instead of a direct salary figure. The static measure calculates the annualized salary automatically.

If an employee's hourly rate or hours change over time, edit the property values from the effective date. The recalculated salary flows through automatically.

***

### Learn about how the values are published

When you [publish the plan](/budgets-and-forecasts/workforce-planning/create-a-workforce-plan/publish-a-workforce-plan.md):

* The calculated annualized salary is spread into daily transactions in the Flex Modes database, using the configured spread method.
* The underlying **Hourly rate** and **Number of hours** properties are published alongside the salary transactions.

The properties are available for analysis:

* In Flex Modes, they are visible in the transaction view alongside the calculated salary.
* In Budgets & Forecasts, use a Reference tab in a multi-measure row or the output view on a Planning tab.

{% hint style="warning" %}
Properties don't aggregate meaningfully at higher levels. For example, summing Hourly rate across employees produces a total that isn't a real hourly rate. View properties at the employee level for accurate values.
{% endhint %}


---

# 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/workforce-planning/create-a-workforce-plan/model-employees-who-dont-receive-an-annual-salary.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.