Mitrefinch

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 — Not a time-recording tool; working time cannot be captured in the product.

3 — Clocking in and out or a timer in the browser or an app, with manual entries; offline use, shared terminals and corrections are basic or not described.

5 — Web and mobile apps for clocking in and out, a shared kiosk, terminal or badge option or offline capture that syncs, and corrections requested by the employee and approved by a manager.

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.

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 — A project or task timer that keeps no attendance record of working time (start, end, breaks).

3 — Start, end and break times recorded per day with a working-time report per employee; ArbZG checks and retention are basic or not described.

5 — Start, end and breaks recorded for the recording duty (BAG 2022 or ArbZG named), automatic break rules, warnings on the daily maximum or the rest period, and overtime balances.

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, a change log on entries, 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.

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

0 — Neither absence handling nor shift planning is part of the product.

3 — Vacation requests with approval and an absence calendar, or a basic shift plan; entitlement rules and rostering are basic or not described.

5 — Absence management with entitlement balances, sickness recording and an absence calendar, plus shift or duty planning with templates or employee availability.

8 — Public-holiday calendars per location, pro-rata entitlement and carry-over, 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.

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; the product records time without any project, task or cost-centre dimension.

3 — Time booked to projects or clients with a report per project; rates and billable status are basic or not described.

5 — Projects and tasks with a billable flag, hourly rates, reports per project and client, and an export or integration toward invoicing.

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.

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 — Payroll is outside the product: it records client or project time only and prepares nothing for payroll.

3 — An export (CSV, Excel or PDF) of hours and absences for the payroll office; named formats and surcharges are basic or not described.

5 — A named payroll integration or a documented export format for at least one major system (e.g. DATEV LODAS/Lohn und Gehalt), 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.

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. Dimensions not proven either way are unknown, not non-European.

0 — Vendor, contracting entity and hosting shown to be outside the EU, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist and one European element is proven (an EU contracting entity or representative, or EU hosting as an option); the rest of the chain is not stated.

5 — An EU contracting entity and EU hosting stated, with a data processing agreement; the subprocessor list is not published in full or includes non-EU providers without a stated safeguard.

8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, the full subprocessor list published with locations, 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.

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 public "from" price per user or one priced tier; how cost scales with modules, hardware or minimum seats is unclear.

5 — Per-user prices public for the main tiers with the billing period stated and the main inclusions given; some pieces (terminal hardware, planning module, payroll export) may be unpriced.

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.