Organize Employee Files, Including What Has to Stay Separate
Somebody asks for an employee's file. What comes back is a folder holding their offer letter, their reviews, a doctor's note and a copy of their passport — three of which several jurisdictions say should not have been in there.
The short answer
Employee documents file under the person, by document type, with one important exception: several categories are commonly required to be held outside the main personnel file, and a folder structure that treats them as ordinary subfolders defeats the requirement. A workflow uses the Read Details from File step to identify the employee and the document type, the Ask AI About the File step to recognise the categories that are set apart, and the Move step to route those to a separate restricted location instead of the personnel folder.
Steps this uses
Before and after
What actually changes
As they arrive
- signed offer.pdf
- note.pdf
- review 2025.pdf
- Scan_0771.pdf
After the workflow
- Personnel/Okafor, D/2024-03-11-offer-letter-signed.pdf
- Personnel/Okafor, D/2025-11-02-performance-review.pdf
- Restricted/Medical/Okafor, D/2026-01-09-medical-note.pdf
- Restricted/Work Authorisation/Okafor, D/2024-03-18-i9-supporting.pdf
Four documents for one employee, two of which are routed away from the personnel file rather than into a subfolder of it.
Setting it up
Described once, then it runs
This is the sentence. Send it to the builder and the steps below appear on a canvas, wired and named, for you to change before anything runs.
When an employee document arrives by email or upload, read the employee and the document type off it and file it under that person — but route medical records, I-9s and investigation files to a separate restricted folder instead of the personnel file.
One folder per person, named one way
Surname first, consistently. Duplicate folders from two spellings of one name split an employment history in half, and nothing surfaces the split afterwards.
Name the categories that are set apart
Decide with your own counsel which document types must be held separately in your jurisdiction, then name those types in the rule. The routing is only as good as that list, and the list is a legal question rather than a filing one.
Route, do not nest
A set-apart category goes to its own restricted location with its own access, not a subfolder inside the personnel file. A subfolder is inside the file, which is exactly what the separation is meant to prevent.
Stop on anything unclear
A document that could be either kind goes to Ask a Person to Approve rather than being routed on a guess. Filing a restricted document into a general personnel folder is the expensive direction of that mistake.
Why a subfolder is not separation
The reason certain document types are held apart is that whoever has access to a personnel file should not automatically see them. A subfolder inherits the parent's access, so it satisfies the appearance of the rule and none of its substance. Separation means a different location with different permissions, and it is worth being pedantic about because the failure mode is invisible: everything looks organized right up until the wrong person opens the wrong folder.
The filing decision happens at the worst moment
Documents that need separating usually arrive in the middle of something else — a return-to-work conversation, an onboarding week, an investigation. That is precisely when somebody drags a file into whichever folder is open. Making the routing automatic removes a judgement call from the moment least suited to making it, which is the whole argument for doing this with rules rather than with training.
What it does not do
It routes documents according to rules you define. It does not know your jurisdiction's requirements, does not constitute legal advice about which categories must be segregated, and does not audit whether your structure is compliant. Which document types are set apart, and how strictly, is a question for your own counsel — the system enforces the answer, it does not supply it.
FAQ
Common questions
How should employee personnel files be organized?
One folder per employee, named consistently, then by document type, with files named date-first in ISO form. The significant refinement is that several document categories are commonly required to be held outside the personnel file entirely, in a separate location with its own access — not as a subfolder within it.
Why can't restricted documents just go in a subfolder?
Because a subfolder normally inherits the access of the folder above it, so anyone who can open the personnel file can open the subfolder. Separation means a different location with different permissions. A subfolder gives the appearance of separation without the effect, which is worse than no attempt at all.
Which employee documents must be kept separately?
That depends on your jurisdiction and the document type — medical information, work authorisation verification and investigation records are commonly treated this way, but the specifics vary and change. Confirm the list with your own counsel. What automation contributes is reliably applying whatever list you arrive at.
What happens to a document that could belong in either place?
It goes to a person to decide, with the proposed destination shown before anything moves. Guessing in this direction is asymmetric: filing a restricted document into a general personnel folder is considerably more costly than pausing on an ambiguous one.
Separate means separate.
Routed by rule at the moment a document arrives, not by memory.
5 GB free · No credit card required