In this guide 6 sections
A shared drive is enough while few people touch few files. Move to a document management system when you need version history, permissions per document, approval steps, expiry reminders or search by field. Test it with three file types: contracts, HR files and project drawings. Wherever the folder tree fails, the system earns its place.
What a folder tree does well
A shared drive is cheap, familiar and quick to set up, and everyone already knows how to drag a PDF into a folder. For a team of five with a few hundred files, it works.
Scale is the problem. Folders force one filing path per file. A signed vendor contract can sit under Vendors, Legal or the project it was signed for, but never in all three.
People copy it. Now two copies exist, and nobody can say which one carries the latest amendment. Try a quick audit of your own drive. Search for the word final and count how many files come back for a single contract. That number is the real cost of folders.
Where contracts break a shared drive
Contracts carry dates that matter: start, renewal, notice period and expiry. A file called Supplier_Agreement_final_v3_signed.pdf holds none of those in a form anyone can filter, so someone must remember them or keep a separate sheet.
A document system stores each date as a field on the record and sends a reminder to the owner sixty days before a notice window closes. It also keeps the signed PDF, the draft and the redline as versions of one record.
Try one test question. Which supplier contracts expire next quarter? A drive cannot answer it, while a field search can. Tag each contract with a department, so finance sees only its own renewals and legal sees the full list. Add the signatory name, which helps when an authorised person leaves.
- Renewal date and notice period as searchable fields
- Counterparty, contract value band and owner
- Draft, redline and signed copy kept as versions
- Reminder sent to the owner, not to a shared mailbox
HR files need permission per document
Drive permissions sit on folders. One employee folder may hold a CV, an offer letter, a salary revision and a medical certificate. The line manager needs the CV. They should never open the salary revision.
Splitting that into four folders with four permission sets is possible. It is tiring to maintain, and it breaks the first time someone moves a file.
A document system sets access on the file or its type, so payroll sees salary letters, the manager sees appraisals and the employee sees only their own offer letter. Every open is logged, which matters when a dispute arrives.
Project drawings expose the version problem
Drawings change constantly. Revision C replaces revision B, and the site team must build from C. On a shared drive someone still downloads B to a laptop and prints it.
A document system marks one revision as current and shows older ones as superseded, and a reviewer approves the revision before release with name and date stamped on it. Check-out locks the file while one engineer edits, so two people never overwrite each other.
One bad print costs more than the licence.
- Current revision flagged, older ones greyed out
- Approval step before release to site or client
- Check-out lock during editing
- Transmittal record of who received which revision
How to decide without a long project
Pick the one document type that hurts most. For many offices that is contracts. Load fifty real files into a trial, set the fields, and ask three people to find things they normally locate by memory.
Then count what a drive could not do: a wrong version found, an expired document missed, a confidential file opened by the wrong person. If the count is zero, stay put and tidy your folder naming.
If it is not zero, list the ten fields you actually search by. Take that list to your first vendor call.
Shared drive versus document system scorecard
Worksheet, one page, three rows for contracts, HR files and project drawings. Columns cover search by field, version history, per document permission, approval step, expiry reminder and audit log. For every cell you tick what the drive does today, what a trial system did, and how many real mishaps happened in the last twelve months. A final line totals the mishaps.
Open a blank worksheet to printQuestions owners ask
Can a shared drive handle version control?
Some cloud drives keep file history, which helps you recover an old copy after a bad save. They do not mark one revision as approved, lock a file during editing or record who received which version.
Do we need a document management system for ten staff?
Often not. If nobody has lost a file, opened a confidential one or missed a contract renewal, folders with strict naming are fine. Revisit when one missed renewal or one wrong drawing costs you real money.
What is the difference between document management and file sharing?
File sharing moves files between people. Document management keeps a controlled record of each file, with versions, owners, dates, access rules, approvals and a log of every action taken on it.
Can old files move into a document system?
Yes, usually in bulk. Deciding the fields and naming rules first is the harder part. Start with this year’s contracts, tag them properly, and load older archives after the layout has proved itself.