- Five reasons files go missing
- Designating one place for shared work
- Group permissions in three or four tiers
- Keeping one current version in one place
The short answer
Companies where files cannot be found usually fail at the same five points: storage is scattered across individuals, nobody agreed how to name things, the contents cannot be searched, permissions are a choice between "everyone" and "just me", and nobody can tell which version is current. All five are half solved by decisions rather than purchases.
The five problems
They are ordered by how much fixing them changes day-to-day life. The first two need agreement, not tools.
1. Storage is scattered across individuals
The same document sits on someone's desktop, in an email attachment, on a USB stick, in a personally signed-up cloud account, and somewhere on the NAS. The person who filed it remembers where — which is why everybody else is the one who suffers.
This is not really anyone's fault; it happens naturally when headcount grows before anyone decides where things go. The first move is not consolidating everything into one place, but designating one place where "if it is here, it is shared". Work in progress can stay where it is. What you are deciding is where finished work lands.
Company files sitting in personal cloud accounts and on USB sticks become unreachable when someone leaves or hardware fails. Start by knowing what is out there.
2. Nobody agreed how to name things
"Quote.pdf", "Quote_rev.pdf", "Quote_rev2.pdf" and "Quote_final.pdf" line up in one folder. The order is obvious to whoever made them and to nobody else.
Three rules are enough: lead with the date, write the date as a four-digit year first, and use the same separator. Something like "20260401_quality-record_process-A.pdf". Keep the name itself to four components at most; rules with more than that stop being followed within months.
3. The contents cannot be searched
Scanned PDFs, photographed forms and slide decks made of pasted images contain no searchable text. The file is in the folder, but search does not return it. This one situation accounts for most of the experience people describe as "I looked and it wasn't there".
Run OCR on scans before filing them, so the text can be searched. Processing the entire backlog is a large job, so decide to work through it starting with the material people search for most often.
4. Permissions have only two settings
Plenty of companies offer exactly two options: a shared folder everyone can read, and an individual laptop. Anything sensitive therefore cannot go in the shared folder, so payroll, appraisals and cost breakdowns stay on personal machines.
What is missing is the middle: HR documents for HR and directors, margin data for sales and finance, work instructions for everyone. Three tiers removes most of the reasons to keep files locally.
Grant access to groups rather than to people. Grant it to individuals and every internal move means auditing every folder; grant it to groups and a move means changing one membership.
Permissions that are too granular generate a different problem — a stream of "I can't open this, could you send it to me" emails. Start with three or four tiers and add only where it hurts.
5. Nobody knows which version is current
The last problem strikes after the file has been found. The person is not confident the document is the current one, so they ask its author — and the time saved goes straight back.
Managing versions through filenames produces "final", "final2" and "confirmed" side by side. Instead, lead the name with the date it was updated and keep one location. Move superseded versions into an "archive" subfolder rather than leaving them alongside. If your system keeps edit history, decide that names carry no version information at all.
How this looks in practice
Suppose a manufacturer of about thirty staff cannot locate its quality control work instructions. Say it turns out four copies exist: on the author's desktop, in the department's shared folder, on the PC out on the floor, and in an old email attachment. The contents differ slightly, and the copy the floor is working from is two years old.
Three changes would address this. Work instructions live in one place on the NAS; names follow "update-date_process_work-instruction"; the old copy on the floor PC is moved, not deleted, into an archive folder. Separately, older records that exist only on paper are scanned, put through OCR, and made searchable by process name.
This can reduce how often people ask where to find the instructions. What does the work is less the search capability than being able to say, without hedging, that the current version exists in exactly one place.
Where to be careful
Trying to fix everything at once stalls. Leave the backlog alone and apply the new rules to what you create from today. For older material, keeping it findable is usually enough.
Also, having one shared location is not the same as putting everything in the cloud. Material shared outside the company, or worked on by several people at once, suits the cloud. Large working files, and anything you want to open instantly, do not have to live in a sync folder. Let the need to share decide where something goes.
Storage and backup are different things. A file being in the shared folder is not protection against it being deleted or corrupted. We cover that separately.
In short
- Designate one place for shared material; personal work areas can stay as they are.
- Keep file names to four components at most.
- OCR your scans so they can be found by search.
- Assign permissions to groups, in three or four tiers.
- Move superseded versions into an archive folder rather than leaving them in place.
APOUL Clipboard
APOUL PDF Split