Which wage keywords are available in CrewPlanner, and how do they work?

Wage keywords automatically insert wage information into contracts and legal documents.

CrewPlanner uses pieces of code called keywords to auto-fill information in legal documents and contracts. Two main keywords, both related to wage information, are ${user.hourly_wage} and ${wage}, each serving different purposes.

What is the ${user.hourly_wage} keyword used for?

It inserts the employee's specific hourly wage or a default wage.

The ${user.hourly_wage} keyword pulls the hourly wage directly from an employee's profile. If the employee’s wage isn’t specified, it uses the general wage settings from the configuration page. This ensures contracts reflect either the hourly wage of the employee profile or the default wage.

CrewTip! ${user.hourly_wage} is available for both legal documents and contract templates. Use it when you need to reflect an employee-specific wage or, if not set, the default wage for the relevant contract type.

What is the ${wage} keyword used for?

It refers to the wage determined by the wage rules in CrewPlanner.

The ${wage} keyword uses the hourly wage determined by the wage rules and will appear as the hourly wage in the CONTRACTS tab of a project. According to your wage settings, either the hourly wage set in the employee profile, the shift function, or the configuration page will apply.

CrewTip! ${wage} is only available for contract templates. Use this keyword when the wage must align with the wage rules.

How are wages from the configuration page integrated into keywords?

They serve as a fallback wage unless overridden by an hourly wage from the employee profile or other wage rules.

The general wage settings on the configuration page act as the default wage unless a different wage is specified.

The ${user.hourly_wage} connects with these general settings as a fallback only if no specific wage is set in the employee's profile, and shift function settings are not applicable in this case. This keyword is ideal for use in legal documents, as shift functions do not apply when sending legal documents.

However, if a contract needs to reflect the wage as determined by the wage rules, the ${wage} keyword should be used.

The following logic is applied: if an hourly wage is present in the employee profile, this applies. If no wage is set in the employee profile, but a wage is set for the applicable shift function, this wage applies. If no wage settings are present in the employee profile or for the shift function, the general wage settings apply as set on the configuration page.

Employee profile > shift function > configuration settings

How do I choose the correct wage placeholder?

• Use ${user.hourly_wage}: For documents reflecting either an employee’s specific wage as set in their profile or a general default wage as set on the configuration page, this applies when shift functions are not applicable.

• Use ${wage}: For contracts that need to reflect a wage according to the wage rules.

Use ${user.hourly_wage}: For documents reflecting either an employee’s specific wage as set in their profile or a general default wage as set on the configuration page, this applies when shift functions are not applicable.

Use ${wage}: For contracts that need to reflect a wage according to the wage rules.

We hope this has helped you!

If you still have questions, take a look at our Crew Academy first. You might find the answer in one of our articles.