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 Skeptic

Weighted verdict

Has read a great many pages claiming to be "BAG-konform" and wants to know which feature makes that true. Reads compliance claims for what they do not say: which module, at which tier, and whether the terminal in the photograph costs extra.

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

Scored by The Skeptic

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 Skeptic

Capture paths run from browser and desktop apps to iOS and Android with offline entry that syncs automatically, plus a punch clock that keeps running through project changes — and a shared time recording terminal appears exactly once in a features list, with no detail and no price. Corrections have a real workflow (retroactive entries, a split function for missed breaks, edit locks with digital signatures) and every edited entry carries a change annotation, but we found no public information on badge readers, geofenced or GPS check-in, or bulk correction with attribution. 3 7 8 9 4

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 Skeptic

The "gesetzeskonform nach BAG-Urteil" claim rests on configurable break rules (full or sliding deduction with a cutoff date), a break-enforcement setting in company settings, and warnings to both employee and employer when working times are not kept — yet no captured page names the 8/10-hour daily maximum or the 11-hour rest period, and retention is addressed only as a generic privacy-policy deletion rule rather than for the working-time record. The vendor's own help centre concedes the automatic break deduction books no break period, so an inspection would not show when the employee actually paused; the employee must record breaks themselves. A change annotation on edited entries exists, but nothing evidenced is tamper-evident, and we found no public information on on-call, standby or travel time. 4 10 3 6

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 Skeptic

Absence is the strong half: ten absence types from vacation to quarantine, approval configurable per type with supervisor release, automatic entitlement with carry-over, country-specific holiday calendars, a team calendar and Outlook/Google synchronisation. But the shift or duty roster — half of what this criterion asks — is absent from every captured page: we found no public information on shift planning, shift templates, substitution or swap workflows, or coverage checks. Approved absences flow into a shared calendar and the payroll preparation, not into any plan that reflows around them. 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 Skeptic

Recorded time carries client, project, subproject and service with a stored hourly rate and lump sums, hour and money budgets with warnings before a project turns loss-making, and interval budgets in the top tier. Billing is a designed handoff rather than an export: invoice drafts arise from project times without retyping and pass by click to the named tools Lexware Office, sevdesk and easybill, with timesheet approvals under edit locks and digital signatures. We found no public information on cost centres, role-based rate cards, a per-entry billable flag, or how rates are treated when they change mid-project. 13 3 14

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 Skeptic

There is a named DATEV Lohn & Gehalt connection, documented in German and English help pages with client and consultant numbers, personnel-number type and wage-type assignment, and absences stand ready for preliminary payroll. The fine print does the deciding: the export is available exclusively for hourly wage earners, and surcharges — or any employee who has stored surcharges — are excluded from it, so night, Sunday and holiday surcharges do not travel this path. 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 Skeptic

The contracting entity is Clockodo GmbH with a German register entry, product pages state data is stored on German servers, and the privacy policy names its processors — Mittwald in Espelkamp, HubSpot Germany, PayPal in Luxembourg, Stripe in the USA — with the EU-US Data Privacy Framework cited as the basis for the American one, which clears non-EU processing being named with a legal basis. It stops short of the full picture: we found no public information on ownership, published data-centre certification, whether the processor list is complete, or an on-premises and private-cloud option. 8 5 6

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 Skeptic

All three tiers carry public per-user net prices with VAT treatment stated, monthly and annual billing, cancellation at any month's end, no base or setup fee, and single users free permanently — the software invoice is computable from the pricing pages alone. Two pieces stay in the dark: the time recording terminal named among the capture paths has no price on any captured page, and from 20 users the vendor invites an individual offer, so a larger buyer cannot compute their annual invoice from public pages. 2 3 8

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 →