Violations
Record discipline events that feed into scores.
Some KPI systems include discipline or behavior — being late, missing a process step, and so on. KManagement handles this with a violation log: a record of dated incidents that can automatically feed into a person’s score.
The violation catalog
An admin maintains a catalog of violation types — each with a code, a name, and a description. The catalog defines what kindsof violations exist; it does not carry point values. How much a violation costs is decided in the framework’s formula, not the catalog, so the same incident can weigh differently in different frameworks.
Recording a violation
Admins and managers record individual violations against a person, with a date. Managers can only record violations for people on teams they manage.
Feeding violations into a score
A countmetric in a framework can be linked to a violation type. When you calculate a cycle, the app counts the matching, non-deleted violation records that fall within the cycle’s dates and fills that metric in automatically. From there, the framework’s formula decides how much each one deducts.
Note
The link is automatic and repeatable: recalculating gives the same count, and a manual override still wins if you need to correct it. This keeps discipline scoring consistent and traceable.