Written procedures and floor sessions: how we document a crew's way of working

Over these autumn weeks I have been asked the same thing by several technical managers: the rig works, the crew is capable, yet one recording day never quite matches the last. Cables are patched differently, a camera is shaded to another reference, a monitor feed is left on the wrong source. Nobody did anything wrong. Each person simply carried the routine in their head.

That is the gap our Workflow Documentation and Training service closes. It pairs written procedures with hands-on sessions so that a crew works consistently from show to show, whoever is on shift. I lead much of it from the camera side, which is why I am writing this note: to set out plainly what the work involves and what you receive at the end.

We did not start offering it because it was fashionable. We offered it because our design plans kept outliving the people who first understood them, and a plan nobody can follow on the day is only half finished.

A procedure we write is not a manual of every button. It describes one task, from a cold start to a clean handover, in the order the crew performs it. Each step names who does it, what they check and what a correct result looks like, so a newcomer can tell at a glance whether they are on track.

We draw on the signal flow diagrams and room layouts already produced for your studio, so the document uses your own labels and your own equipment names rather than generic ones. Where a step has a common failure, we note the symptom and the first thing to try, kept short enough to read standing at a desk with a headset on.

We keep each document to a few pages. Long procedures are rarely opened under pressure, and a short one that is trusted beats a thorough one that sits in a folder. Where a task is genuinely long, we split it into stages with a clear stopping point between them.

• One task per document, in working order
• Your own equipment names and room labels
• Symptom and first check for common faults
• Short enough to use during a live shift

Writing a procedure is the easier half. The sessions are where it proves itself. We bring the draft to your studio or control room and ask the crew to follow it exactly, while we watch and say as little as possible. Wherever someone hesitates or reads a line twice, the wording needs work, and we mark it there and then.

Groups stay small so everyone handles the equipment rather than watching a colleague do it. A session usually centres on one workflow, such as a camera line-up before rehearsal or the close-down routine after a show, and we repeat it until the crew can run it without prompting.

Afterwards we revise the documents the same week and send back the corrected versions. The crew then sees their own corrections reflected in the final text, which is a large part of why they keep using it. People follow a procedure they helped shape.

Since camera control is my own field, I will use it to show the level of detail we aim for. A line-up procedure covers powering the camera chains, confirming the control unit assignments, setting the reference and checking each shading panel against the same chart, then recording the result so the next team can compare.

We include the order in which sources are checked at the vision mixer and the point at which the director is told the cameras are ready. That small handover is often where a show loses a minute, simply because nobody was sure who should speak first.

The same pattern applies to remote heads and to routing changes between productions. If a studio shares one control room across several formats, we write a short reset procedure for each so the room is returned to a known state before the next crew arrives, whatever the previous show left behind.

• Power-up order for camera chains
• Common reference and chart for every shading panel
• Who confirms readiness to the director, and when
• Reset steps between different formats

The more we can see of how you really work, the better the result. We ask for your existing floor plans, any signal flow diagrams, the equipment list and, if you have them, the notes crew members already keep for themselves. Those informal notes are often the most honest account of what happens on the day.

We also ask you to name one person who can answer questions about decisions that are not obvious from the equipment alone, such as why a certain input is never used. That person does not need to attend every session, but a short conversation early on saves us from documenting a workaround as though it were the intended method.

If a show is coming up, tell us. We would rather observe a real recording day than reconstruct one from description, and we can usually schedule a session around a rehearsal rather than disturb a live schedule.

• Floor plans and signal flow diagrams
• Current equipment list
• Any crew notes already in circulation
• A named contact for questions on past decisions

It is worth being clear about the edges. Documentation and training describes and teaches the way your facility is set up; it does not redesign the studio, change the lighting grid or alter the audio routing. If our work shows that a layout causes repeated trouble, we will say so in writing, and that finding can lead to a separate design conversation.

We also do not train crews on equipment we have not seen in your room. The sessions are built around your installation, which is why they cannot be reused word for word elsewhere. That specificity is deliberate and is what makes them useful.

Cost depends on how many workflows are written and how many sessions you want, and our prices page sets out how enquiries, quotations and payment work. For a fixed picture of your own studio, the contact page is the place to start.