Everything TimeTK does

Clock in, clock out and breaks are recorded where the work happens — in a browser, on a phone or at a shared terminal. Every action is stored as an event and never overwritten.

• Clocking in a browser on any device, with nothing to install
• Shared kiosk with a personal PIN per employee, for teams without their own work device
• Clock actions captured while the connection is down are held in the browser and submitted later
• Location capture is optional, off by default, and only ever recorded at an explicit clock action
• Durations are exact to the minute, and every calculation traces back to the individual events

A versioned rule set per organisation decides how clock events become hours. The calculation is deterministic: the same inputs always produce the same result, months later included.

• Normal and maximum working time per day and per week
• Break requirements (e.g. 30 minutes after 6 hours) and minimum daily rest between shifts
• Night-work window, grace periods for arrival and departure, threshold for unusual overtime
• Holiday lists per country and year; contracts with a weekly pattern and mid-period changes
• Rule changes are versioned — closed periods never change retroactively

Anything that departs from the rules is detected automatically, classified, and put in front of someone to resolve — instead of surfacing at month end.

• Detected cases include missing clock-ins and clock-outs, missing or insufficient breaks, overlaps, work during an absence, daily and weekly limits, insufficient rest, late arrival and early departure
• Three severities — info, warning and blocking; only blocking cases hold up a payroll close
• Correction requests and after-the-fact entries go through an approval
• A correction supersedes the original without deleting it — the full history stays visible

Leave, sickness and other absences are requested, approved, and feed straight into balances and reporting.

• Organisation-defined absence types, grouped as vacation, sickness, medical, compensatory time, unpaid and custom
• Requests with approval, rejection and cancellation, each recorded
• Team calendar: who is away and when, before the next request is granted
• Paid and unpaid absence flow separately into the daily calculation and into exports

Master data, contracts and structure in one place — with history, because working-time models change mid-year.

• Contracts with weekly hours and a working-time pattern, valid from a date; earlier periods stay calculated under the previous contract
• Teams and locations, with management responsibility assigned
• E-mail invitations with address confirmation, password reset and session management
• Five roles: owner, administrator, manager, payroll reviewer and employee

The current picture for managers, their own figures for employees — both from the same data.

• Live attendance: who is present, remote or away
• Daily reports with manager acknowledgement
• Monthly summaries per person: target, actual, overtime, night hours, absence and balance
• Every person sees their own hours, balances and requests — transparency rather than surveillance
• Monthly PDF for employees

The record of clock events and log entries only ever grows. Nothing is changed quietly, and every decision stays attributable.

• Clock events and audit entries are append-only — no updates, no deletes
• Approvals, corrections, rule changes, period closings and exports are logged with actor and timestamp
• Searchable audit view for administrators and payroll reviewers
• Roles and permissions limit every view to what the role needs

Plan the week and hold the plan against reality: conflicts are reported before they happen.

• Weekly planning per team and location
• Conflict detection across teams and locations
• Shift changes with manager approval
• Approved leave is visible in the plan; planned and actual sit side by side in reporting

Attribute working time to a project or a customer — for internal costing or for billing outward.

• Projects and customers per organisation, active or archived
• Attribution at the moment of clocking, with no second system to fill in
• Time per project and customer over any period

A period is checked, closed and frozen. Whatever is exported afterwards comes from the frozen version — not from data that has moved on.

• Readiness check before closing: open corrections, blocking exceptions, missing approvals
• Closing produces an immutable snapshot per employee and period
• Blocking cases can be overridden with a reason, and the reason is recorded
• Reopening is possible and is logged as an event in its own right
• Wage types are configurable: normal hours, overtime, night hours, paid and unpaid absence

The same closed period, in whatever format payroll needs — as often as required and always with the same result.

• CSV and Excel for further processing
• PDF as a monthly summary and as an individual record per employee
• BMD-style and DATEV-style files with configurable wage-type codes
• Saved export configurations and a history of every export run, re-downloadable
• Exports are reproduced from the snapshot, never from live data

Ask questions in plain language instead of building filters. The figures come from the same deterministic calculation as every report.

• Answers are composed only from calculated figures, filtered by the asker's permissions
• The language model phrases the answer, it does not compute it — figures are never invented
• With no model configured the assistant still works and answers deterministically

Multi-tenant, hosted in Europe, and open enough to fit into an existing system landscape.

• Runs on European infrastructure in Germany; traffic encrypted in transit over HTTPS, passwords stored only as a hash
• Every query is scoped to your own organisation; membership in more than one is supported
• Time zone per organisation, with calendar dates computed in that zone
• Interface in seven languages, selectable per organisation and per person; Arabic renders right to left
• Self-service billing: switch modules on and off at any time

Your data stays reachable — from your own reporting, from a terminal, or from the AI assistant you already work with. The REST API is part of the product; the MCP connection and the CLI are set up together with you.

• A documented REST API across attendance, absences, shifts, reports, payroll periods and exports
• An MCP connection for AI tools such as Claude Desktop, so working-time questions can be asked where you already work
• CLI access for terminals, scripts and scheduled jobs — a nightly export into your own systems, for instance
• Every route of access follows the same roles and permissions as the interface; an assistant never sees more than the person it works for
• Every response carries a request ID that reappears in the audit log

Where the standard product stops, we build the missing piece — inside the same system, with the same data handling and the same audit trail. It is often about evidence: companies want to show who was where and when, or to bring machine and access data together with working time.

• A camera at the kiosk: a photo at the moment of clocking as evidence, against people clocking in for each other
• Sensors, access control, turnstiles, RFID and badge readers as an additional source of clock events
• Machine and plant data alongside working time, for utilisation and proof on the shop floor
• Custom reporting, monitoring views and connections to the systems you already run
• Delivered as a scoped project: in Austria and Germany, evidence and monitoring features normally require a works agreement and a data protection impact assessment — we plan for that, but we do not replace legal advice