The time tracking in Kibi Connect enables the digital recording of working hours, breaks, and absences. The module is fully compliant with the Working Hours Act (ArbZG) and the EU Working Time Directive. Violations of legal requirements are automatically detected and reported.
Time tracking must be activated for your client. Please contact your administrator if the page is not visible.
In the navigation bar, there is a small round button. This serves as a digital time clock.
Gray dot: You are currently not clocked in. Tap it to clock in.
Green, pulsing dot: You are clocked in. Tap it to view details or clock out.
After clocking in, a popup shows the start time, a running timer, and the total working time for the day. You can clock out at any time using the red button.
Clocking in and out works immediately (optimistic UI). The display updates right away while the data is saved in the background.
The "Today" card shows all work entries for the current day:
Start and end time of each entry with the respective duration
Active entries (still clocked in) are marked with a green badge
The total working time for the day is displayed at the top right
Break times are listed separately at the end
The weekly view provides an overview of all seven days of the current calendar week. You can navigate between weeks using the arrow keys.
For each day, you see:
The time period (e.g., 08:00 - 17:30)
Break duration in minutes
Total working time
If there are ArbZG violations, a yellow warning dot appears next to the working time
The current day is highlighted in color. Weekend days are displayed in gray. At the end of the week, the weekly total is shown.
The time account shows the monthly working time balance:
Target: The expected working hours for the current month according to the working time model
Actual: The actual working hours worked
Balance: The difference between target and actual. Overtime is shown in green, negative hours in red
Annual Balance: The cumulative balance since the beginning of the year
The time account is automatically recalculated with each booking. Closed (locked) months are no longer modified.
Using the "Request Absence" card, you can submit vacation, sick leave, or other absences.
Click the "+" symbol to open the form
Select the type of absence (e.g., vacation, sick leave)
Enter the start date. The end date is automatically set to the same date
Adjust the end date if needed. The number of working days (excluding weekends) is automatically calculated
Optionally add a note
Click "Submit Request"
After submission, your request is forwarded to the HR department. You will receive a notification once the request is approved or rejected.
Under "My Absences," you can see all your previous requests with their current status:
Status |
Meaning |
|---|---|
Pending (yellow) |
The request is waiting for approval |
Approved (green) |
The request has been confirmed by the HR department |
Rejected (red) |
The request was rejected |
Canceled (gray) |
The request was withdrawn by you |
As long as a request has the status "Pending," you can cancel it yourself using the red X symbol.
Kibi Connect automatically checks each time booking to ensure compliance with the legal requirements of the Working Hours Act (ArbZG) and the EU Working Time Directive. If violations occur, warnings are generated, and the affected employees as well as the HR department are notified.
According to ArbZG §3, the daily working time must not exceed 10 hours. Kibi Connect automatically checks this for each working day and generates a warning if the limit is exceeded.
According to ArbZG §4, the following minimum breaks apply:
Working Time |
Minimum Break |
|---|---|
More than 6 hours |
30 minutes |
More than 9 hours |
45 minutes |
The break time is automatically calculated from the gaps between consecutive bookings. If the minimum values are not met, a warning appears.
According to ArbZG §5, there must be at least 11 hours of uninterrupted rest between the end of one working day and the start of the next. Kibi Connect checks this across days and issues a warning if the requirement is not met.
According to ArbZG §3 and the EU Working Time Directive, the weekly working time must not exceed 48 hours (Monday to Sunday). A warning is generated if this limit is exceeded.
The EU Working Time Directive requires a continuous rest period of at least 35 hours per week. Kibi Connect calculates the longest uninterrupted rest block within each calendar week and issues a warning if this value is not met.
Check |
Legal Basis |
Limit |
|---|---|---|
Daily Maximum Working Time |
ArbZG §3 |
10 hours |
Break after 6 Hours |
ArbZG §4 |
30 minutes |
Break after 9 Hours |
ArbZG §4 |
45 minutes |
Rest Period Between Working Days |
ArbZG §5 |
11 hours |
Weekly Maximum Working Time |
ArbZG §3 / EU Directive |
48 hours |
Weekly Minimum Rest Period |
EU Working Time Directive |
35 hours |
Warnings are for information and documentation purposes. They do not prevent clocking in or out but draw attention to violations so they can be corrected promptly.
HR managers and system administrators see two additional sections on the time tracking page: the team overview and absence management.
The team overview shows all employees with the following information:
Status Today: Active (clocked in), Absent, or Inactive
Actual Hours: Working hours completed in the selected month
Target Hours: Expected hours according to the working time model
Balance: Overtime or undertime (color-coded)
Warnings: Number of open ArbZG violations
Absence Days: Approved absence days in the month
Clicking on an employee opens a detailed view with:
Time entries grouped by calendar week (day, date, clock-in, clock-out, duration)
Editable entries (pencil icon) for corrections by HR
Locked entries (lock icon) can no longer be modified
Entries corrected by HR are marked with a blue badge
ArbZG warnings with date, type, and acknowledgment button
Using the "Lock Month" button, all time entries for a month can be permanently locked. Locked entries and time accounts can no longer be changed.
Locking a month cannot be undone. Ensure all entries are correct before locking the month.
In the "Absence Requests" section, HR managers can:
Filter all incoming requests by status (Pending, Approved, Rejected, All)
View details of each request (employee, type, period, working days, note)
Approve or reject requests with an optional reason
When a request is approved or rejected, the requesting employee automatically receives a notification.
Administrators can configure various working time models under Administration and assign them to employees.
Parameter |
Description |
|---|---|
Name |
Designation of the model (e.g., "Full-time 40h") |
Type |
Fixed working hours or flexitime |
Weekly Hours |
Target working hours per week |
Working Days |
Days of the week on which work is performed |
Daily Target Minutes |
Expected working minutes per working day |
Flexitime Framework |
Earliest and latest allowed clock-in/out times |
Core Working Hours |
Mandatory attendance time |
Rounding |
Time rounding to 1, 5, or 15 minutes |
Max. Daily Hours |
Overrides the ArbZG standard value of 10 hours |
Individual break rules can be stored for each working time model. Example: "After 360 minutes of work, at least 30 minutes of break are required."
Working time models are assigned to employees with an optional validity period. This allows changes (e.g., switching from full-time to part-time) to be seamlessly documented.
Administrators can customize the available absence types:
Name: Display name (e.g., Vacation, Sick Leave, Special Leave)
Color: Color coding in the overview
Paid: Whether the absence is considered paid leave
Approval Required: Whether an HR manager must confirm the request
Vacation Deduction: Whether the days are deducted from the vacation entitlement
Time tracking triggers automatic notifications in the following cases:
Event |
Recipient |
|---|---|
New Absence Request |
All HR Managers |
Request Approved |
The requesting employees |
Request Rejected |
The requesting employees |
ArbZG Violation Detected |
The affected employees and HR managers |
Notifications appear as in-platform notifications. Depending on the configuration, they can also be delivered as push notifications or emails.