Solution · Public & co-determined workplaces
Time tracking and rosters for works-council environments
Introducing time tracking where a Betriebsrat has co-determination rights is not a software purchase, it is a negotiation. The software can either give that negotiation facts, or make it harder. Ours was designed around the questions councils actually ask.
"Where does the data live?"
On your server. Every entry, clock-ins, corrections, rosters, absence records, sits in your Nextcloud's database, on infrastructure you choose. There is no vendor cloud copy to audit, no sub-processor list to review, no cross-border question to resolve. For many councils this answer alone decides the direction of the discussion.
"Who sees what?"
Role separation is built in, not configured in: employees see their own records, approvers see their team's, administrators see what administration requires. The system distinguishes between viewing (what a role can open) and exporting (what a role can pull out), a distinction councils care about, because a tool that lets any supervisor export everything to a spreadsheet is a monitoring tool with extra steps.
"Can entries be changed afterwards?"
Yes, transparently, which is the important part. Corrections do not overwrite: the append-only audit trail records what changed, who changed it, and when. Month closures freeze the period into a snapshot; reopening is a deliberate, logged act. A council evaluating the software can verify this behaviour in the source code and in the changelog, not just in a brochure.
"What happens with the roster data?"
DutyCheck publishes rosters inside the same infrastructure. Roster snapshots preserve what was actually published, so "the posted plan said something different" is verifiable rather than he-said-she-said. That is the property behind our audit-trail article: these features exist so the software can defend itself, and your staff, in a dispute.
"What does it cost: and what does it enable?"
The web apps are AGPL and free; the mobile companions are paid per seat (published prices, small floors). There is no per-head analytics upsell, no premium reporting tier that turns employee data into a feature bundle. The paid thing is a licence key, not a data relationship, a sentence your council will appreciate because it is short.
Co-determination done well makes rollouts faster, not slower: a council that can verify the facts approves with confidence instead of delay. If you are preparing that conversation, the sales FAQ and the release notes are the documents to put on the table, everything in them is checkable.