Time Tracking & Attendance
clockodo
EU-Made Report an errorPanel 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 panel's verdict
clockodo scores strongest where time turns into money: project and billing runs 7 to 8, with entries carrying client, project, service and hourly rate, hour and money budgets warning before a project turns loss-making, and invoice drafts passing to Lexware Office, sevdesk or easybill. Pricing transparency holds at 7 — public net per-user prices (Basic 4 €, Pro 10 €, Pro Plus 12 €, plus package +2 €), a single user free permanently. The weakest criterion is absence and planning at 4 to 5: absence types, per-type approvals and automatic vacation accounts are documented, but we found no public information on shift or duty rostering, substitution or swap workflows. Working time law sits at 5 to 6, the vendor's own help stating the automatic break deduction books no break period; payroll export, 5 to 6, rests on a DATEV connection available exclusively for hourly wage earners that excludes surcharges. Weighted totals span 5.4 to 6.7; the widest single spread, sovereignty at 6 to 8, sets unnamed processor categories against subprocessors named with addresses and a trust centre.
Speaks for it
- Project and billing scored 7 to 8, with hour and money budgets warning before a project turns loss-making and invoice drafts passing to Lexware Office, sevdesk or easybill without retyping.
- Pricing transparency holds at 7: public net per-user prices for all three tiers, cancellation at any month's end, a single user free permanently and a 14-day free trial.
- Time capture scored 6 to 7, with browser, desktop and mobile apps capturing offline and syncing automatically once a connection returns, plus retroactive entries, a split function for missed breaks and a change annotation on edited entries.
- The absence half is documented: ten absence types, approval configurable per type, automatic vacation accounts with carry-over and country-specific public holidays.
- Sovereignty scored 6 to 8 on a German GmbH with a register entry at Amtsgericht Hamm, product pages stating data is stored on German servers, and subprocessors named by company and country, including Stripe in the USA under the EU-US Data Privacy Framework.
Held against it
- Absence and planning scored 4 to 5: the drag-and-drop planner arranges absences, not shifts, and we found no public information on rostering, shift templates, substitution or swap workflows.
- Payroll export scored 5 to 6: the vendor states the DATEV export is available exclusively for hourly wage earners and excludes surcharges and employees who have entered them.
- Working time law scored 5 to 6: the vendor's own help states the automatic break deduction books no break period, and we found no public information on daily-maximum or eleven-hour rest-period checks.
- The time-recording terminal carries no public price, and from 20 users the vendor invites an individual offer, so larger buyers cannot compute their annual invoice from public pages.
- We found no public information on GPS or geofenced check-in, bulk corrections, or a change history naming who altered what and why.
Best for
- You run a project-based service business that bills recorded time and wants invoice drafts handed to Lexware Office, sevdesk or easybill without retyping.
- Your staff are hourly wage earners without surcharges and your payroll runs through DATEV Lohn & Gehalt.
- You need capture across browser, desktop and mobile apps with offline sync and a correction workflow of retroactive entries and annotated changes.
- You manage absence — vacation, sickness and child sickness among ten types — with per-type approval and Outlook or Google calendar sync.
Avoid if
- You schedule shift or duty rosters — the captured planner arranges absences by drag and drop, not shifts, and absence and planning scored 4 to 5.
- You pay night, Sunday or holiday surcharges — the documented DATEV export excludes surcharges and the employees who have entered them.
- You rely on automatic break deduction for your working-time record — the vendor states it books no break period, so employees must record breaks themselves.
- You need to compute an exact annual invoice for 20 or more users in advance — from 20 users the vendor invites an individual offer and the time-recording terminal carries no public price.
The scores
Capture in the real workplace
Show reasoningHide reasoning
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.
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
The Payroll Officer
Browser, desktop and smartphone apps plus a named time-recording terminal give several capture paths, the mobile app records offline and syncs automatically, and employees can book forgotten times themselves, with a note left on every changed entry and digital signatures releasing work records. We found no public information on GPS or geofenced check-in, on badge readers, or on bulk correction with an attributable trail of who changed what. 3 4 7 8 9
The Works Council Advocate
Browser, desktop and smartphone apps sit alongside a shared time-recording terminal, times captured offline sync automatically once a connection returns, and employees may file forgotten times themselves rather than queue at an admin desk. We found no public information on GPS or geofenced check-in, on bulk corrections, or on a change history naming who altered what and why — the only evidenced trail is a general Vermerk on a changed entry, which is thin for a works agreement on corrections. 3 4 7 8
The Agency Owner
Browser, desktop and Android/iOS apps plus a shared time-recording terminal give several paths for forty people to clock in, and the mobile apps store entries offline and synchronise automatically once a connection returns. Retroactive entries, a split function for missed breaks and a change annotation on every edited entry cover honest mistakes; we found no public information on geofenced or GPS check-in, and none on bulk correction of entries. 3 4 7 8 9
The Field Supervisor
Browser, desktop and smartphone apps plus a shared time-recording terminal, and the apps capture offline and sync automatically once a connection returns — that is the basement test passed. Retroactive entries, a split function to book a missed break afterwards, and an annotation whenever someone changes a time entry give a foreman a correction workflow. We found no public information on GPS or geofenced check-in or on bulk correction. 3 4 7 8 9
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
Working-time law & audit record
Show reasoningHide reasoning
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.
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
The Payroll Officer
Begin, duration and end are recorded minute-accurately with the recording duty cited, break rules are adjustable, breaks can be enforced in company settings, and both employee and employer are warned when working times are not kept. The vendor's own help pages state the automatic break deduction books no break period, so an inspection would not show when the break was taken unless the employee records it, and retention appears only as the privacy policy's four-year default with a ten-year tax archive. We found no public information on daily-maximum or eleven-hour rest-period checks, tamper-evident storage, or an export built for an inspection. 4 6 7 9 10
The Works Council Advocate
The vendor cites the BAG 2022 duty, lets break rules be configured and enforced in company settings, warns employee and employer alike when working times are breached, and annotates every changed entry — the warning reaching the employee too is a point in its favour. But the help text itself states that automatic break deduction books no break period, so on inspection it would not be evident when the employee actually paused. We found no public information on rest-period or daily-maximum checks, on retention tied to the recording duty, or on tamper-evident change history. 4 10 3 6
The Agency Owner
The vendor cites the BAG 2022 duty, records start, duration and end, offers configurable break rules that can be enforced, warns when working times are breached, annotates changes and locks timesheets behind digital signatures. The vendor itself states the automatic break deduction books no break period, so on an inspection it would not be evident when a break happened unless the employee records it; we found no public information on daily maximum or eleven-hour rest checks, or on an export shaped for an inspection. 3 4 6 10
The Field Supervisor
The vendor names the BAG 2022 duty, records begin, duration and end minute-exact, and offers configurable break rules, an enforce-breaks setting and a warning to both sides when times are not kept, with a change annotation on every entry. Its own help page states the automatic break deduction books no break period, so at an inspection it would not be evident when the break was taken unless the employee records breaks. We found no public information on checks for the daily maximum or the 11-hour rest period. 4 7 10
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
Absence & shift planning
Show reasoningHide reasoning
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.
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
The Payroll Officer
Vacation accounts with remaining leave and holidays are calculated automatically, sickness and a long list of absence types carry per-type approval rules into a team calendar, country-specific public holidays can be stored, and absences sync to Personio. We found no public information on shift or duty rostering, availability, substitution or swap workflows — the planner in view arranges absences by drag and drop, not shifts. 11 12 15
The Works Council Advocate
Vacation accounts with remaining leave computed automatically, country-specific public holidays, ten absence types with approval set per type, sickness and child-sickness, mobile requests with supervisor notification and a shared team calendar — the absence half is solid and maps cleanly onto a works agreement. We found no public information on shift rosters, shift templates, substitution or swap workflows, availability or coverage checks; the drag-and-drop planner places absences, not duties. 11 12 8 7
The Agency Owner
Absence is genuinely handled: automatic vacation accounts with carry-over and holidays, sickness and child sickness among ten absence types, approval configurable per absence type, a team calendar and country-specific public holidays. Shift planning is the other half of this criterion and we found no public information on rosters, shift templates, availability or swap workflows. 3 11 12
The Field Supervisor
Vacation accounts with carry-over and country-specific holidays, ten absence types with per-type approval rules, a team calendar and mobile entry are all evidenced, and sickness runs through the same system. We found no public information on shift or duty rostering, availability, or substitution and swap workflows — the planning half of this criterion. 8 11 12
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
Project, cost-centre & billing
Show reasoningHide reasoning
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.
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
The Payroll Officer
Every entry carries client, project, subproject, service and an hourly rate, hour and money budgets trigger automatic warnings before a project runs at a loss, and invoice drafts pass per click into named invoicing tools — Lexware Office, sevdesk and easybill — without retyping, with approvals by digital signature on the work record. We found no public information on cost centres, role-based rate cards, or rate behaviour when a rate changes mid-project. 1 3 13 14
The Works Council Advocate
Entries carry customer, project, subproject, service, employee, description and hourly rate at capture; budgets in hours and money trigger warnings before a project slides into loss; and recorded times become invoice drafts handed to Lexware Office, sevdesk or easybill without retyping, with reports exported as PDF or CSV. We found no public information on a cost-centre field, a billable flag, or how rates behave when they change mid-project. 13 3 14
The Agency Owner
Entries carry customer, project, subproject, service, employee, description and hourly rate at capture, budgets in hours and money trigger warnings before a project slides into loss, and the billing workflow pushes filtered project times with automatic rates into named invoicing tools — Lexware Office, sevdesk, easybill — where the invoice draft is created. Timesheets with digital signatures give an approval step before billing; we found no public information on a billable flag, cost centres, or how a rate change mid-project is handled. 1 3 13 14
The Field Supervisor
Every entry carries client, project, subproject, service, employee and hourly rate at capture, hour and money budgets warn before a project runs into loss, and invoice drafts pass at a click into named invoicing tools — Lexware Office, sevdesk, easybill — with PDF and CSV as fallback. We found no public information on a cost-centre field, a billable flag, or how a rate change mid-project is handled. 1 3 8 13 14
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
Payroll handoff
Show reasoningHide reasoning
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.
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
The Payroll Officer
A maintained connection to DATEV Lohn & Gehalt exists in the product, with client number, consultant number, personnel-number type and salary-type mapping to configure, and absences and the hours account stand ready for payroll preparation. But the vendor's own setup pages state this export is exclusively for hourly wage earners and excludes any employee who has entered surcharges — so night, Sunday and holiday work leaves the payroll run through no documented path. We found no public information on a lock step before transmission or on corrections after the close; the captured pages show reports leaving as PDF or CSV. 3 11 15 16
The Works Council Advocate
A maintained DATEV Lohn & Gehalt connection is documented in detail — client and consultant numbers from the tax adviser, personnel-number type, wage-type mapping before export — and absences are stated as ready for preparative payroll, with interfaces to payroll programs and CSV as fallback. The export is restricted to hourly wage earners and excludes employees with surcharges, and we found no public information on a lock step before transmission, retro corrections after the close, or scoped access for the tax adviser. 15 16 11 3
The Agency Owner
A documented connection to DATEV Lohn und Gehalt exists, with client and consultant numbers sourced from the tax adviser, wage types assigned in configuration and absences ready for preparative payroll. But the vendor states the export is available exclusively for hourly wage earners and that surcharges, and employees who have entered surcharges, are excluded from it; we found no public information on a lock step before transmission or on retro corrections after the close. 3 11 15 16
The Field Supervisor
A documented DATEV Lohn und Gehalt connection exists, with client and consultant numbers, personnel-number type and salary-type mapping, and recorded absences stand ready for payroll preparation. The same help pages state the export is available exclusively for hourly wage earners and excludes anyone with surcharges entered, so night and holiday surcharge work leaves this path. We found no public information on a lock step before transmission or retro handling after the close. 3 11 15 16
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
European sovereignty
panel opinion
Show reasoningHide reasoning
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.
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
The Payroll Officer
Clockodo GmbH is the German contracting entity with German register details, the product stores data on German servers, and the privacy policy names processors with addresses — including a US payment provider processed under the EU-US Data Privacy Framework — alongside a trust centre carrying the data-processing agreement, technical measures and data-centre information. Processor categories such as the conference platforms remain unnamed, and we found no public information on data-centre certification or an on-premises option. 5 6 8
The Works Council Advocate
The contracting entity is a German GmbH, the product pages state data sits on German servers, a trust centre publishes the processing agreement, technical measures and data-centre information, and processors are named — Mittwald and HubSpot in Germany, PayPal in Luxembourg, Stripe in the USA with the Data Privacy Framework given as basis — while logfiles are bounded at thirty days, a bound I welcome. We found no public information on ownership or data-centre certification, the product is cloud only with no on-premises option evidenced, and registration stores IP addresses for abuse prevention — a watchful detail I note without applause. 5 6 8
The Agency Owner
Clockodo GmbH is a German entity registered at Amtsgericht Hamm, the system is stated to store data on German servers, and the privacy policy publishes its subprocessors — Mittwald and HubSpot in Germany, PayPal in Luxembourg, Stripe in the USA — with the EU-US Data Privacy Framework and standard contractual clauses named as transfer mechanisms. A trust centre covers processing agreements, technical measures and data centres; we found no public information on ownership structure or an on-premises option, and the operator of the application's own data centre is not separately named. 5 6 8
The Field Supervisor
German company, data stored on German servers, a trust centre carrying the processing agreement and data-centre information, and subprocessors named by company and country, including Stripe in the USA with the Data Privacy Framework as the stated basis. The product is presented as a cloud solution; we found no public information on an on-premises or private-cloud option, and the captured pages do not name the data-centre provider behind the application data itself. 5 6 8
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
Pricing transparency
Show reasoningHide reasoning
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.
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
The Payroll Officer
All plans carry public per-user net prices — Basic at 4 € per user per month, Pro at 8 € for the first twelve months then 10 €, Pro Plus at 10 € then 12 €, the plus package at +2 € — with monthly or annual billing, cancellation at month end, VAT treatment stated, and no base or setup fee. A time-recording terminal is offered as a capture point, but we found no public information on terminal pricing or on a calculator that produces the annual invoice for a given headcount. 2 3
The Works Council Advocate
Every tier carries a public per-user price — Basic 4 €, Pro 8 € for the first twelve months then 10 €, Pro Plus 10 € then 12 €, plus package +2 € per user per month — with monthly or annual billing, cancellation at month's end, no base or setup fee, net prices plus statutory VAT, and a single user free permanently. We found no public price for the time-recording terminal, and the vendor invites firms with at least twenty users to request an individual offer, so a buyer cannot compute the annual invoice for a larger headcount from public pages alone. 2 8 3 13
The Agency Owner
The pricing page gives per-user net prices for three tiers — Basic at 4 €, Pro at 10 € with 8 € for the first twelve months, Pro Plus at 12 € with 10 € for the first twelve months — plus a Plus package at +2 € per user per month, with monthly or annual billing, cancellation to any month-end and VAT treatment stated, so most of an annual invoice is computable. The time-recording terminal and the DATEV payroll add-on carry no public price, and from twenty users the vendor invites an individual offer — so for a forty-person firm like mine the real annual cost ends in a conversation. 2 3 8
The Field Supervisor
Every tier is priced publicly as a net per-user monthly price — Basic 4 €, Pro 10 € with 8 € for the first twelve months, Pro Plus 12 € with 10 € likewise, the Plus package at +2 € — with monthly or annual billing, cancellation to month end and VAT treatment stated. We found no public information on a price for the time-recording terminal hardware, and from 20 users upward the vendor invites individual offers rather than published maths. 2 3
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
European sovereignty — proven facts
1 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Incorporated in DE | 3/3 pts | 5 Report an error |
|---|---|---|---|
| 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
- Evidence ages. The oldest capture behind this page is from 15 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
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.
- 26 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 13 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 5 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 hosting facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 data fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 subprocessors fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (16)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.clockodo.com Checked 15 Sep 2026 Details →
- 2 Pricing www.clockodo.com Checked 15 Sep 2026 Details →
- 3 Features www.clockodo.com Checked 15 Sep 2026 Details →
- 4 Working-time recording www.clockodo.com Checked 15 Sep 2026 Details →
- 5 Imprint www.clockodo.com Checked 15 Sep 2026 Details →
- 6 Privacy policy www.clockodo.com Checked 15 Sep 2026 Details →
- 7 Capture in the real workplace — found from sitemap www.clockodo.com Checked 1 Oct 2026 Details →
- 8 Capture in the real workplace — found from sitemap www.clockodo.com Checked 1 Oct 2026 Details →
- 9 Working-time law & audit record — found from sitemap support.clockodo.com Checked 1 Oct 2026 Details →
- 10 Working-time law & audit record — found from sitemap support.clockodo.com Checked 1 Oct 2026 Details →
- 11 Absence & shift planning — found from sitemap www.clockodo.com Checked 1 Oct 2026 Details →
- 12 Absence & shift planning — found from sitemap support.clockodo.com Checked 1 Oct 2026 Details →
- 13 Project, cost-centre & billing — found from sitemap www.clockodo.com Checked 1 Oct 2026 Details →
- 14 Project, cost-centre & billing — found from sitemap support.clockodo.com Checked 1 Oct 2026 Details →
- 15 Payroll handoff — found from sitemap support.clockodo.com Checked 1 Oct 2026 Details →
- 16 Payroll handoff — found from sitemap support.clockodo.com Checked 1 Oct 2026 Details →