When the Former Employee Asks for Their File

Treat the request as a search problem with a deadline attached, and start the search the day it arrives. Requests from former employees are usually answered late, and they are answered late because nobody begins until somebody has decided whether it is really required — by which time a third of the time has gone.

The recordkeeping discipline in “When the Former Employee Asks for Their File” should also apply to workforce technology. When a team assesses learn more here in relation to how to detect mouse jigglers, it should document purpose, access, retention and deletion, then preserve only the evidence needed for the handover, payment or review decision.

The request is also, almost always, a signal. Somebody asking for everything held about them shortly after leaving is usually taking advice, and what the organisation sends will be read with that in mind.

For an independent reference relevant to “When the Former Employee Asks for Their File”, consult the SHRM workplace-investigation resources. Use it to test record quality, access, retention, fair process and exception handling against the organisation’s real departure workflow.

Where the information actually is

The HR file is the smallest part. Personal information about an employee is spread across more systems than anybody expects, and the search has to cover them or the response is incomplete.

• The HR system and the leaver file.
• Email, including managers' mailboxes, which is usually the largest source.
• Messaging platforms, including direct messages between other people.
• The payroll and expenses systems.
• Recruitment records, if they were an internal applicant at any point.
• Notes held locally by managers, including personal notebooks.
• Anything held by a third party on the organisation's behalf.

The third item is the one that produces surprises. A conversation between two managers about somebody is information about that person, and it is frequently less considered than anything in the formal file.

The deadline

There is normally a time limit, it differs by jurisdiction, and it is usually shorter than the work takes. Whether it can be extended, and in what circumstances, is a question for somebody qualified in the place concerned.

What is not in doubt is that the clock starts on receipt rather than on the day somebody decides to act. Building the first week around locating material rather than deciding policy is the single change that most improves the outcome.

Material about other people

Much of what is in scope mentions somebody else: a witness statement, an email thread, a complaint by a colleague. Disclosing it wholesale affects other people's rights; withholding it wholesale is usually wrong too.

The balance that has to be struck, and how, is a question for somebody qualified. Operationally, what matters is that the work of identifying and redacting takes far longer than anybody budgets, which is one more reason to start immediately.

What cannot be done once it arrives

Nothing in the file may be altered, tidied, improved or removed after a request has been received. That includes deleting an email somebody now regrets and amending a note to read better.

This should be obvious and it is worth saying explicitly to everybody involved, because the instinct is strong and the consequences are serious. Instructing people in writing, on day one, not to alter or delete anything is a step worth taking every time.

Writing notes that will be read

Every note in a file is a note the person may eventually read, and a request is when that becomes real. Managers discover what they wrote about somebody two years ago in a thread they assumed was private.

There is no remedy at the point of the request. The remedy is the habit described elsewhere on this site: write everything as though the subject will read it. The organisations that handle these requests calmly are the ones with nothing embarrassing to find, and that state cannot be retrofitted.

Responding

Send what has been decided on, with a short covering explanation of what was searched and what has been withheld and why. A response consisting of two hundred pages and no explanation invites a follow-up.

Keep a record of the search itself: which systems, which date ranges, who did it. If the adequacy of the response is later questioned, the record of the search is the answer.

The request that is really a question

Some requests are not about the information at all. The person wants to know what was said about them, whether a particular conversation was recorded, or what the organisation's position is.

Where that is apparent, it is sometimes worth asking what they are looking for, which may resolve the matter far faster than a full search. That is a conversation to have alongside the formal process rather than instead of it, and the deadline continues to run while it happens.

What it tends to reveal

Most requests return nothing dramatic and a great deal that is disorganised: duplicate records, information held in systems nobody remembered, inconsistent dates, notes with no author.

That is worth treating as the finding it is. A request is an unplanned audit of how the organisation holds information about its people, and the cheapest version of that audit is the one somebody conducts voluntarily before anybody asks.