Most shared-drive cleanups start with good intentions and a folder nobody wants to open. Someone begins moving files, and within an hour the team has lost track of which copy is current and who can see what. The safer way to reorganize a drive is to slow down at the level of a single record and ask four questions before anything moves.
Start with one file, not the whole drive.
A whole-drive cleanup is hard to plan and easy to abandon. It also creates risk, because the person doing the moving is rarely the person who understands every record.
Choose one file that people already argue about. A budget, a report, a participant list, an agreement. Follow that single record from the moment it arrives to the moment someone archives it. The problems in the drive will show up along that one path.
Ask the four questions in order.
Owner. Who is responsible for this record? Not who made it, and not who opened it last. Who is accountable for it being right and current.
Status. Is it active, closed, replaced, or uncertain? A closed record and a live one should not sit in the same place with the same weight.
Privacy. Who should be allowed to see it? This is a decision to make, not a description of the setting it already has.
Approved copy. Is this the version people should use? If two copies exist, one needs to become the record and the other needs to move or go.
Privacy is the question teams skip.
Ownership and versions get attention because staff feel them every week. Access usually gets attention only after something goes wrong.
Participant records, case notes, personnel files, incident reports, and signed agreements often sit in general folders because that is where the work happened. Nobody decided they should be open. They inherited the access of the folder around them.
Ask the question deliberately for each type of record. If the honest answer is that fewer people should see it, that is worth acting on before any reorganizing begins.
When an answer is unclear, mark it Needs Review.
Uncertainty is normal in a drive that has grown for several years. The mistake is settling it with a guess.
Create one place called Needs Review. Put the record there with a short note about which question you could not answer. Do not delete it, do not rename it into something that sounds more confident, and do not widen access to make it easier to work on.
Needs Review is not a failure. It is the difference between a reorganization the team can trust and one that quietly loses things.
Test the change with one team for thirty days.
A structure that works on paper can still be wrong for the people using it. Agree on the folders with one program or one team, then use them for thirty days without changing anything else.
At the end, ask three plain questions. Could people find what they needed. Did anyone make a copy outside the structure. Did anything land in Needs Review that should have been obvious.
Fix the structure based on those answers, then move to the next team. A small tested change spreads. A large untested one usually gets abandoned.
A shared drive becomes dependable when every important record has a known owner, a known status, a deliberate access decision, and one approved copy.
Companion workbook
A one-page worksheet for running the four questions on your own records. Print it, or work through it with a team.
Download the workbook (PDF)