01
Capture the Current Structure
You create a factual baseline before deciding what should change. You separate confirmed details from guesses and missing data.
Made for Administrators
Clean Up Your Shared Drive Without Breaking It
Also useful for: people in Government
120 min
Advanced
Government
Administrator
Get Organized
Career outcome:
Avoid Professional Risk
Turn a cluttered shared drive into a practical cleanup plan with a folder map, naming rules, duplicate decisions, safe move sequence, and filing guide.
We'll use them to write your prompt.
Completed ✓
Make Your Play
Give us the situation. We’ll build the prompt.
You can reduce search time and duplicate files without rushing into risky moves.
Your answers save as you type.
What you'll do
This is the plan inside your prompt. Add your details first. Then follow these steps with ChatGPT or Claude.
02
Classify What You Have
You sort folders into useful working categories so active files, records, archives, and unclear areas don't receive the same treatment.
03
Flag Conflicts and Risks
You find the conditions most likely to cause lost access, broken links, duplicate records, or accidental disposal.
04
Choose the Target Structure
You design a folder tree that matches how your work is found and maintained, not just how the old drive grew.
05
Set Naming and Filing Rules
You create rules that keep the new structure usable after the initial cleanup.
06
Build the Move Register
You turn proposed changes into a controlled list that can be reviewed, approved, tracked, and reversed.
07
Plan Safe Migration Waves
You group approved changes into small waves so you can test the structure before touching sensitive or heavily used areas.
08
Create Protection and Rollback Checks
You define what you must verify before and after each wave so you can catch problems early and restore the prior state if needed.
09
Publish the Filing Guide
You give your team short rules for finding, saving, naming, and reporting files after the change.
10
Run the Final Readiness Review
You check whether the plan is safe enough to approve and isolate anything that must remain untouched.
Make Your Play
Clean Up Your Shared Drive Without Breaking It
Tell us what the prompt needs to know
Start with the questions below. Each answer personalizes the playbook and builds the prompt you’ll use at the end.
Your situation
Provide your folder tree, exported file list, or a representative map with paths, owners, dates, and sizes when available.
0/10000
List the problems you need to fix, including duplicate areas, unclear names, lost files, deep nesting, or inconsistent filing.
0/10000
Choose the platform your shared files use so your checks account for platform behavior.
Provide the rules that control how long you must keep records and who can approve disposal.
0/10000
Describe your access groups, restricted folders, inherited permissions, or areas that mustn't change.
0/10000
List your known shared links, shortcuts, templates, automations, reports, or systems that depend on current paths.
0/10000
State the exact part of the drive you want to plan now.
Choose the organizing model you prefer, or let your material determine the recommendation.
Set the maximum number of files or folders you want in your first low-risk test wave.
This playbook was updated. Review your inputs before copying.
What you'll do
Check a step when you finish it.
01
Capture the Current Structure
You create a factual baseline before deciding what should change. You separate confirmed details from guesses and missing data.
02
Classify What You Have
You sort folders into useful working categories so active files, records, archives, and unclear areas don't receive the same treatment.
03
Flag Conflicts and Risks
You find the conditions most likely to cause lost access, broken links, duplicate records, or accidental disposal.
04
Choose the Target Structure
You design a folder tree that matches how your work is found and maintained, not just how the old drive grew.
05
Set Naming and Filing Rules
You create rules that keep the new structure usable after the initial cleanup.
06
Build the Move Register
You turn proposed changes into a controlled list that can be reviewed, approved, tracked, and reversed.
07
Plan Safe Migration Waves
You group approved changes into small waves so you can test the structure before touching sensitive or heavily used areas.
08
Create Protection and Rollback Checks
You define what you must verify before and after each wave so you can catch problems early and restore the prior state if needed.
09
Publish the Filing Guide
You give your team short rules for finding, saving, naming, and reporting files after the change.
10
Run the Final Readiness Review
You check whether the plan is safe enough to approve and isolate anything that must remain untouched.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
You can start with one department or one top-level folder instead of the full drive. Export a file list if your platform allows it, or paste a simple outline of folder names and important files. Remove passwords, personal details, and confidential file contents before you upload anything.
You should treat every proposed move as a draft. Get approval before you change shared locations, permissions, retention records, or active folders.
Advanced instructions
You can include file paths, owners, modified dates, sizes, permission groups, sensitivity labels, retention categories, shortcut targets, and known automation dependencies. Ask for a move register that you can import into a spreadsheet or task tracker.
You should run the plan in controlled waves. Take a baseline inventory, test a small folder, validate access and links, record exceptions, and pause the rollout if your checks fail.
Use this when
Use this when your shared drive has duplicate folders, vague names, abandoned files, inconsistent filing, or documents that your team struggles to find.
You'll need
- Drive inventory
- Drive problems
- Drive platform
- Retention and records rules
- Permission concerns
- Linked dependencies
- Cleanup scope
- Preferred filing model
- Pilot size
You'll get
- A current-state map, a target folder tree, naming rules, a move register with approvals and holds, sequenced migration waves, validation checks, a rollback plan, and a filing guide
- You can identify every unresolved risk before any live change begins.
By the end of this playbook
You will have:
- A current-state map, a target folder tree, naming rules, a move register with approvals and holds, sequenced migration waves, validation checks, a rollback plan, and a filing guide
- You can identify every unresolved risk before any live change begins.
Examples
Progress 1 of 10