timecockpit

The Operations Lead

Mobile capture is a browser app rather than an installable native one — the one-tap timer, touch-optimized bookings and vacation requests work on phones, but the pages list offline mode, geolocation and a native app as planned rather than shipped, and the docs describe needing at least a 3G connection with automatic reconnect for short dropouts. I found no public information on any shared kiosk, terminal or badge capture for workshop crews, on GPS or geofenced check-in, or on a correction and approval workflow for time entries with an audit trail. 1 4 5

Report an error

The Payroll Officer

Browser, desktop and a mobile web app with a one-tap timer serve the desk, and sidekick records computer work with the signals kept local, but offline mode and geolocation appear only as planned features and a native app is still under consideration. I found no public information on shared terminals, badge readers, or a correction and approval workflow for recorded time. The reconnect handling covers short interruptions, which is a network hiccup, not a day on a site with no signal. 1 4 5

Report an error

The Works Council Advocate

Capture runs in the browser and on phones and tablets via a web app with a one-tap timer and touch-optimised booking, and we found no public information on offline capture (the vendor lists offline mode as planned), on any shared terminal or kiosk, or on a correction workflow for time entries. The optional sidekick records what a person worked on at their computer; the vendor states the signals stay on each person's own machine, which is the right design, but it is a monitoring feature a works council will insist on having off by default. 1 4 5

Report an error

The Agency Owner

Browser, PC, Mac and a phone-friendly web app with a one-tap live timer cover my desk people, and sidekick records computer work automatically with signals kept local — but offline mode is only listed as planned, and I found no public information on shared terminals, geofenced or GPS check-in, or a correction-and-approval workflow for time entries. 1 4 5

Report an error

The Field Supervisor

What the pages show is a browser tool with a phone-friendly web app and a one-tap timer, and it lives on the network: the vendor's own mobile guide rates 3G as the minimum and lists an offline mode as a future feature, with a native app still under consideration — nothing my crews can lean on in a basement this week. We found no public information on shared terminals, badge or kiosk capture, or a time-entry correction workflow a foreman can run with approval and an audit trail. For site work that leaves time filled in from memory on Friday. 1 4 5

Report an error

The Skeptic

Browser, PC, Mac and a progressive web app for phones and tablets, plus automatic signal capture on Windows and macOS whose data stays local — but the offline mode for mobile appears only on a planned-features list, and I found no public information on shared terminals, badge readers, or a correction workflow with approval for time entries. The reconnect documentation covers short interruptions, not a shift without network. 1 4 5 3

Report an error

The Operations Lead

The working-time model is genuinely parameterized rather than one flat rule: predefined sets for Germany (10-hour daily maximum, 48-hour week, the 30- and 45-minute break rules) and Austria, per-user limits, break validation, rest checks for nights, weekends and public holidays, separate ceilings for travel time, and retroactive validation surfaced in a per-employee violations view. I found no public information on retention of the record, change history on individual entries, handling of on-call or standby time, or an export shaped for an inspection, which keeps it out of the top band. 6 7

Report an error

The Payroll Officer

Predefined Austria and Germany rules with configurable daily, weekly, break and rest-period checks, per-user limits, travel-time variants and retroactive validation, plus a per-user violations view, go beyond a flat break rule. I found no public information on statutory retention of the time record, tamper-evident change history, overtime and time-account rules, or an export shaped for an inspection, so I stop short of the top of this range. 6 7 12

Report an error

The Works Council Advocate

Predefined rule sets for Germany and Austria model daily and weekly maxima, break thresholds and night, weekend and holiday rest periods, configurable per user and valid retroactively — a real basis for the recording duty, with per-user violation views and exportable lists covering inspection questions. We found no public information on a stated retention period, on tamper-evident change history for bookings, or on on-call and standby handling, so I cannot call the record inspection-proof. 6 7 12

Report an error

The Agency Owner

Germany and Austria ship as preset rule sets — ten-hour daily maximum, split break rules, night, weekend and public-holiday rest checks — configurable per user and per limit, with a per-employee violations view for any period and active and passive travel time modelled. I found no public information on retention for the recording duty, overtime or time-account rules, or an export built for an inspection, which is what would carry it further. 6 7

Report an error

The Field Supervisor

Rule sets for Austria and Germany ship out of the box — daily and weekly maxima, break thresholds with split options, night, weekend and public-holiday rest checks, and travel-time limits including active and passive travel — and the violations view lets me pull one worker's breaches over any period, even retroactively with the correct limit for that time. We found no public information on overtime and time-account rules, statutory retention of the records, or an export shaped for an inspection, so I stop short of calling it inspection-ready. 6 7

Report an error

The Skeptic

Predefined limit sets for Germany and Austria with daily and weekly maxima, break thresholds, night/weekend/holiday rest checks, per-user limits and a violations view with retroactive validation — the rules are modelled, not approximated. What an inspection would test next is missing: I found no public information on retention of the time record beyond a 35-day backup window, on tamper-evident change history, or on documented handling of exceptions. 6 7 3

Report an error

The Operations Lead

Vacation, sick leave and compensatory time are all recordable full-day or hourly, with a per-type approval workflow routed to supervisors or HR-Admin, automatic lead notifications, rejection reasons and a role-scoped absence calendar with cross-user visibility. I found no public information on automatic vacation entitlement or carry-over, and none on any shift or duty roster, availability planning or coverage checks — for an operation my size the planning half of attendance simply is not evidenced. 5 8 9

Report an error

The Payroll Officer

Vacation, sick leave and compensatory time with hourly or full-day entries, a configurable approval workflow with approver roles, notifications and rejection reasons, and a combined absence calendar with role-based visibility is a real workflow, not a spreadsheet. I found no public information on automatic entitlement and carry-over, public-holiday calendars per location, or any shift or duty roster at all. 8 9

Report an error

The Works Council Advocate

Vacation, sick leave and compensatory time are recorded hourly or by the day with an approval workflow, notifications and role-based visibility that hides the absence type from colleagues — exactly the data economy a works council wants to see. We found no public information on automatic entitlement calculation, on carry-over, or on shift and duty rostering. 5 8 9

Report an error

The Agency Owner

Vacation, sick leave and time off in lieu all run through a real approval workflow — department-lead notifications, rejection reasons, retroactive approval, role-based visibility in a shared absence calendar — which is more polish than most. But I found no public information on automatic entitlement calculation, carry-over, or any shift or duty rostering at all, and that is the half my clients' teams actually run on. 8 9

Report an error

The Field Supervisor

Vacation, sick leave and time off in lieu are real entries, full-day or hourly, with a solid approval chain: supervisor or HR-Admin decides, department leads get notified, rejections carry a reason, and the calendar shows pending requests with role-based visibility — vacation requests also work from the phone. But we found no public information on automatic entitlement or carry-over, and no public information on shift rosters, duty plans or substitution workflows — the half of attendance that decides whether the plan survives the 5am sick call. 5 8 9

Report an error

The Skeptic

Vacation, sick leave and compensatory time with a real approval workflow, lead notifications, rejection reasons and a role-scoped absence calendar — that half is well documented. I found no public information on automatic entitlement, carry-over, or any shift or duty roster, which is the other half of this criterion. 8 9 5

Report an error

The Operations Lead

Customers, projects and tasks sit in a hierarchy with hourly rates definable at each level plus an effective-rate calculation, budgets in hours and money per project and per task, billable flags, and invoicing built into the product itself — invoice items generated from bookings, the rate snapshotted at invoicing time, entries turning read-only once billed, credit notes, VAT handling and ZUGFeRD output. I found no public information on a cost-centre dimension or rate cards by person and role, and interfaces to SAP or Microsoft Dynamics are described as built on request rather than maintained handoffs. 1 10 11

Report an error

The Payroll Officer

Customer, project and task hierarchy with rates at each level and an effective-rate calculation, budgets in hours and money, billable flags, and time turned into invoice items where the valid hourly rate is frozen into the billed field and entries go read-only after billing — the rate snapshot is exactly what a rate change mid-project needs. I found no public information on a cost-centre dimension, budget warnings, or a maintained handoff into named accounting systems. 1 10 11

Report an error

The Works Council Advocate

The customer–project–task hierarchy with rate inheritance, billable flags, budgets in hours and money, and invoices generated directly from booked time with a rate snapshot at billing is genuinely usable for an agency or professional-services firm. We found no public information on cost centres, on per-person rate cards, or on a maintained handoff into named accounting systems — interfaces to SAP or Microsoft Dynamics are built on request. 1 10 11

Report an error

The Agency Owner

This is my world and it holds up: customers, projects and tasks with a billable flag, budgets in hours and money at project and task level, rates cascading customer to project to task, and the valid rate snapshotted onto each entry at invoice time so a mid-project rate change never reprices last month. Time becomes invoices in-product with automatic invoice items, ZUGFeRD PDFs, credit notes and read-only locking after billing; I found no public information on per-person or role rate cards, cost centres, overrun warnings, or a maintained handoff into a named accounting system. 1 10 11

Report an error

The Field Supervisor

Customers, projects and tasks sit in a proper hierarchy with rates set per customer, per project and per task, budgets in hours and money, and a billable flag, and booked time turns into invoice items with the hourly rate frozen at billing — a rate change mid-project cannot rewrite what was already invoiced, and billed entries become read-only. We found no public information on cost centres or per-person rate cards, and the only named system interfaces are ones the vendor builds on request. 1 10 11

Report an error

The Skeptic

Customer–project–task hierarchy with rate overrides at each level, billable flags, budgets in hours and money, and invoicing that snapshots the valid rate at billing time, makes billed entries read-only and writes ZUGFeRD PDFs. What the pages do not show: cost centres, rate cards by person or role, budget warnings, and approval of timesheets before billing. 10 11 1

Report an error

The Operations Lead

The month leaves as an Excel export — every list exports with template and script automation that can even mail per-user reports — and I found no public information on any named payroll system such as DATEV, a defined payroll format, lock-before-transmission steps, or handling of night, Sunday and holiday surcharges. Connections to SAP or Microsoft Dynamics are stated as built on request, which is a project, not a maintained payroll path. 1 12 13

Report an error

The Payroll Officer

The recorded month leaves as an Excel export — templates, scripted queries, even automated per-user pivot reports by email — and a Web API exists for building a bridge yourself, but I found no public information on a named payroll system, a defined payroll format, a lock step before transmission, or surcharges for night, Sunday and holiday work. To me this is a handoff someone assembles after the fact, not one that was ever designed for payroll. 1 12 13

Report an error

The Works Council Advocate

Every list exports to Excel, Word and PDF, template and scripted exports exist, and a web API can move time entries between systems — but we found no public information on any named payroll system, on a defined payroll format, or on night, Sunday and holiday surcharge handling. As things stand, the month's data reaches payroll only as something the buyer builds and retypes themselves. 1 12 13

Report an error

The Agency Owner

The month leaves as Excel from any list — plain, template-driven or fully scripted and emailed — and there is a REST/OData API for building a feed, but that is a do-it-yourself path. I found no public information on a named payroll system such as DATEV, a defined payroll format, surcharge handling for nights, Sundays and holidays, or a lock step before transmission. 1 12 13

Report an error

The Field Supervisor

The month leaves as Excel, Word or PDF from any list, with script-based Excel exports for special cases and a general web API for exchanging data with other systems — but we found no public information on a named payroll system such as DATEV, on night, Sunday and holiday surcharges, or on a lock step before transmission. As it stands, someone in the office retypes it. 1 12 13

Report an error

The Skeptic

The month leaves as Excel, Word or PDF — every list exportable, with templates, scripts and automated per-user email reports — plus a web API for exchanging time entries. I found no public information on any named payroll system, DATEV or otherwise, and nothing on night, Sunday or holiday surcharges, time accounts, or a lock step before transmission. 12 13 1

Report an error

The Operations Lead

The contracting entity is software architects gmbh in Leonding, Austria, and the service runs in named Microsoft Azure data centers in Amsterdam and Dublin with a dedicated database cluster per customer, a data processing agreement, and ISO 27001 referenced for the data centers. Providers processing outside the EEA are named with their legal basis (adequacy decision or standard contractual clauses), though they appear in the privacy statement rather than a full published subprocessor list, and the pages state the Microsoft Privacy Statement also applies when you subscribe — something I would want our lawyer to look at. 1 2 3

Report an error

The Payroll Officer

The vendor's own pages state an Austrian contracting entity, Microsoft Azure data centres in Amsterdam and Dublin with a dedicated database per customer and ISO 27001 certification, a published list of processors, and a named legal basis for processing outside the EEA. The independently gathered sovereignty attributes nonetheless leave legal jurisdiction, data residency and processor exposure unconfirmed, so I hold the score below the top of this range despite the vendor's statements. 1 2 3

Report an error

The Works Council Advocate

The controller is an Austrian company in Leonding, the service runs in Azure data centres in Amsterdam and Dublin with a dedicated database per customer and support access only on request, and any processing outside the EEA is named with the EU-US Data Privacy Framework or standard contractual clauses as its basis. We found no published subprocessor list, and the independently sourced sovereignty attributes came back unconfirmed, so I stop short of full credit. 1 2 3

Report an error

The Agency Owner

An Austrian entity in Leonding with an Austrian VAT number, the Austrian data protection authority named, and hosting in Azure data centres in Amsterdam and Dublin with a dedicated three-node database cluster per customer, an offered DPA, and any US processing based on the adequacy decision or standard contractual clauses. I found no public information on a full published subprocessor list beyond the providers named in the privacy statement, and the only private option is a database in the customer's own Azure subscription on request, not on-premises. 1 2 3

Report an error

The Field Supervisor

The paper trail is decent: an Austrian company in Leonding is the contracting party, the data sits in Microsoft Azure in Amsterdam and Dublin with ISO 27001 certification, standard contractual clauses and a data processing agreement, and any processing outside the EEA is named with its legal basis. We found no public information on ownership or a maintained subprocessor register, and everything runs in the vendor's cloud — the only step toward our own infrastructure is a database in the customer's own Azure subscription on request. 1 2 3

Report an error

The Skeptic

The vendor's own pages document an Austrian contracting entity, Azure hosting named to Amsterdam and Dublin in ISO 27001 certified data centres, a data processing agreement, and Microsoft standard contractual clauses plus the Data Privacy Framework as basis for non-EU processing. It falls short of the top marks because the named providers are largely website services and Microsoft, without a published full subprocessor list for the product itself, and the buyer's own sourcing found entity and ownership details unconfirmed outside the vendor's pages. 1 2 3

Report an error

The Operations Lead

A per-user price of €10.85 per user per month is public, with daily billing, cancellation any day, a 30-day trial without credit card, and a one-time €29.90 first year on the Starter plan for teams of up to 10 users. I found no public information on VAT treatment or on the price of the enterprise offering where single sign-on, a sandbox database and a database in your own Azure subscription sit, so the full annual invoice for a 200-person operation is not computable from public pages alone. 1 3

Report an error

The Payroll Officer

A per-user price of €10.85 per user per month is public, with billing on a daily basis and cancellation any day, a 30-day trial without a credit card, and a one-time €29.90 for the first year on the Starter plan for teams of up to 10 users. The enterprise option that covers single sign-on and the sandbox database carries no published price, and VAT treatment is not stated. 1 3

Report an error

The Works Council Advocate

A per-user price of €10.85 per user per month is public, alongside 30 days free without a credit card, daily billing with cancellation any day, a one-time €29.90 for the first year on the Starter plan for teams of up to 10 users, and the first year free for freelancers. We found no public information on which plan the monthly figure belongs to, on separately priced modules, or on VAT treatment, so a buyer still cannot compute the real annual invoice from public pages. 1 3

Report an error

The Agency Owner

The headline reads €10.85 per user per month, billed on a daily basis and cancelable any day, with a 30-day trial without credit card, freelancers free for the first year, and teams up to ten users at a one-time €29.90 for the first year on the Starter plan — refreshingly few traps. I found no public information on VAT treatment or on a price for the enterprise tier named alongside the sandbox database and single sign-on, so I cannot compute the full annual invoice from public pages alone. 1 3

Report an error

The Field Supervisor

The headline is public and unusually honest: €10.85 per user per month, billed on a daily basis and cancelable any day, 30 days free without a credit card, and first-year offers for small teams (a one-time €29.90 for up to 10 users on Starter) and freelancers stated in plain figures. The gaps: single sign-on and the sandbox database are said to sit on the enterprise tier with no public price, and we found no public information on the VAT treatment of these figures. 1 3

Report an error

The Skeptic

One public price of €10.85 per user per month with billing stated as daily and cancellation any day, a Starter offer of a one-time €29.90 for the first year for up to 10 users, and a first year free for freelancers — the cancellation terms are unusually generous. But the pages describe an enterprise tier whose sandbox database, database in the customer's own Azure subscription and single sign-on carry no price, and I found no public information on VAT treatment. 1 3

Report an error