Starting with a signal map on paper
Every review we run begins with a plain drawing of where signals go. We sketch cameras, sources, routers, mixers, recorders and outputs, then draw a line for each connection and label it with the format it carries. It sounds basic, but most teams have never seen their whole chain on one sheet. People who work at the vision desk know their part, the audio team knows theirs, and nobody owns the joins.
We use pencil and a large sheet first, and only tidy it into a clean diagram afterwards. Mistakes show up quickly on paper: a feed that is converted twice, a monitor fed from a point nobody can adjust, a return path that exists only because someone ran a cable years ago.
Walking the drawing with the people who use the room daily is the real value. They correct our assumptions, and we usually leave with a list of questions rather than answers.
- Label every line with its format and frame rate
- Mark each conversion point
- Note who can change each connection
A file-handling sheet that follows one clip
Signal routing is only half of a workflow. The other half is what happens to a recording once it exists. We follow a single clip from the moment it is recorded to the moment it reaches its destination, and write down every step on a simple sheet: where it lands, who moves it, what it is renamed to, what is copied and where the copies live.
This tracing exercise tends to expose duplicated effort. Two people may be copying the same material to different drives, or a naming habit may force someone to rename dozens of files by hand before they can be found.
We do not need special software for this. A shared spreadsheet and a willingness to watch the process as it really happens, not as the procedure document describes it, is enough to see where hours disappear.
- Record each hand-off and who performs it
- Count the copies of every file and where they sit
- Check names against what the receiving team expects
Test files and a stopwatch
Opinions about speed are unreliable, so we measure. We prepare a few short test clips in the formats the team actually uses and run them through the real chain, timing each stage with a stopwatch. Ingest, transcode, review, approval and delivery each get a figure, even if it is only a rough one.
The numbers rarely point where people expect. A team convinced that editing is the slow part may find that most of the waiting happens at a file transfer scheduled to run once an hour.
We repeat the timing after any change, using the same clips, so the comparison is fair. It is a modest method, but it keeps conversations about workflow grounded in what happened rather than what felt slow.
- Use clips in the formats your team really uses
- Time each stage separately
- Repeat with the same files after every change
Checklists written with the crew
Once we understand the chain, we turn the findings into short checklists. These are not long procedure manuals. Each one fits on a single page and covers one moment: opening the studio, preparing for a live feed, closing a recording session, handing material to the delivery team.
We write them alongside the people who will use them, in their own words, because a checklist that reads like someone else's rules gets ignored by the second week. We cut anything that does not prevent a real problem we have seen.
The aim is to remove decisions that do not need making. If the same three checks happen before every transmission, they belong on paper where nobody has to remember them under pressure.
- One page per situation
- Written in the crew's own wording
- Reviewed after the first few uses and trimmed
Keeping the kit list honest
Many workflow problems trace back to equipment nobody has recorded properly. We keep a simple inventory for each client as part of a review: what each device is, what it connects to, which firmware or settings matter, and who looks after it. It is nothing more elaborate than a table.
This matters most when something fails. A team that knows exactly which converter sits between the mixer and the recorder can fix a fault in minutes. A team without that knowledge starts by tracing cables.
We also note what is no longer used. Spare routes, forgotten adaptors and idle machines add confusion without adding capability, and removing them often simplifies the room more than buying anything new.
- List device, connections and settings that matter
- Name an owner for each item
- Flag anything that is no longer in use
What we leave out on purpose
We try not to bring tools that a team will not keep using after we leave. A complicated tracking system, a new naming scheme that needs training, or software that duplicates what the studio already has will usually be abandoned within a season.
Our preference is for methods that a producer or studio manager can maintain alone: a drawing that can be edited, a sheet that can be copied, a timing routine that takes an hour. If a change cannot be explained in a short meeting, we ask whether it is really necessary.
That restraint is deliberate. A workflow improves most reliably when the people running it understand every step and can adjust it as their work changes through the year.
Our review tools are deliberately plain: a signal drawing, a file-handling sheet, timed test clips, short checklists and an honest kit list. None of them needs special software, and all of them can be kept up by the team after our visit. If you would like to talk through how these methods might suit your studio or event setup, the contact page is the place to start.