What the Records Cannot Tell You
Questions people ask of attendance data that it cannot answer, and where the real answer is.
What not to do
A record of who was present answers a narrow question well. Asked to answer wider ones, it produces confident nonsense.
Whether someone is committed
Absence reflects health, caring responsibilities, transport and luck at least as much as anything about the person.
The person with a chronic condition and the person with a new baby will both have higher absence than someone with neither, and neither fact is about commitment.
Where to look instead: the work.
Whether an absence was genuine
The record shows a date, not a state of health.
Suspicion in the absence of evidence is a poor basis for anything, and acting on it is how a small business acquires a tribunal claim.
Where to look instead: the return-to-work conversation, and if there is a real concern, the proper process with advice.
Why absence is rising
The data shows that it is, and where.
It does not show why, and the causes are usually conditions: a shift pattern, a workload, an illness going round, a manager.
Where to look instead: ask people, starting with the team where it is concentrated.
Whether you are overstaffed or understaffed
Attendance shows who was there, not whether that was enough.
A team with no coverage failures may be comfortably staffed or may be quietly working short.
Where to look instead: coverage failures alongside the minimum staffing sheet, and whether people are taking their leave.
Who is the problem
The question itself is usually wrong.
Where absence concentrates, look at the conditions first, consistently, and say publicly that this is the policy.
Because the alternative teaches people to conceal reasons, and then the data describes nothing at all.
How to answer when asked
Say what the records do support: who was present, on which days, for what broad reason, and where absence concentrates.
Say what would answer the actual question, which is almost always a conversation.
Do not produce a number you cannot defend. In a business of twenty people, a chart presented as evidence about an individual will be remembered long after the chart is gone.
What they do support
Coverage planning.
Leave balances and pay calculations.
Statutory records.
Patterns by team, shift or period, which is where the useful findings are.
Four things, answered reliably, and defending that boundary is what keeps those four trusted.
Say what would answer it
The response that keeps you useful rather than obstructive.
Name what the records do support.
Name what would actually answer the question — usually a conversation, sometimes a different measurement.
Where nothing is measuring it, say so. That is a finding about the business rather than a failure of the attendance record.
Do not produce a weak number because a number was asked for. In a small business it will be remembered and repeated long after the caveat is lost.
Connect policy to configuration
The practical choices behind this note can be compared with this implementation prompt. Keep the written purpose in control of the setup, enable only data needed for that purpose and review the result with affected employees.