Scheduled balance check
On a date you choose, notifies the employees whose balance on one time account is above or below a threshold.
“On 1 March, tell everyone still holding more than 40 hours of flex.”
When to use
Use it for the recurring nudge that belongs to a date rather than to an event: flex that should be spent down before the year closes, vacation that should be planned before the season fills up, a balance that has drifted negative.
If what you care about is a balance lapsing, use Expiring balance instead — it works from the expiry date and warns about the amount that will actually be lost.
Parameters
| Parameter | Description | Default |
|---|---|---|
| Account | The time account whose balance is checked. | — |
| Schedule | Once a year (month and day) or Every month (day only). | Once a year |
| Month | The month of a yearly check. | — |
| Day | The day of the month the check runs on. | — |
| Condition | Whether to notify employees above or below the threshold. | Above the threshold |
| Threshold | The value to compare against, in the account’s own unit — days for a days account, hours for an hours account. | — |
How it works
On the scheduled date mTime reads each employee’s current balance on the account and sends the message to those who pass the threshold. Employees on the right side of the threshold get nothing.
The balance is the number the employee sees on their own dashboard, negative values included — so “below 0” is a legitimate thing to watch for.
Each scheduled date sends at most one email per employee. If the nightly check could not run on the day itself, it still sends for up to three days afterwards, and the catch-up does not duplicate a message that already went out.
A monthly check set to a day the month does not have runs on that month’s last day, so “every 31st” means month end rather than “every 31st except in the five short months”.
Message
Leaving the subject and text empty sends:
{employee_name}’s {account_name} balance is {balance}
On {date} {employee_name}’s {account_name} balance is {balance}, past the threshold of {threshold}.
Available variables: {employee_name}, {workspace_name}, {date}, {account_name}, {balance} and {threshold}.
Examples
Spend down flex before the year closes
- Add an advisory and select the Scheduled balance check trigger
- Choose the flex Account
- Leave Schedule on Once a year, set Month to November and Day to 1
- Leave Condition on Above the threshold and set Threshold to 40
- Turn on Employee as the recipient
A monthly watch on negative balances
- Set Schedule to Every month and Day to 1
- Set Condition to Below the threshold and Threshold to 0
- Send it to the manager
Troubleshooting
| Issue | Solution |
|---|---|
| Nothing was sent on the day | Check the activation window on the advisory, and that the Employees section matches someone who holds this account. |
| Everyone was notified | Check Condition — Below the threshold with a high value matches almost everybody. |
| The threshold does not behave as expected | It is expressed in the account’s own unit: 40 on an hours account is 40 hours, on a days account 40 days. |
| An employee at exactly the threshold got nothing | Expected: the comparison is strictly above or strictly below. |
| The advisory stopped working after the account was deleted | Expected. Point the trigger at an existing account. |