Make Sense of a Drive After the Person Who Built It Leaves
Somebody leaves, and the folders they leave behind are organized around how they personally thought about the job. Nobody else can read it, the person who could is gone, and the clock on reassigning their storage is already running.
The short answer
The drive is legible again once its documents are named from their contents rather than from one person's shorthand. A workflow triggered by On a Schedule runs over the inherited folder, uses Ask AI About the File and Read Details from File to work out what each document is and who it concerns, then Rename and Move put it into the same structure the rest of the department uses. Ask a Person to Approve in front of the move means the result is a proposal somebody signs off rather than a second reorganization nobody asked for.
Steps this uses
Before and after
What actually changes
As they arrive
- From R Mensah/stuff/final ones/doc7.pdf
- From R Mensah/misc/Untitled.docx
- From R Mensah/2024 wip/acme thing v3.pdf
- From R Mensah/scans/scan_0091.pdf
After the workflow
- Clients/Northwind/2024-11-06-statement-of-work.pdf
- Needs Review/Untitled.docx
- Clients/Acme/2024-08-21-proposal.pdf
- Clients/Lighthouse/2024-03-14-signed-agreement.pdf
One person's private filing system read back into the department's, with the one document nothing could be concluded about held aside.
Setting it up
Described once, then it runs
This is the sentence. Send it to the builder and the steps below appear on a canvas, wired and named, for you to change before anything runs.
Once a day, go through the folder I inherited, read each document to work out what it is and which client it belongs to, rename it date-first, and show me where you propose to file it before moving anything.
Copy before you touch anything
Work on the inherited folder only once you are certain nothing is being preserved for a dispute. If there is any prospect of one, stop: reorganizing a leaver's drive moves and renames files, and that is not a safe thing to do to material somebody may have to account for later.
Point it at the department structure
The destination is the structure the rest of the team already uses, not a new one invented for this drive. The whole objective is that the leaver's work stops being a separate territory with its own conventions.
Let it propose rather than act
Ask a Person to Approve pauses with the proposed filing in front of whoever inherited the work. They will recognise things the reader cannot, and the cost of reviewing a list is far below the cost of finding out later that a year of project files went somewhere odd.
Run it over days, not in one pass
The On a Schedule trigger lets the job run in batches, which keeps each approval small enough that somebody actually reads it. A single approval covering four thousand files gets rubber-stamped, which defeats the point of having one.
Why this is predictable enough to plan for
Staff turnover is the moment records practice most reliably breaks, and it is the one moment you can see coming. Institutions that handle it well ask the departing person to prepare a handover while they are still there. That works when somebody gives notice and does the work, and it does not work when they leave abruptly, which is why the fallback matters at least as much as the policy.
The structural fix is filing by function
A drive organized around a person collapses when that person goes. A drive organized around what the department does survives both a leaver and a reorganization, because the functions outlast the people performing them. If you are already reorganizing an inherited folder, it is the cheapest moment you will ever get to move to a functional structure rather than recreating somebody else's.
Stop if anything is under hold
Reorganizing a leaver's drive renames and moves files, and where a document lived can itself carry evidential weight. If a matter, audit or investigation is open or anticipated, none of this should run. That judgement comes from your legal office rather than from anything the workflow can detect, and the fact that a departure has a deadline attached is not a reason to proceed without it.
Limits
What to know before you build it
It can work through what is already there
This one runs on a schedule over a folder you point it at, so the documents sitting in it now are read and filed alongside the ones that arrive later. A large backlog is an overnight job rather than an instant one, because each document is read rather than pattern-matched.
What you need to run it
Pointed at a folder in The Drive AI, this works on every plan including the free one, because the files are already here. Pointing it at a Google Drive, OneDrive, SharePoint or Dropbox folder instead means connecting that account, which is on the Max plan or any team workspace.
FAQ
Common questions
What should happen to a departing employee's files?
They should be reviewed and moved into the department structure before the person's storage is reassigned, so the records outlast the account. Many institutions allow a fixed window after departure, commonly thirty days, and explicitly suspend it where a litigation hold applies.
Can a workflow reorganize an inherited folder on its own?
It can read each document, propose a name and a destination, and hold the batch for approval. Letting it move files unattended is possible but rarely wise on an inherited drive, because the person reviewing recognises context the reader does not and that context is exactly what was lost.
What about documents nothing can be concluded from?
They go to a review folder. On an inherited drive this pile is usually larger than on a live one, because the documents with the least context are the ones the leaver understood without needing to write anything down.
Is it safe to do this while a legal matter is open?
No. Reorganizing moves and renames files, and both location and naming can matter evidentially. If litigation, an audit or an investigation is open or anticipated, preservation takes priority over tidiness, and the decision belongs to your legal office rather than to whoever inherited the folder.
The drive should outlast the person who built it.
Read what is there, propose where it belongs, and move nothing until somebody agrees.
5 GB free · No credit card required