Administrators and Power Users can set clocking requirements, which determine how many daily entries employees must record to track their work. These requirements can be set at a company-wide level or customized for individual users based on their specific roles or needs.
Generally, we recommend following the requirements specified in the employee's labor contract. However, depending on which features you have enabled, some settings may be more effective than others. Here are the most common scenarios and our recommendations.
If employees must clock in/out for their shift and unpaid breaks
To monitor the duration of unpaid breaks (such as lunch), select the Every clock-in / clock-out (including breaks) requirement.
Users with this setting must clock in and out at:
The start and end of their assigned shift.
The start and end of any unpaid breaks defined in their shift.
💡 If you also need to track paid breaks (such as travel or short rest periods), see the Special cases section below.
If employees only clock in/out for their shift (with automatic break deduction)
If you do not need to monitor the exact duration of unpaid breaks, choose Start / End of shift. This works best if shifts have fixed hours and include a scheduled break. In this case, users only clock in at the start and out at the end, and Fluida automatically deducts the scheduled break from the total hours worked.
Note: If you use flexible shifts (e.g., "8 hours" without specific start/end times) or only use the Clock-in clock-out feature without the Attendance Management feature, the system won't know the break duration and cannot deduct it automatically. In these cases, you would need to manually adjust the exported data or switch to Every clock-in / clock-out (including breaks) to let the system handle calculations automatically.
If employees only need to report their presence once a day
If tracking actual hours worked isn't necessary and you only need proof that the employee was present, choose Once-a-day presence. Users only need to clock in once at any time. If they have an assigned shift (fixed or flexible), the system will automatically count all scheduled hours as worked, minus any recorded absences or overtime.
💡 If the user does not have an assigned shift (for example, if Attendance Management is disabled), the system cannot calculate total hours worked. To get this data automatically in this scenario, consider using Every clock-in / clock-out (including breaks) instead.
If employees don't need to clock in but must track attendance/absences
Choose None if recording hours via clocking isn't required. Users won't need to clock in; if they have a shift assigned, the system automatically counts those hours as worked, accounting for any absence or overtime requests.
💡 Again, if no shift is assigned, the system cannot show total hours worked. For automatic totals in this case, use Every clock-in / clock-out (including breaks). Alternatively, you can keep the requirement as None and only ask employees to clock in manually when specifically needed.
Special cases
Tracking travel time or paid breaks (e.g., short rest periods)
Fluida is designed to track:
General presence.
Start and end of the workday.
Start and end of unpaid breaks (like lunch).
Clocking for paid breaks is not standard, as these periods do not affect the total hours worked or payroll processing. However, if you need to track them for safety or internal monitoring, and you have both the Clock-in clock-out and the Attendance Management features active, you can:
Ignore any anomalies generated by these extra clock-ins, so they remain part of the total hours worked.
Justify anomalies using custom request types (e.g., "Other absence") to specify paid breaks in your attendance export.
Set up a second Fluida account with only the Clock-in clock-out feature active, dedicated exclusively to tracking paid breaks.
