The personnel file grows over years
Employment contract, amendments, job descriptions, objective agreements, written warnings, parental leave requests, training records, health and safety briefings, exit paperwork and the reference letter: across ten years of service, fifty documents accumulate easily. The value of consistent names shows not when filing but when looking something up, when a matter from 2019 has to be reconstructed. A pattern with date, document type and employee identifier produces a chronological file without anyone maintaining an index.
Applications are the special case
Application documents follow a different logic from the personnel file: they are temporary. After a rejection the data is usually deleted within a few months, because keeping it beyond the period in which claims are possible cannot be justified. These documents therefore never belong in the same structure as active personnel files. A separate folder with a pattern of arrival date, job title and name makes visible what came in when, and makes timely clearing out much easier.
Not every detail belongs in the filename
Filenames show up in backups, in directory listings and in email attachments, places with a different circle of access than the file itself. Dates of birth, diagnoses from sickness certificates or details about disability status have no business there. An employee number is a leaner identifier than a full name and sufficient for internal purposes. At this point the naming pattern is a data protection decision rather than a matter of taste, and it deserves to be made deliberately once.
Several retention clocks run in parallel
Payroll records carry their own tax retention period, social security payroll documentation has to be kept until the next audit, working time records two years under the Working Hours Act, while the employment contract itself stays relevant as long as claims can arise from it. These periods run for different lengths, and a single folder holds documents from every group. Only when document type and year appear in the filename can a deletion routine be applied sensibly at all.
Co-determination and the path of the analysis
Technically it works like this: the PDF is read on the workstation, the text content is transmitted encrypted for AI analysis, and only the detected details come back. Renaming then takes place on the device again, and the personnel documents are not kept in storage. Since employee data is involved, introducing such a tool should be agreed with your data protection officer and, where a works council exists, with the works council too. Where the analysis should run through keys the company holds itself, that is what the Custom plan is for.
Introducing it without a migration project
The simplest start is the inbox folder: everything scanned or saved out of emails runs through Filery once before it goes into the file. The existing archive stays untouched at first and can be brought along folder by folder whenever someone is working in it anyway. Scanned references and older contracts without a text layer need the optional OCR. Every rename appears in the history, so the original filename stays traceable.
FAQ
Related topics
Download Now
Choose your platform and start with automatic document renaming
Windows
Windows 10 & 11
We are currently working on official code signing for Windows. The download is already available – Windows Defender or SmartScreen may show a warning because the app is not yet certified. Choose “More info” → “Run anyway” to install.
System requirements: macOS 10.14+, Windows 10/11
All downloads are transmitted securely via HTTPS.