whats-best.ai
Search Sign in

Time Tracking & Attendance

clockodo

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 4 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by clockodo GmbH · www.clockodo.com

Compare with ZEP → Compare with Toggl Track → Report an error on this page Is this your product? →

Read this page as one judge. Each weighs the same scores by what they care about.

The Operations Lead

Weighted verdict

Runs a 200-person operation with office, workshop and field staff, and has to record all of them since the BAG ruling. Wants capture that fits each of those groups and a roster that reflects reality. Unmoved by a beautiful desktop timer that half the workforce cannot use.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Operations Lead

Capture in the real workplace

How this is scored

How time actually gets recorded across the workforces a buyer has — desk staff, field and site crews, shift and deskless workers — and what happens when the network is not there.

0 — One browser timer and nothing else; anyone away from a desk records nothing.

3 — Web plus a mobile app, but no offline capture, no shared terminal, and corrections are an admin task rather than a workflow.

5 — Web, mobile and at least one shared capture point (kiosk, terminal or badge), with offline capture that syncs, and a correction workflow with approval.

8 — Several capture paths including hardware terminals or badge readers, reliable offline handling, GPS or geofenced check-in where the vendor states its limits, and bulk correction with an audit trail of who changed what.

10 — Capture fits the workforce rather than the reverse: desk, deskless, field and shift models all first-class, offline as a designed state rather than a failure mode, and every correction attributable, reasoned and reversible.

Report an error

The Operations Lead

Browser, desktop and smartphone apps plus a shared time-tracking terminal are all named, and the mobile app is documented as running in the background and syncing automatically once a connection returns, which covers my office, workshop and field crews. Corrections are a workflow rather than an admin chore: retroactive entries, a split function for missed breaks, a change annotation on edited entries, and timesheets with editing locks and digital signature release. We found no public information on GPS or geofenced check-in for field staff, and none on bulk correction across a whole team. 3 7 8 4 9

Report an error

Working-time law & audit record

How this is scored

Whether the record satisfies the German recording duty (BAG 2022, § 3 ArbSchG) and the ArbZG rules around it — breaks, maximum hours, rest periods, retention — and whether it survives being inspected.

0 — Hours are summed and nothing else; no break handling, no limits, no retention statement.

3 — Break deduction exists but is a flat rule; no daily maximum or rest-period checks, and no stated retention period.

5 — Configurable break rules, warnings on the 8/10-hour daily maximum and the 11-hour rest period, and per-employee reports covering the recording duty.

8 — The ArbZG rules are modelled rather than approximated: break and rest enforcement with documented exceptions, overtime and time-account rules, the two-year retention handled by the system, and an export built for an inspection.

10 — The vendor treats the record as evidence: tamper-evident entries with full change history, retention and deletion executed per statute, documented handling of on-call, standby and travel time, and published guidance mapping features to the ArbZG sections they serve.

Report an error

The Operations Lead

The vendor cites the EuGH 2019 and BAG 2022 rulings, records start, duration and end, and models breaks properly with configurable rules, full or sliding deduction with a cutoff date, and a setting that enforces pauses, plus a warning to employee and employer when working times are not kept. The vendor's own help states that the automatic break deduction books no break period, so when an employee actually took their break would not be visible in an inspection unless they record it themselves. We found no public information on daily maximum or eleven-hour rest-period checks, or on a stated retention period for the working-time record itself. 4 10 3

Report an error

Absence & shift planning

How this is scored

Vacation, sickness and the shift or duty roster — the half of attendance that decides whether the time data means anything.

0 — No absence handling; vacation lives in a separate calendar or spreadsheet.

3 — Vacation requests with approval, but entitlement is manual, carry-over is not handled and there is no rostering.

5 — Automatic entitlement and carry-over, sickness recording, an absence calendar, and basic shift planning with availability.

8 — Public-holiday calendars per location, pro-rata entitlement, substitution and swap workflows, shift templates with qualification and rest-period checks, and coverage warnings before publication.

10 — Planning and recording are one system: rosters that respect statutory rest and the works agreement, absence that reflows the plan automatically, and forecast-versus-actual reporting a team lead can act on.

Report an error

The Operations Lead

Absence is genuinely handled: ten absence types from vacation to child sickness, automatic vacation accounts with carry-over and country-specific public holidays, approval configurable per absence type, and a shared team calendar with Outlook and Google sync. For the roster side we found no public information on shift planning, shift templates, availability, substitution or swap workflows, or coverage warnings before publication — which is exactly the half I need for field crews. 11 12 3

Report an error

Project, cost-centre & billing

How this is scored

Whether recorded time can carry the allocation an agency, workshop or professional-services firm needs — project, task, cost centre, billable status — through to an invoice or a client report.

0 — Attendance only; no project, task or cost-centre dimension at all.

3 — A free-text note or a single project field, with no rates, no billable flag and no per-project reporting.

5 — Projects and tasks with a billable flag and per-project reports, plus a rate per person or per project.

8 — Multi-level structure (client, project, task, cost centre), rate cards by person, role and project, budget tracking with warnings, and an invoice-ready export.

10 — Time becomes revenue without re-entry: approval before billing, rate rules that survive a rate change mid-project, client-facing reports, and a maintained handoff into named accounting or invoicing systems.

Report an error

The Operations Lead

Entries carry client, project, subproject, service, employee, description and hourly rate right at capture, with budgets in hours and money, warnings before a project runs into loss, and lump sums such as travel costs. Billing is a real handoff: the invoice builder filters by project, applies stored rates, lets you pick text building blocks, and transmits to Lexware Office, sevdesk or easybill where the draft is created. We found no public information on rate cards by role, a billable flag, or cost centres as a separate dimension. 13 14 3 1

Report an error

Payroll handoff

How this is scored

How the recorded month reaches payroll — DATEV, Lohn und Gehalt, an in-house system or the tax adviser — and how much of it is automated rather than retyped.

0 — No payroll path stated; the month leaves as a spreadsheet someone retypes.

3 — Generic CSV said to be usable for payroll, with no named system, no defined format and no handling of surcharges.

5 — A named payroll integration or a documented export format for at least one major system, covering hours, absences and overtime.

8 — Vendor-maintained integration with a named provider, covering night, Sunday and holiday surcharges, time accounts and mid-month changes, with a lock step before transmission.

10 — Payroll is designed for, not exported to: several named systems maintained, an auditable approval and lock, retro handling for corrections after the close, and the tax adviser given their own scoped access.

Report an error

The Operations Lead

There is a documented DATEV Lohn & Gehalt connection with client and consultant numbers, employee-number type and wage-type mapping, and approved absences are stated to be ready for payroll preparation. But the vendor's own help states this export is available exclusively for hourly wage earners and excludes surcharges and any employees who have entered them — with night, Sunday and holiday supplements, that is precisely the gap I would face for shift staff. We found no public information on time-account export, mid-month changes, or a lock step before transmission. 15 16 11

Report an error

European sovereignty

How this is scored

Where the data lives, who the contracting entity is, who the subprocessors are, and whether that is documented rather than assumed. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it.

0 — Non-EU vendor and contracting entity, hosting region unstated or non-EU, subprocessors not named.

3 — EU hosting offered as an option, but the contracting entity is non-EU or the subprocessor list is absent.

5 — EU hosting as standard and an EU contracting entity, but the subprocessor chain includes non-EU providers without an explained safeguard.

8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, full subprocessor list published, and any non-EU processing named with its legal basis.

10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor in the EU, data-centre certification published, and an on-premises or private-cloud option for buyers who need it.

Report an error

The Operations Lead

The contracting entity is Clockodo GmbH in Unna with a German register number and VAT ID, the system is stated to store data on German servers, and the privacy policy names its subprocessors with addresses: Mittwald in Espelkamp for hosting, HubSpot Germany in Berlin, PayPal in Luxembourg and Stripe in the USA. The US processing is named with the EU-US Data Privacy Framework and standard contractual clauses as its legal basis, and a trust centre publishes the processing agreement, TOMs, security standards and data-centre information. We found no public information on an on-premises or private-cloud option for buyers who need one. 5 6 8

Report an error

Pricing transparency

How this is scored

Whether a buyer can compute the real annual invoice for their headcount — including terminals, modules and minimums — from public pages alone.

0 — No public prices at all; every tier is a sales conversation.

3 — A per-user headline exists, but hardware, modules or a minimum seat count are unpriced or unmentioned.

5 — Per-user prices public for the main tiers with the billing period stated, but at least one commonly needed piece (terminal hardware, planning module, payroll export) sits in an unpriced bundle.

8 — Every tier and module priced publicly with per-user maths, billing period, minimum term and VAT treatment stated; only genuinely custom work lacks a number.

10 — Complete price computability: a calculator or table producing the annual invoice for a given headcount and module selection, including hardware, setup and renewal terms.

Report an error

The Operations Lead

Per-user prices are public for every tier — Basic at 4 € per user per month, Pro at 10 € with 8 € for the first twelve months, Pro Plus at 12 € with 10 € for the first twelve months, and a plus package at +2 € per user per month — with billing period, monthly cancellation, no base or setup fee and net prices plus VAT all stated. What I cannot compute for two hundred people: the pricing page invites buyers with at least 20 users to request an individual offer, and the time-tracking terminal named in the features pages carries no public price. We found no public information on terminal hardware or setup costs. 2 3

Report an error

European sovereignty — proven facts

1 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Ownership Not determined — uncited Report an error
Data residency Not determined — uncited Report an error
Subprocessors Not determined — uncited Report an error

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Do you know more about clockodo? Tell us Report an error on this page

Sources (16)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage www.clockodo.com Checked 15 Sep 2026 Details →
  2. 2 Pricing www.clockodo.com Checked 15 Sep 2026 Details →
  3. 3 Features www.clockodo.com Checked 15 Sep 2026 Details →
  4. 4 Working-time recording www.clockodo.com Checked 15 Sep 2026 Details →
  5. 5 Imprint www.clockodo.com Checked 15 Sep 2026 Details →
  6. 6 Privacy policy www.clockodo.com Checked 15 Sep 2026 Details →
  7. 7 Capture in the real workplace — found from sitemap www.clockodo.com Checked 1 Oct 2026 Details →
  8. 8 Capture in the real workplace — found from sitemap www.clockodo.com Checked 1 Oct 2026 Details →
  9. 9 Working-time law & audit record — found from sitemap support.clockodo.com Checked 1 Oct 2026 Details →
  10. 10 Working-time law & audit record — found from sitemap support.clockodo.com Checked 1 Oct 2026 Details →
  11. 11 Absence & shift planning — found from sitemap www.clockodo.com Checked 1 Oct 2026 Details →
  12. 12 Absence & shift planning — found from sitemap support.clockodo.com Checked 1 Oct 2026 Details →
  13. 13 Project, cost-centre & billing — found from sitemap www.clockodo.com Checked 1 Oct 2026 Details →
  14. 14 Project, cost-centre & billing — found from sitemap support.clockodo.com Checked 1 Oct 2026 Details →
  15. 15 Payroll handoff — found from sitemap support.clockodo.com Checked 1 Oct 2026 Details →
  16. 16 Payroll handoff — found from sitemap support.clockodo.com Checked 1 Oct 2026 Details →