Time tracking
Time tracking documents the hours worked per person and day – mandatory in Germany since the Federal Labour Court ruling of 13 Sept 2022 (1 ABR 22/21). Staff record start, end and break themselves, the back office approves. Start/end/duration are captured objectively, reliably and accessibly.
Live preview — real view with sample data
M33 · Time tracking
| Date | Person | Category | Start | End | Duration (min) | Status |
|---|---|---|---|---|---|---|
| 10/06/2026 | Entry 2 | Done | 08/06/2026 | 06/06/2026 | Record 3 | In progress |
| 21/06/2026 | Record 3 | Reviewed | 19/06/2026 | 17/06/2026 | Item 4 | Done |
| 02/07/2026 | Item 4 | Open | 30/06/2026 | 28/06/2026 | Entry 5 | Reviewed |
| 13/07/2026 | Entry 5 | In progress | 11/07/2026 | 09/07/2026 | Record 6 | Open |
| 24/07/2026 | Record 6 | Done | 22/07/2026 | 20/07/2026 | Item 7 | In progress |
Not a screenshot: the same interface you get in production.
What you do here
Use „Record time“ to create an entry with person, date, start, end and break – the duration is calculated automatically and shown in hours (8:07 h). In the list you filter open, submitted and flagged entries, on the board you move entries through the approval flow, the calendar shows which days were recorded. Submitting an entry moves it from draft to approval; the back office approves or rejects.
Working-time protection (ArbZG)
Every entry is checked against the Working Hours Act on save: minimum break (§4: over 6 h ≥ 30 min, over 9 h ≥ 45 min), maximum hours (§3: more than 10 h per working day is not allowed) and rest period (§5: at least 11 h since the previous entry). Flagged entries carry the status „Check“ and appear in the tab of the same name. Night (23:00–06:00) and Sunday work are marked – the basis for surcharges in the payroll export.
Audit safety & deadlines
Staff may record and change their own entries while they are not approved – afterwards they are locked. Every change is logged with who, when and why in the entry's history, including corrections by the administration; this log is immutable. Under § 17 MiLoG hours must be recorded within 7 days of the work (late entries are flagged). Retention: at least 2 years (ArbZG/MiLoG), up to 10 years for payroll-relevant data (§ 147 AO/GoBD).
Target/actual & overtime
The monthly balance shown on each entry is derived from the stored working-time model (weekly hours per person) and the approved actual hours. Carryovers, corrections and payouts go through an audit-safe ledger, not direct overwriting. Privacy: working-time data is employee data (§ 26 BDSG, data minimisation); by default everyone sees only their own entries, management/back office the team or everything.
What's inside
- Time tracking
- Approval
- Calendar
- Time entry
- Record time
- Submit
- Approve
- Reject
- Set status
- Assign person
- Book time-account entry
Fits together with
Other blocks from the same area.
Absence
Here staff request holiday and report absences (sickness, home office, special leave, maternity, parental leave); the back office approves or rejects them – with an optional stand-in. The per-person, per-year leave account shows entitlement, taken, planned and remaining days.
M29Client master
The central client record for care: one person with everything around them – master data, home access, relatives and legal guardianship, payers, care level with history, physician's order. The basis for routes, visits and care documentation.
M30Employee master
The central employee master: maintain all staff with their core data, employment and contact details in one place – independent of the app login.
M31Member master
The central member master for clubs: core data, membership, offices and divisions in one place – plus a real fee account (charge/payment/open balance) with SEPA direct debit, independent of the app login.