Before You Commission a Production Workflow Audit: A Checklist

An audit is only as useful as the question behind it. Before you contact anyone, write down in a sentence or two what is going wrong or costing you time. Perhaps a studio show takes forty minutes longer to turn around than it should, or the same intermittent fault returns after every rig. Perhaps nothing is broken and you simply suspect the chain has grown by accident over several seasons.

I see audits go well when the producer and the technical director agree on that sentence first. They go badly when each has a different complaint in mind and the reviewer is asked to satisfy both without being told which matters more. If the two of you cannot agree, that disagreement is itself useful information, and worth stating plainly when you make your enquiry.

• One sentence describing the main problem
• Who noticed it first, and on which kind of show
• Whether it is a fault, a delay or a worry

Most production teams hold more documentation than they think. Look for signal flow diagrams, patch lists, rack layouts, crew call sheets, rehearsal schedules and any fault log, even an informal one kept in a shared spreadsheet. None of it needs to be tidy or current. A diagram that is two years out of date still shows the reviewer what people believe the chain looks like, and the gap between belief and reality is often where the faults sit.

If nothing is written down, say so. That is a finding in its own right and it shapes how the review is planned, because someone will need to sit with your engineers and map the chain by hand. Allow time for that conversation rather than expecting the reviewer to infer the set-up from a few photographs of the rack.

• Signal flow diagrams and patch lists
• Crew schedules and rehearsal plans
• Any fault log, however informal

A written review of a production chain depends on people as much as equipment. The vision mixer, the sound supervisor, the person who rigs cameras and whoever runs the gallery each hold a piece of how work actually happens. Check that those people can give the reviewer an hour or so, ideally during a real rehearsal or a live day rather than a quiet afternoon when everything behaves.

Think too about who will read the finished document. If the technical director commissions it but the head of operations signs off any resulting spend, include that person early. A report that lands with someone who was never told it was coming tends to sit unread, and the practical changes inside it never get tried.

• Named engineers available for short interviews
• A real rehearsal or live day to observe
• The person who approves any follow-up changes

Decide what is in and what is out. A review can cover the whole route from camera to transmission, or it can look only at audio routing, or only at how the crew is scheduled across a multi-day event. Each is a reasonable choice, but a narrow scope should be a deliberate decision and not a surprise discovered when the report arrives with a gap in the middle.

Also be honest about what you are not able to change. If a contract fixes you to a particular piece of kit for another year, or the building limits where cable can run, the reviewer should hear that at the start. Recommendations that ignore a hard constraint are of no use to you, whereas recommendations that work around it can save real effort over a season.

• Which parts of the chain are in scope
• Fixed contracts, rooms or kit that cannot change
• Whether crew scheduling is included

Agree before work begins what you expect to be handed back. A useful audit report describes the chain as found, lists the faults and delays observed, and then proposes changes in an order you can act on, with the simplest and cheapest first. It should say plainly which findings are certain and which are judgement calls, so your team knows where to test before spending anything.

Ask whether the report will be a document you keep or a conversation that fades. A written review can be handed to a new engineer, revisited after the next rebuild and compared with a later audit. That lasting value is much of the reason to commission one rather than relying on advice given across a desk during a busy rehearsal.

• Chain as found, faults observed, changes proposed
• Changes ranked from simplest to most involved
• Clear separation of fact from judgement

Last, confirm the practical points. Agree the dates, the access you will provide, who receives the report and in what format, and how ordering works: an enquiry, a written quotation or confirmation, then an invoice paid by bank transfer. Read the cancellation terms in the payment and refund policy so nobody is surprised if a live schedule shifts and a visit has to move.

If you can tick every item in this list, you are ready to ask for a review. If you cannot, you have still learned something: the gaps in the checklist usually point to the very habits an audit is meant to improve, and closing them yourself first makes the eventual report shorter, sharper and easier to use.