Docs

Gyrator for works councils

A one-page explanation for employee representatives. In Germany, co-determination under BetrVG §87(1) no. 6 applies to technical systems suitable for monitoring behaviour or performance.

What it collects

Once per cycle (two weeks by default), people answer about 15 short sliders on their phone: how well connections between groups work, one or two items about their own state such as energy and safety, the share of their time that reaches the people who judge the result, and whether the project’s goal is understood and should change. Optionally, who they asked for help. Answers can be “can’t judge”. Nothing is read from calendars, chat, email or code.

What it cannot do

  • Show an individual’s answers. Results exist only per group, and the software has no screen, export or API that returns a person’s answers. Tests in the code enforce this.
  • Score or rank people. There is no combined score and no colour coding of people.
  • Feed decisions about pay, promotion, hiring or dismissal. The optional AI writes questions for the team’s retrospective, never assessments, and it never receives names.
  • Run without the team knowing. People answer from their own link and see the same team results.

Things to agree locally

  • Small groups. A group of one or two people is identifiable by construction. The software tells a person who is alone in their group before they answer. Agree whether such groups are used at all.
  • The cooperation network (who asked whom for help) is off by default and is not drawn below five people. A person’s name appears on it only if that person consents on their own questionnaire, and only admins see names; consent can be withdrawn at any time. Switching the network on, and whether names are used at all, are team decisions worth recording.
  • The AI layer is off unless the operator sets an API key. If on, it receives group-level numbers and free text with names removed; every request is logged on the server for audit.
  • Email invitations are off unless the operator sets a Resend key. If on, the admin can email each person their own link when a check-in opens; Resend, the mail provider, then receives that person’s name, email address and link, never any answer.
  • Data location. Self-hosted, everything stays on your server, apart from the two optional services above. Retention and deletion follow your policy; deleting a person deletes everything they answered.

More detail: Privacy.