Records written into the past

Most check-ins and check-outs reach the system within seconds of the badge touching the phone. A few do not, and the gap matters. Backdated records, in the Advanced part of your menu, lists every check-in and check-out that reached the system well after the moment it claims — in plain terms, every record that was written into the past.

Why a record can honestly be late

The commonest reason is an offline gate. When the officer’s phone loses signal, scans queue up on the device and are sent through later — sometimes hours later. The system believes the time the device gives, because the device was the only witness to when each learner actually walked through, and it accepts a claimed time up to eighteen hours old. Every one of those late arrivals shows up on this list, and every one of them is honest.

There is a limit to that trust. A claim older than eighteen hours, or one from a clock running ahead of the real time, is not believed as given — the system records its own estimate instead and flags those separately, on the estimated times list you review at day close. This list is different: everything on it was believed exactly as claimed. The record on the school’s books carries the time the device gave, and nothing else in the product marks it as unusual.

Why a person still reads this list

Because a record typed in after the fact looks identical to an honest late one. Somebody with staff access who enters yesterday afternoon’s check-out this morning produces exactly the same shape of record as an offline phone catching up — a claimed time in the past, received later. The system cannot tell those two stories apart, and it does not try to. What it does instead is make sure both are seen: nothing on this list is hidden, blocked or quietly accepted. A record written into the past always gains a witness.

Each row puts the two halves of the story side by side — On the school’s record, the moment the record claims, and Reached the system, the moment it was actually written — with a chip stating plainly how far apart they are. The row also names who made the record, and how: which member of staff, whether it was a badge scan or typed in by hand, and at which gate.

The list also does one honest piece of arranging for you. Records that reached the system within moments of each other are gathered under a single label — so many records arrived together, consistent with an offline device sending its scans through late — because that burst is the one shape a catching-up device cannot help making. The label is an observation about arrival times, not a verdict: the system still cannot prove any single record’s story, and a record typed in after the fact at the same moment a device happened to drain would sit inside the group looking the same. What the grouping buys you is the opposite case: the row that deserves a second look now stands alone — a single record, typed in by hand, the morning after the day it describes — instead of hiding in a crowd of honest ones.

What to do about a row that does not fit

Open the full record. The link on each row takes you to that learner’s timeline with the record in question already in view. The record itself never changes — what happened at the gate is permanent, which is precisely what makes it worth trusting — but every record can carry notes, and a note is the right instrument here: write down what you know of the day, who you asked and what they said, and the account stays attached to the record for anyone who asks later.

When the list is empty the screen says so plainly: every check-in and check-out reached the system close to the time it claims. For most schools, on most days, that is what you will see.