Files and Folders: Plan a Tree and Track Copy, Move and Rename

Files and folders: follow the path, then the operation

A file name tells you only part of the story. Two folders can contain different files named notice.odt, and a familiar item in a navigation list may be a link to a location elsewhere. A reliable answer therefore records the complete location before predicting what copy, move or rename will do.

Use this fictional project as a paper exercise. All operations finish successfully, destination names are available unless a task explicitly says otherwise, and no files are edited during a sequence. We count ordinary files only, not folders or navigation links. Each worked case starts again from the original six-file tree; the cases are not cumulative.

Read the tree and plan by purpose

ToolProject is the root of this small diagram, not the root of a whole disk. Drafts holds work in progress, Images holds artwork and Approved holds completed material. These purposes help a reader decide where to look without creating a separate folder for every file.

• ToolProject
  • Drafts
    • notice.odt
    • stock.ods
  • Images
    • map.png
    • badge.svg
  • Approved
    • notice.odt
    • checklist.pdf

The path ToolProject/Drafts/notice.odt means enter ToolProject, then Drafts, then identify notice.odt. Slashes are a convenient notation in this lesson. Windows File Explorer normally displays backslashes or a breadcrumb address; this difference in presentation does not change the sequence of folders.

The full filename includes its extension: .odt, .ods, .png, .svg or .pdf. We will keep extensions visible in every answer. The two notice.odt files have the same complete filename but different full paths. The Drafts version says “Return desk opens at noon”; the Approved version says “Return desk opens at ten”. They are different files, even though their names match.

Predict the operation before changing the inventory

For every instruction, underline the source path, circle the destination folder and write the final filename. Do not guess an operation from a drag gesture: real applications can choose different drag-and-drop actions in different contexts. Here the requested operation is stated explicitly.

Worked case 1: copy a stock sheet

Before: use the original tree above. Copy ToolProject/Drafts/stock.ods into ToolProject/Approved, keeping the name stock.ods. The destination does not already contain that filename, so the predicted result has no naming collision.

• ToolProject
  • Drafts
    • notice.odt
    • stock.ods
  • Images
    • map.png
    • badge.svg
  • Approved
    • notice.odt
    • checklist.pdf
    • stock.ods

After: Drafts still contains stock.ods, and Approved now contains another stock.ods. Both initially hold the copied content. They are separate ordinary files, so later editing one is not an instruction to update the other. The total rises from six to seven. An answer showing the stock sheet only in Approved has simulated a move instead.

Worked case 2: move, then rename

Before: reset to the original tree. Move ToolProject/Images/map.png into Drafts. Its intermediate path is ToolProject/Drafts/map.png. Then rename that file route.png, leaving it in Drafts.

• ToolProject
  • Drafts
    • notice.odt
    • stock.ods
    • route.png
  • Images
    • badge.svg
  • Approved
    • notice.odt
    • checklist.pdf

After: the required path is ToolProject/Drafts/route.png. Images has only badge.svg. The total remains six after each step: moving did not produce an extra file, and renaming did not produce one either. The picture data has not changed merely because the name is clearer.

Worked case 3: prevent an ambiguous destination

Before: reset to the original tree. Rename Drafts/notice.odt to notice-v2.odt. Copy that renamed file to Approved, then move Approved/checklist.pdf to Drafts. All paths in this paragraph are relative to ToolProject.

• ToolProject
  • Drafts
    • notice-v2.odt
    • stock.ods
    • checklist.pdf
  • Images
    • map.png
    • badge.svg
  • Approved
    • notice.odt
    • notice-v2.odt

After: Approved contains the old notice.odt and the newly copied notice-v2.odt. The revised name avoids a collision with the existing notice. The checklist has changed folder. The three steps produce totals of six, seven and seven respectively. The word “Approved” is merely a folder name; copying a draft there does not prove anybody reviewed its contents.

Check the final inventory

Counts are a useful cross-check, but they cannot prove the paths are right. Case 2 would still total six if route.png were mistakenly left in Images. Verify both the total and every affected path. Also check that unrelated files, such as badge.svg, have stayed where the instructions left them.

Three solved practice tasks

Task 1: identical names, different content

Starting from the original tree, which notice says the desk opens at ten? Would “open notice.odt” uniquely identify it?

Solution: ToolProject/Approved/notice.odt contains that sentence. The name alone is ambiguous because Drafts also contains notice.odt. Give the full path. Neither alphabetical order nor the word “notice” establishes which content is newer or correct.

Task 2: a navigation shortcut is not a moved folder

A learner sees Approved under Quick access and concludes that all its files have moved into a new folder called Quick access. What is wrong?

Solution: A pinned navigation entry provides a route to the folder; its appearance in that view does not establish a new storage location or a copied document. Check the opened folder’s address. In this simulation, the two original Approved files still have their original paths and the inventory stays at six.

Task 3: extension changes and collisions

A learner proposes renaming Drafts/notice.odt to notice.pdf and copying it into Approved as notice.odt. Does the first step create a PDF, and is the second destination unoccupied?

Solution: Renaming an extension does not convert the document’s format. A genuine PDF requires an appropriate export or conversion, outside this exercise. Approved/notice.odt already exists, so the proposed copy has a naming collision. Stop the paper sequence at that unresolved instruction rather than assuming replacement, an automatic suffix or a particular application prompt.

Connecting the model to software

Microsoft’s File Explorer guidance documents Copy, Cut, Paste and Rename in Windows 11, and distinguishes navigation through Quick access. The paper model avoids version-specific clicks. Microsoft also explains why changing a filename extension does not convert the file.

A second copy in the same project is useful for this counting exercise, but it is not a guarantee against device loss, damage or all other failures. The lesson establishes locations and operation effects, not a backup plan.