Skip to content
CheckBiz360by EncodeBiz

Advanced branch configuration

Each branch in CheckBiz360 supports settings that adapt the system's behaviour to the particularities of that workplace: how far the clocking zone extends, how hours are counted and how breaks are recorded. This article describes each parameter, where it is configured, its effect and when it is worth modifying.

Article 58 of 924 min read

Where to find each setting

A branch's advanced configuration is split across two places, depending on what you want to adjust:

  • The branch record (Branches in the side menu → edit) holds the site's details and the operational configuration: the check zone.
  • The calendar (Calendar in the side menu → Branch tab) holds the weekly schedule, the breaks, the workday mode and the break mode.

Parameter table

ParameterWhereTypeDescription
Check zone in metresBranch recordInteger (metres)Radius around the coordinates within which clocking is accepted
Check zone enabledBranch recordBooleanWhen disabled, the geofence stops being validated at this branch
StatusBranch recordActive / InactiveAn inactive branch does not accept clock records
Additional dataBranch recordKey/valueFree fields specific to your organisation
Weekly schedule and breaksCalendarTime windowsShifts per day and breaks within each shift
Strict / flexible workdayCalendarBooleanCount the official schedule or the time actually worked
Strict / flexible breakCalendarBooleanDeduct a fixed duration or the actual break time
Break time (minutes)CalendarInteger (minutes)Duration deducted when the break is strict

Detailed description of each parameter

Check zone enabled

When this option is disabled, the system accepts clock records from any GPS location without checking whether the employee is within the defined radius. The GPS coordinate is still recorded in the system, but is not used as a validation criterion.

When to use it: branches where employees work on the move, at client premises or in spaces with poor GPS coverage (basements, warehouses with thick walls). It is also useful during the initial configuration period, when the radius has not yet been adjusted precisely.

Break mode

Breaks have two modes, chosen in the branch calendar:

  • Strict break: the system deducts exactly the minutes configured. The employee does not mark the start or end of the break, and longer or shorter breaks are not recognised.
  • Flexible break: the employee marks the start and end of each break from the app, and the system counts the effective duration.

When to use strict: fixed breaks set by collective agreement, the same every day, where requiring two more clock records a day adds nothing. When to use flexible: variable breaks depending on workload, or when the real duration of breaks has to be evidenced.

Break time

When the break is strict, this value —in minutes— is what is deducted from the workday. Set it to the break time stipulated in the collective agreement applicable at that branch.

With a flexible break the field does not apply: the time the employee records governs.

Workday mode

Decides whether counting follows the official schedule (strict workday) or the time actually worked (flexible workday). It is the setting with the greatest impact on hours reports and is explained in detail in Strict and flexible workday.

Interaction between parameters

  • The workday mode and the break mode are independent: you can have a strict workday with a flexible break, or the other way round.
  • The break time only applies with a strict break; with a flexible one it is ignored.
  • Disabling the check zone is independent of the rest and can be combined with any configuration.
  • Everything in the calendar follows the organisation → branch → employee inheritance: whatever the branch does not define, it inherits from the organisation.
Was this article useful?

Cookie settings

Choose what you want to allow. You can change your mind at any time from “Cookie settings”, at the bottom of the page. Read the cookie policy

NecessaryAlways on

They make the site work and remember this very choice, so we don’t have to ask you again. They identify no one and never leave this site, so they don’t depend on your permission.

They tell us which of our ads bring visitors and which don’t, so we stop spending on the ones that fail. That’s the Meta pixel (Facebook and Instagram) and Google Tag Manager (Google Analytics and Google Ads): they set first-party cookies and send data to Meta Platforms Ireland and Google Ireland.