What an employee file is
An employee file is the organised set of documents and data an organisation keeps on each of its workers, from contracting through to the end of the relationship.
Two words in that definition carry most of the weight. Organised, because an unstructured collection of the same documents is not a file in any sense that helps anybody. And from contracting to the end of the relationship, because the file’s usefulness depends on it being a continuous record rather than a snapshot of the present state.
What it usually contains
- The employment contract, its annexes, and any variation that was agreed.
- Identity, residency and qualification documents, with their expiry dates.
- Wage and allowance data, and every change made to it.
- Leave balance and the attendance record.
- Performance reviews and administrative actions, where any exist.
- End of relationship documents and the clearance record.
Why organising it is an operational matter, not an archival one
The file is asked for at moments that do not allow time to search: a claim, an inspection, the renewal of a document that is close to expiring, or a dispute about what was agreed. Its value at those moments lies in being complete and historical: in showing what was in force on a particular date, rather than only the latest state.
That is why successive versions of the contract are kept rather than only the most recent one. A file holding only the current contract can answer what the terms are today. It cannot answer what the terms were on the date the disagreement is about, which is the question actually being asked. The same applies to wage data: the current figure is rarely the one in dispute.
Dates are the critical part
The unpleasant surprise in an employee file rarely comes from a missing document. It comes from an expired one that nobody noticed: a residency permit, a professional licence, or a fixed term contract that has reached its end. For that reason the file is built around dates that carry an alert, rather than around a folder somebody opens when the need arises.
An alert is only useful if the lead time is long enough for the renewal to be completed within it, which makes the lead time a decision rather than a default. Take a document expiring on 14 July 2026 and read three common choices from it:
- A 30 day lead gives an alert on 14 June 2026.
- A 60 day lead gives an alert on 15 May 2026.
- A 90 day lead gives an alert on 15 April 2026.
These are operational choices about how much room the organisation wants, not periods drawn from any instrument, and they should be set from how long the relevant renewal actually takes in practice rather than from a round number. The point of the arithmetic is that the earliest and the latest of the three dates are 60 days apart, with 30 days between each adjacent pair, so the choice of lead time decides whether the alert is useful or merely early enough to be ignored and late enough to be a problem.
A second property matters as much as the lead time: the alert has to reach somebody who can act on it. An alert delivered to a shared inbox that nobody owns is the same as no alert, and it is worse in one respect, because it creates the impression that the risk is being watched.
The data side
The contents of the file are personal data, and handling them falls under the Personal Data Protection Law (نظام حماية البيانات الشخصية) in the Kingdom, which includes determining the purpose for which data is collected and limiting collection to the minimum that serves that purpose. The disciplined practice is that access is restricted to those who need it for a stated purpose, rather than being available to anyone who holds an account.
Access control is the part that is easiest to defer and hardest to retrofit, because permissions granted informally during a busy period are rarely reviewed afterwards. The practical test is whether the organisation could produce a list of who can open a given employee’s file, and why each of them can. An organisation that cannot produce that list does not have access control; it has a system that has not yet been asked the question.
What gets handed over when somebody asks for the file
Usually one of the collections below. Each exists in most organisations, each holds documents about employees, and each is offered in good faith. What separates them from a file is not the contents but whether they answer the questions the file exists to answer.
- The recruitment folder. Applications, interview notes, scoring sheets. It belongs to the hiring decision and it ends at the offer. Carrying it forward wholesale moves material collected for one purpose into the working record of another, which is the opposite of limiting collection to what serves the stated purpose.
- The payroll history. An authoritative record of what was paid, and not a record of what was agreed. The file needs the agreement, the variation to it, and the date each took effect. Payroll shows only the outcome, so it can confirm that a figure changed and not why or on whose authority.
Then there is the shared drive with a folder per person, which deserves its own paragraph because it is the one most often mistaken for a file. It holds the documents and answers none of the questions above, since nothing in it carries an expiry date, a version, or a record of who opened it. The documents really are all there, and that is precisely what makes the gap hard to see: having every document and having a file are different things, and only the second of them can be asked a question.
Paper and digital
The format is not a matter of preference. A paper file is one copy in one place, so reaching it, searching it and tracking who has looked at it are all harder. A digital file solves those problems and adds a requirement of its own, which is deliberate management of permissions and backups.
What the two have in common is the thing that actually determines whether the file is worth having: what is not kept up to date cannot be relied on, whether it is on paper or on a screen. A digital file that is complete for the first month of employment and empty thereafter is no better than a paper one in the same state, and it is easier to mistake for a working system because it looks orderly.
Where the file is fed from
Almost nothing in an employee file originates in the file itself. The contract and the probation dates arrive from employee onboarding, the wage and allowance history arrives from the payroll statement each period, and the clearance documents arrive at the end of the relationship, where the deadlines are set by the Saudi Labor Law and are covered in our guide to wage payment dates and the final settlement.
That is worth stating plainly because it locates the real failure point. Files are seldom neglected on purpose. They fall out of date because the process that should have written to them finished somewhere else, and nobody noticed that the last step never happened. The exit interview is a good example: it produces a record that belongs in the file, and it happens at exactly the moment when everyone involved is focused on the departure rather than on the paperwork it generates.
A standalone Saudi HR system
One employee file holding the contract, the documents and their expiry dates, the attendance record, leave, salary and end-of-service entitlements. End-of-service, overtime and leave-balance calculations are built into the system.
A standalone system on its own subscription. The connection to Qoyod Accounting is now available.