Frame Ledger / file order

Give a Photo Project a Clear Folder Shape

Separate originals, working notes, and outputs without overbuilding.

The decision

A folder structure should make the next retrieval obvious. It does not need dozens of nested categories, and a photo organizer may add its own catalog structure above the physical files.

A practical sequence

Choose a project name that identifies the event or subject without exposing private details. Use a date when it helps distinguish repeated shoots. Make separate areas for originals, notes, and exports. Confirm where new files actually land after import. Open the project from its intended storage location before deleting any temporary copies. Keep paths stable if your organizer tracks files by location.

Worked example

For repeated garden visits, a project such as “2026-10-garden-autumn” can contain “originals,” “notes,” and “exports-newsletter.” A later spring visit gets a different project, not an extra layer of ambiguous folders named “new.” The folder name need not contain a home address, client phone number, or other information that could leak during sharing.

What can go wrong

Moving files outside a catalog-aware organizer can leave missing-file references. Use the supported move or relink workflow for your application. Do not interpret a missing thumbnail as proof the original was erased. Check the actual storage and backups before taking corrective action.

Your completion record

Write down the project root and the export destination. Test retrieval by closing the file browser and finding one original again. A structure passes when the next visit is understandable without a remembered sequence of clicks.

Before continuing, check the record against the actual files rather than relying on memory. Keep uncertain decisions labeled as uncertain. The next useful step is the specific task named in your completion record, not a fresh pass through the entire archive.