Custom app for employee file access and access requests
An employee is entitled to see what has been recorded about them. In practice, that means an email to HR, a folder someone compiles by hand and a reply that takes weeks. With an app, it's a single screen, and that changes not only the convenience but also the quality of what's in the file.
What access means in practice
A personnel file contains data with widely varying retention periods. Application data is usually deleted within four weeks of the procedure. Data without a statutory retention period is generally kept for up to two years after the employee leaves. Wage tax declarations and a copy of the ID document are kept for five years, and parts of the payroll records for seven.
That means giving access is more than opening a folder. Some data should no longer be there, other data must not be visible to everyone in HR, and still other data is special category data subject to separate rules. Anyone who builds access without that separation ends up showing exactly too much or exactly too little.
In practice, access is also a quality tool. As soon as employees can see their own file, it becomes clear how much of it is outdated, duplicated or incorrect. That is uncomfortable, but it is also the fastest clean-up programme there is, because the corrections come from the one person who knows for certain what is right.
There is one more reason for organisations with people who have no fixed workplace. If you work in healthcare, construction or logistics, you have no desk and no company laptop. A file that can only be reached via an intranet is, in practice, out of reach for that group.
How we build this
The core is what an employee may and may not see. That is a design question answered before building, not a setting applied afterwards.
Define for each type of data whether the employee can view it themselves and, if not, why not.
Access to your own file requires strong authentication, even when someone opens it on a personal phone.
What was viewed and when, because access to personnel data is itself a form of processing.
A request for correction or deletion gets a deadline and a visible status, instead of disappearing into a mailbox.
What the app actually does
Viewing your own file carries the whole thing. What else you need depends on your size and on how many people work without a fixed workplace.
View own file
What has been recorded about someone, organised by type, with the retention period shown so it's clear how long it will be kept.
Request a correction
If something is wrong, the employee submits a request on the data item itself rather than in a separate message.
Request status
Received, in progress, completed, with a deadline that is visible to both sides.
Download documents
Retrieve payslips and statements without anyone having to send them.
Works on a personal phone
Secure sign-in and no data left on the device when someone leaves the company.
Every access logged
Who has viewed the file, including within HR. That is exactly the answer an employee sometimes wants.
Who we build for
Who works with this differs per organisation. Four situations.
Employees without a fixed workplace
Healthcare, construction and logistics: no desk, no company laptop, but a phone.
HR departments
They currently compile files by hand for every request, and that is work nobody will miss.
Data protection officers
They need to be able to show that access rights work in practice and not just on paper.
Works councils
They are involved in agreements on employee data and want to know what employees can see for themselves.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and integrations
Retention periods change, new data types are added and systems are replaced. Visibility, data types and retention periods should be configurable rather than hard-coded in the app.
For organisations that want to track DPIAs with measures and owners, there is our DPIA workflow tool.
Why Appfront
Access is the fastest clean-up programme
As soon as people see their file, the errors come to light. Those corrections come from the one person who knows for certain.
Not everything should be visible
Special category data and notes from third parties call for their own assessment. That is design work, not a switch.
For many people, a phone is their only workplace
A file behind an intranet is out of reach for field staff and care workers.
Access is itself a form of processing
Anyone who views the file should be logged. Within HR too, and especially there.
Security and privacy
This is an app that lets someone reach their own employee data, often on a personal device. That sets high demands for sign-in and for what remains stored locally: we do not keep any file data on the device and make sure access lapses as soon as someone leaves the organisation. Special category data such as sickness absence is kept separate from the rest, with its own permissions and its own visibility.
For this topic, what matters is reliability at the point in time. In the event of a complaint about the file, what counts is what it contained at that moment and who had looked at it. We record access and changes immutably with timestamp and person, and make a correction a visible correction alongside the original entry. How we handle security ourselves is set out in our information security policy.
Frequently asked questions about access to the personnel file
Not automatically. A file contains data of varying sensitivity, including special category data on sickness absence and sometimes notes involving other people. Decide per data type whether the employee can view it themselves and why or why not; that is a design decision you make before the build.
Those of the data type. Application data usually goes within four weeks of the procedure, data without a statutory period generally up to two years after the end of employment, the copy of the ID document five years and parts of the payroll records seven years. Showing that period makes the file easier to understand.
It gets a deadline and a visible status: received, in progress, resolved. The big difference from current practice is that the request is attached to the data item rather than disappearing into a mailbox, so both sides can see where it stands.
Yes, provided it is set up securely. That means strong authentication, no file data left behind locally, and access that lapses as soon as someone leaves the organisation. For people without a fixed workplace, a personal phone is often the only realistic route.
Because viewing employee data is itself a form of processing. In the event of a complaint, the question is who looked in the file and when, and you can only answer that if you have kept a record. That applies to access within HR too, and especially there.
From the system in which they are monitored and carried out. We describe that on our page about software for retention periods and data deletion. See also our approach to building an app.
How long does it currently take before someone sees their file?
Ask your HR department how much work it is to compile a single complete personnel file. If it takes more than half an hour, that is the reason employees don't ask for it. We build this as a standalone app and as part of a broader app development project.