Where Does the File Actually Live?

“It's in Google” is not a location model.

A school assignment can exist as a cloud-native Google file, a downloaded Microsoft Office copy, an uploaded image, a shortcut to another Drive location, or a file synchronized to a device. Those objects can look related while behaving differently.

Trace the object, not the icon

Start with four questions:

1. What is the object? Google Doc, PDF, .docx, image, Sheet, shortcut?
2. Where is its authoritative location? Drive, local Downloads, another shared Drive location?
3. Who owns or controls it? You, another account, a shared workspace?
4. What operation happened? Open, upload, download, copy, move, or create shortcut?

A download usually creates another file. It does not magically move the cloud original.

Google Doc in Drive
      │
      └── Download as .docx
              ↓
        local .docx copy

Now there are two editable objects. Changing the .docx does not prove the Google Doc changed.

Worked trace

Jordan receives a shared Google Sheet called Device Inventory. Jordan downloads it as an Excel file, changes three rows, and later opens the original shared Sheet. The changes are missing.

Nothing mysterious happened. The evidence says Jordan edited the downloaded copy, not the cloud original.

Build a File Location Trace

Use only harmless course files. Perform or inspect three different file states:

• one cloud-native file in Drive;
• one downloaded copy of a course-safe file;
• one uploaded file or teacher-supplied example of an uploaded file.

For each, record object type, location, owner/controller, and what would need to happen for a change to reach another copy.

If device policy blocks downloads or uploads, use a supplied scenario instead. The learning target is the trace, not defeating a device restriction.

Common failure: confusing a shortcut with a copy

A shortcut is a path to another object. A copy is a separate object. If you remove a shortcut, the target can still exist. If you copy a file, later changes can diverge.

The exact Google interface may show different icons over time; the underlying distinction remains.

Evidence check

Submit the File Location Trace and answer:

Which file in your trace would you treat as the authoritative version, and what evidence supports that choice?

Do not answer “the newest one” unless you actually have trustworthy modification-time and ownership evidence. Location, ownership, and workflow purpose matter.