What the Record Will Support
A biometric read is stronger evidence than a card swipe and weaker than people assume. Knowing the weight of each entry prevents it being overloaded.
The records a time clock produces get used for things far beyond payroll: disciplinary cases, insurance claims, incident investigations, contract disputes, inspections. Each of those asks the record to support a conclusion.
The record in “What the Record Will Support” becomes useful only when people understand what it proves and how to correct it. For teams exploring getting teams to meet deadlines, the provider website can connect time and project context with manager review, provided collection is proportionate, access is limited and consequential decisions remain subject to human explanation.
Different entries support different weights, and the system presents them all as rows in the same table. Knowing which is which, before the moment somebody relies on one, is the difference between a position and an embarrassment.
For an independent benchmark relevant to “What the Record Will Support”, consult the Microsoft Project documentation. 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.
The hierarchy, strongest first
A biometric read: this person presented a body part at this terminal at this time, verified against their own template above the configured threshold. Strong, and limited to exactly that statement.
A credential read: this card was presented. Attributable to the person only on the assumption the card was in their possession, which is an assumption and not a fact.
A self-service code entry: this code was entered. Same assumption, slightly weaker, because a code can be transmitted without handing anything over.
A supervisor override: a named person asserted a time on behalf of another. This is testimony, not measurement, and it is worth what the supervisor's recollection is worth.
A later correction with no reason recorded: almost nothing. It says somebody changed a number.
Why the hierarchy is invisible in the data
Because most systems normalise everything into a single entry type with a timestamp. The method is recorded somewhere, often in a field the standard report does not show.
So the report that goes to a hearing shows a clean column of times with no indication that three of them are measurements and two are recollections. Whoever prepared it is not being dishonest; they exported what the system offered.
The one configuration change that fixes it
Surface the method on every entry, in every report, as a visible column. Not an exception flag, not a footnote — a column that says biometric, card, code, override, corrected.
That single change means nobody can overload an entry by accident, because the weakness is printed next to the time. It is available in most systems and switched off in most installations, and it costs nothing.
What a biometric read still cannot tell you
That the person started work. That they were where the terminal is for any length of time. That they were not immediately leaving. And on a multi-purpose reader, that they intended to clock in at all rather than to open a door.
That last one produces real errors. A turnstile that records a clocking whenever it admits will record one when somebody comes back from the car park at lunchtime, and the system will interpret it according to rules nobody has read.
Using it in a disciplinary case
The honest position is that the record is one source and other records exist. The operational system, the work allocated, the people who were there, the CCTV if there is any.
A case built on one clock entry is a case built on the proposition that the system never errs, which the refusal rate in the same system contradicts. A case built on the clock plus two corroborating records is a different thing entirely, and assembling the corroboration takes an hour.
What to say when the records are produced
A sentence that belongs on the front of any export used outside payroll: this report shows when a credential or biometric was presented at a terminal, by method as shown, and entries marked as override or correction were entered by a named person rather than recorded at the time.
Two lines. They prevent the single most common failure in this area, which is a table of times being read as a table of facts of equal weight by somebody who was never told otherwise.
Two records that disagree
A common and awkward case: the clock says one thing and the operational system says another. The person clocked in at 07:02 and logged into the till at 06:51.
That is not a contradiction to be resolved in favour of whichever is more convenient. It is evidence that the person was present and working before the clock entry, which is a finding about the boundary rather than about the person. Where the two sources disagree systematically in the same direction, the clock is in the wrong place.