Six Mistakes in Setup Reviews and Handover Notes, and Fixes

Treating the review as a formality

The first mistake is the quickest to make: a setup review that amounts to a glance at each camera and a nod. A review has one job, which is to compare what the team believes is set with what is actually set. Menus drift. A lens gets swapped, a card slot changes, a picture profile is switched for one job and never switched back. Without a written starting point, nobody notices until two cameras disagree in the edit.

The fix is to treat the review as a short, structured pass with a fixed order. Start with the delivery format, because every other choice depends on it. Then go camera by camera through frame rate, shutter, white balance, picture profile and recording format, noting each value as you read it off the screen rather than from memory.

In the course we ask learners to bring their own cameras for this exercise. The surprise is nearly always the same: a setting somebody was certain about turns out to differ between two bodies of the same model.

• Read values from the camera, never from memory
• Settle the delivery format before any other setting
• Write the value down at the moment you read it

Skipping the test session or running it too late

A test session scheduled for the morning of the shoot is not a test session, it is a rescue. By then the venue is filling, the client is asking questions and nobody has the patience to chase a small colour shift. Problems found at that hour get patched with a quick correction instead of being understood.

Book the test session a few days ahead and keep it modest. Use the same lights, the same cameras and the same lenses you intend to use, and record a short clip of a grey card and a person standing where the subject will stand. Ten minutes of footage is enough if it is shot under real conditions.

Then look at it on the screen you will edit on, side by side, before anyone leaves. The aim is not perfection. The aim is to find the two or three differences that matter while there is still time to adjust a setting rather than apologise for it.

• Hold the session days ahead, not on shoot morning
• Use the real lights, lenses and positions
• Compare clips side by side on the editing screen

Testing with a stand-in instead of the real conditions

Another common slip is testing in a room that looks nothing like the venue. A bright studio test tells you little about a dim hall with mixed tungsten and window light. Cameras that match under one source can drift apart under another, particularly in skin tones, which is where viewers notice first.

Whenever you can, run the test where the work will happen, at the same time of day. If that is impossible, recreate the main light source and note honestly what you could not reproduce. That note is useful: it tells whoever runs the shoot where to look first if something seems off.

Keep the subject realistic as well. A grey card confirms the neutral point, but a person in the colours the client will actually wear shows you contrast and skin response that a card cannot. Use both, and keep the clips labelled so the comparison is easy to repeat.

Writing handover notes nobody can follow

Handover notes fail in two opposite ways. Some are a single line saying everything is set up as usual. Others are pages of screenshots no one reads under pressure. Neither helps the person who inherits the cameras, who may be a colleague who was not at the test session.

Good notes are short and ordered the way a person actually works: what to check on arrival, the agreed values for each camera, and what to do if something looks wrong. Use plain words and the same names for settings that appear on the camera menu, so nobody has to translate.

Write them for someone tired and in a hurry. If a step needs explaining, explain it in one sentence beside the step. Notes that survive that standard also survive a change of crew, which is the real test of whether a handover has worked.

• Order the notes in the sequence of the working day
• Use the exact names shown on the camera menu
• Add one sentence of reason beside any unusual step

Leaving out the recording requirements

Teams often record the camera settings carefully and forget to record why they were chosen. A frame rate of twenty-five frames per second means little to a newcomer who does not know the delivery is for a particular broadcast format or a client's existing edit timeline. Without the reason, the value gets changed to something that looks nicer on the day.

State the recording requirements at the top of the notes: the delivery format, the frame rate and shutter relationship, the codec, the expected clip length and where the files go afterwards. Then list the models and lenses in use, since two bodies of one family can still behave differently.

This is also the piece we ask clients to prepare before a review: a list of their camera models and what they need to record. It takes ten minutes to write and removes most of the guessing from the session.

Never revisiting the notes after the shoot

The last mistake is treating the notes as finished the moment the shoot ends. A real day always teaches something: a setting that needed nudging, a light that changed, a card that ran out sooner than planned. If those lessons stay in someone's head, the next team repeats the same trouble.

After the job, spend a few minutes updating the notes with what actually happened. Mark any value that was changed and why, and strike anything that proved unnecessary. A short, honest correction is worth more than a polished document that no longer matches the cameras.

Over several jobs this habit builds a reliable record. The review gets faster, the test session gets shorter, and the handover becomes something a new team member can pick up and use without a phone call.

• Record every value changed on the day, with the reason
• Remove steps that proved unnecessary