Writing a Camera Setup Guide Your Crew Will Actually Use

Start with the job the guide has to do

Most camera setup guides fail because they try to be a manual. A manual explains every menu; a setup guide gets a camera from the cupboard to a matched, working position in a known number of steps. Before writing anything, I decide who will hold the page and in what conditions: a camera operator at half past six in the morning, with a rigger waiting and a director asking for pictures. That reader does not want background theory. They want the order of work, the values to enter and the point at which to stop and ask someone. If a sentence does not help them do the next thing, it belongs in an appendix or nowhere at all.

I write the purpose of the guide in a single line at the top, for example: bring a studio camera from power-up to matched output on the house reference. Everything below that line either serves it or is cut. This also makes the guide easier to review, because a colleague can check each step against one clear aim rather than against a vague idea of completeness. Keep one guide per camera type and per role. A pedestal camera in the studio and a handheld on an outside broadcast share some steps, but mixing them produces pages of exceptions, and exceptions are where people go wrong.

• State the purpose of the guide in one line
• Name the reader and where they will use it
• Write one guide per camera type and role

Rigging notes that survive a busy floor

Rigging is the part of the guide that people skim, so it has to be physical and specific. Describe the order in which things are attached: head to pedestal, then balance, then drag, then viewfinder and prompter if fitted. Give the checks in the language of the floor, such as whether the head holds at the steepest tilt you expect and whether cables have enough slack through a full pan. I add a small photograph or line drawing wherever a description would take more than two sentences. A cable route is far quicker to read as a picture than as a paragraph, and a picture is harder to misread when someone is standing on a ladder.

Record the weights and accessories that change the balance, because a prompter or a larger lens alters everything downstream. Where a rig is shared between productions, add a short note on what to reset when it changes hands. Finally, write down what a correct rig looks like when finished. A crew member who can compare their camera to a described end state will catch their own mistakes before the director does, and that is the real test of a rigging section.

• Give attachment steps in physical order
• Use a drawing where text runs past two sentences
• Describe the finished rig so it can be checked

Colour matching without a long preamble

Colour matching is where a guide earns its keep, because the work is repetitive and easy to do inconsistently. I set out the sequence plainly: confirm the reference source and the monitoring, set white and black, then match exposure and gamma, and only then adjust colour. Each step names the control, the value or target, and what the waveform or vectorscope should show. Keep the vocabulary consistent. If the guide says black level on one page and pedestal on the next, a newer operator will assume they are different controls. Pick the term your studio uses and keep to it throughout.

Say clearly what is fixed and what is left to the operator's judgement. Some studios lock paint values and allow only small trims; others expect a full match each day. The guide should state which applies, along with the tolerance that counts as matched. I also record the lighting conditions the match was made under. A match made on a warm set will look wrong on a cooler one, and noting this saves an afternoon of puzzling over a fault that is really a change in the room.

• Follow a fixed order: reference, white and black, exposure, colour
• Use one term per control throughout
• State the tolerance that counts as matched

Documenting the signal path

A signal path section should let someone trace a picture from lens to output without guessing. I draw it left to right as a simple chain and label every connector type, cable run and conversion, including any point where the format changes. If a fault appears, the reader can then work along the line and test each stage in turn instead of swapping equipment at random. Include the intercom, tally and return feeds in the same drawing. They are often left out, and they are the first things an operator needs when something stops working during a rehearsal.

Beside the drawing, keep a short table of expected formats and settings at each stage, so a mismatch is visible at a glance. A camera set to one frame rate feeding a chain set to another is a common cause of trouble, and it is dull enough that nobody thinks to check it. Date and version the drawing. Studios change patching more often than they update paperwork, and an out-of-date signal path is worse than none because it sends people confidently in the wrong direction.

• Draw the chain left to right with labelled connectors
• Include intercom, tally and return feeds
• Version and date every diagram

Keep the guide short and testable

Length is the enemy of use. I aim for a guide that fits on a few pages and read it aloud as I draft, because any step that makes me stumble will make a tired operator stumble too. Numbered steps, one action each, and a clear sign of when a step is complete are better than elegant paragraphs. Where a choice has to be made, give the rule rather than the reasoning. The reasoning can live in a separate note for those who want it, but the page on the floor should not ask anyone to weigh up options under pressure.

Before a guide goes into use, have someone who did not write it follow it on a real camera, with the author watching and saying nothing. Every hesitation marks a sentence to rewrite. I usually find two or three in a first pass, and they are never the ones I expected. Then set a date to review it. Firmware updates, new lenses and changed lighting all make parts of a guide wrong without anyone noticing, so a short scheduled check keeps it trustworthy.

• Use numbered steps with one action each
• Have a newcomer test the guide unaided
• Set a review date after every equipment change

Where guides usually go wrong

The commonest fault is writing for yourself. An engineer who knows the camera well leaves out the steps that feel obvious, and those are exactly the steps a new operator needs. I read my drafts as though I had never seen the camera, and add whatever I would have to ask someone about. The second fault is hiding the warnings. A step that can damage equipment or lose a recording should be marked plainly and placed before the action, not tucked into a note afterwards.

The third is treating the guide as finished. A guide is a working document, and the useful ones carry a line of corrections made in the field. When an operator finds a better way, it should be easy to feed back and quick to adopt. If a studio has no written setup guide at all, the best first step is modest: choose the one camera that causes most questions, and write a single page for it. That page will teach you what the rest need.

A good camera setup guide is short, ordered and honest about what it expects the reader to know. Cover rigging, colour matching and the signal path in that sequence, mark the warnings, and test the pages on someone who has never used the camera. Revisit them whenever equipment or lighting changes. Written this way, the guide stops being paperwork and becomes the thing your crew reaches for first.