Ask three colleagues where the signed contract for a particular employee is and you will usually get three answers: “in the HR folder”, “in an email somewhere”, and “on my desktop, I think”. The record exists. It just cannot be found, which in practice is the same as not existing.
Fixing this does not require new software. It requires an agreed structure, a naming rule, and a habit of using both.
Step 1: Decide the top-level structure once
For a small or mid-sized office, five or six top-level folders are enough:
01_Employees
02_Finance
03_Compliance
04_Projects
05_Admin
06_Shared-Reference
The numbering matters: it fixes the order so everyone sees the same layout and folder names sort predictably.
Two rules protect the structure from chaos:
- Only the owner of the folder creates subfolders. Otherwise everyone invents their own.
- Nothing is saved at the top level. Documents belong in a folder, not floating beside it.
Step 2: Use the same subfolders everywhere
Within each employee folder:
01_Contract
02_Joining
03_Changes
04_Appraisals
05_Leave
06_Training
07_Disciplinary
08_Exit
Within the compliance folder:
01_Licences-and-Renewals
02_Audits
03_Policies
04_Registers
05_Corrective-Actions
06_Reports
A fixed structure means a new colleague can guess where something lives — and usually be right.
Step 3: One naming convention, applied everywhere
Use the pattern date_document-type_name, with the date first so files sort chronologically:
2026-04-15_contract_ram-sharma.pdf
2026-05-02_policy-leave_v3.docx
2026-06-30_payroll-summary_asoj-2083.pdf
2026-07-11_warning-letter_sita-gurung.docx
Three rules make it work:
- No spaces. Use hyphens. Spaces break some systems and look messy everywhere.
- No
final,final2, orlatest. Version numbers or dates, nothing else. - Nothing personal in the file name that you would not want seen. Names are appropriate in HR files; passport or account numbers are not.
Step 4: Version control that people actually follow
- Working documents: use a version suffix
_v1,_v2,_v3. The highest number is the current version. - Approved documents: mark as
APPROVEDand keep the approved copy in a read-only or restricted location. - Superseded versions: move to an
_archivefolder inside the same section. Do not delete them — you may need to explain what an earlier version said. - Dates in the document itself: every policy and form carries a version date in its footer.
Rule of thumb: if two people are editing the same document, decide who owns it and when it moves from working to approved stage.
Step 5: Backups that have been tested
- Two copies, two locations: the working location plus a backup, ideally with one off-site or cloud copy.
- Test the restore at least once. Open the backup and retrieve a file. An untested backup is a hope.
- Monthly reminder on the calendar, with a named owner.
- Backups are not working folders. Nobody should edit the backup copy directly.
Step 6: Share access deliberately
- Give access to folders by role, not by request.
- Review access monthly: who has access to the personnel folder, and why?
- Remove access on the day someone leaves — including shared folders, email, and phone apps.
- Use link sharing with expiry where sharing outside the organisation is unavoidable, and never for personnel data.
A folder map document that saves arguments
Keep one short document: “Where documents live”. It should list every major document type and its folder path. One page, updated twice a year. It settles ninety per cent of “where should this go?” questions and makes onboarding easier.
Habits that keep it working
- Save in the right place the first time. Moving twenty files afterwards takes longer than choosing the right folder once.
- Clear your desktop and downloads weekly. Anything worth keeping goes into the structure; everything else goes.
- Delete drafts that were replaced, once the final version is approved and archived.
- Assign each top-level folder an owner. Someone must be responsible for keeping it clean.
- Review the structure once a year. If a folder has not been opened in a year, question whether it needs to exist.
A 20-minute cleanup plan
If the current state is a mess, start here:
- Create the numbered top-level folders and subfolders (10 minutes).
- Move the current year’s documents from desktops and downloads (5 minutes).
- Rename the twenty most-used documents to the convention (5 minutes).
- Write the “where documents live” page and share it with the team.
- Set the monthly backup reminder.
Then do the historical backlog one section at a time, not in one heroic afternoon.
Community discussion
Comments 0
Comments are reviewed before they appear publicly. Be respectful and avoid sharing private information.
No approved comments yet. You can be the first to share a useful thought.
Add a comment
No account or login is needed. Your comment is emailed for moderation and is published only after approval in the CMS.