Systems you keep when the editor leaves

Somebody takes a full time job, raises their rates, or simply stops replying. The next person arrives and asks you the things the last one had already learned, and you spend a month rebuilding a working relationship you thought you owned.

The files come back, if you asked for them properly. What does not come back is the knowledge: that your name has an accent on it, that you never want music under the section explaining how the memberships work, that the intro has been cut down twice and does not need cutting again, that Thursday is your review day because Wednesday is teaching.

That knowledge is an asset, it is yours, and almost nobody writes it down. Six things survive a change of supplier if you build them, and one is worth more than the other five.

What walks out of the door?

Not the footage. The working knowledge.

A supplier accumulates a great many small decisions about you in a year, and most were never stated as rules. Corrections you gave once, preferences they inferred from what you approved, habits built around your calendar. All of it lives in one person's head and in a message thread you cannot search.

It feels like bad luck rather than a design fault because it only shows up on the day somebody leaves. Until then the system works, because a person who remembers is holding it together.

What survives if you build it?

Six things to keep together.

A file naming convention. One agreed pattern, documented and updated when the work needs it.

A folder structure. The same shape every project, so a new person finds the audio without asking where the audio is.

A shared tracker. One row per video, showing its state and who is holding it.

A stated review flow. Who watches, in what order, by when, and who sends the notes.

An archive rule. What is kept, where, for how long, who can reach it and how deletion is agreed.

A preference document. Every preference you have ever had to explain, written as a standing rule.

The first five make the work easier to locate and continue. The preference document carries the details that make the work yours.

A naming convention works harder than it looks

Because it decides whether a folder can be read by somebody who was not there.

Date first, in a form that sorts correctly, then the series or subject, then what the file is, then the version. Everything else is preference. What matters is that it is one pattern rather than four, and that it survives the person who thinks their own system is better.

The test is not tidiness. It is that a file found on its own still says what it is. A folder of clips named after the day somebody exported them gets watched from the beginning by whoever inherits it, and you pay for those hours without ever seeing them itemised.

What goes in the preference document?

Anything you have had to say twice.

How your name and your business name are spelled and pronounced. Terms you never abbreviate. The claim you are not allowed to make and the phrasing you use instead. Music you will not have. Whether the intro returns at the end. What a thumbnail must never do. Which day of the week you can review things.

Each looks trivial alone. Together they decide whether a new supplier is useful in a week or in a quarter, and they are the whole content of the conversation you dread having again.

How do you write it without setting aside a day?

You do not write it. You accumulate it.

Every time you give a note, ask one question first: is this about this video, or about all of my videos. If it is about all of them, it goes in the document as a rule, in the words you just used, with the date next to it. The note still gets sent. The rule outlives it.

And a rule that has stopped being true gets struck through, not kept out of loyalty to the day you wrote it. A brand loosens, a thing you once banned becomes the thing you do, and the document is meant to move with that. You are building a foundation that keeps changing, not a rulebook that freezes the version of you that existed in March, and that difference is the whole point: the first frees the next person to work, the second makes them re-enact your old taste.

Doing that for a few months produces something no consultant could have written for you, because it is made of the corrections you had to make. It is the cheapest insurance available against the day somebody leaves.

What does the archive rule say?

That superseded work is archived rather than deleted, that anything with a legal life attached is stored where you can reach it, and, written beside each of those, how long it is kept and who can get to it. A stated retention period stops the archive being kept forever by accident or wiped by surprise, and a named point of access stops the whole store depending on one person still working with you.

Keep versions according to the agreed retention policy. They can help you reverse a decision, but also need storage, access control and a clear record of which file is current. Keep music and stock licence records with the relevant piece, including the uses and limits they cover.

The new-editor test

What could a competent stranger pick up in a week without asking you anything.

Hand them the folder, the tracker and the preference document, and watch which questions still come back. Those questions are the holes, and they are a better audit than any checklist, because they come from the real gap between what you know and what you have written down.

A documented system helps the next supplier pick up the work with less reconstruction. When we build brand notes around your preferences, those notes are yours to take with you. Agree the handover and retention of production files separately.

So the decision worth making this week is small with a long tail: open a document, write the last three notes you gave as rules rather than requests, and put today's date next to them.

Sources and evidence

What is established. UK government guidance on using music online states that using copyright music online generally requires a licence from the relevant rights body, and PRS for Music's own description of commercial synchronisation licensing frames it as tied to a specific use rather than a blanket permission, meaning what a licence covers, where it may run and for how long are properties of that particular licence rather than assumptions that carry over automatically. That is the basis for keeping a licence's terms written down alongside the video it was bought for, so a question raised years later is a document to check rather than a memory to reconstruct.

Our method. Six things are built to survive a change of supplier: a file naming convention, a folder structure, a shared tracker, a stated review flow, an archive rule, and a preference document built from every correction that turns out to apply to more than one video. Music and stock licences are filed per piece, in the partner's own folder, with what each licence covers and for how long written next to it.

References.

• UK Government. Licences to use music online or on mobile technology. gov.uk. Online use of copyright music generally requires permission or a licence. The exact rights depend on use, repertoire and agreement.
• PRS for Music. Commercial Music Sync Licence. prsformusic.com. Synchronisation rights are use-specific. Check publisher and recording rights separately.