The Thing You Are Spending

Almost every record in this collection is created by someone reporting something about themselves. That makes the whole system rest on a thing that does not appear in it.

Where the data comes from

Sickness: they tell you.

The reason for an absence: they tell you.

Whether a late arrival was transport or an alarm: they tell you.

Whether they are well enough to return: they tell you.

None of it is observed. It is reported, which means its accuracy is a function of the relationship rather than of the system.

What people do when the relationship goes

They report sickness as holiday, to avoid the trigger, which removes it from your absence picture entirely.

They come in ill, which spreads infection and lengthens the eventual absence.

They stop mentioning a condition that an adjustment would help, which turns a manageable situation into a long absence.

They give the shortest possible explanation, which removes the work-related causes you would otherwise have found.

Each makes your data worse while making the numbers look better, which is the trap.

What spends it

Public displays. Demanding diagnoses. Notes for a single day. Automatic triggers. Selective application. Discussing someone's absence with colleagues.

Each is individually small. The effect is cumulative and it is not reversible quickly.

What builds it

Applying the process to everyone, including the reliable.

Fixing what the return-to-work conversation surfaces, which shows that reporting a cause produces a change rather than a mark on a record.

Covering absences without visible resentment.

Holding the boundary on health information, which people notice.

Saying no to the requests in the refusal note, publicly, which is the clearest possible signal about what the system is for.

The honest tension

Some people do take advantage, and pretending otherwise is not useful either.

But the response to one person is not a system change for everyone, which is the most common mistake in this area.

Deal with the individual through the ordinary process, and leave the arrangement that works for the other nineteen alone.

The measure

Are people telling you things before they become problems?

A team that mentions a developing health issue, a transport change, a caring responsibility, is a team where the arrangement is working.

A team that reports nothing until it is a crisis has told you what it thinks of the system, and no amount of tracking will replace what has been lost.

Do not change the system for one person

The most common mistake in this area.

Someone takes advantage. It happens.

The response is to deal with that individual through the ordinary process.

Not to introduce a scoring system, a note requirement or a public display for the other nineteen who were not doing anything.

A system change punishes the compliant and barely inconveniences the person it was aimed at, who will adapt faster than anyone.

A concrete product reference

When translating this principle into a buying test, employee screen monitoring software provides a concrete workflow reference. Verify the current behaviour in a trial, retain the exported evidence and judge it against the purpose and limits described above.

Independent reference

For an external point of reference, see the CIPD. Its people-management resources provide a broader reference when evaluating how an attendance process affects trust and employee relations.