Why teams with more than one editor need logged footage

One editor can run a library from memory. Two cannot. The moment a second editor opens the project, every piece of knowledge that lives only in the first editor's head becomes a tax on the whole team, and most post teams pay it daily without ever naming it.

The scene is always the same. A new editor joins mid-season and gets "the tour": ninety minutes of over-the-shoulder folklore. The good interview is on the drive marked JULY, except the second half, which is on the desktop. Skip the wide from day two, the boom is in frame. The b-roll folder called MISC is actually the best stuff. Nobody wrote any of this down, so it gets performed, live, for every new hire, and half of it is forgotten by Thursday.

Tribal knowledge is a single point of failure

Ask a blunt question about your own team: if the person who knows the footage left tomorrow, what would the drives be worth. Not emotionally, operationally. On most teams the honest answer is "a fraction", because the map of what exists, what is good, and what is cleared lives in one head. People leave mid-project. They get sick during finishing. They take the vacation they already cancelled twice. A team whose footage knowledge is one person's memory is one resignation away from re-watching an entire season of material.

Logged footage is the succession plan. When "what do we have on the northside factory" is a filter instead of a phone call, the person who shot it can leave, and the team keeps its velocity.

One vocabulary, or five private ones

Two editors will invent two vocabularies by lunch. One types "interview", the other "ITV". One rates keepers with stars, the other flags them, a third drags them into a folder called GOLD. Every private system works fine alone and fails the moment anyone else has to search it, which is the entire situation of a multi-editor team.

The fix is boring and it works: one controlled vocabulary, agreed once, enforced by the tool rather than by memos. This is exactly why ClipLogger builds logging around a shared palette: the fields, their allowed values, and even their synonyms are defined once per project, so "TD" and "touchdown" resolve to the same value no matter who typed it, and the schema travels inside the project document to every machine that opens it. Whatever tool you use, the principle stands: pick the words together, then make improvising new ones impossible.

A handoff should be an open, not a tour

Watch what happens when a project moves between editors on a logged team. The incoming editor opens the folder, filters to the confirmed selects, reads the notes on the clips that matter, and starts cutting. No meeting. No shared doc titled READ FIRST. No week of "quick questions" to the last editor, who is trying to be on another job.

Sidecar metadata is what makes this physical. When the record of every decision sits in plain files beside the footage (ClipLogger writes these as .logger.json sidecars, with XMP, Resolve CSV, FCPXML, or ALE on top if your pipeline reads them), handing off a project is handing off a drive. A second machine that mounts the same storage picks up the same tags, notes, and selects without anyone reprocessing or exporting a thing. Author stamps matter here too: a marker signed @maya reads very differently from an anonymous one, and a disagreement gets settled by asking the right person instead of re-watching the clip.

Assistants cutting selects on day one

The standard waste on a growing team is the assistant editor spending week one "getting familiar with the footage", which means watching all of it at 1x with the door closed. On a logged project the same assistant filters to the two people in tomorrow's scene, sorts by rating, and has a selects sequence by the afternoon. Familiarity with the footage arrives as a side effect of doing real work.

This is also the honest division of labor with AI logging: a machine proposes descriptions, transcripts, and who appears where, a human confirms what is true, and the confirmed record is what the next person builds on. Suggestions nobody reviewed stay quarantined as suggestions, out of exports and searches. The assistant is not trusting a robot, they are trusting a teammate's confirmations.

What to standardize this week

None of this needs new software to start, it needs four agreements. One: a shared vocabulary, written down, with the allowed values for each field. Two: a definition of a select, meaning what a flag or a star promises the next editor. Three: a naming convention, since the file name is the only metadata every tool and portal preserves. Four: the rule that knowledge about footage lives in files beside the footage, never in one person's project file or one person's head. A team that keeps those four agreements can swap editors mid-project and barely feel the seam.

A library only one person can navigate is not an asset, it is a liability with that person's name on it, so write the knowledge down where the footage lives.