Shared company document library vs department folders

The short answer: split by audience, not by author

A shared company document library should hold anything that people outside the authoring department need to read or use, while department folders should keep working files that only that team touches. Most enterprises need both, and the mistake is letting department folders double as the place where everyone else goes looking for policies and forms.

Department folders mirror the org chart, which suits the people who create documents. Staff who consume them do not think in org charts. A site supervisor looking for the vehicle booking form does not know, or care, whether it belongs to admin, facilities or finance.

Where department folders still earn their place

Drafts, working papers, supplier correspondence, internal trackers and anything containing restricted information belong with the team that produces it. Access is simpler to manage when a folder maps to one team, and people are more willing to keep rough work tidy in a space that feels like theirs.

Department folders also suit material with a short life, such as event planning files or a one-off renovation project. Pushing those into a company-wide library clutters search results for everyone else and creates documents nobody will maintain.

Finance and HR are the clearest cases. Payroll workings, supplier negotiations and disciplinary files must stay restricted, and mixing them into a library most staff can browse invites an access mistake. Keeping them in department folders with tight permissions is safer and easier to audit.

Signs the folder model has stopped working

The admin inbox is the best indicator. If a recurring share of messages are staff asking where to find something, or asking for a file to be emailed to them, the structure is hiding published documents inside private working areas.

Other signs are just as practical. Two departments keep their own copies of the same form with slightly different fields. A regional office has built a parallel folder because head office permissions are too tight. New joiners are told to ask a colleague rather than search. Each of these means the published version of a document has no single home.

Audits and disputes expose the same problem. When someone asks which version of the purchasing procedure applied last March, and the answer depends on whose folder you check, the organisation has lost track of its published documents. One published location with superseded versions archived behind it makes that question easy.

A quick test for each document type

Run every recurring document type through a few questions before deciding where it lives. If the answer to any of the first three is yes, it probably belongs in the shared library:

• Do people outside the authoring team need to read or complete it?
• Is it referred to in another policy, form or onboarding pack?
• Would a new joiner at any site need it in their first month?
• Does it contain restricted or personal data that limits who can open it?
• Will it still be in use after the current project or year ends?
• Is there a named owner willing to keep it current?

Moving documents into the shared library in stages

Start with forms, because they are used most often and their owners are easy to identify. Move one department's forms at a time, put a short note in the old folder pointing to the new location, and leave the old copy read-only for a few weeks before archiving it. Broken links in onboarding packs and intranet pages will show up during that window, and they are easier to fix while the old file still exists.

Policies come next. Agree a top-level structure built around what staff are trying to do, such as travel, leave, purchasing, workplace and conduct, rather than which department issued each one. Keep the owning department visible on the document itself so accountability does not disappear when the folder name changes.

Leave department folders in place for working files. The goal is a clear line between published and in-progress material, not one giant drive.

Keeping the split clean after the move

The structure decays unless someone checks it. A brief quarterly look at the shared library for duplicates, missing owners and documents past their review date keeps it trustworthy, and publishing rights should sit with a small group so new uploads follow the agreed structure.

Make the boundary part of the publishing step. When a department finalises a document for wider use, the publisher moves it, adds the owner and review date, and replaces the working copy with a link. Departments then never need to decide whether a file is official; if it sits in the shared library, it is.

Teams that want the library tied to requests and follow-up rather than a bare drive can ask Fasttrade about BukuAdmin, its company administration product, which covers company documents along with internal requests and bookings. Fasttrade confirms fit and scope directly with each organisation.

Frequently asked questions