Dynamic Fields

Use dynamic fields to automatically populate text in your contracts

Updated over a week ago

Dynamic fields can speed up the process of sending contracts to multiple employees by automatically populating information or giving you the opportunity to edit text without needing an entirely new contract.

What is a dynamic field?

Dynamic fields act as placeholders in your contracts and automatically populate based on the information entered in employee profiles and account settings.

These placeholders allow you to use the same template for multiple employees, and automatically update the contents of the contract that are likely to change between staff like name, hourly rate, or employment type.

Depending on the type of contract being sent, some employees may not have all the information in their profile to populate the dynamic fields in a contract. When this happens, you'll have the opportunity to manually populate the dynamic field when sending the contract. Learn more about this in the Send Contracts guide.

Automatically populated dynamic fields

When the related information is entered on the employee's profile or in your account settings, these fields will automatically populate when sending a contract.

Important to note: The formatting of these automatic fields must match exactly to how they appear in the table below for them to automatically populate

E.g. {{phone_number}} will automatically populate, but {{phone number}} will not.

Dynamic Field

Where information comes from

{{date}}

The current date

{{contract_start_date}}

If contract changes are being made, this is the date they take effect

{{contract_finish_date}}

If contract changes are being made, this is the date they will stop taking effect

{{dob}}

Date of birth as entered in the onboarding form or in the Payroll tab of the employee profile

{{name}}

Full name as entered in the onboarding form or in the Personal tab of the employee profile

{{phone_number}}

Phone number as entered in the onboarding form or in the Personal tab of the employee profile

{{email}}

Email address as entered in the onboarding form or in the Personal tab of the employee profile

{{emp_address}}

Employee's address as entered in the onboarding form or in the Onboarding tab of the employee profile

{{award}}

Industry award the employee is covered by as entered in the onboarding form or in the Payroll tab of the employee profile

{{previous_award}}

If contract changes are being made to their industry award, this is the previous award they were covered by

{{emp_type}}

Employment type of the employee as entered in the onboarding form or in the Payroll tab of the employee profile (e.g. Casual, Apprentice)

{{previous_emp_type}}

If contract changes are being made to their employment type, this is the previous employment type they were classified as

{{classification}}

Classification under the award as entered in the onboarding form or in the Payroll tab of the employee profile (e.g. Level 1)

{{previous_classification}}

If contract changes are being made to their classification, this is the previous classification they were configured as

{{allowances}}

Allowances applicable to the employee as entered in the Payroll tab of the employee profile

{{previous_allowances}}

If contract changes are being made to the allowances they receive, these are the previous allowances they were receiving

{{hourly_rate}}

Base hourly rate as entered in the onboarding form or in the Payroll tab of the employee profile

{{previous_hourly_rate}}

If contract changes are being made to their base hourly rate, this is the previous hourly rate they were receiving

{{salary}}

Annual salary as entered in the onboarding form or in the Payroll tab of the employee profile

{{previous_salary}}

If contract changes are being made to their annual salary, this is the previous annual salary they were receiving

{{regular_hours}}

Regular hours of work as entered in the Regular Hours tab of the employee profile

{{minimum_base_hours}}

Contracted minimum base hours as entered in the Regular Hours tab in the employee profile

{{preferred_hours}}

Preferred weekly hours for rostering as entered in Personal tab of the employee profile

{{payroll_id}}

Payroll ID as entered in the Payroll tab of the employee profile

{{pay_period}}

Length of pay period for this employee as configured in the Payroll tab of the employee profile

{{pay_period_day}}

Start day of the pay period for this employee as configured in the Payroll tab of the employee profile

{{start_date}}

Employment start date as entered in the Payroll tab of the employee profile

{{org_name}}

Organisation name as entered in the account settings

{{org_abn}}

Organisation ABN as entered in the account settings.

If multiple ABNs exist for locations in your account, the ABN for the employee's default team will be used.

{{location_name}}

The name of the location of the employee's default payroll team as configured in the onboarding form or in the Personal tab of the employee profile

{{location_address}}

The address of the location of the employee's default payroll team as configured in the onboarding form or in the Personal tab of the employee profile

{{position}}

The position assigned to the employee.


Manually populated dynamic fields

Manually-populated dynamic fields can be used to add placeholders in a contract template when the information may not be entered on the employee profile or in the account settings.

With these, you'll need to populate the dynamic fields when reviewing the contracts. Learn more about the review process in the Send Contracts guide.

Formatting requirements

When adding a manually-populated dynamic field to your contract template, ensure the following formatting requirements are being followed:

Requirement

Example

Include two curly braces before and after the dynamic field

{{role title}}

Avoid using any symbols or special characters in the dynamic field

(excluding underscores)

Use {{weekly pay}}

Do not use {{weekly pay $}}

Avoid using any other brackets in the dynamic field

Use {{team or teams}}

Do not use {{team (or teams)}}

Did this answer your question?