Templates Go Stale

A biometric template is a snapshot. The thing it describes carries on changing: hands wear, faces age, weight shifts, an injury heals into a scar across a ridge pattern. The template does not change at all.

The enrolment decision in “Templates Go Stale” is the moment to explain the whole attendance workflow, not only the reader. An organisation considering Monitask resources for remote desktop monitoring software for remote desktop monitoring software should tell people which records managers can see, how time can be corrected and what fallback applies before any optional identity or activity setting is enabled.

Most installations have no routine for this. Enrolment is treated as a one-time event, and the slow drift between the record and the person shows up years later as a rising refusal rate that gets attributed to the reader, the weather, or the individual.

For an independent benchmark relevant to “Templates Go Stale”, consult the European Commission working-time resources. Use it to test notice, accessibility, security, recordkeeping, retention and exception handling against the real operating process rather than treating a device report as self-explanatory evidence.

How quickly it actually matters

For most office populations, not very: a face template can hold up for years and a fingerprint template for longer. For manual work it is a different picture, because the hand is being actively reshaped by the job.

The useful mental model is that the template ages at the rate the body part is being used. A warehouse operative handling cardboard all day has measurably different prints after two years. A fitter working with solvents can change inside one. This is why the departments with the worst refusal rates are often the ones with the longest-serving staff, which looks like a people problem and is a records problem.

The events that should trigger it immediately

An injury to the enrolled finger or hand. A significant change to the face where face recognition is in use. A prolonged absence, where the person returns and the first week is full of refusals. And any case where a person has needed the fallback more than a handful of times in a month.

None of these are detected automatically by any system in common use. They have to be noticed by a person, which means somebody has to be watching the figures, which brings us back to the single report this whole collection keeps returning to.

Finding the people who need it, from data you already have

Pull per-person fallback counts for the last quarter and sort descending. The top of that list is the re-enrolment queue, and it is almost always shorter than people expect: twenty or thirty names on a site of four hundred.

Work down it. For each person, re-enrol, with more fingers than last time, in a room rather than a corridor. Record the date and the reason. Most of them will drop off the list entirely, and the ones who do not are the people for whom this method is never going to work, which is also worth knowing definitively rather than suspecting.

Making it routine rather than remedial

An annual pass costs very little if it is attached to something that already happens: the safety refresher, the appraisal cycle, the badge renewal. Ten minutes in a room, two or three fingers, done.

What does not work is a calendar reminder to "review enrolments", because nobody has time for an abstract review. Attaching it to an existing event that people already attend is the difference between a routine that happens and a line in a procedure document that does not.

The conversation to avoid

The one where a person who has been refused four mornings running is told to present their finger more carefully. It is almost always wrong, it is heard as an accusation, and it is the main reason people stop reporting problems with the reader at all.

The correct response to repeated refusals is a re-enrolment appointment, offered without ceremony, in the same tone as replacing a worn-out tool. Framed that way it is routine maintenance of the system. Framed the other way it is a performance conversation about somebody's hands, which is not a thing any supervisor should be having.

What to record

Date, who, which method, which fingers, how many attempts, and why the re-enrolment happened. Keep the previous entry rather than overwriting it.

The history is what makes the pattern visible. A person re-enrolled three times in two years is telling you something about the method and the job, not about themselves, and that sequence is invisible in a system that only ever shows the current template. Keeping it costs a row in a table and it is the evidence behind any eventual decision to move a whole department to something else.