Text guides

Digital organization

Give files and information a place you can find again. Plan changes in small batches and check what must stay before deleting or moving anything.

12 practical tasks. Each guide includes a sample request and a way to check the answer.

Design a folder structure for one projectSplit the project into three zones: material you received, files you are still changing, and outputs someone has approved. Give each folder one stated purpose, one owner and one naming convention. If a sample file could live in two folders, tighten the purpose statements.
Plan email rules before turning them onA rule needs a pattern you can describe precisely and an action you can undo. Write each rule on paper first, list the exceptions that must still reach your inbox, and test the wording against real messages before switching anything on.
Turn a messy bookmark collection into a useful indexOrganize bookmarks by the job each one helps you do, not by website or topic. List each link with its task, note whether you still use it, flag duplicates and set a next action. A link you never open is different from a link that no longer loads.
Make a plan for sorting a downloads folderA downloads folder mixes installers, temporary copies and documents you may need later. Group files by type and likely purpose, then ask where each keeper would live. A file name is a clue, never proof that a file can go.
Prepare a shared-folder permission reviewRecord what each shared folder is for, who can reach it now and who should. Copy the current sharing details from your storage provider's own screens. Compare the two lists and leave every change for the folder owner to decide.
Identify the current version of a working fileGather every candidate copy and compare what changed between them, who approved which, and whether the content matches the decision that was made. A modified date shows when a file was saved, not which version people agreed on.
Plan a move between notes appsMove a handful of representative notes first, not the whole library. List the kinds of notes you keep, export a sample of each and open the results in the new app. Switch only after structure, formatting and attachments survive, and leave the original untouched until then.
Create a weekly review for saved links and notesReview saved links and notes by the use you expect to make of them. Turn a useful item into a next action or file it as a reference; discard what you have checked and no longer need. Put ambiguous items in a dated holding queue for a closer look.
Explain how a group should add to a shared albumTell contributors what the album is for, what belongs in it, how to name or caption files and who may see or reuse the photos. State plainly that adding a photo to the album does not give anyone permission to post it elsewhere.
Make an account inventory without collecting passwordsAn account inventory can record which services exist, why they matter, who controls recovery and when to review them without containing a single password. Store the type of recovery method, such as a phone number or a backup email, and leave the details out.
Plan a cloud-folder move without losing shared workList who uses the folder and which links depend on it before changing its location. Check your provider's current instructions and choose a recoverable test. Prepare a backup or rollback method for the real move, then verify access, ownership and links with a collaborator.
Decide which notifications you actually needKeep a notification when it prompts something you would act on and cannot easily learn another way. List each app's notification types, name the action each triggers and choose when it should arrive. Treat security alerts and essential service notices separately from everything optional.

Related topics