Sick-leave overview

Why put sick leave in the WRA?

It has to be there — it has been a requirement in Danish WRA work since 2010. In practice, most small companies handle sick leave in their payroll tool, and then it never becomes part of the work-environment conversation. It is also hard to take seriously when you see the number as a single raw percentage. What is five days on average when you run a ten-person company through a busy season?

The sick-leave overview brings the numbers into the place where they actually matter — next to the WRA where you are already taking a position on the work environment. The goal is not to turn absence tracking into a policing project. The goal is to let the numbers point at where the physical and mental wear really sits, so the action plan hits the right spots.

What it will look like

You enter the leave once per quarter — either as a bulk import from payroll or manually if that is faster. APV then works out patterns over a rolling twelve months: which months see leave climb, which job types precede sick notes, where repetition shows up with the same employees.

The result is shown as simple graphs and short observations, not as statistics reports. “Leave climbs in February and March for the last two years” is useful. “Employee X averaged 4.3 sick days over the period” is not. When patterns appear, you can turn them into an action-plan item with a single click.

What happens to the numbers?

The numbers live in your own WRA and do not leave the company. You decide who can see them — typically the owner and a work-environment representative. Individual sick days are anonymous from the outside, but visible in aggregate for those responsible. When you export the WRA binder for the labor inspector, the aggregated view goes with it without exposing individual cases.

Have thoughts on how sick-leave data can sit inside the WRA without feeling like surveillance? Get in touch.