Workflow

Post Supervising When the Studio Never Stops

This piece is a general reflection on high-volume online post-production. It does not describe any one company’s internal workflow, commercial strategy, client work, release process or confidential production system.

Over the past few years, I have watched simple post workflows grow into something much more complex: constantly moving production pipelines with multiple edits, deliverables, revisions and approvals happening at the same time.

That shift changes the job of post supervision. The challenge is no longer just getting one project finished. It is keeping several pieces of work moving at once without letting the whole system collapse into reactive, last-minute delivery.

In a traditional project-based post environment, the workflow is often built around a defined job: one series, one delivery schedule, one finishing path, and a team scaled around that specific production. In online-first production, the rhythm can be very different. The work does not always arrive neatly, and the studio does not really stop. One piece may be in offline, another waiting on graphics, another being prepared for finishing, another being reviewed, and another already being checked for release.

To keep a pipeline like that moving, you have to make compromises. You have to switch priorities intentionally so the right deliverables hit the right dates. You have to automate carefully, but only where the process underneath it is already solid. You have to keep adapting the system as new demands arrive, because if you do not stay on top of it, small delays can very quickly snowball.

That is the part of post supervision I find most interesting. It is not just knowing the software, or knowing what order the work should happen in. It is knowing where the pressure is building before it becomes visible to everyone else.

Here is how I think about the main stages of that kind of pipeline.

Ingest

Ingest is where the whole system either starts clean or starts accumulating problems.

In high-volume production, footage does not always arrive in a neat, predictable pattern. Some material comes from planned production blocks. Some comes from smaller shoots, pickups, additional content days, sponsor-led work, or quick-turnaround ideas that need to move through post quickly.

That makes ingest much more than just copying media. It is the point where the post department decides how footage will be identified, where it will live, how it will move, and how easily people will be able to find it again later.

In a lower-volume environment, you can sometimes get away with fixing messy organisation after the fact. In a higher-volume environment, that becomes dangerous. If naming conventions are inconsistent, if project structure is unclear, or if media is moved without a clear record of its status, the cost is usually paid later by the editor, assistant, online editor, or supervisor trying to track something down under pressure.

That is why I think the media cycle has to be treated as a controlled loop rather than a one-way path. The goal is not just to get footage copied. The goal is to make sure every piece of media has a known status, a known location, and a clear reason for staying active or moving into archive.

The exact storage setup will change from one facility to another, but the principle stays the same: active media should be easy to work with, protected media should be recoverable, and archived media should not become a mystery box that only one person knows how to navigate.

Editorial

Editorial is where the workflow starts to become a scheduling problem as much as a creative one.

In a more traditional setup, an editor might stay focused on one project for a long stretch of time. That can be ideal creatively, especially on long-form work where tone, pacing and story need deep attention. But in high-volume online production, the work often has to move differently. Editors may need to shift between projects, formats or deliverables depending on what is closest to release, what is waiting on another department, and what can realistically move forward that day.

That kind of switching can sound chaotic, but it does not have to be. Managed properly, it can actually keep the work healthier. Editors get variety, the release calendar keeps moving, and the department avoids having one person blocked on a single project while other work piles up elsewhere.

The key is to make the switching intentional. Moving an editor between projects should not just be a panic response. It should be based on priority, complexity, release timing and what each project is waiting on. A difficult episode or piece of content may need to start earlier because it has more dependencies after lock. A simpler piece may be able to move forward quickly while another waits for graphics, sound, VFX or approvals.

Short-form and social deliverables also need to be thought about carefully. The person who has worked closely with the footage is often in the best position to identify moments that can survive outside the context of the full piece. They know what nearly made the cut, what landed well, and what could work as a shorter standalone clip.

But selection and finishing are not the same thing. A useful workflow lets editors mark or plan potential cutdowns during offline, while avoiding unnecessary rework by waiting until the main piece is properly finished before creating final versions. Otherwise, graphics, grade, effects and sound can end up being rebuilt across multiple outputs, usually at the worst possible point in the schedule.

Online

Online is where all the promises made earlier in the workflow become real.

By this point, the project is no longer just an edit. It is becoming a delivery package. Any platform-specific calls to action need to be correct. Graphics need to be in the right place. Effects need to be final or clearly versioned. Sound, picture and finishing requirements need to line up. Anything that was casually left as “we’ll fix it later” has now arrived at later.

This is one of the trickiest parts of a high-volume workflow to keep efficient, correct and flowing. The online stage is where creative, technical and delivery requirements all meet. If earlier parts of the process were vague, online usually exposes it.

It is also the point where different types of work need to be treated differently. A complex piece with multiple dependencies cannot be scheduled the same way as a simpler piece with a cleaner path to finish. If that difference is not identified early, online becomes a traffic jam.

For every project, I want to know: what is missing, who owns it, when it is due, what it blocks, and whether the current version is safe to send forward. That sounds obvious, but when several things are moving at once, those five questions are the difference between a controlled workflow and a pile-up.

Online is also where version control becomes critical. If a department is not clear about which version is current, which assets are final, and which notes have actually been addressed, people start wasting time checking the same things repeatedly. Worse, the wrong version can move forward because it looks finished enough to someone who does not know the history of the project.

Grading and QC

In fast-moving post environments, grading, online and QC can easily get compressed together. That can be efficient, but it can also create risk if the same person is finishing the work, judging the work and trying to get it out the door at the same time.

I used to think that combining those stages was mostly a practical advantage. The person finishing the piece already has the project open, already understands the problems, and is already close to the final output. But the more volume you push through a pipeline, the more dangerous that thinking becomes.

When the end of the pipeline is moving quickly, the person finishing the work is often the worst person to be the only person checking it. You are too close to the decisions. You know why a compromise was made. You remember the problem shot from two versions ago. You may also be trying to hit a deadline, which changes how you see the work.

The danger is not just that mistakes slip through. It is that one mistake changes the way people watch the whole piece. Once someone notices a bad graphic, a missed fix, an inconsistent grade or a technical issue, they stop watching the work and start looking for more problems. The suspension of disbelief is gone.

That is why QC has to become a layer in the workflow, not just a final pass at the end. Some of it can be supported by automation. Some of it has to be human. But it cannot live entirely in the head of the person who is also trying to finish the project.

The most useful QC systems are not just about catching errors. They are about creating confidence. They give everyone involved a shared understanding of what has been checked, what still needs attention, and what is safe to move forward.

The Schedule Is the Workflow

The more I have worked in this kind of environment, the more I have realised that the schedule is not separate from the workflow. The schedule is the workflow.

It is easy to think of a post schedule as a list of due dates. This project locks here, this one goes to grade here, this one delivers here. But when you have multiple projects moving at the same time, the schedule becomes a map of dependencies. Every date is connected to something else.

If offline runs late, finishing starts late. If finishing starts late, QC gets squeezed. If QC gets squeezed, mistakes are more likely to make it into review. If mistakes make it into review, the final delivery becomes reactive instead of controlled.

That is how a workflow starts to break down. Not usually from one huge failure, but from a chain of small delays that nobody catches early enough.

For me, post supervision is largely about spotting those chains before they become obvious. I am constantly trying to work out which project needs attention now, which one can safely wait, which piece of work is quietly becoming a problem, and which deadline is only achievable if a decision gets made today.

This is also why I do not think a post schedule should only track the edit. The edit is just one part of the system. A useful schedule needs to show the state of offline, finishing, graphics, sound, QC, cutdowns, platform requirements and archive status. If those things are tracked separately, the supervisor ends up becoming the only person who can see the whole picture. That might work for a while, but it does not scale.

The best workflow improvements I have made have usually come from making invisible dependencies visible. A missing graphic is not just a missing graphic. It might be blocking finishing. A delayed asset is not just a delayed asset. It might affect the final export, the cutdown, the review process and the release timing. A piece of media sitting in archive is not just archived. It might be unavailable at the exact moment someone needs to make a last-minute change.

When you can see those dependencies clearly, you can make better compromises. You can decide which project needs extra attention. You can move a simpler piece forward while a complex one waits on another department. You can hold off on cutdowns until the main version is actually ready. You can protect QC time instead of hoping there will be space for it at the end.

That is the real job. Not making a perfect plan at the start and expecting it to survive. The real job is constantly adjusting the plan while the work is already moving.

Checklists Before Automation

Automation is tempting in a busy post department because the pressure is obvious. There are too many repeated tasks, too many files to check, too many versions to track and too many small things that can be missed when everyone is moving quickly.

But automation only helps when the process underneath it is already clear. If the workflow is vague, automation just makes the mistakes happen faster.

Before automating anything, I think it is worth asking a few basic questions. What decision is being made? Who currently makes it? What information do they use? What happens when the answer is unclear? What does a successful result look like? If those questions cannot be answered, the process probably needs a checklist before it needs a script, tool or integration.

Checklists are not glamorous, but they are one of the best ways to find out what a workflow actually is. They expose the assumptions people are carrying in their heads. They show which steps are repeatable, which ones need judgement, and which ones only work because one person remembers to do them.

Once that is visible, automation becomes much safer. You can automate verification, reminders, naming checks, status updates, folder creation, reporting, or parts of QC because the logic is already understood. The automation is then supporting the workflow, not inventing it.

That is where I think the biggest gains are in modern post-production. Not replacing people, and not pretending software can understand every creative or technical decision. The real opportunity is cutting the busywork around the work, so editors, assistants, supervisors and finishing artists can spend more time on the decisions that actually need them.

Final Thoughts

High-volume online post-production is not just a faster version of traditional post. It has its own pressures, its own failure points and its own rhythm. The work is more continuous, the deliverables are more varied, and the workflow has to keep adapting while the machine is already running.

The best systems I have worked with are not the most complicated ones. They are the ones where people can see what is happening, understand what is blocked, find what they need, and trust that the next step in the process is clear.

That is what good post supervision is really trying to protect: not just the final file, but the flow of the whole department.