Create an asset inventory from a folder

An inventory should describe what files exist and what requires review, without deleting or reorganizing anything during the first pass.

Bound the operating task

Provide the relevant records and define what is a draft recommendation versus an approved action. Keep original records intact and ask for an output manifest so you can find the result. Start with file generation and human review before adding any external action through a connected tool. A useful operations deliverable should make exceptions and missing information visible.

Inputs for this workflow: A dedicated folder and desired file categories.

Work through the task

1. List files with relative paths and formats.
2. Flag naming conflicts and likely duplicate candidates.

A brief you can adapt

Create inventory.csv and review-notes.md. Record relative path, extension and purpose when evident. Do not move or remove files.

The filenames above are examples. Replace them with your actual inputs and destination before submitting the task.

Review the deliverable

Compare the inventory count with the folder and inspect candidates before deciding they are duplicates.

Where this approach can fail

Matching filenames or sizes do not prove identical content.

For the related desktop setup, see review results.