From policy PDF to consistent practice

Nearly every employer we work with has an absence management policy. It usually says something like: three absences in a rolling twelve months leads to an informal meeting, and further absences lead to a written warning.

Nearly every employer also admits it is applied unevenly. One store manager follows it to the letter. Another has never held an informal meeting. A third applies it to the people they find difficult.

Why it is uneven

Because it depends on someone counting. Counting absences over a rolling year, across people who move between stores, while remembering which absences should not count at all, is tedious work that nobody is thanked for.

Let software do the counting

Because every absence already comes through the AI absence line, the counting can be automatic. You tell Jaluru your trigger points. When someone crosses the first one, they are tagged for an informal meeting and the right manager gets an email.

For the later steps, such as a written warning, the system only recommends. A manager confirms each one. We designed it that way deliberately. A disciplinary step is a decision about a person, and a person should make it.

Room for judgment

A fair policy needs exceptions. Managers can reclassify an absence, for example marking a pregnancy-related absence as protected so that it never counts, or changing an unauthorised absence to authorised when there was a good reason for short notice.

The audit trail

If a decision is ever challenged, you have the transcript of each absence call, the time it was made, the notice given, and the Return to Work report. The paperwork is the same for everyone.

An unexpected effect on morale

We expected managers to like this. We did not expect staff to. But the complaint we hear most from crew about absence is not that the rules are strict. It is that they are applied to some people and not others. When the process is visibly the same for everyone, that complaint goes away.