| Note: From October 1st, 2025, we introduced new plans that better reflect how our customers use Deputy: Lite, Core, and Pro. If you're an existing customer, look out for an email with all the details you’ll need. Learn more about the new plans and what this change means for you. |
This article discusses the Days Worked In Period pay rule calculations as part of Deputy's Pay Rate Builder.
Before you begin, please read about adding and editing pay rule calculations
- Description
- Example use case
- Supported rule types
- Outputs
- Configurable parameters (standard)
- Configurable parameters (advanced)
Description
The Days Worked In Period pay calculation rule returns if a team member works more than a certain number of days in a defined period.
Example use case
If a team member works more than 10 days in a two-week period, overtime should be paid for all hours.
In this case, you can set the threshold as 10 days and the period as two weeks.
Note that days worked are counted as days when a team member clocks in during that day, not counting overnight shifts.
Supported rule types
This rule is available as a base rate or as a loading. Each minute of a timesheet is assigned a base rate to fill it, depending on whether it meets the rules criteria and the priority of these rules.
Outputs
Base Rates are only available hourly.
By default, it will return all hours worked once the threshold has been reached.
Depending on which option you select, loadings will return the whole shift in hours or one unit.
Configurable parameters (standard)
You can configure these standard fields in the Shift Loading pay rule calculation.
| Name | Defines the name of the pay rule |
| Days Worked in Period Threshold | This sets the number of days that must be worked in the period before this rule starts triggering. This number must be exceeded in the period to trigger. |
| Days Worked In Period |
This allows you to set the period over which this rule will trigger. By default, it uses a Weekly period on a Core plan or the Pay Period on a Pro plan. It can also be configured to a set number of days, weeks, and months. If set manually (recommended), set the First Day of the Worked In Period to a day in the past for this rule to operate correctly. |
| Shift Length Threshold | Shift must be a minimum of this length to count towards the limit. |
| Pay After | This allows you to set limits on when this rule should apply. This is particularly useful when the rate changes after a certain number of hours, where you can make two pay rules, one for the first two (as an example) hours, and one for after two hours. This does not apply when using this rule as a shift loading. |
| Export code | Defines if this pay rule should be exported to payroll. If yes, they can also specify a code for the rule. |
| Days of the week this calculation applies |
Defines which days of the week this rule applies to. For example, if Saturday and Sunday are selected, this rule calculates only parts of the timesheet overlapping Saturday and Sunday. |
| Time of the day this calculation applies |
Defines which part of the day this rule applies to. By default this is all day. However, it can be used to define a portion of a day (eg. a defined night shift, such as 6pm-6am). If this is done, only those parts of the timesheet that overlap with this are calculated. |
| Public holiday |
Select whether this pay rule applies:
|
| Areas |
The rule applies to all areas by default. However, you can apply it only when a timesheet is worked in a specific area/location.
|
| Classifications | If you have set up classifications within the pay rate, you can select if a rule only applies to a particular classification. |
Configurable parameters (advanced):
These are the advanced fields you can configure in the Consecutive days worked pay rule calculation
| Apply to Training |
This pay rule will only be applied to team members with the selected Training record on their employee profile. Read more at Managing Training Records. |
|
Does this apply to a specific date |
If set as Yes, the pay rule will only apply on the defined date, assuming the date falls on the previously defined allowable day and time above. |
| Apply pay rule to unscheduled shifts |
Defines how the pay rule interacts with scheduled and unscheduled shifts:
|
| Pay portion rule |
Generally, an hourly rate will be assigned according to the exact hours that are matched, however, it is possible to enforce an hourly rate for a full shift even if it only matches a minor or major portion of that shift. Deputy recommends using the Exact Hours option in most cases. |
| Rate type |
Categorizes the pay rule as Overtime, Ordinary, Penalty or Non-Payable time. These are used to define time worked for other calculation types (for example, Periodic Overtime counts Ordinary and some penalty hours towards it). |
| Rate tag |
A custom value that can be applied to the timesheets. Deputy recommends only using this if advised by your implementation consultant. |
|
Pay once per day |
If set as Yes, this pay rule may only apply once per day. If No, it may apply to multiple timesheets on a given day. |
| Clock in and out requirements |
For this rule to apply, the team member must clock in and clock out within the defined periods. By default this is midnight to midnight (ie. any time is allowed.) |
| Apply this pay rule for custom timesheet fields |
With this, the rule will only apply if particular values are selected in the custom timesheet field questions. Note that only List and Boolean questions are available. Read more at Creating custom timesheet fields for shift questions. |
| Apply this pay rule when shift custom fields |
This rule will only apply if particular values are selected in the custom shift fields in the schedule. Note that only List and Boolean questions are available. Read more at: Creating custom shift fields |
| Custom Employee Fields |
This rule will only apply if particular values are selected in the employee’s custom fields (for example, job position). Note that only List and Boolean fields are available. (Available to customers on most Deputy plans). Read more about setting up custom fields for team members. |