Eighteen months after a payroll officer leaves, a records request arrives for a period she processed. Whether the institution can answer it depends less on its filing than on its access: whether her entries still carry her name, whether her documents were filed to the employee or to her own folder, and whether her successor reaches the record by role or by her old password. One invented request shows where continuity fails.
Maintained by the TriblockHR Compliance Team. Updated 2 October 2026. This page describes record continuity in TriblockHR; it states no records-law requirement or retention period.
The request, eighteen months later
Take an invented statutory authority, the Harbour Development Authority. In October, a former employee, Trevor, asks for the records behind an overtime payment he disputes from the spring of the previous year.
The payroll officer who processed that period, Simone, left the Authority fourteen months ago. Her successor, Andre, has to produce the record. Nobody in the office was there when the period was run.
Three ways it usually fails
The leaver’s login. In many organisations, when someone leaves, their account is either deleted or handed to the person who replaces them. If Simone’s account was deleted, every change she made may now show as made by nobody. If it was handed to Andre, every change she made now looks as though Andre made it, and anything Andre does is mixed in with what she did.
The personal folder. Simone kept the overtime approvals and Trevor’s signed timesheet in a folder on her own drive, because that was where she worked. When her drive was cleared after she left, the documents went with it.
The approval only one person could see. The overtime was approved by a supervisor through a step that only Simone and the supervisor could see. Both have left. The approval exists somewhere, but nobody in the current office can reach it.
None of those is a filing failure in the usual sense. The records were made. They were made in places tied to a person, and the person has gone. Continuity failed at access first.
No access, and attribution that survives
In TriblockHR, no access is one of the seven roles. An account can exist, be on the establishment, and reach nothing.
That is what a leaver should become. When Simone left, her account should have moved to no access. It should have been neither deleted nor handed on. Her account remains, so every entry she made remains attributed to her. She can no longer sign in or reach anything.
The evidence then outlives her:
- History with the actor. About forty per-entity history tables hold before and after values with the actor who made each change. Simone’s entries for Trevor’s overtime still show her as their author.
- Recorded approvals. A pay run moves through staged approval with recall and cancel, and a line-level audit trail. The approval of the spring run, by whom and when, is on the run’s record.
Andre reaches all of it through his own role and scope, as the current payroll officer. He does not need Simone’s login, and he should never be given it.
Filed to the employee
The documents are the other half. In TriblockHR, signable PDF forms are filed to the employee’s record, and documents can require sign-off. A licence or certificate is a document with an expiration date on the same record.
So Trevor’s signed overtime claim, if it was a form in the system, sits on Trevor’s record. When Simone left, nothing about it changed. Andre opens Trevor’s record and finds it.
The practical rule for an institution is that anything about an employee is filed to that employee’s record. A personal folder, a shared drive or an email thread is a place a document can be lost when the person who used it leaves.
Andre also needs his own access to be right. Sign-in uses Microsoft Entra ID single sign-on, so the Authority enforces its own multi-factor and conditional-access policy, with password policy, lockout and session timeouts. Andre signs in as himself, with his own role. Core HR covers roles and the record.
What the institution decides
Some of this is the institution’s procedure, and it should be written down:
- Who moves a leaver to no access, and when. The Authority decides that HR moves every leaver’s account to no access on their last working day, as part of offboarding. Onboarding and offboarding covers the leaver’s checklist.
- Who inherits a leaver’s approvals. If a leaver had approvals in progress, someone has to take them over. The Authority names the role that does, by default the leaver’s line manager.
- How a successor is given access. By role and scope, set by an administrator. Never a shared password and never the leaver’s login.
- How long records are kept. The Authority sets its own records schedule. Export is available on demand, and deletion is on instruction, so the schedule is the institution’s to set.
Whether a records law applies, and what it requires, is a question for the institution and its counsel.
For Trevor’s request, the Authority can now answer: here is the overtime entry for the spring period, made by Simone on the date shown; here is the approved run it was paid in, approved by the supervisor on the date shown; here is the signed claim filed to your record. None of it depended on anyone who was there. The report builder page covers pulling the period’s figures, and the government page the wider operation.
Questions
What should happen to a leaver’s account?
It should move to no access, so the account and its attribution survive while the access does not.
Do a leaver’s entries keep their name?
Yes. History tables hold the actor on each change, which remains after the person leaves.
Where should employee documents be filed?
On the employee’s record. Signable forms are filed there.
How should a successor get access?
By their own role and scope, set by an administrator. Never by a shared password or the leaver’s login.
Keep every record attributed and filed to the employee, so it can be produced after anyone leaves.
- SOC 2 Type II attested
- AES-256 at rest
- 99.9% uptime
- Built in The Bahamas
