How to organize a nonprofit shared drive without replacing your tools

1. Begin with the searches staff need to make

Ask a few people who use the shared drive every week: What are you trying to find? Where do you look first? What makes you unsure you have the current version? What do you do when you cannot find it?

Write down real tasks in plain language, such as locating the latest approved template, finding the current version of a procedure, or handing a recurring report to a colleague. The aim is to learn how staff describe their work, not to design a perfect folder tree in a meeting.

Include people with different roles and levels of access. A structure that makes sense to the person who created it may be difficult for a new staff member or someone who uses it only once a month.

2. Inventory before moving files

List the places where work information currently lives, who relies on each place, and what commonly goes wrong. You do not need to catalogue every file to spot patterns. A focused review of important folders and recurring tasks is often a better first step.

For each area, note:

• What kinds of information belong there?
• Which role is responsible for keeping it useful?
• Are there multiple versions or duplicate copies?
• Can staff find the item using the words they naturally search for?
• Are there access, retention, or ownership questions that need an organization-level decision?

Keep the inventory separate from the proposed design. That makes it easier to see what is working, what should change, and what needs a decision before anything moves.

3. Organize around durable work

Use names that reflect stable functions, programs, or processes that staff recognize. Avoid making the top level a mirror of the current staff chart: people change roles, while core work often continues. Keep the structure as shallow as practical, and add a new folder only when people can explain what belongs in it and who will maintain it.

There is no universal nonprofit folder structure. A small organization with a few shared workflows may need very little hierarchy. A larger or more distributed team may need clearer boundaries and ownership. Start with the fewest categories that let people complete common tasks reliably.

4. Agree on simple naming rules

Names should help staff tell what a file is without decoding internal abbreviations. Decide together which details matter: the subject, document type, period, status, or version. Use a consistent date format when dates help distinguish files, and agree on a small set of status words if drafts and approved copies otherwise get mixed together.

Test the rule against files people actually use. If staff cannot apply it quickly and consistently, simplify it. Naming rules work when they reduce uncertainty; they do not need to encode every detail about a document.

5. Give each area an owner and a maintenance habit

Assign responsibility by role where possible, so the system does not depend on one person's memory. Make the basic decisions explicit: who can create new folders, who updates shared templates, how a finished project is handled, and where staff can ask when something does not fit.

Keep the guidance short enough to use. A one-page map, a few naming examples, and a clear contact for questions can be more useful than a long manual no one consults. Include the same basics in onboarding and handoffs.

6. Move in small, verifiable steps

Before a large reorganization, try the proposed structure with a representative area and the people who use it. Check whether they can find common items, identify the current version, and understand where new work belongs. Confirm that needed access and links still work. Record unresolved duplicates or ownership questions instead of making assumptions about them.

For retention and records-handling decisions, follow your organization's approved requirements and qualified advisors (our guide to nonprofit records retention covers how to set those up). A cleanup project is not a reason to guess whether a record can be deleted or who should be allowed to see it. Keep those questions visible and resolve them through the appropriate organizational process.