In bob’s settings you can define the standard holiday and working pattern for each place you have an office. We call these “Sites”. 

Calendars tell bob which days are public holidays and should not be counted as leave days. The working pattern tells bob which days of the week are working days. 

Before getting started, you need to have defined your site settings, see here

Creating your Calendars

The first step is to define your calendars. You do this under Settings > Calendars. Calendars tell bob which days are bank holidays.

Once you have created your calendars, you can add them to sites that you have previously defined.

Working Pattern

Tell bob which days are working days for this site. Working days are marked with a tick. This allows bob to calculate which days should count when a leave request is made.

If you have someone who does not follow the working pattern or the calendar of the site they are assigned to, you can give them a custom calendar and/or working pattern. 

Custom Calendar and Working Patterns

If you have employees that work different patterns to the site they are assigned to, you can give override it by:

  • Editing the employment record on the payroll tab or adding a new row if it is an employment change - see below
  • Bulk import 

Time Off Override

You can personalise the time off settings for each site. Note this will override the policy settings for those individuals assigned to that site. 

See more about time off policies here.

Change the cycle start date if this site differs from the main policy start date. For example, everyone in your company may begin their leave years on the 1st of Jan, except Australia which begins then on the 1st of July.

Changing the cycle type affects how bob calculates balances. If monthly, bob will treat the balance at the end of each month as final. If annual, bob will treat the balance at the end of the year as final. Annual is the most common cycle type.

Balance Rounding

Control how you want bob to display the balance to employees in this site.

Did this answer your question?