We are releasing some improvements to leave and unavailability which are designed to make managing time off requests even easier with Tanda.

Summary of improvements:

  • Combined time off calendar
  • Approval process for unavailability
  • Custom events + blackouts

Combined Time Off Calendar

Before you approve a request you need to be confident that doing so won't understaff your business, we realise that that means having a clear picture of all of the existing requests first. 

To make it easier for you to check all existing requests prior to making an approval we have released a combined time off calendar. Instead of having two separate calendars, one for leave and one for unavailability you can now see everything in one simple place:

If you have a large number of staff in your business, the calendar might seem a little overwhelming, however we will be adding team and location filtering options in the coming weeks to help with this.

The time off calendar will be accessible from the main time off menu:

Leave and unavailability will be signified by different icons that match those used on Rosters > Staff view.

Unavailability will display in orange when it is pending and charcoal once approved.

Leave will display as orange when it is pending and green once it is approved.

An approval process for unavailability

To help give you more control and oversight over unavailability requests we have added an optional approval process (just like leave).

When these improvements go live, unavailability approval will be turned on by default. Meaning all unavailability will require manager approval, if you would like to switch this off you can do so in your settings: 

General settings > Time Off > Unavailability.

Note: only admin users on your account will have permission to do this.

If you do choose to have this setting on, when staff go to enter their unavailability it will show up as pending until you have approved it. Here is how it will look for staff in their app when it is pending vs approved:

Once these changes go live in your account, the unavailability page that you would be used to seeing (pictured below) will be removed. Instead, all unavailability will be viewed, created and approved / declined on the Time off requests page. 

As you can see below, both leave and unavailability requests will be visible on this page: 

Unavailability requests will be labelled as below:

Unlike leave, unavailability won't be exported to payroll so it won't be displayed on timesheets. 

If you have require approval turned on, then each request will have approve / decline buttons on the right side. As with leave requests you can either decline or approve the request and the employee will receive an email notification of the outcome.

If you don't have approval turned on, requests will go straight to the approved tab.

Managers will still receive an email notification when unavailability is entered either way.

Custom events + blackouts

The last improvement to time off is the addition of custom events with time off blackouts. You can now add custom events to days on your roster to help you keep track of things happening in or around your business that are going to impact how busy you will be.

When creating a custom event, you can flag it as a ‘blackout’ to discourage staff from applying for time-off on that day. 

With this setting on, staff will see a warning when applying for leave and unavailability that lets them know what events are occurring during that period and that time-off is discouraged. 

Being transparent about your business needs to employees makes them feel more engaged with their workplace and less likely to submit a time off request during a blackout.

For employees to see these warning messages they need the latest version of the Tanda mobile app.

These events will also be displayed on your combined time off calendar:

The combined time off calendar and leave blackouts are both live in your account now. 

Unavailability approval and the removal of the existing unavailability page will be going live this week. 

Did this answer your question?