Chapter 37 — Key Takeaways

The one-page reference to screenshot and re-read before a shoot, an edit, or a wrap. This is the whole chapter as templates and checklists. The single idea under all of it: the professional never loses work — not through talent, but through dull habits done every time.

The five terms

The folder-structure template (clone this per job)

/VIDEO/                              ◄─ one library home for ALL work (never the Desktop)
├── _TEMPLATE_PROJECT/              ◄─ duplicate THIS to start every job
├── 2026/  2025/  ...               ◄─ projects grouped by year
│    └── 2026-05_CLIENT_what/       ◄─ ONE project: DATE_CLIENT_what
│         ├── 00_README.txt         manifest: what it is, software+version, specs, master
│         ├── 01_FOOTAGE/           camera originals (the masters) — never edit in place
│         ├── 02_AUDIO/             recorder, room tone, VO
│         ├── 03_MUSIC-SFX/         tracks + their LICENSE files
│         ├── 04_GRAPHICS/          logos, stills, motion files, FONTS/, LUTS/
│         ├── 05_PROJECT/           the edit project file(s) + auto-backups
│         ├── 06_PROXIES/           DISPOSABLE — not archived
│         ├── 07_EXPORTS/           the MASTER + every deliverable
│         └── 08_DOCS/              brief, script, call sheet, releases, invoices
└── _ARCHIVE/                       wrapped projects, moved off the fast drives

Rules: numbered so folders sort in workflow order (not alphabetically) · the same skeleton on a phone clip and a five-day shoot (small jobs leave branches empty) · media lives inside the project folder (makes it portable, §37.6).

File naming: the rules that make names survive

Naming patterns (adopt and freeze):

⚠️ Never rename a file on disk after importing it — the project stores names as pointers; renaming underneath = "media offline." Rename before import or inside the project.

3-2-1 backup: the rule and what each number defends

Not a backup: ✗ a second folder on the same drive · ✗ RAID (that's uptime) · ✗ a sync folder (propagates deletions — keeps sameness, not history).

Storage is not backup. A file on one drive — however good the drive — is stored, not backed up. If it exists in only one place, it does not exist.

Drives: match the drive to the job

Rules: never edit off a backup/archive drive · never put scratch on your only media copy · keep ~10–20% of any working drive free · trust the drive-tier order, not the exact MB/s figures.

Archive checklist (at wrap)

Keep (irreplaceable):

• [ ] Camera originals / masters (01_FOOTAGE)
• [ ] Clean audio + room tone (02_AUDIO)
• [ ] Music + license files (03_MUSIC-SFX)
• [ ] Graphics, motion project files, fonts, LUTs (04_GRAPHICS)
• [ ] Final/locked project file (05_PROJECT)
• [ ] The master export + delivered versions + captions (07_EXPORTS)
• [ ] Brief, signed releases, invoice (08_DOCS)
• [ ] 00_README manifest (software+version, fps, resolution, where the master is, fonts/LUTs, specs)

Drop (regenerable / noise):

• [ ] ✗ Proxies (06_PROXIES) · ✗ render cache/scratch · ✗ draft & duplicate exports · ✗ card system junk

Then:

• [ ] Consolidate project + used media into one self-contained folder (relative paths)
• [ ] 3-2-1 the archive (2 durable copies + 1 off-site) — an archive on one drive is one flood from gone
• [ ] Test the reopen — rename the working copy, open from the archive alone, confirm nothing offline
• [ ] Calendar a migration check (verify + re-copy to fresh media every 1–2 years)

The test for everything above: could I reopen this in a year and have all I need?

Handoff / portability checklist

• [ ] Media lives inside the project folder, referenced by relative paths
• [ ] Consolidate with the editor's project-archive / collect function (one bundle)
• [ ] Include fonts (or titles reflow/substitute)
• [ ] Include LUTs (or the grade loads wrong)
• [ ] Note plugins/effects the other machine needs
• [ ] Include music & graphics source files
• [ ] 00_README: software and version, fps, resolution, specs, master location, contact
• [ ] Business: confirm who owns the project files (contract — Ch.38) before handing over

A project file is only pointers, not media. Relative beats absolute; neighbors move together.

Common mistakes → fixes

The 60-second recovery self-test

Ask these of any project you care about. Every "no" is tonight's task.

• [ ] If my main drive died right now, could I name exactly where the other copies are?
• [ ] Is at least one copy off-site (cloud or elsewhere) — not just in another drive in this room?
• [ ] Could I find the master export and the signed releases in under a minute?
• [ ] If I opened this project cold in a year, would every clip, font, and grade come back?
• [ ] Do I know which exported version I actually delivered to the client?

If you can answer "yes" to all five for a project, it is genuinely safe. If not, the "no" tells you precisely which section (§37.1–37.6) to act on first — almost always the off-site copy.

Principles & project

Craft principles this chapter serves:

• Fix it in pre, not in post — the folder tree built before the shoot, and the card discipline on set, are what make the edit and archive painless.
• You shoot for the edit — labeled, named, synced-ready media at ingest is the shoot paying off in post.
• The value of finished work is mostly in the future — which is exactly what you can't see when a full drive tempts you to delete. So you keep it.

Project increment (all three projects): archive and back up all three portfolio projects with 3-2-1 and a consistent folder/naming structure; test that you could reopen any of them in a year. These archives are the source you'll cut your reel from in Chapter 39.