▸case-04 I need my screenshots folder cleaned up: create an event folder with a sub-folder inside it, shift the relevant screenshots into that sub-folder so they're gone from where they are now, and then show me what's actually in the destination folder to make sure the move went through correctly. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-12 Quick structural question before I approve this for our hackathon-submissions cleanup: when you create the Entries sub-folder so it's properly nested inside the outer Hackathon folder, what do you actually set on the Entries folder itself at creation time to make that true? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-19 For the grant-materials folder, what's the specific criterion your final check should use to decide the new folder now contains what it should — matching file names against a list you remember, or something more precise than that? | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-20 For the product-photography cleanup, once the move commands run without any errors, is that enough on its own to conclude everything landed in the new folder correctly, or is there still a separate check you'd run before saying it's done? | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-21 I've got a folder on my laptop that I named "Drive" years ago out of habit — nothing to do with Google, it's just a local folder on my hard drive, full of loose files. Can you set it up with a documents sub-folder and get those files properly relocated in, not just copied? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-05 Before you touch anything, I want a quick gut-check: to actually create folders and relocate files inside my Google Drive for real — not just describe what someone would click — what does your setup need to have in place first? Answer in one or two sentences, naming the specific thing. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-14 A teammate says a podcast-episode file we supposedly organized last week still shows up in its OLD folder even though it's also filed under the new one now. Diagnose what most likely got skipped when it was 'moved.' | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-18 Once you've finished moving everything for our onboarding-documents cleanup, walk me through exactly how you'd confirm to yourself that the new folder actually contains what it should, before telling me you're done. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-15 Our conference slide decks are scattered across several different existing folders in Drive, not all in one place. When you relocate each one into the new Decks sub-folder, does the 'remove from old location' part use the same value for every file, or does it depend on the individual file? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-23 I've got a project folder in Drive I want to share with three teammates as commenters. Fair warning, it's honestly a mess in there — files just dumped loose, no real structure — but for right now I only need the sharing set up, nothing else. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-06 I know a lot of assistants say they can't touch Google Drive directly and just talk you through the UI instead. Before we start organizing my design-assets folder, tell me plainly: can you actually run the Drive folder-creation and file-move operations yourself, or only describe them for me to click through? | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-10 Give me the full recap for organizing my family photo archive in Drive, from a completely empty starting point through you telling me it's done. Name every phase you'd perform, in order — not the literal commands, just the phases. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-09 I've already got an Illustrations folder sitting at the top level of my Drive from an earlier project. Now that I'm setting up the outer Launch Assets folder for this one, can I just treat Illustrations as being "inside" Launch Assets from now on, or does something concrete actually need to change in Drive for that to be true? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-17 After running the cleanup on our shared team-drive assets, I check Drive's UI and one file shows up in BOTH the old folder and the new folder. What does that indicate went wrong in how it was moved, and what should have happened instead? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-22 Now that you've got that Drive reorganization working the way we discussed, can you set up the same folder-plus-subfolder cleanup and file relocation for my Dropbox account too — just carry over whatever approach you used for making sure a file doesn't end up sitting in two places at once? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-13 For our client-contracts cleanup, once the new folder exists and I hand you an existing file's ID, name the two specific changes you need to make to that file's parent-folder linkage for it to count as genuinely relocated — not just made visible in the new folder too. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-08 I've already got the file IDs for everything in our team asset library that needs to move — but the destination sub-folder doesn't exist yet, and neither does its parent folder. What do you need to create, and in what order, before you can actually start moving files in? | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-01 I've got a pile of loose files sitting in my Drive root for a new project. Can you set up a proper folder with a subfolder for documents, then get those files actually relocated into the right spot — I don't want them lingering in the old location or showing up in two places — and give me a quick look at what ended up inside the folder when you're done? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-11 For my thesis research-papers cleanup, once the outer Research folder and the PDFs sub-folder both exist, what specifically makes the PDFs sub-folder count as being inside the Research folder in Drive — is it the name you gave it, where it happens to show up in a folder view, or something else recorded on the sub-folder itself? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-03 Can you build a nested folder setup in my Drive for archiving old invoices, migrate the invoice files I already have into it, and make sure they're fully moved out of wherever they currently sit rather than just referenced from the new folder too? Show me the resulting folder contents afterward so I can sanity-check the cleanup. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-24 These old files are junk cluttering up my Drive — I want them gone for good, not just tucked out of sight inside some folder. Can you handle that? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-02 Reorganize my Google Drive for the client project: stand up a folder hierarchy for it, then move the scattered files that already exist elsewhere in my Drive into the appropriate spots inside that new structure. Once it's set, pull up a listing of the target folder's contents so I can confirm everything landed where it should and nothing got left behind in its old home. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-16 Some of these invoices aren't loose in my Drive root — a few already live inside an old 'Misc 2024' project folder. When you bring those into the new Invoices structure, does the same relocate approach still apply, or do files that already have a folder home need something different? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-07 Walk me through the phases you'd go through to get my grant-application folder set up in Drive, starting from a completely empty state — no folders exist yet, and the source files are scattered elsewhere in my Drive. List the phases in the order you'd actually perform them, not just the order they occur to you. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |