The post-production pipeline audit, explained.

Most post facilities lose hours to the same handful of structural problems — and stop counting. A pipeline audit finds exactly where. Here is what one is, when you need it, and how to run it.

What a pipeline audit is

A post-production pipeline audit is a structured diagnosis of how footage moves through your facility — from the card coming off set to the deliverable leaving the building. It maps the real workflow, finds where time is lost or work is duplicated, and ranks the findings by risk so you fix the thing that hurts most first. Done well, it is a diagnosis, not a sales call: even if you change nothing, you leave with an honest picture of your pipeline.

Signs you need one

• The same problems — relink, conform, naming, render queue — recur every project.
• Only one person knows how a critical step actually works.
• Deliverables get rejected by a platform or broadcaster more than rarely.
• You can’t confidently retrieve a complete project from 12 months ago.
• Nobody knows the cost per finished minute of your content.

The areas to examine

A thorough audit walks the whole chain. The high-value areas:

• Acquisition & ingest — is OCF preserved untouched? Is checksum verification (MD5/xxHash) run on offload?
• Editorial — proxy workflow, version control, and how editorial hands off to finishing.
• Colour, sound & finishing — calibrated grading, a defined colour pipeline, a real QC step before delivery.
• Delivery — naming and versioning, spec sheets reviewed up front, a named sign-off owner.
• Infrastructure — storage type, a 3-2-1 backup strategy, a structured and tested archive.
• Team & process — a written, current pipeline document and an enforced file-naming convention.
• Cost — per-project cost tracking, so savings can actually be identified.

How to run one

1. Document the real workflow, stage by stage, using actual recent jobs — not the idealised version.
2. Interview the people who do each step; the undocumented logic lives in their heads.
3. Flag the risks. No checksum on ingest, no backup, no naming convention and no QC are the classic high-risk findings.
4. Rank by impact, so the first change is the one that removes the most pain or risk.
5. Write it down as a plain-language report you can act on and revisit.

The output that matters is a ranked plan: what’s safe to change today, and what is quietly costing you right now.

Run it with FORGE

FORGE begins every engagement with exactly this audit — a structured questionnaire across acquisition, editorial, finishing, delivery, infrastructure, team and cost, weighed against the failure patterns we see repeatedly across post pipelines. You receive a written Pipeline Audit Report: a map of your workflow, the specific points where time is lost, which of those FORGE addresses, and a recommended starting point. See the FORGE.Audit.