Projects live or die by how their files are organized. Source media, project files, exports, and notes all accumulate quickly, and a project that cannot be found is a project that cannot be finished. Asset management is the set of habits that keeps every file findable.

Folder conventions

Consistency matters more than any particular scheme. A common convention separates source media, exports, and project files at the top level:

The value is navigability: anyone opening the project, including the future version of you, can find a given file without reading the whole tree.

Naming conventions

File names should carry the information that the folder structure cannot: what, when, and which version. Dates in a fixed sortable form and version numbers prevent the classic failure of overwriting or losing work to a vague name.

Examples: Interview_20230115.mp4, Meeting_20230115.wav, Product_Shots_20230115.jpg. When a file changes, the version number changes too, so that the current file is always identifiable at a glance.

Keeping a manifest

A manifest is a single inventory of project assets: a spreadsheet or a plain list that records each asset, its location, and its relevant metadata, such as date, version, format, resolution, bitrate, sample rate, color space, and aspect ratio. A manifest pays off on larger projects, where many assets and people are involved, and where the alternative is asking around or searching by hand.

Separating masters from delivery copies

Masters and delivery copies serve different purposes and should live apart. The master is the unaltered or highest-quality version, kept untouched so that any future change can be made without losing quality again. Delivery copies are generated from masters for a specific destination. A separate delivery folder, with its own naming, makes it clear which files are safe to hand out and which must be preserved.

Backups

One copy is zero copies when a drive fails. The durable pattern is redundancy in more than one place: an external drive plus a cloud storage service, or two of either, with copies refreshed on a schedule. The important part is that a backup that has not been tested is a hope, not a backup.

The value of a short readme

Every project folder benefits from a short readme: project description and goals, recording dates, team members, software requirements or plugins, and the export settings used for final deliverables. A readme is cheap to write and expensive to be without: it is the difference between a folder that speaks for itself and one that only its author can navigate.

Conclusion

None of these habits is glamorous, and all of them compound. Folder conventions, honest naming, a manifest, separated masters, tested backups, and a readme are what let a project scale past what one person can hold in their head. The right system is the one you will actually apply consistently, so keep it simple enough to survive contact with a deadline.