A shared folder structure your team can find

Begin with the files people actually look for

Ask a few colleagues to name files they needed recently: a current proposal, approved welcome pack, supplier contact note or project handover. Watch how they describe each item. Do they start with a client, a project, a business function or the document type? Their language gives you practical naming clues.

Try a small findability test using ordinary work. Ask someone who did not create a file to locate it and explain why they believe it is the right version. Record where they hesitate. The issue may be an unclear title, duplicate locations or a missing owner rather than too few folders.

List the active areas that create the most uncertainty. Select one for the pilot. Keep unrelated historical material outside the first pass unless it directly prevents the team using the new structure. A folder project should have a clear boundary, just like other delegated work.

Build a filing map around recurring work

Choose a main organising principle for each area and apply it consistently. A project area might start with project names, while a general administration area might start with business activities. Mixing client names, years, authors and document types at the same level makes it harder to predict where a new file belongs.

Fictional example: a small training provider uses the following map for its operational files. The entries describe purposes rather than access permissions. Separate information with different access requirements through arrangements agreed with the person responsible for the system.

Write the rules for awkward cases

Most filing confusion lives at the boundaries. A proposal could seem to belong under a client, a project or sales administration. Agree its primary home and explain how the team should refer to it from elsewhere. Avoid creating several independently edited copies just to satisfy different browsing habits.

Write a few examples of filenames that identify the subject without opening the file. “Workshop joining instructions, approved, November event” is more informative than “Document 7”. Choose a consistent pattern for dates, statuses and project identifiers. Test it with the actual people filing the work.

• State the primary home for documents that could fit in more than one area.
• Explain where drafts, approved material and superseded copies belong.
• Name the person who resolves uncertain filing decisions.
• Give temporary incoming material an owner and a review point.

Move a pilot area in a controlled sequence

1. Agree the boundary

   List the source folders and work included in the pilot. Tell the affected people what is moving, when the change will happen and where active work should be saved during the move.

2. Resolve obvious uncertainty

   Ask document owners which copies are current and which records require a decision. Keep an exceptions list for unknown files rather than making assumptions about deletion or status.

3. Set up the destination

   Create the agreed structure and have the system owner check access arrangements. Confirm the intended users can reach the required files before relying on the destination for everyday work.

4. Move and test

   Follow the agreed move plan, update the team’s references and repeat the findability test. Tell people how to report a missing item or unexpected access problem.

Keep ownership and access decisions visible

A folder name does not decide who should see its contents. Record an owner for each area and ask that person to agree who needs access for their work. Where arrangements are unclear, involve your system administrator or IT provider. Do not widen access merely to avoid a filing inconvenience.

The NCSC advises organisations to use separate work accounts for individuals. Keep that distinction when setting up shared filing: people should reach the files through the access arrangement agreed for their own work account, rather than using a colleague’s login. Check the provider’s current instructions for your particular system.

Review the practical responsibilities too. Who maintains the approved templates? Who closes a project folder? Who answers a question about an unfamiliar record? A structure can remain visually tidy while its contents lose an accountable owner.

Maintain the structure with ordinary work

Give the pilot area a short review after people have used it for real tasks. Look at the incoming area and exceptions list. Repeatedly misplaced files may mean the categories are unclear. Change the rule or example before adding another layer of folders.

Extend the structure only when the pilot is understandable and maintained. Clerica Solutions can discuss organising shared folders and filing structures within an agreed administrative support scope. A defined starting task could be mapping an active folder area, documenting proposed rules and referring ownership or access decisions to the business.