Time and attendance
A clocking record that cannot be quietly rewritten
Most time-tracking tools store hours in a table anyone with database access can edit. That is fine until the day somebody asks you to prove a number in front of an inspector, a tribunal or a client.
The question behind the question
When an auditor or the other side's lawyer asks for your working-time records, they are not asking for a spreadsheet of hours. They are asking something harder: can you show these are the hours recorded at the time, and not the ones somebody decided last week they should have been?
Almost every tool answers the first question and quietly fails the second. Clocking in writes a row; clocking out updates it; a manager fixing a mistake updates it again. What you hand over is the last state of a value overwritten an unknown number of times, and nothing in the file says so.
Here the record is appended to, never edited
Every clock-in, break, return, clock-out, amendment and annulment is a new row. Nothing is updated and nothing is deleted: the database itself prevents it, not the program. The hours on screen are not stored anywhere — they are worked out by reading the marks, the way a bank balance is the sum of its transactions.
Amending a time does not rewrite the original: it adds a mark saying which one it replaces. Both stay, with who signed the change and when. And deleting a day does not delete it: it adds an annulment, so the day stops counting but the record still shows it existed. A deletion with no trace is indistinguishable from an entry that never existed, and that is exactly the difference you need to be able to demonstrate.
Three layers, and what each one does not cover
Vendors say «immutable» and stop there. Being precise matters, because the three usual mechanisms defend against different things and none covers all three.
- Database triggers. A rule that rejects any UPDATE or DELETE on the records table. This stops the realistic accident: a badly written migration, a script run against the wrong environment, somebody fixing one row by hand.
- A SHA-256 chain. Each mark carries the fingerprint of the previous one for that person, salted with a per-account secret that appears on no screen, in no export and in no API response. It covers what triggers cannot: if the table were emptied and rewritten, the chain would not add up. It catches deletions, which triggers are blind to.
- A verification you run. A button on the team clocking screen walks the whole chain and reports how many marks it read, how many were altered and how many are missing. A record only its keeper can verify verifies nothing, so the button belongs to the customer, not to us.
And what it does not give you
It does not stop somebody clocking in for a colleague. It does not prove the person holding the phone is who they say they are. It does not make a wrong entry right. What it gives you is narrower and more useful than the usual marketing: whatever went in is still there, unchanged, and anything corrected shows both versions and who signed the correction.
It travels, and you can show it to anyone
The raw register downloads as a spreadsheet and reads through the REST API, fingerprints included, so you can keep your own copy or verify it outside Fichaloto. It is read-only in both: writing a mark by hand would forge a link, and an API that lets you do that is not more capable, it is less trustworthy.
History from your previous system does come in, through the normal import door, and what comes in becomes well-formed marks instead of slipping in sideways.
Frequently asked questions
Is an append-only record legally required?
No jurisdiction we know of specifies the storage design. Spanish law (article 34.9 of the Estatuto de los Trabajadores) and most equivalents require a daily record, kept four years, available to staff, their representatives and the labour authority. Append-only is not a legal requirement — it is what makes the record worth producing.
What happens when somebody genuinely makes a mistake?
They ask for a correction saying what actually happened, and somebody with permission approves it. The correction is a new mark pointing at the old one. Both stay. A record each person can edit at will is not a record.
Can I verify the chain myself?
Yes, and that is the point. There is a «Check the chain» button on the team clocking screen. It answers two separate questions: marks whose content no longer matches their fingerprint, and gaps where a mark is missing. Run it whenever you like and show the result.
What about the history from before we moved to Fichaloto?
It loads through the import screen, one day per row with its clock-in and clock-out, and becomes marks through the same path that generates the real ones. It is flagged as «imported», which distinguishes it forever from what somebody actually pressed on a clock.
Getting started
Fourteen full days, no card and nothing to install. If it has not saved you work by then, there is nothing to cancel. And if you would rather see it first, book a demo and we will set it up with two or three of your real projects, which is where you find out whether it fits.