Recent incidents
Log a new incident
Log
Summary
Reference lists that drive the dropdowns β add, rename or remove. Renaming updates past records; removing only hides the name from future dropdowns. Each Management entry can hold an email address (its address book) β used to send reports to that manager.
Escalation ladder
| Stage | Level | Meaning | Typical action |
|---|---|---|---|
| 1 | Awareness | First notice β minor or one-off issue. | Informal word at the point of work. |
| 2 | Verbal Given | Repeat or more significant issue. | Documented one-to-one; targeted support. |
| 3 | Disciplinary | Continued issues after a verbal warning. | Formal disciplinary meeting; report as evidence. |
| 4 | Termination | Final stage of the escalation policy. | Formal termination review. |
How levels are decided
The warning level is assigned per incident when it is logged. "Highest level reached" and the status flags reflect the highest warning assigned to that employee, department or manager in the selected period. A manager held accountable (as the subject) appears only in the Management views.
Cross-device sync (GitHub gist)
Sync this log across mobile and desktop through a private GitHub gist. Data is stored on your device and mirrored to the gist; the token is stored only on this device and never leaves it except to GitHub.
Appearance
Saved on this device only (not synced). Doesn't affect printed reports.